Thread Subject: Re: 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: Sailesh Panchang
Date: Mon, Oct 30 2006 1:45 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Hoffman, Allen: "Re: Group A: 21(c) Keyboard focus"
- Previous message in thread: Peter Korn: "Re: Group A: 21(c) Keyboard focus"
- Messages sorted by: Author | Thread | Date
Andi quoted the current wording:
1194.21(c) 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.
I think re-stating the above as follows will make it more understandable and
easier to interpret. Suggestion:
"(c) A well-defined on-screen indication shall be provided for every
interactive interface element as it gains input focus. The focus shall be
programmatically exposed so that assistive technology can track focus and
focus changes. "
The Guide states:
The position on a screen where an action will take place is referred to as
the "focus". For example, when a menu item in a program is highlighted -
meaning that if the user clicks the mouse or presses the enter key - the
feature will activate and that item has the focus. Providing a visual
indication of the focus allows someone who is viewing the screen to
accurately access the programs' features.
This is in line with Jim's assessment:
>This is talking about input focus. When an interactive element receives
>focus, that fact is indicated by a dotted rectangle or highlight and that
>fact can be programmatically detected.
My understanding is that this standard apparently does not have anything to
do with helping users locate the search results after hitting the search
button or identifying form controls that fail validation upon form
Senior Accessibility Engineer
Deque Systems Inc. (www.deque.com)
11130 Sunrise Valley Drive, Suite #140,
Reston VA 20191
Phone: 703-225-0380 (ext 105)
E-mail: = EMAIL ADDRESS REMOVED =
- Next message in Thread: Hoffman, Allen: "Re: Group A: 21(c) Keyboard focus"
- Previous message in Thread: Peter Korn: "Re: Group A: 21(c) Keyboard focus"