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: Jim Thatcher
Date: Mon, Oct 30 2006 10:46 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Peter Korn: "Re: Group A: 21(c) Keyboard focus"
- Previous message in thread: Fratkin, Mike: "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.
"Do we want to make 508 broader and more comprehensive in this area?"
And Don added:
"At least to my knowledge, it isn't testable or measurable"
I think that this provision (1194.21(c)) is fully testable and says what it
should. Furthermore it is one of the most important accessibility
requirements for all kinds of disabilities. 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
Testability is not necessarily automatic; not necessarily easy.
Peter Korn writes:
"What I think is wanted is a way for E&IT to indicate to AT that "something
new and interesting has happened here; you might want to convey it to your
Sure - but that is a different situation from the requirement here - current
input focus, so important for all users who don't use a pointing device.
Accessibility Consulting: http://jimthatcher.com/
- Next message in Thread: Peter Korn: "Re: Group A: 21(c) Keyboard focus"
- Previous message in Thread: Fratkin, Mike: "Re: Group A: 21(c) Keyboard focus"