E-mail List Archives
Re: testing web apps for accessibility
From: Sam Foster
Date: Mar 21, 2006 11:10PM
- Next message: Sam Foster: "javascript and webapps"
- Previous message: Sam Foster: "Re: testing web apps for accessibility"
- Next message in Thread: None
- Previous message in Thread: Sam Foster: "Re: testing web apps for accessibility"
- View all messages in this Thread
>Of course, having users with disabilities performing tasks with the app
>won't find all the problems in the app, but it should find the major
>problems with performing those tasks.
>
>
>
What troubles me with this is, if the test users do stumble through all
of some of the application, how do I interpret this result - does that
mean it is accessible? In other words, how do I know if these users are
*representative*, when we are talking about a huge potential range of
disabiliies and circumstances that could all highlight different
problems. I realize there's no such thing as certifying something as
accessible, but I'd want to avoid misleading results.
>Another thing to remember is that applications tend to have a consistent
>user interface. To increase efficiency, you only need to test sections
>of the interface that are unique or that are representative of a
>repeated user interface.
>
Very true.
Thanks again,
Sam
- Next message: Sam Foster: "javascript and webapps"
- Previous message: Sam Foster: "Re: testing web apps for accessibility"
- Next message in Thread: None
- Previous message in Thread: Sam Foster: "Re: testing web apps for accessibility"
- View all messages in this Thread