W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2008

Re: EOWG's replies to WCAG WG resolutions of EOWG comments on May 2007 Draft of WCAG 2.0

From: Wayne Dick <wed@csulb.edu>
Date: Fri, 08 Feb 2008 18:21:56 -0800
Message-ID: <47AD0E44.2070202@csulb.edu>
To: Loretta Guarino Reid <lorettaguarino@google.com>
CC: Shawn Henry <shawn@w3.org>, public-comments-wcag20@w3.org, "EOWG (E-mail)" <w3c-wai-eo@w3.org>

Dear Loretta,

I not going to die if I don't get my way, but the WCAG WG does seem to 
missing something important.  The definition of accessibility-supported 
refers to actions that have been done to support accommodation not 
accessibility.  The accessibility state is a neutral state that permits 
accommodation with assistive technology.  Thus you have defined 
accommodation-supported but you want accessibility-supporting.

That's my 2 cents, and I'm not too worked up about either name.

Wayne


Loretta Guarino Reid wrote:
> Shawn,
>
> (Note that this is a response to the thread opened on the November
> 2007 Public Working Draft, and does not respond to the related comment
> on the December 2007 Last Call Draft).
>
> "Accessibility supporting" would talk about what the technology does.
> That is, it supports accessibility. "Accessibility supported" refers
> to what has been done to (or is true of) a technology. That is, that
> there is accessibility support FOR the technology.  We mean the latter
> not the former.
>
> So "accessibility supported"  would be the correct term and would be
> hyphenated whenever used as an adjective.
>
> Regards,
>
> Loretta Guarino Reid, WCAG WG Co-Chair
> Gregg Vanderheiden, WCAG WG Co-Chair
> Michael Cooper, WCAG WG Staff Contact
>
> On behalf of the WCAG Working Group
>
>
> On Jan 11, 2008 9:24 AM, Shawn Henry <shawn@w3.org> wrote:
>   
>> Dear WCAG WG,
>>
>> Thank you for considering our comments on previous drafts of WCAG 2.0. Below are replies to the comments you sent on 11 December 2007 (archived at http://lists.w3.org/Archives/Public/w3c-wai-eo/2007OctDec/). They are grouped in two sections: Need additional followup, EOWG accepts resolution.
>>
>> Need additional followup:
>>
>> Comment 4: use accessibility-supported technologies
>> http://lists.w3.org/Archives/Public/w3c-wai-eo/2007OctDec/0174.html
>>
>> EOWG comment:
>> We are concerned that the following sentence is still difficult to parse: "Any information or functionality that is implemented in technologies that are not accessibility supported must also be available via technologies that are accessibility supported." Particularly, the phrasing of "accessibility supported technology" throughout is a difficult construct.
>> We suggest that using the phrase "technologies with accessibility support" may facilitate comprehension here, and possible everywhere that the current phrase "accessibility supported technologies" is used. Such replacement here would yield:
>> "Any information or functionality that is implemented in technologies without accessibility support must also be available via technologies with accessibility support."
>>
>> WCAG reply:
>> Accessibility-supported is a descriptor that we use in many places and is defined in the glossary. It is a bit awkward to get used to at first but it is a critical concept and term for WCAG 2.0. Your rephrasing makes for an easier to read sentence but the concept is lost as a defined descriptor.
>>
>> EOWG reply, Jan 2008: OK, we agree with having it as a defined descriptor. However, do need to correct the grammar. Change "supported" to "supporting" and hyphenate so it's: accessibility-supporting technologies.
>>
>>     
>
>
>   
Received on Saturday, 9 February 2008 02:23:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:47 GMT