Thread Subject: 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: Andi Snow-Weaver
Date: Fri, Jan 12 2007 8:25 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Robinson, Norman B - Washington, DC: "Re: Web Gaps - keyboard operation"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
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
- Next message in Thread: Robinson, Norman B - Washington, DC: "Re: Web Gaps - keyboard operation"
- Previous message in Thread: None
WebAIM is an initiative of:
