Thread Subject: Re: Startingdiscussionson theAccessibility APIproposal

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: Brett, Thomas F
Date: Fri, Jan 05 2007 11:15 AM

Hey Don....just wanted to give you a little jab....never end a sentence
with a preposition as in:

Rather than ATIA being afraid of an API, I should think they would
welcome it, as long as it is one their members can code to.

Tom Brett,
2026061206
= EMAIL ADDRESS REMOVED =

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
Barrett, Don
Sent: Friday, January 05, 2007 12:33 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware]Startingdiscussionson theAccessibility
APIproposal

The other piece of this is that A T is always playing catch up with new
I T technologies as they develop. Support for web-based tables and
JavaScript event handlers are two good examples. Once 508 specified
table markup for headers and cell associations for multi-level tables,
and functional text for scripts, A T vendors jumped on these issues, and
screen readers got better and better over time in handling these
elements. The more specific an API can be for mainstream I T vendors,
the more the marketplace will be established so A T can come in and meet
the specified market needs.

Rather than ATIA being afraid of an API, I should think they would
welcome it, as long as it is one their members can code to.

Don

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University