Thread Subject: Re: Platform software requirement to provideaccessibility services
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Andi Snow-Weaver
Date: Fri, Aug 17 2007 9:25 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Hoffman, Allen: "Re: Platform software requirement toprovideaccessibility services"
- Previous message in thread: Barrett, Don: "Re: Platform software requirement toprovideaccessibility services"
- Messages sorted by: Author | Thread | Date
Andi's proposal:
Platform software shall provide a set of services that enable assistive
technologies to interact with other software sufficient to enable
compliance with the "AT interoperability" and "Information and
Relationships" provision."
<Andi notes that there is a typo in her proposal. It should be "User
interface components" instead of "Information and Relationships">
Allen's Comment:
First, I feel this is essential to provide both rationale for platform
producers to include this kind of functionality, and second for
requiring officials to select based upon this, and third, to map our AT
interoperability more fully across the board as this is an end-to-end
set of responsibilities. Next, this kind of provision is more clear
than the current items in 1194.21(b). Finally, might this be tweaked to
include:
Allen's alternate proposal:
Platform software shall provide a set of services that enable
applications and assistive technologies to interact with other software
sufficient to enable compliance with the "AT interoperability" and
"User Interface Components" provision."
Allen, this provision is only about platforms providing a set of services
to enable AT to interact with other software. The AT interoperability and
User Interface Components provisions are the ones that require applications
to actually do the things needed to interact with AT.
I don't see it as related to the current 21(b) provision which is about
accessibility "features". I think of accessibility "features" as end user
functionality and accessibility "services" as programming interfaces.
So I don't think we should add "applications" to this provision.
Andi
- Next message in Thread: Hoffman, Allen: "Re: Platform software requirement toprovideaccessibility services"
- Previous message in Thread: Barrett, Don: "Re: Platform software requirement toprovideaccessibility services"
WebAIM is an initiative of:
