WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Testing with Screen Readers (was RE: Wai Aria how useful?)

for

From: Birkir Rúnar Gunnarsson
Date: Jul 28, 2010 7:00AM

At the conference I attended in Vienna (and some of you attended as
well, I believe) there was talk about the need for screen reader/AT
software simulation tools or plug ins for development environments, so
the developers get a feel for the problem and how their code would
work for a screen reader user.
It is an interesting idea, though there are some limitations, e.g.
that one should expect an SR user, or user of any other AT, to have
developed some skills with the product and be able to do more with it
than, perhaps, a developer would see at first glance.
Also building accessibility testing and compliance into CMS and other
development software would definitely, I think, be a very good step,
and I know there are projects going on in the area.
I see the practical problem of testing with real users, it is
expensive, there are marked differences in what each screen reader
does well and does badly, so you might need different testing based on
your potential user group etc.
Sometimes a particular SR has not implemented technology that exists,
and it is hard for the developer to do anything about it.
Cheers
-B

On 7/28/10, Langum, Michael J < <EMAIL REMOVED> > wrote:
> John writes:
>> The other point that must be considered is that to really be able to
>> 'test' with any screen-reader,
>> you should be a daily screen-reader user. ....
>
> I agree in principle, but in the "real world" time and resources do not
> permit the additional time and cost of testing by "a daily screen-reader
> user."
>
> I am only able to do detailed testing at the code level (e.g. "alt" text;
> semantic structure; <label> for <input>, column and row headers, etc. We do
> randomized testing on some content, and react immediately if we get any user
> complaints.
>
> Jared, Do you think there might be value in doing a survey on testing
> methodologies? Do developers actually test? Do they go beyond the use of
> automated testing tools? Do they do "functional" testing with various AT
> products? Do they do this functional testing on each file developed?
>
> -- Mike
>
>
>
>
>>