WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: screen reader usage?

for

From: Joe Chidzik
Date: Feb 9, 2016 8:21AM

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
>
> > > http://webaim.org/discussion/archives
>