Re: Are web applications that accessible?
Gene
It doesn't matter what a web page element is for in
terms of a sighted user. The purpose of telling a blind student to use the
check box is to help the student learn to recognize patterns on web pages and
this is one pattern. On a new page, where usual means don't work well, the
student either learns to look at the page and find patterns such as this or the
student flounders on any page that doesn't implement such things as move by
headings as the blind person expects.
A mailbox isn't placed at a certain part of a
sidewalk to tell a blind person that the building he is looking for is to the
right of the mailbox but what good blind traveler wouldn't use such a means of
locating the building efficiently? Intent, as to how a sighted person
works is irrelevant. How a blind person can use such elements and patterns
is what is relevant.
Gene
----- Original Message -----
From: Devin Prater
Sent: Monday, October 07, 2019 10:18 AM
Subject: Re: [nvda] Are web applications that
accessible? I use the keyboard commands given by Gmail for use within their web app. J
to go to the next conversation, K to go to the previous one. Enter opens a
conversation, then N and P move to the previous or next message in that
conversation. Its great so far. But then you get excess chatter, which simply
slows the screen reader user down.
Sure, one can use the site in browse mode, finding good little tips to go
from message to message, but it isn’t intuitive to teach a student to move by
check box to get through messages, as that’s just not what check boxes are for,
mainly. On the other hand, workarounds have to be used. Indeed, a screen reader
is one big workaround. That doesn’t mean that screen reader manufacturers and
web app devs should just accept that unneeded speaking of web page elements when
navigating by keyboard commands is okay, or even desirable.
|
|