W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2005

RE: Server side maps

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Sun, 4 Dec 2005 18:16:33 -0600
To: "'Gregg Vanderheiden'" <gv@trace.wisc.edu>, <jim@jimthatcher.com>, "'Guide Lines list'" <w3c-wai-gl@w3.org>
Message-ID: <016b01c5f931$2749d130$ee8cfea9@NC6000BAK>

Actually i should have said that it should be on NEITHER. 

It belongs in the How to Meet section of the understanding Doc rather than
in the guidelines doc.  

By the way the How to Meet doc for 2.1.2 says that is is exactly the same as
2.1.1 except it has no exception. 

Thanks Jim - we'll remove it from Guidelines and put in "how to meet doc" 

 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 


-----Original Message-----
From: Gregg Vanderheiden [mailto:gv@trace.wisc.edu] 
Sent: Sunday, December 04, 2005 6:06 PM
To: 'jim@jimthatcher.com'; 'Guide Lines list'
Subject: RE: Server side maps

Should be on both.  They are identical except for the exception.  


 
Gregg

 -- ------------------------------
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison 


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Jim Thatcher
Sent: Sunday, December 04, 2005 4:34 PM
To: 'Guide Lines list'
Subject: Server side maps


Can someone describe the difference between SC 2.1.1 and SC 2.1.2 as they
apply to server-side maps? The note about server-side maps is attached to
the level 3 SC 2.1.2. Why not attached to 2.1.1? Does the requirement for
equivalent text links for server side maps stem from (an implementation of)
2.1.1 (as well as 2.4.5 which is level 2).

Jim
 
Accessibility Consulting: http://jimthatcher.com/
512-306-0931

2.1.1. All functionality of the content is operable in a non time-dependent
manner through a keyboard interface, except where the task requires analog,
time-dependent input. 

Note: This does not preclude and should not discourage the support of other
input methods (such as a mouse) in addition to keyboard operation. Note:
MouseKeys does not satisfy this success criterion.

2.1.2. All functionality of the content is designed to be operated through a
keyboard interface. [Level 3.] 

Note: Server-side image maps are not keyboard accessible.

2.4.5. Each programmatic reference to another delivery unit or to another
location in the same delivery unit, is associated with text describing the
destination. [Level 2.]
Received on Monday, 5 December 2005 00:16:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:41 GMT