WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: screen reader usage?

for

From: Sean Murphy
Date: Feb 10, 2016 2:19AM

All,

My only comments are:

Tab and shift+tab is a base line for navigation in a web page as all screen reader's should honour these keystrokes on any platform. After this point it is fair game on how the user uses their technology. I use all the methods that have been described to navigate a page depending on the context. EG: navigating between form elements I will use the tab to make it quicker. Jumping through large chunk of the page I will use elements. The arrow keys I use when I want to read something specifically.

Note, Braille users will work similarly.

Sean

> On 10 Feb 2016, at 3:34 am, Angel Chesimet < <EMAIL REMOVED> > wrote:
>
> Hello,
>
> I am a screen-reader user and a tester and I agree with the comments
> already mentioned here. Screen-reader user skills vary like the
> varying individuals and their technology skills of members on this
> list vary. So using testers with a variety of experience is ideal.
>
> Angel
>
> On 2/9/16, Joe Chidzik < <EMAIL REMOVED> > wrote:
>> As you've observed, users will work in different ways, so it is important to
>> involve them in any testing process for best results. Novice screenreader
>> users will work in a different way to more experienced users, and so on for
>> advanced users.
>>
>> That said pre-user testing can be useful to remove obvious issues and allow
>> user testing to focus on more relevant issues.
>>
>> Note that I am a sighted user, using a screenreader, but when carrying out
>> screenreader testing, I try to:
>> -Arrow downup through page content
>> -Navigate data tables appropriately; traversing to make sure headers are
>> properly picked up
>> -Navigate controls via tabshift-tab to check for focus order, and that
>> controls are announced as expected
>> -Review content of the JAWS dialogs for Headings, Form controls, Links (or
>> other screenreader equivalents) - useful to see all linksheadings out of
>> context, and the forms list is great for quickly spotting a mis-labelled
>> form field.
>> -For forms, important to check both labellinginstructions, but also
>> behaviour when erroneousmissing data submitted. Are errors announceduseful
>> etc.
>>
>> Hopefully some actual screenreader users will be able to chip in here with
>> their experiences too.
>>
>> Cheers
>> Joe
>>
>>
>>> -----Original Message-----
>>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ]
>>> On Behalf Of Joseph Sherman
>>> Sent: 09 February 2016 14:54
>>> To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
>>> Subject: [WebAIM] screen reader usage?
>>>
>>> Is there a "regular" way screen reader users navigate pages? The users
>>> that
>>> I've worked with all seem to have different methods when a page loads.
>>> Some hit down arrow, some use navigation aids (links, headings, regions),
>>> some use tab, etc. And the method used can change the usability of a
>>> page-
>>> tabbing can skip text or instructions for example.
>>>
>>> Thoughts?
>>>
>>>
>>> Joseph
>>>
>>> >>> >>> at
>>> http://webaim.org/discussion/archives
>>> >> >> >> >> >>
>
>
> --
> Angel Chesimet, MS, LPCi
> Counselor
>
> Disability Services
> Portland Community College
> Rock Creek Bldg: 9 Rm: 109
> Office hours: Mon./Wed.
>
> Voicemail: 971-722-8007
> E-mail: <EMAIL REMOVED>
> www.pcc.edu/resources/disability
>
> Caution: This email may not be secure or confidential.
> > > >