Re: Another Wording Question


I just checked and Chrome reads the button with the phrase "choose files".  Your explanation makes more sense than my guess and its simpler.  I had wondered if there were certain generic buttons that meant certain things and that screen-readers might express the meanings differently.  But, as I said, your explanation makes more sense.

----- Original Message -----
Sent: Friday, December 29, 2017 12:47 PM
Subject: Re: [nvda] Another Wording Question

I just went to and looked at the HTML source for
the page.

Assuming you meant that Chrome reads the button as "Upload file", I think I can
see the reason why - the HTML source for this button contains the actual text
(shown on the screen) as "Browse" but the HTML "input" tag contains the ID
string "upload_file":

<a class="button">
<input type="file" id="upload_file" name="upload_file[]" class="file" size="1"
multiple />
<button class="sbtn" onclick="$('#upload_file').trigger('click');return

I suspect this is why different browsers and/or screenreader combinations can
give different results - they're paying attention to different parts of the
underlying HTML.


On Friday 29 December 2017 at 19:36:39, Gene wrote:

> Joseph lee's message raises a question I've wondered about a bit now and
> then.  If it can gbe described to the layman without unreasonable effort,
> I've wondered why a screen-reader might read a control one way and another
> screen-reader read it with different wording.  Until perhaps a year ago, I
> had assumed that controls all had readable text and that screen-readers
> would read them all the same, but an earlier comment from Joseph and a
> variation I observed on a button caused me to realize that screen-readers
> don't necessarily speak the same things.  So how do screen-readers know
> how to read controls and why are there differences?
> For example, on the Send Space home page, the button that opens the select
> file to upload dialog is read as "browse".  Chrome reads it as something
> like "choose file".  So evidently, this button is not labeled with text
> but is recognized as a category or function control.  I'm not sure if I'm
> expressing it as clearly as I might but I think it's understandable.
> In the specific help page being asked about, can these controls be labeled
> with text or alt text so they will all be read the same regardless of
> screen-reader?
> Gene
> ----- Original Message -----
> From: Gene
> Sent: Friday, December 29, 2017 12:22 PM
> To:
> Subject: Re: [nvda] Another Wording Question
> I don't think there is exact wording that you need to worry about.  What
> you wrote is very understandable and whether the item would say close this
> window or just close, I think your explanation makes any reasonable
> working of the actual control fine.  for consistency, you might want to
> have the control say close this window since that's what you write in the
> description but as far as a prescribed wording, I doubt there is any.
> Gene
> ----- Original Message -----
> From: tonea.ctr.morrow@...
> Sent: Friday, December 29, 2017 10:14 AM
> To:
> Subject: [nvda] Another Wording Question
> I am creating a text version of a help page. I need to describe in text a
> common pop-up window that the windows operating system displays. It would
> be shown as a picture to sighted users. To describe it, I have written:
> When the file is made, you will be asked whether to open it or save it. A
> pop-up window will appear to ask "Do you want to open or save filename
> from" followed by the buttons Open, Save, Cancel, and Close
> this Window.
> As a sighted user, I see an X on the pop-up window and know that it means
> "Close this Window". But, how does it read to you? Is it called "Close
> this Window" or what is it called by the screen reader?
> Likewise, the Save button is really a drop-down menu that is defaulted to
> Save. How does it call out the menu to you? I want to use the right words
> in my description.
> Thanks and sorry for the bother,
> Tonea

Bill Gates has personally assured the Spanish Academy that he will never allow
the upside-down question mark to disappear from Microsoft word-processing
programs, which must be reassuring for millions of Spanish-speaking people,
though just a piddling afterthought as far as he's concerned.

 - Lynne Truss, "Eats, Shoots and Leaves"

                                                   Please reply to the list;
                                                         please *don't* CC me.

Join to automatically receive all group messages.