E-mail List Archives
Re: Accessibility user testing
From: Tim Harshbarger
Date: Jul 19, 2016 7:47AM
- Next message: Gillen, Lori: "Re: section 508 vs wcag 2.0"
- Previous message: Moore,Michael (Accessibility) (HHSC): "Re: Accessibility user testing"
- Next message in Thread: Dana Douglas: "Re: Accessibility user testing"
- Previous message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: Accessibility user testing"
- View all messages in this Thread
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.
- Next message: Gillen, Lori: "Re: section 508 vs wcag 2.0"
- Previous message: Moore,Michael (Accessibility) (HHSC): "Re: Accessibility user testing"
- Next message in Thread: Dana Douglas: "Re: Accessibility user testing"
- Previous message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: Accessibility user testing"
- View all messages in this Thread