Thread Subject: Group A: 21(c) Keyboard focus
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, Oct 27 2006 7:30 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Brett, Thomas F: "Re: Group A: 21(c) Keyboard focus"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
21(c) current wording:
A well-defined on-screen indication of the current focus shall be provided
that moves among interactive interface elements as the input focus changes.
The focus shall be programmatically exposed so that assistive technology
can track focus and focus changes.
ISO has two provisions that address this issue: "Software shall provide a
focus cursor that visually indicates which user interface element currently
has the keyboard input focus, as well as the focus location within that
element when one exists." ISO does not contain a provision specifically
addressing programmatic exposure of keyboard focus but it does include one
that requires using system standard input and output services. If you use
standard input services, doesn't that imply that the keyboard focus is
ISO does have a provision on event notification which would cover keyboard
focus changes and all other type of user interaction events: "Software
shall provide assistive technology with notification of events relevant to
It includes the following expanatory note:
Events relevant to user interaction include, but are not limited to,
changes in user interface element status (such as creation of new user
interface elements, changes in selection, changes in focus and changes in
position), changes in attributes (such as size, colour and name), and
changes of relationships between user interface elements (such as when one
user interface element contains, names, describes or affects another). Just
as important are input events, such as key presses and mouse button
presses, and output events, such as writing text to the screen or playing
audio information. This also applies to user interface status values (such
as the states of toggle keys).
Do we want to make 508 broader and more comprehensive in this area?
This function is not required by 508 for Web content and applications
(1194.22). Do we need to add this for Web content and applications? WCAG
2.0 does not contain such a provision.
- Next message in Thread: Brett, Thomas F: "Re: Group A: 21(c) Keyboard focus"
- Previous message in Thread: None