W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2003

Re: Accessible Dynamic Menus

From: David Woolley <david@djwhome.demon.co.uk>
Date: Wed, 28 May 2003 21:05:02 +0100 (BST)
Message-Id: <200305282005.h4SK53405639@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org

> OK, so you are saying that audio browsers would be reading the page as 
> viewed by a normal browser?  I thought they read the html as 'seen' by 
> a basic text browser like Lynx.

Lynx is only quoted because, for people that don't have a company to
pay US$1000 for JAWS, a common solution to accessing the web is to
use Lynx with a simple screen reader program.  They experience
is based on how Lynx displays things.

JAWS, which seems to be the reference point for companies wanting 
accessibility with little change to their systems, uses Microsoft
Active Accessibility and, possibly, other techniques to try to make
real world web pages as useable as possible.  As it is based on MSAA,
but probably as much as anything because real world web pages are
all designed only for visual media, it uses the document as rendered
for visual media as part of its input.   At least that is what I 
understand from what people have written here.
Received on Wednesday, 28 May 2003 16:12:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:15 UTC