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

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.


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

> >----------------------------------------------------------
> >Comment 4: use accessibility-supported technologies
> >Source:
> >
> >(Issue ID: 2274)
> >
> >2. [conformance section] Explain clearly & simply, as part of the
> >introductory paragraph, that some technologies support assistive
> >technologies, and that these are the ones that one should use.
> >
> >Response from Working Group:
> >
> >The Introduction section was moved to Understanding WCAG, but
> >'accessibility supported' is mentioned in the introductory sentence
> >(all there is) and then clearly explained in conformance requirement
> >#6 which follows shortly after.
> EOWG reply on comment #4:
> 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."

Received on Tuesday, 11 December 2007 23:59:56 UTC