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

wording placement on techniques for specific technologies

From: Michael Cooper <cooper@w3.org>
Date: Wed, 02 Jul 2014 09:22:50 -0400
Message-ID: <53B407AA.5030902@w3.org>
To: WCAG WG <w3c-wai-gl@w3.org>
Here is a proposal for the remainder of the issue raised in LC-2895 
about disclaiming the role of techniques for technologies. We already 
accepted a paragraph for the disclaimer. This proposal is intended to 
increase the likelihood of people seeing the disclaimer. It has had 
preliminary approval from people present on last week's WCAG 
teleconference, and has been approved by the EOWG. So now I'm running it 
by the entire list to solicit formal approval from the WCAG WG at next 
week's meeting. Michael

For each individual Technique page (e.g., 
<http://www.w3.org/TR/WCAG20-TECHS/ARIA1>), update as follows:

  * Add a new section at the top entitled "Important information about
    Techniques" with content:

    See Understanding Techniques for WCAG Success Criteria
    <http://www.w3.org/TR/UNDERSTANDING-WCAG20/understanding-techniques.html>
    for important information about the usage of these informative
    techniques and how they relate to the normative WCAG 2.0 success
    criteria. The Applicability section explains the scope of the
    technique, and the presence of techniques for a specific technology
    does not imply that the technology can be used in all situations to
    create content that meets WCAG 2.0.

  * Delete the section "Techniques are Informative" from the bottom of
    those pages, since it is made redundant by the above addition at the
    top of the pages.

For each technology-specific page (e.g., 
<http://www.w3.org/TR/WCAG20-TECHS/aria.html>, in the info at the top, 
add the middle paragraph below (wording that WCAG WG & EOWG already 
agreed upon):

    This Web page lists [technology] Techniques from Techniques for WCAG
    2.0: Techniques and Failures for Web Content Accessibility
    Guidelines 2.0. Technology-specific techniques do not replace the
    general techniques: content developers should consider both general
    techniques and technology-specific techniques as they work toward
    conformance.

    Publication of techniques for a specific technology does not imply
    that the technology can be used in all situations to create content
    that meets WCAG 2.0 success criteria and conformance requirements.
    Developers need to be aware of the limitations of specific
    technologies and provide content in a way that is accessible to
    people with disabilities.

    For additional important information about the techniques, see
    Introduction to Techniques for WCAG 2.0. For a list of techniques
    for other technologies, see the Table of Contents.
Received on Wednesday, 2 July 2014 13:22:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:15 UTC