W3C home > Mailing lists > Public > w3c-wai-au@w3.org > July to September 2011

Fwd: ATAG comments

From: Jeanne Spellman <jeanne@w3.org>
Date: Fri, 16 Sep 2011 11:26:38 -0400
Message-ID: <4E736AAE.9070801@w3.org>
To: AUWG <w3c-wai-au@w3.org>
For those not subscribed to the public list, these ATAG comments came in 
on the 15th.


-------- Original Message --------
Subject: ATAG comments
Resent-Date: Fri, 16 Sep 2011 15:02:15 +0000
Resent-From: public-atag2-comments@w3.org
Date: Thu, 15 Sep 2011 22:01:15 -0400
From: Web Standards / Normes Web <ws-nw@tbs-sct.gc.ca>
To: 'public-atag2-comments@w3.org' <public-atag2-comments@w3.org>

The consistent use of terminology is important to the understanding of 
any detailed documentation. This document is largely successful in that 

One area of concern, however, is the inconsistent use of the terms 
"accessible" and "accessibility."
For titles and principles, the use of the terms "accessible" and 
"accessibility", on their own, do not pose an issue.  In the body of the 
detailed guidance, however, it is important that the terms  be used 
consistently to avoid confusion and  posing more challenges to those who 
are implementing the recommendations.

The introductory paragraph contains the statement: "This document 
includes recommendations for assisting authoring tool developers to make 
their authoring tools more accessible to people with disabilities, 
including blindness and low vision, deafness and hearing loss, learning 
disabilities, cognitive limitations, motor difficulties, speech 
difficulties, and others."
This statement aligns with the WCAG 2.0 use of the term "more accessible."

The document then goes on, however, to use the term "accessible" in 
different contexts which may be interpreted in absolute terms and which 
will not be either possible in terms of perfect accessibility for all or 

"The authoring tool is responsible for ensuring that editing-views 
display the web content being edited in a way that is accessible to 
authors with disabilities (e.g. ensuring that text alternatives in the 
content can be programmatically determined)."

The subjective use of the term "accessible" is open to interpretation 
and cannot be measured.

The same holds true for the use of the phrase "not accessible."

"Rationale: If authoring tools automatically specify web content that is 
not accessible, then additional repair tasks are imposed on authors."

It would be clearer to state "web content that is not conforming to WCAG 

Many occurrences of the terms "accessible" and "accessibility" are 
linked to the definition of "accessible Web Content." This would not 
pose a problem if the terminology was consistent.

Below are some examples which are all linked to the same definition:

accessible content (linked to definition: accessible Web Content)
*       web content (linked to definition: accessible Web Content)
*       accessible (linked to definition: accessible Web Content)
*       accessible web content (WCAG) (linked to definition: accessible 
Web Content)
*       accessibility (linked to definition: accessible Web Content)
Terms linked to a common definition should be consistent. The clearest 
of the five terms is "accessible web content (WCAG)" and using this 
would remove ambiguity surrounding the intent of the statements.

One of the objectives of ATAG is the production of WCAG 2.0 conformant 
code and this should be clearly identified.  Where WCAG 2.0 defines the 
desired outcomes for accessibility, it makes sense to align other 
recommendations with WCAG 2.0 in the use of common terminology.

Web Standards Office
Information Technology Division
Chief Information Officer Branch
Treasury Board of Canada Secretariat
Ottawa, Ontario K1A 0R5
Received on Friday, 16 September 2011 15:26:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:01 UTC