Expanding the web's potential for people with disabilities

Getting Started

Introduction to web accessibility

WebAIM Training

May 21-22
Training Details

From the Blog

Community

You are here: Home > TEITAC Archives > Mailing List Archives

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: Peter Wallack
Date: Wed, Sep 12 2007 2:05 PM

Return to this mailing list's archives
View all messages in this thread
Next message in thread: Gregg Vanderheiden: "Re: note for focus cursor"
Previous message in thread: Sean Hayes: "Re: note for focus cursor"
Messages sorted by: Author | Thread | Date

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I'm fine with this language, though I do want to point out that the
whole concept of 'people familiar with...' might be a much more
challenging topic to cover should 508 end up requiring testing with AT.
 
<pre class="moz-signature" cols="72">Peter Wallack
Accessibility Program Director
Oracle Corporation</pre>
 
 
Sean Hayes wrote:
<blockquote
cite="mid: = EMAIL ADDRESS REMOVED = "
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>

</style>

<div class="Section1">
<a moz-do-not-send="true" name="_MailEndCompose">Thanks,
Greg. That does
address that concern.<o:p></o:p></a>
<o:p> </o:p>
On
re-reading the provision however,  I have another
concern with the section :<o:p></o:p>
“Software
must support at least one mode that ...”<o:p></o:p>
<o:p> </o:p>
Which
implies that the application software must implement this
itself, but typically it is the platform software which provides this
functionality
for applications, for example embodied in a ‘widget set’ or library;
and even if the application designer could override the platform
behaviour,
they typically would not do so in order to fit in with the platform
user
interface guidelines<o:p></o:p>
<o:p> </o:p>
In
the case of a web application it may be the browser or plugin
which provides this (but not always).<o:p></o:p>
<o:p> </o:p>
Perhaps
a better wording would be something along the lines of:<o:p></o:p>
<o:p> </o:p>
“Platform
software must support at least one mode that
provides a highly visual indication of which user interface object
currently
has the keyboard focus. Application software that provides user
interface
objects must either use the focus mode provided by the platform
software or provide
such a mode directly”<o:p></o:p>
<o:p> </o:p>
<div>
Sean
Hayes 
Incubation Lab 
Accessibility Business Unit 
Microsoft<o:p></o:p>
<o:p> </o:p>
Office: 
+44 118 909 5867,  <o:p></o:p>
Mobile:
+44 7875
091385<o:p></o:p>
</div>
<o:p> </o:p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0cm 0cm;">
From: <a class="moz-txt-link-abbreviated" href="mailto: = EMAIL ADDRESS REMOVED = "> = EMAIL ADDRESS REMOVED = </a>
[<a class="moz-txt-link-freetext" href="mailto: = EMAIL ADDRESS REMOVED = ">mailto: = EMAIL ADDRESS REMOVED = </a>] On Behalf Of Gregg
Vanderheiden 
Sent: 12 September 2007 19:39 
To: 'TEITAC Web/Software Subcommittee' 
Subject: [teitac-websoftware] note for focus cursor<o:p></o:p>
</div>
</div>
<o:p> </o:p>
At
the very close of the meeting – I
noticed that this provision does talk about “without moving the
cursor”.  Thus knowledge of the cursor WOULD be required as Sean had
identified.  (apologies Sean).   I have edited the note below to
include his comment (I think). <o:p></o:p>
<o:p> </o:p>
I
also put a generic note for those who
are not designing software.  <o:p></o:p>
<o:p> </o:p>
<ul type="disc">
<li class="MsoNormal" style="">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.<o:p></o:p></li>
<li class="MsoNormal" style="">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. <o:p></o:p></li>
</ul>
<h4><a moz-do-not-send="true" name="Editorial_review_of_use_of_terms"></a> <o:p></o:p></h4>
<o:p> </o:p>
<o:p> </o:p>
 
Gregg 
 
------------------------<o:p></o:p>
Gregg
C Vanderheiden Ph.D. 
Professor
- Depts of <ns0:State><ns0:place>Ind.</ns0:place></ns0:State> Engr.
& BioMed Engr. 
Director - Trace R & D Center 
University
of Wisconsin-Madison 
<<a moz-do-not-send="true"
href="http://trace.wisc.edu/" target="_blank">http://trace.wisc.edu/</a>> FAX
608/262-8848  <o:p></o:p>
DSS
Player at <a moz-do-not-send="true" href="http://tinyurl.com/dho6b">http://tinyurl.com/dho6b</a>
<o:p></o:p>
If
Attachement is a mail.dat try <a moz-do-not-send="true"
href="http://www.kopf.com.br/winmail/">http://www.kopf.com.br/winmail/</a><o:p></o:p>
<a moz-do-not-send="true"
href="http://trace.wisc.edu:8080/mailman/listinfo/"> </a><o:p></o:p>
<o:p> </o:p>
<o:p> </o:p>
</div>
<pre wrap="">
<hr size="4" width="90%">

Next message in Thread: Gregg Vanderheiden: "Re: note for focus cursor"
Previous message in Thread: Sean Hayes: "Re: note for focus cursor"

WebAIM is an initiative of: