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

RE: Some comments on conformance levels in UA guidelines draft

From: <schwer@us.ibm.com>
Date: Thu, 2 Dec 1999 12:28:53 -0600
To: peter.b.l.meijer@philips.com
cc: w3c-wai-ua@w3.org
Message-ID: <8525683B.00669253.00@d54mta08.raleigh.ibm.com>

Whose OSM? OSM's are screen reader vendor specific and are not resident on
any platform other than OS/2 and Windows.


Rich Schwerdtfeger
Lead Architect, IBM Special Needs Systems
EMail/web: schwer@us.ibm.com http://www.austin.ibm.com/sns/rich.htm

"Two roads diverged in a wood, and I -
I took the one less traveled by, and that has made all the difference.",

peter.b.l.meijer@philips.com on 12/01/99 02:19:13 PM

To:   w3c-wai-ua@w3.org
cc:   ij@w3.org, danson@miseri.edu
Subject:  RE: Some comments on conformance levels in UA guidelines draft

Denis Anson wrote

> I think that we can fix this issue.  (I've raised it myself on several
> occasions.)  The key, I think, is that the user agent might not have to
> provide screen reading natively, but it does have to provide a standard
> interface to screen readers.  If a browser exposes the content to third
> party assistive technology in a standard and documented way, then it
> be compliant.  If the information is not accessible, or must be "reverse
> engineered" to access, then the browser is not compliant.

Yes, I agree with you, Denis, and this is basically what I meant.

I was thinking of the "off-screen model" as a possible interface
level, such that the screen reader developer can tap these data
structures (in practice they already do) while the application
developer just needs to know which API calls, and/or visual controls
added via a resource editor, end up passing their key parameters
or events into the off-screen model. For the application developer,
it is sufficient to know, for instance, whether range and position
info for a progress bar ends up in the off-screen model of the GUI
(and whether this part of the off-screen model will be supported by
the envisioned "reference" screen reader specification, defining the
minimum requirements for compliance). The application developer
does not need to know how it is done or in what precise format the
data is stored in the off-screen model: only the screen reader
developer needs to know that in order to tap the off-screen model.

Additional work will be needed to forge this into a solid and open
standard, particularly if we want this as independent from any
particular operating system as possible, while I think all of this
should not delay the approval/release of the UA guidelines. I merely
suggest to move the whole conformance/compliance issue to this
proposed second phase that could follow approval/release of the UA

Best wishes,

Peter Meijer

The vOICe Internet Sonification Browser
Received on Thursday, 2 December 1999 13:41:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:24 UTC