Thread Subject: Re: Gaps in Web Requirements -keyboard operation
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, Dec 18 2006 9:10 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Andi Snow-Weaver: "Re: Gaps in Web Requirements - keyboardoperation"
- Previous message in thread: Fratkin, Mike: "Re: Gaps in Web Requirements - keyboardoperation"
- Messages sorted by: Author | Thread | Date
One of the advantages of using WCAG provisions is that there is a support
document (understanding WCAG) that provides easy to point to descriptions,
examples and techniques that are sufficient to meet the guidelines as well
as known failures. MouseKeys for example is specifically notes as not
sufficient to meet this guideline. The Understanding doc never modifies
the guideline but helps people less familiar understand what the rest of us
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Fratkin, Mike
> Sent: Monday, December 18, 2006 7:51 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Gaps in Web Requirements -
> keyboard operation
> At the present the keyboard requirement (1194.21a) is one of
> the most misunderstood requirements primarily due to its
> wording. The typical response we see on VPAT's is that mouse
> keys are supported. Secondly, it also needs to be included
> in the web requirements. Additional considerations include:
> Logical tab order
> Hotkeys/access keys - when to use, browser conflicts
> Testability - number of keystrokes to be comparable to mouse
> navigation Voice navigation - should it be separate from
> keyboard requirement
> [Andi wrote]
> Do we need to recommend a new requirement on keyboard operation?
> Note that WCAG 2.0 has one:
> All functionality of the content is operable through a
> keyboard interface without requiring specific timings for
> individual keystrokes, except where the underlying task
> requires analog, time-dependent input.
- Next message in Thread: Andi Snow-Weaver: "Re: Gaps in Web Requirements - keyboardoperation"
- Previous message in Thread: Fratkin, Mike: "Re: Gaps in Web Requirements - keyboardoperation"