Thread Subject: Re: Focus Cursor
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:35 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Jared Smith: "Re: Focus Cursor"
- Messages sorted by: Author | Thread | Date
I hit Undo one to many times before sending. The last sentence should
read, "Other *comparable* methods may be used."
On 8/15/07, Jared Smith < = EMAIL ADDRESS REMOVED = > wrote:
> 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
- Next message in Thread: None
- Previous message in Thread: Jared Smith: "Re: Focus Cursor"