- From: T.V Raman <raman@google.com>
- Date: Tue, 31 Jul 2007 15:58:30 -0700
- To: rob@robburns.com
- Cc: raman@google.com, public-html@w3.org
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. Robert Burns writes: > > On Jul 31, 2007, at 5:40 PM, T.V Raman wrote: > > > In its early days I used to actively hunt down and flame people > > who dared call Emacspeak a screenreader:-) I dont do that as > > actively any more, but Emacspeak still remains a talking > > application, not a screenreader. > > Well lucky for me you've tired of chasing down such blasphemers :-). > I did list Emacspeak under both screen reader and aural browser to > recognize both roles it plays (more so than any other screen reader). > > > But you raise an important point with respect to the state of > > screenreaders and HTML/CSS -- as you point out, their focus has > > been traditionally in some ways less than, and in others more > > than "Web pages" -- they look at the screen, not at content. > > Yes, I think that's an important point that needs stressing. Often > times people point to a screen readers lack of support for HTML and > CSS facilities as evidence that "even the screen readers" don't want > those features. However, it's really a matter of them having a > different focus than a talking application or aural browser. Their > focus may be changing slowly, but they still don't seem to be > focussed on necessarily consuming HTML or CSS specific features. > > Take care, > Rob -- 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 Tuesday, 31 July 2007 22:58:58 UTC