W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2002


From: David Woolley <david@djwhome.demon.co.uk>
Date: Sat, 19 Oct 2002 10:32:07 +0100 (BST)
Message-Id: <200210190932.g9J9W7Y02730@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org

> described below is because, in the utopian sense of the word, a screen 
> reader simply reads what is rendered on the screen, and does not perform 

In practice, what people call screen readers are not pure screen readers - in
fact, with GUI type operating systems, such could only be created by using
optical character recognition techniques.  At the very least, they would
need to invoke copy and paste capabilities in the application (or
in the application's run time system - e.g. Visual Basic), and, in the
case of the most often quoted of "screen readers" for web pages, they
use MSAA, Microsoft's Accessiblity API, to interface with accessibility
support features in the basic browser.

Real screen readers tend to be used with tools like Lynx, although they
may be quite common amongst those who pay for their own AT.
Received on Saturday, 19 October 2002 06:18:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:20 UTC