Provide no keyboard trap information in context

Name: Roger Hudson
Email: rhudson@usability.com.au
Affiliation: 
Document: W2
Item Number: Success Criterion 2.1.2
Part of Item: 
Comment Type: technical
Summary of Issue: Provide no keyboard trap information in context
Comment (Including rationale for any proposed change):
In cases where moving focus away from a component with the keyboard is relatively complex, this criterion requires users to be advised of a method for doing this. However, neither the Success Criterion nor the How to Meet and Understanding documents appear to suggest where or how this advice should be provided. It would seem to be most appropriate to offer the advice within the context of the component and in my view providing the advice on a generic accessibility information page would not be adequate.

Proposed Change:
Success Criterion rewritten as follows:

2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if moving focus away requires more than unmodified arrow or tab keys, a mechanism is provided in conjunction with the component to advise users how to move focus away. (Level A)

Received on Tuesday, 22 January 2008 00:34:27 UTC