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: Robinson, Norman B - Washington, DC
Date: Wed, Sep 19 2007 7:10 AM

Andi,

What about the link to the API/programmed interface/OS
accessibility layer? I'm think the below works for functions but won't
necessarily work when talking about assistive technologies (e.g., MAGic
auto focuses on the system event and drives the magnified focus to the
object based on MSAA/window widget events).

1. It isn't "the user interface" of the program that is
providing this, it is my assistive technology.
2. I can create a program that meets the below wording, yet
doesn't use the accessibility API on my OS/platform and that would be
very bad for use of assistive technologies.

Regards,


Norman B. Robinson
Section 508 Coordinator
IT Governance, US Postal Service
phone: 202.268.8246


-----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