Thread Subject: 3-T focus: suggested addition
Note
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: Hoffman, Allen
Date: Fri, Oct 19 2007 1:30 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
Suggestion:
Insert reference to the other standard requiring focus is exposed
programmatically here, with continuation documenting why the visibility
portion is separated from the programmatic exposure standard.
proposed language:
This provision is restricted to the visibility of the focus. focus must
also be programmatically exposed for assistive technology usage--see
3-U.
3-T - Focus Indicator
Software must support at least one mode that provides a highly visual
indication of which user interface object currently has the keyboard
focus.
list of 2 items
* Note: If the object is a text entry field, a visual indication of the
text insertion point is sufficient as a focus cursor.
* Note: A focus cursor that is visually locatable by people with
unimpaired vision at 2.5 meters when software is displayed on a 38 cm
(15 inch) diagonal
screen at 1024 x 768 pixels resolution, without moving the cursor is
sufficient.
list end
Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
- Next message in Thread: None
- Previous message in Thread: None
WebAIM is an initiative of:
