Thread Subject: Re: 3-w at-interoperability and 3-V

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: Hoffman, Allen
Date: Wed, Sep 05 2007 3:50 PM

To ensure that assistive technologies have access to the information
they need to then render for people with disabilities in an alternate
fashion or format, the first step is to identify what information is
available. Once this is accomplished, and the information is deemed
sufficient, we get in to "quality" issues such as if the information is
accurate, or if the information is complete. So, for example if I find
that there are two buttons in a dialogue box labeled "error:", and the
buttons are labeled "yes" "no", but the text in the box that says
"system reboot due to user disinterest...", or some such, then our first
step would identify that we don't have sufficient information to then
present a voice output version of that page--but we might have enough to
allow enlarged text?

So, this is similar to the quality of information for alternate text,
but other issues around multiple systems of providing the information
come up.

For example, if information is provided directly in an available API,
but other information is in another separate API, these both need to be
documented, and supported by the AT and platforms in use, or something
will be missing.

I'm less worried about the information quality since this is often a
mistake of a developer than an intentional error. I'd like to get the
basics made easily testable, and then use AT to determine information
quality.

Introduction of AT in the testing process while needed is not the
optimal path for reliable success.



Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303

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