WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Excellent paper on how screen reader users interactwith webpages

for

From: Lucy Greco
Date: Apr 11, 2012 6:42PM

Hello:
You bring up a vary important point. I have had the same thing happen to me. I had a site I consulted on use every accessible element I know of to make the site easy and friendly. And I would do the same thing again. But what to my dismay when I found my students did not know how to read a table or move through a form or even use headers on a web page. So I started teaching better browsing as well smile. Now I teach not only those things but I also teach place marks and land marks. And here is my wish. So in the last few versions of screen readers it is possible to move by land marks now I want the ability to move to only the main land mark or the nav or so on. I need three more keys on my quick keys.

Lucy Greco
Assistive Technology Specialist
Disabled Student's Program UC Berkeley
(510) 643-7591
http://attlc.berkeley.edu
http://webaccess.berkeley.edu


-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
Sent: Wednesday, April 11, 2012 1:14 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Excellent paper on how screen reader users interact with webpages

Very good point, and my bad for not picking up on it (the speed
reading aspectsof screen reading obviously used to not-so-great effect
there).
What kind of interests me,and I wonder if that has changed at all, is
the SR design and training aspects of web accessibility and web
browsing.
Jaws still says "skip to content" with emphasis on the second syllabol
(latest version of Jaws 13), so that bug has not been fixed since it
was pointed out in 2002.
In particular I wonder about the user training.
If users today do not use "h" ";" and other navigation keys that take
advantage of a well structured page (headings and landmarks
respectively for these two keys). If users are not generally aware of
"skip to" links and other features implemented to make web pages more
accessible, how useful is all the work that we are doing and the
things we are recommending to webpage designers, based on best
practices?
There is no point in having a perfectly structured page, if the user
has no idea how to take advantage of it.
Is there an on-going conversation between webpage designers, SR
developers and atrainers that work with users (I would assume TVIs in
this case) , making sure that we are all following the same practices,
in design, implmentation and training?
The reason I found this article so timely is I am fighting this very
same battle in Iceland. The new AT teacher, who is extremely smart and
someone I respect a lot, uses her own techniques to browse websites
and does not teach the standard ways of browsing with the navigation
keys, so that the users of a page I recently did a lot of work on, did
not find its accessibility much improved, if at all.
Once I sat down with a few of them and explained how they can use
headings and tables to find what they wanted instantly, then they were
somewhat impressed and more receptive to my design recommendations.
Of course I have started a discussion with the person in question, and
fortunately this situation is easy to resolve, but it makes me wonder
how we do this here, with such diverse group of users and systems and
A.T. training.
It seems to be extremely important that the end users can take
advantage of the work we are doing, especially now that we are looking
at more complex issues such as web applications and focus management,
as underlined in recent discussions on this list.
Cheers
-B

On 4/11/12, Jennifer Sutton < <EMAIL REMOVED> > wrote:
> This article seems to be picking up steam in circulation. I
> recommend that readers keep in mind that it came out a number of
> years ago like 2002 or 2003.
>
> The article reads, in part:
> "Between November 2002 and February 2003, we observed and listened to
> 16 blind users as they worked with Web sites using assistive devices
> that read the screen to them (screen readers)."
>
>
> No NVDA, no VO . . .
> And hasn't the Web changed? And many new versions of screen readers
> since then?
>
> It may be useful/thought-provoking, but dates on this kind of
> information/research matter, even if they are not always easy to notice.
>
> Jennifer
>
> At 12:29 PM 4/11/2012, you wrote:
>>I generally only use Twitter to distribute this kind of info, rather
>>than overload the list, but I find this article and study very
>>interesting, especially in that it provides tips and ideas not just
>>for designers but also for SR vendors.
>
>
>>http://www.redish.net/content/papers/interactions.html
>>>>>>>
> > > >