- From: T.V Raman <raman@google.com>
- Date: Wed, 1 Aug 2007 16:50:17 -0700
- To: jason@jasonjgw.net
- Cc: public-html@w3.org
Well said, but to achieve that the so called "accessibility community" will need to dig itself out of its self-dug hole where accessibility is defined to be how things work with a screenreader. If coding for a given browser is evil, coding for a browser/screenreader combination is doubly so. Jason White writes: > > On Tue, Jul 31, 2007 at 03:58:30PM -0700, T.V Raman wrote: > > > > > > The HTML support becomes much more important in UAs like Firefox > > 3 that are beginning to lean far more heavily on the DOM -- > > rather than having screenreaders scrape an off-screen-model by > > watching render calls. > > Furthermore, since HTML 5 is intended to influence the evolution of the Web > over the coming decade, it is more important to support current and future > assistive technologies that will, and do, take advantage of HTML semantics, > either directly via the DOM or through increasingly rich accessibility APIs, > than to constrain the design by reference to the limitations of screen readers > which only examine the rendered presentation. Operating within such > constraints would serve only to perpetuate them by depriving more advanced AT > systems of the semantics with which to build superior user interfaces. > -- Best Regards, --raman Title: Research Scientist Email: raman@google.com WWW: http://emacspeak.sf.net/raman/ Google: tv+raman GTalk: raman@google.com, tv.raman.tv@gmail.com PGP: http://emacspeak.sf.net/raman/raman-almaden.asc
Received on Wednesday, 1 August 2007 23:50:54 UTC