Thread Subject: Re: Web Gaps - keyboard operation

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: Lybarger, Barbara (MOD)
Date: Tue, Jan 16 2007 5:16 PM

How about adding "or numbers" at the end. Otherwise, I like it.

Barbara Lybarger

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Friday, January 12, 2007 10:23 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] Web Gaps - keyboard operation


In our discussion yesterday of the keyboard proposal, there were two
issues:

- concern that this may except devices that do not have a keyboard but
which do have keyboard interfaces that may be used by other devices or
AT software. For example, speech recognition software may use the
keyboard interface for voice navigation.
- confusion over the term "discerned textually". Most interpret this to
mean that free-form drawing functions do not need to be keyboard
operable.
But drawing "objects" such as rectangles or circles can be described by
the attributes - length, width, radius, position on screen, etc. So
these types of drawing functions which are optimized for the mouse, do
need to be keyboard operable.

Here's one more attempt at a proposal for a keyboard requirement for
Web:

For Web content or applications that are designed to run on a system
that has a keyboard interface, product functions shall be executable
from a keyboard interface where the function itself or the result of
performing a function can be described in words.

Andi

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