W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2007

FW: Open action items on 1.1.1

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Tue, 3 Apr 2007 19:11:38 -0500
To: <w3c-wai-gl@w3.org>
Message-ID: <010601c7764d$d10eb5b0$a117a8c0@NC84301>
 

Gregg and Sean had an action item to resolve wording issue on 1.1.1

 

ACTION: Gregg and John to review Sean's concerns in the how to meet for
1.1.1 [recorded in
http://www.w3.org/WAI/GL/2007/03/15-wai-wcag-minutes.html#action07  

 

The issue dealt with the following part of 1.1.1

 

*  Controls-Input: If non-text content is a control or accepts user input,
then it has a name
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20070220/#namedef>  that
describes its purpose. (See also Guideline
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20070220/#ensure-compat>  4.1
Support compatibility with current and future user agents, including
assistive technologies) 

 

The concern had to do with ambiguity of 'control' which has dual meanings to
a programmer and also seems to be redundant with "accepts user input"

 

Proposed resolution

 

Delete  "is a control or"  so that it reads

*  Controls-Input: If non-text content accepts user input, then it has a
name <http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20070220/#namedef>  that
describes its purpose. (See also Guideline
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20070220/#ensure-compat>  4.1
Support compatibility with current and future user agents, including
assistive technologies) 

 

And then just put into the "How to meet"  that  controls are examples of
thing that accept user input. 

 

 

 


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

 

 




Received on Wednesday, 4 April 2007 00:11:50 GMT

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