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

Tasks: browser <-> screen reader

From: jaap van lelieveld <Jaap.van.Lelieveld@inter.NL.net>
Date: Sun, 05 Apr 1998 21:15:33 +0100
To: w3c-wai-ui@w3.org
Message-ID: <lZ+J18h/n7TX092yn@inter.nl.net>
During the LA UA meeting we started a discusion on what tasks
should be done by the screen reader and what tasks should
be done by the browser.
There it was not the place and not the time to extend this
discussion. I expected some more arguments on this here.
Since they did not come up to now ... I'd like to start this discussion.

It is my opinion you should - if possible - solve a problem only
once.
Since a browser is only one of the appication I run the screen readers
must give the intelligent suport needed anyway.

Therefore ... do NOT implement non-browser specific reading requirements
in the browser.
- This will only complicate the browser,
- increase costs and/or wait time (before the browser is ready)
- Reduce the chance of rapid upgrades,
- increase the change of reading conflicts.

For a discussion on general applications with screen reader
features and intelligent screen reader features  
please see my comments on:
http://www.inter.nl.net/users/jvleliev/ebutc.htm

If you do not agree ... please let me know.

Best regards,
Jaap

Message from: Jaap van Lelieveld      The Netherlands
              Chairman of EBU commission on Technical Devices and Services
E-mail:       Jaap.van.Lelieveld@inter.nl.net

USING: YARN V0.92 as an offline reader, and
       UQWK / OLMENU under UNIX for mail and news transfer
Received on Sunday, 5 April 1998 15:35:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:20 UTC