Thread Subject: Re: Startingdiscussionson theAccessibility APIproposal
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: Lazzaro, Joe (ITD)
Date: Tue, Jan 09 2007 9:30 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jessica M. Brodey: "Re: Startingdiscussionson theAccessibility APIproposal"
- Previous message in thread: Jonathan Avila: "Re: Startingdiscussionson theAccessibility APIproposal"
- Messages sorted by: Author | Thread | Date
It will be a long time before there is one all-encompassing
accessibility API that runs across all platforms. Lambs will lie down
next to the lions when that happens. But we can specify that operating
systems should have accessibility APIs with a specified feature set.
That, I believe, is very doable both technically and politically.
Manager: Assistive Technology Group
Commonwealth of Massachusetts
Information Technology Division
One Ashburton Place
Boston, MA 02108
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
Sent: Tuesday, January 09, 2007 9:39 AM
To: TEITAC Web/Software Subcommittee
Cc: Peterson, Bill
Subject: Re: [teitac-websoftware]Startingdiscussionson theAccessibility
Norman Robinson wrote:
"I'll second that Allen (that an accessibility stack
description/model/index would be useful).
I also can't help but comment that the previous versions of MSAA were (I
thought) unencumbered by patent issues. We need something open and
consistent if we ever are to make a suggestion that industry consider
using a specific API."
I don't think we can say industry *must* use a specific API, but maybe
we can say that OS(s) have a requirement to include such an API and make
it available for use, and then require AT vendors to as possible make
use of available API9s). some of that is already there, but not
I don't think we can specify the openness of the API or cost factors.
Allen Hoffman -- 202-447-0303
DHS office on Accessible systems & technology
- Next message in Thread: Jessica M. Brodey: "Re: Startingdiscussionson theAccessibility APIproposal"
- Previous message in Thread: Jonathan Avila: "Re: Startingdiscussionson theAccessibility APIproposal"