Thread Subject: Re: note for 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: Hoffman, Allen
Date: Tue, Sep 18 2007 5:55 AM

Would it be worth adding a final note to match this with the provision
which requires focus be programmatically exposed, to highlight why we
have focus addressed in two places?



Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Monday, September 17, 2007 6:16 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] note for focus cursor

Okay, it looks like we have reached consensus on this as the final
wording now with the existing and modified notes:

"Any keyboard operable user interface must have a mode of operation
where the indication of keyboard focus has a high degree of visibility.
This can be provided by the interface itself or by the interface in
combination with focus services provided by the platform."

- 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 (familiar
with what the focus cursor would look like) who have 20/20 vision at
3.5 times the typical viewing distance without moving the cursor is
sufficient.

- NOTE: Since computer software would be displayed on unknown screen
sizes: for computer software a focus cursor that is visually locatable
by people (familiar with the cursor) who have 20/20 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.

Objections only please.

Andi

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