WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Why Doesn't AT do X?

for

From: Ryan Hemphill
Date: Apr 16, 2012 12:00PM

That is a very interesting question. I can only speak to my own
experience, but here goes.

Windows handles accessibility by pushing content to the AT/Screen Reader
with a feed originating from a thing called MSAA. It is, to put it
politely, very crude. In Internet Explorer, this delivery system requires
companies like Freedom Scientific (JAWS) to create hacks all over the place
to make sure its product works. I believe that most of these would be
considered hacks by the dev community. While I have never seen the code
itself, I suspect there are hacks built on hacks built on hacks, resulting
in an unstable piece of software. The other thing is the number of
developers. I believe that practically all of them are understaffed at
best. Another issue stems from the fact that information architecture in
these products falls woefully short and it does not appear that much 'new
blood' is entering these companies that could clean up the problems that
exist.

So that is what I think. Bad a11y support in the OS, too many hacks in the
AT, massive developer team issues and a lack of new perspectives brought in
from outside the current group(s).

It could also be a competition problem, I would agree with that - but I'd
say it is more likely to be based on the details above.

Ryan

On Mon, Apr 16, 2012 at 1:02 PM, Carol E Wheeler < <EMAIL REMOVED> > wrote:

> I have been wondering about AT, specifically screen readers throughout
> several threads. Is the problem mostly too small a pool of users for
> real competition? Why DO screen readers do so poor a job?
>
> -- cew
>
> *Carol E. Wheeler*
>
> Web Co-ordinator
> American Institute for Cancer Research
> 1759 R Street NW
> Washington DC 20009
>
> Direct Dial: 202-600-3001
> Tel: 202-328-7744
> Fax: 202-328-7226
>
> <EMAIL REMOVED>
> http://www.aicr.org
>
> > > >



--



Shipping is a Feature...Perhaps the Most Important Feature.