WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessibility user testing

for

From: Birkir R. Gunnarsson
Date: Jul 19, 2016 8:29AM

Just one more thought. If you are not familiar with screen reading,
you might want to try and find an expert screen reader user, even an
accessibility person, in your area and do a pilot test with that
person face to face.
I think it may help you set expectations and get a little bit of a
feel for the task.
You can be successful without it, but I often find that, as a screen
reader user, sitting down with usability testers and going through the
tasks informally helps them feel more comfortable.
Cheers



On 7/19/16, Tim Harshbarger < <EMAIL REMOVED> > wrote:
> This is one reason why the usability test should focus on tasks and not just
> single components.
>
> Ultimately, everyone who uses an interface is trying to complete some kind
> of task or achieve some kind of goal. Some components of the interface might
> be accessible and others might be inaccessible. But what matters to the user
> is whether or not they can complete the task.
>
> So, in the example, the search box evidently was an accessibility disaster
> while other parts of the site were fine. However, if the search box prevents
> users from completing any other task, then the amazing accessibility of the
> rest of the interface does not matter--at least not until the search box is
> fixed.
>
> So, you probably want to talk about the results of a usability test in
> relation to how those accessibility barriers impacted user tasks--rather
> than talk about each accessibility problem as though it were a separate
> self-contained thing.
>
>
>
>
>
>
>