Thread Subject: Re: API Requirements proposal

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: Gregg Vanderheiden
Date: Mon, Apr 02 2007 10:35 PM


Very nice.

This is a nice model for things like this.

Do we want to say something about being on a system that supports AT or
something? Else this could get applied to phones, or even advance
calculators?


Nicely done.


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi Snow-Weaver
> Sent: Monday, April 02, 2007 6:57 PM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] API Requirements proposal
>
>
> The API requirements sub-group is ready to put forward a
> proposal for modifications to 1194.21 (c), (d), and (f). [1]
>
> Please review this proposal and provide your comments and
> feedback via the mailing list. We will add this to the agenda
> for Wednesday's meeting.
>
> [1]
> http://teitac.org/wiki/Web_and_Software:_Accessibility_API_Req
> uirements_Draft_3
>
> Andi
>
>


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