toggle quoted messageShow quoted text
Lack of accessibility isn’t an error? I am quite certain that nobody in the accessibility field will agree with you but I am done with this conversation. You are free to respond to this if you like but I will, unfortunately, resume my habit
of skipping your messages so your response will not be read by me.
firstname.lastname@example.org <email@example.com> On Behalf Of
Sunday, May 29, 2022 11:46 AM
Re: [nvda] help with an edit field
I didn't say anything about what other words someone might want to use, but bug is not correct. You might want to call it a flaw or an omission, or use some sort of word or phrase that indicates that it is
no longer acceptable not to include accessibility, but it isn't a bug.
One definition from Google I just looked up is:
"an error in a computer program or system."
Lack of accessibility isn't an error. It may be unconscionable, unacceptable or you may wish to use other wording, but it is not an error.
On 5/29/2022 10:27 AM, David Goldfield wrote:
> I don't consider lack of accessibility to be a bug.
As an accessibility tester I disagree. I understand what you are saying in your example of a stove which doesn’t take inclusive design into account. However, if you have a Web site
which has no labels on form fields or which doesn’t expose an edit field to a screen reader this is definitely considered a bug or defect and needs to be treated as such.
I don't consider lack of accessibility to be a bug. A bug is an unintended behavior. Saying a lack of accessibility is a bug implies that the item was intended to be accessible but
isn't because of unanticipated problem or problems.
If a stove isn't accessible and isn't designed to be, that isn't a bug. You may call it a flaw, a serious flaw, you may describe it as you wish in terms of advocating for more accessibility, but it isn't a bug. It is operating as designed.
If my stove is designed to be accessible and the speech is giving inaccurate numbers as I move through settings, that is a bug.
On 5/29/2022 7:49 AM, mike mcglashon wrote:
On considering this further, I don't know if this is a bug in anything.
It may be that the results shown as you move aren't announced because the function isn't designed to be accessible.
Wow, wouldn’t that be considered a “major” bug then? Or,
At least a “big flaw”?
Isn’t that bad if someone designs a control on a page to be purposefully inaccessible?
(especially a school clearing house)?
It appears i was wrong about the edit field. It appears to be a standard edit field. I didn't hear anything about number of results and moving up and down, as I recall. I did
try using the search field where you enter a key word to find your school and I then got results like yours.
I figured out how to find a school name. Its a little work but you can accomplish this in the following way:
Follow the key word search link.
An edit field will become available. If you are not in forms mode go into forms mode. Just pressing enter where you are after following the link should do it.
Be in forms mode in the key word search edit field.
Type a word such as Chicago.
You will hear how many results there are.
Down arrow to the first one. You won't hear the school read but you will hear that you are on the first result.
Press enter. You have now placed the name in the field you are in and it can be read while in forms mode. I don't recall if you automatically hear it but you can use read current line or maybe just pressing the down or up arrow will read it.
If that is not the result you want, select all, control a, and press delete.
Write Chicago again.
Down arrow to the second result and press enter.
Again, you will be able to hear the word.
Follow this procedure until you hear the name you want.
Once you do, it is in the field it should be in and you can then activate the continue button, which will now be available.
On considering this further, I don't know if this is a bug in anything. It may be that the results shown as you move aren't announced because the function isn't designed to be accessible.
On 5/29/2022 7:07 AM, Gene via groups.io wrote:
No, it isn't standard. I had to press enter on select a school to make the field editable in the first place. Then I had to press enter again, since I am using manual switching
in NVDA, to go into forms mode. You may have to as well, since you are in a field that is not initially editable.
As far as the select a school edit field is concerned, is that the field you are discussing? I'll look at the field again but I thought I heard select a number when I was
On 5/28/2022 11:36 PM, Bob Cavanaugh wrote:
Yes, that's standard edit commands. However, when I start typing the
name of a school, NVDA says "this is an auto complete element and
there are # results available. Keyboard users, use up and down arrows
to select an option." The # in the example is, as one might guess, an
actual number. However, when using up and down arrow with NVDA in
focus mode, I just get the same auto complete message and NVDA reads
what I've already typed in, it won't let me actually choose a result.
The question is how do I actually choose a result as intended?
On 5/28/22, Gene <gsasner@...> wrote:
When you are on the line that says enter the name of the school, press
enter. That makes the field editable and you can then press enter again
to go into focus mode if you aren't automatically placed in it.
On 5/28/2022 10:07 PM, Bob Cavanaugh wrote:
Is the edit field on this page not a conventional one? I play Heardle
every day, and it looks like the edit box on this page should work
similar to that one, but I can't seem to get the one here to work. All
I hear is NVDA telling me that this is an edit box that contains
multiple selections, and how many results are available, but I can't
seem to choose any results. The same happens when you're trying to
select a school to send to, and I suspect I won't have to enter as
much information as it's asking for if I could choose a result. Any
help on this would be appreciated, as I've put this off for two weeks
already. The link is