W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > December 2007

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

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Tue, 11 Dec 2007 16:07:56 -0800
Message-ID: <824e742c0712111607l40914567kd6735039cfb2dfc7@mail.gmail.com>
To: "Shawn Henry" <shawn@w3.org>
Cc: public-comments-wcag20@w3.org, "EOWG (E-mail)" <w3c-wai-eo@w3.org>

We have revised SC 3.1.4 to read as follows:

3.1.4 Abbreviations: A mechanism for identifying the expanded form or
meaning of abbreviations is available. (Level AAA)


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 23: Please clarify
> >Source:
> >http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0408.html
> >(Issue ID: 2293)
> >----------------------------
> >Original Comment:
> >----------------------------
> >
> >21. [SC 3.1.4] We debated this but could not agree on a common
> >interpretation. Please clarify.
> >
> >---------------------------------------------
> >Response from Working Group:
> >---------------------------------------------
> >
> >We believe that the definition of mechanism in the glossary and the
> >explanation and examples in Understanding Success Criterion 3.1.4 are
> >sufficient to understand what kinds of mechanisms might satisfy this
> >success criterion. "Mechanism" covers both author-supplied
> >functionality and user-agent or assistive-technology supplied
> >functionality.
> EOWG reply on Comment 23 Please clarify SC 3.1.4:
> EOWG still finds this SC unnecessarily difficult to understand; the definition adds confusion and complication, and does not clarify the SC.
> EOWG strongly suggests simplifying SC 3.1.4 to: "The expanded form or meaning of abbreviations is available." or "The expanded form or meaning of abbreviations is available to users."
> "A mechanism for finding" seems unnecessary -- if it's not findable, it's not *available* to users. Indeed, the sufficient techniques clarify the different ways that abbreviations can be made available to users.
> For background, see http://lists.w3.org/Archives/Public/w3c-wai-eo/2007OctDec/0078.html and http://lists.w3.org/Archives/Public/w3c-wai-eo/2007OctDec/0084.html
> (We have an additional, lower priority suggestion: In Understanding SC 3.1.4, Examples of Success Criterion 3.1.4, move the third example to the top. Rationale: this is the easiest to understand, and easiest for both authors to implement and users to get in many cases.)
Received on Wednesday, 12 December 2007 00:08:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:45 UTC