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: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Thu, 7 Feb 2008 15:59:29 -0800
Message-ID: <824e742c0802071559q8a8f61bqe335857166dcbbb5@mail.gmail.com>
To: "Shawn Henry" <shawn@w3.org>
Cc: public-comments-wcag20@w3.org, "EOWG (E-mail)" <w3c-wai-eo@w3.org>

Dear Shawn,

The word "mechanism" was added specifically to allow pages to either provide
the information on the page or to provide a mechanism for obtaining the
information.   Removing the word Mechanism would not allow the latter or
could lead to argument as to whether the latter was allowed (thus rendering
the SC untestable and contestable).

We also determined that we cannot use the phrase "users can" since
there is no way for an author to determine what a user can do.  And in fact
it is known that there will always be some user with extreme and or multiple
disabilities who will not be able to do it.


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:
>
> Comment 23: Please clarify [SC 3.1.4]
> http://lists.w3.org/Archives/Public/w3c-wai-eo/2007OctDec/0180.html
>
> EOWG Comment:
> 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."
>
> WCAG Reply: 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)
>
> EOWG reply, Jan 2008: Accept, and request that WCAG WG considers further simplifying the wording in related SC. Note that while this is not a substantive issue, it is a significant issue in simplifying WCAG and limiting criticisms that it is unnecessarily complex.
>
> We looked at all the SC with "A mechanism is available" type phrasing and wondered if any could be simplified, for example,
> - Take it out of SC 3.1.4 altogether, so it's: "The expanded form or meaning of abbreviations is available."
> - In 3.3.4 instead of "A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission." more simply and directly: "Users can review, confirm, and correct information..."
>
> Here are the others:
> 1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume which can be set to be a different level from the system volume level.
> 1.4.8 Visual Presentation: For the visual presentation of blocks of text, a mechanism is available to achieve the following: ...
> 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
> 2.4.9 Link Purpose (Link Only): A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.
> 3.1.3 Unusual Words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
> 3.1.4 Abbreviations: A mechanism for identifying the expanded form or meaning of abbreviations is available.
> 3.1.6 Pronunciation: A mechanism is available for identifying specific pronunciation of words where meaning is ambiguous without knowing the pronunciation.
> 3.2.5 Change on Request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
> 3.3.4 Error Prevention (Legal, Financial, Data)...A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
>
Received on Thursday, 7 February 2008 23:59:53 GMT

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