Thread Subject: Focus Cursor

Return to this mailing list's archives

From: Gregg Vanderheiden
Date: Tue, Aug 14 2007 11:50 AM
Subject: Focus Cursor

This is an old problem that we still have with this provision.



- The ORIGINAL 508 provision called for a "well defined" focus cursor

- ISO & ANSI call for a highly visible cursor

"Software shall provide at least one mode where keyboard focus cursors and
text cursors should be 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."



The current proposed language doesn't call for anything that isn't already
provided by almost every piece of software. The problem is that the
indication is so slight that people with low vision cannot see it - which
was the reason for the provision in the old




Current proposed language




Software must provide a visual 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, and is
sufficient.




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.






Gregg

------------------------

Gregg C Vanderheiden Ph.D.
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848

DSS Player at http://tinyurl.com/dho6b

If Attachement is a mail.dat try <http://www.kopf.com.br/winmail/>
http://www.kopf.com.br/winmail/

<http://trace.wisc.edu:8080/mailman/listinfo/>

From: Andi Snow-Weaver
Date: Tue, Aug 14 2007 4:30 PM
Subject: Re: Focus Cursor

Yes Gregg. You're absolutely right. That's why there is this note with the
provision: Note that we are still working on testable wording that
captures the existing 508 concept of a "highly visible" focus indicator.

I plan to work on this for tomorrow. Thank you for restating the proposal
you put on the mailing list before. Now I don't have to go searching for
it. <grin>

Andi




Gregg
Vanderheiden
< = EMAIL ADDRESS REMOVED = To
u> "'TEITAC Web/Software
Sent by: Subcommittee'"
teitac-websoftwar < = EMAIL ADDRESS REMOVED =
= EMAIL ADDRESS REMOVED = >
itac.org cc

Subject
08/14/2007 12:07 [teitac-websoftware] Focus Cursor
PM


Please respond to
TEITAC
Web/Software
Subcommittee
<teitac-websoftwa
= EMAIL ADDRESS REMOVED =
g>






This is an old problem that we still have with this provision.

- The ORIGINAL 508 provision called for a �well defined� focus cursor
- ISO & ANSI call for a highly visible cursor
�Software shall provide at least one mode where keyboard focus cursors and
text cursors should be 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.�

The current proposed language doesn�t call for anything that isn't already
provided by almost every piece of software. The problem is that the
indication is so slight that people with low vision cannot see it � which
was the reason for the provision in the old

Current proposed language

Software must provide a visual 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, and is
sufficient.

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.



Gregg

------------------------
Gregg C Vanderheiden Ph.D.
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison
<http://trace.wisc.edu/> FAX 608/262-8848
DSS Player at http://tinyurl.com/dho6b
If Attachement is a mail.dat try http://www.kopf.com.br/winmail/





_______________________________________________
teitac-websoftware mailing list
= EMAIL ADDRESS REMOVED =
http://list.teitac.org/mailman/listinfo/teitac-websoftware

From: Gregg Vanderheiden
Date: Tue, Aug 14 2007 4:50 PM
Subject: Re: Focus Cursor

Always happy to oblige (grin).

( was working off of the chart/table from the second link in your email and
didn't see that note)

Anything to save you time. You are working so hard on all this. Great job.


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



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi Snow-Weaver
> Sent: Tuesday, August 14, 2007 5:28 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Focus Cursor
>
> Yes Gregg. You're absolutely right. That's why there is this
> note with the
> provision: Note that we are still working on testable
> wording that captures the existing 508 concept of a "highly
> visible" focus indicator.
>
> I plan to work on this for tomorrow. Thank you for restating
> the proposal you put on the mailing list before. Now I don't
> have to go searching for it. <grin>
>
> Andi
>
>
>
>
>
> Gregg
>
> Vanderheiden
>
> < = EMAIL ADDRESS REMOVED =
> To
> u> "'TEITAC Web/Software
>
> Sent by: Subcommittee'"
>
> teitac-websoftwar
> < = EMAIL ADDRESS REMOVED =
> = EMAIL ADDRESS REMOVED = >
>
> itac.org
> cc
>
>
>
> Subject
> 08/14/2007 12:07 [teitac-websoftware]
> Focus Cursor
> PM
>
>
>
>
>
> Please respond to
>
> TEITAC
>
> Web/Software
>
> Subcommittee
>
> <teitac-websoftwa
>
> = EMAIL ADDRESS REMOVED =
>
> g>
>
>
>
>
>
>
>
>
>
> This is an old problem that we still have with this provision.
>
> - The ORIGINAL 508 provision called for a "well defined" focus cursor
> - ISO & ANSI call for a highly visible cursor
> "Software shall provide at least one mode where keyboard
> focus cursors and text cursors should be 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."
>
> The current proposed language doesn't call for anything that
> isn't already provided by almost every piece of software.
> The problem is that the indication is so slight that people
> with low vision cannot see it - which was the reason for the
> provision in the old
>
> Current proposed language
>
> Software must provide a visual 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, and is sufficient.
>
> 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.
>
>
>
> Gregg
>
> ------------------------
> Gregg C Vanderheiden Ph.D.
> Professor - Depts of Ind. Engr. & BioMed Engr.
> Director - Trace R & D Center
> University of Wisconsin-Madison
> <http://trace.wisc.edu/> FAX 608/262-8848 DSS Player at
> http://tinyurl.com/dho6b If Attachement is a mail.dat try
> http://www.kopf.com.br/winmail/
>
>
>
>
>

From: Jared Smith
Date: Wed, Aug 15 2007 12:30 PM
Subject: Re: Focus Cursor

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.

From: Jared Smith
Date: Wed, Aug 15 2007 12:35 PM
Subject: Re: Focus Cursor

I hit Undo one to many times before sending. The last sentence should
read, "Other *comparable* methods may be used."

Jared

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