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: Sean Hayes
Date: Tue, Sep 18 2007 3:25 AM

Doesn't that kind of make the note redundant? Not that I'm arguing that a text insertion indicator should get some special dispensation or anything. But the note kind of reads any mechanism which meets the provision is a sufficient mechanism.

Perhaps all we need to say is:

NOTE 1 the presence of a text insertion point can be considered a visual indication of keyboard focus for a text area.


Which is what i think we were after in the first place (to not require a separate indication on the text widget).

Sean Hayes
Incubation Lab
Accessibility Business Unit
Microsoft

Office: +44 118 909 5867,
Mobile: +44 7875 091385


-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gregg Vanderheiden
Sent: 18 September 2007 06:15
To: 'TEITAC Web/Software Subcommittee'
Subject: Re: [teitac-websoftware] note for focus cursor

Andy this is good. One small edit

Note 1 should read:

NOTE: If the object is a text entry field, a visual indication of the text
insertion point is sufficient as a focus cursor as long as it meets the
above provision.

OR

NOTE: If the object is a text entry field, a visual indication of the text
insertion point that meets the above provision is sufficient as a focus
cursor.


RATIONALE:
Note 1 is ambiguous. It says that the entry cursor is sufficient as a focus
cursor - which is good. But it also implies that that would be sufficient
to meet the provision. That would only be true if the focus cursor met the
provision.


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi Snow-Weaver
> Sent: Monday, September 17, 2007 5: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