Thread Subject: Re: Reminder: Meeting today

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: Peter Korn
Date: Thu, Feb 08 2007 10:20 AM

Hi Allen,

> I believe the speaker in the afternoon had only a couple viable
> suggestions for regulatory items, one of which was to require glossary
> functionality for user-interfaces. I suppose this may be doable, and is
> certainly testable.

What I captured in my notes was:

- Cognitive A11y features / Some features are appropriate to require
- alternatives to speeded responses
- word lookup, or compatibility with word lookup tools
- text reading, or compatbiility with text reading tools
- spelling correction for spelling-sensitive interactions
- provision for suppressing unneeded functions

The first of these we already have.

The next three - word lookup (or compatibility with AT), text reading
(or compatibility with AT), and spelling correction [to which I would
add "or compatible with AT"] I believe can *all* be done via compatible
AT using the existing API Requirements Proposal. The set of "Additional
object information needed for objects that contain text" (see
http://teitac.org/wiki/Web_and_Software:Accessibility_API_Requirements_Proposal#Additional_object_information_needed_for_objects_that_contain_text:)
and the set of " Additional object information needed for editable text
objects:" (see
http://teitac.org/wiki/Web_and_Software:Accessibility_API_Requirements_Proposal#Additional_object_information_needed_for_editable_text_objects:)
should provide what is needed to support an add-on AT product that does
those three functions.

That then leaves the provision for suppressing unneeded functions. This
is a very difficult provision to measure, as a determination of what is
unneeded is highly subjective.

Still, if we get 4 out of his 5, I'd say we are significantly advancing
a number of cognitive disability use cases.


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.




>
> Allen hoffman -- 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> Barrett, Don
> Sent: Wednesday, February 07, 2007 5:16 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Reminder: Meeting today
>
> Nancy Ward was wonderful; our big problem is to try and distinguish
> actual access issues from usability issues; for the cognitive folks,
> many of the issues surround usability issues and would be tough for 508.
> I think that is why the original EITAC couldn't wrestle anything 508ish
> for the cognitive folks into the standard, although I applaud any effort
> to try and simplify Federal information. Lots to think about.
>
>
> Don Barrett
> Section 508 Coordinator
> U.S. Department of Education
> (202)-205-8245
> = EMAIL ADDRESS REMOVED =
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
> Snow-Weaver
> Sent: Wednesday, February 07, 2007 7:10 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] Reminder: Meeting today
>
>
> Please see the agenda for details on today's meeting. [1]
>
> We will spend an hour or less on the API Requirements proposal. Then we
> are privileged to have a guest speaker on cognitive disabilities. Her
> name is Nancy Ward, and she is an editor of an online website for
> disability benefits information, focused to the needs of persons with
> cognitive disabilities. We will allow at least 1/2 hour for discussion
> and Q&A with Ms. Ward.
>
> [1] http://teitac.org/wiki/Web_and_Software:_February_7
>
> Andi
>
>

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