Gregg,
Rather than getting into minutia, let me just jump to Mary Jo's proposal:
<snip>
>
> So I think we should go with Mary Jo's version.
>
>
> *MARY JO WROTE*
>
> *- services provided by an operating system, user agent, or other
> platform software that can be used by non-web documents or
> software to expose information about the user interface and events
> to assistive technologies.*
>
>
>
> (if you don't like USED maybe use "relied upon"
I think we can go with a variant of this. To wit:
*- services provided by an operating system, user agent, or other
platform software that ENABLE non-Web documents or software to
expose information about the user interface and events to assistive
technologies.*
The software may or may not actively use these accessibility services.
To be an accessibility service, it has to enable something to happen.
And "exposing information" isn't as active - it is something one could
reasonably say is being done by markup (e.g. "ALT=..." is exposing
information, and the underlying accessibility service is utilizing that
exposed information).
Just as I wouldn't quibble with high school physics teaching Newtonian
physics and omitting relativity, I don't see any reason to quibble with
accessibility services "enabling non-Web documents" to this audience.
Peter
--
Oracle <http://www.oracle.com>
Peter Korn | Accessibility Principal
Phone: +1 650 5069522 <tel:+1%20650%205069522>
500 Oracle Parkway | Redwood City, CA 94064
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment