Thread Subject: Re: Focus Cursor

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: Jared Smith
Date: Wed, Aug 15 2007 12:30 PM

Here's my stab at wording that clarifies a few things and (hopefully)
covers the issues brought up in today's call:

At least one mode must provide a highly visible indication of which
user interface object currently has the keyboard focus.

Note: If the object is a text entry field, a visual indication of the
text insertion point is sufficient in meeting this provision. One
method of determining sufficient visibility of focus indication is if
they are visually locatable without moving the cursor 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. Other
similar methods may be used.

Jared Smith

On 8/14/07, Gregg Vanderheiden < = EMAIL ADDRESS REMOVED = > wrote:
>
> Suggestion:
>
> Software must provide a highly visible indication of which user interface
> object currently has the keyboard focus. If the object is a text entry
> field, a visual indication of the text insertion point must be provided.
>
> (if we want testability – then add the following as a note – or include in
> provision)
>
> Note: Keyboard focus cursors and text cursors that are 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 are sufficient.

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University