Important note: This Wiki page is edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.


Difference between revisions of "WCAG 2 FAQ Notes"

From Education & Outreach
Jump to: navigation, search
(Techniques)
(Proposal for addressing the issue:)
Line 55: Line 55:
 
   <li>Develop a short, succinct paragraph or two with a pointer to the Techniques for details, and put it in:
 
   <li>Develop a short, succinct paragraph or two with a pointer to the Techniques for details, and put it in:
 
       <ul>
 
       <ul>
         <li>A [http://www.w3.org/QA/2012/01/wcag_techniques_learn_more.html W3C QA blog post] with the usual WAI announcements, W3C news blurb, tweet, etc.</li>
+
         <li>A [http://www.w3.org/QA/2012/01/wcag_techniques_learn_more.html W3C QA blog post] with the usual WAI announcements, W3C news blurb, tweet, etc. pointing to it (along with the updated Techniques drafts for review)</li>
 
         <li>WCAG 2.0 FAQ question [http://www.w3.org/WAI/WCAG20/wcag2faq.html#techs Do I have to follow the Techniques to meet WCAG?]</li>
 
         <li>WCAG 2.0 FAQ question [http://www.w3.org/WAI/WCAG20/wcag2faq.html#techs Do I have to follow the Techniques to meet WCAG?]</li>
 
         <li>[http://www.w3.org/WAI/WCAG20/quickref/#about-techs About the Techniques section] of How to Meet WCAG 2.0: A customizable quick reference...</li>
 
         <li>[http://www.w3.org/WAI/WCAG20/quickref/#about-techs About the Techniques section] of How to Meet WCAG 2.0: A customizable quick reference...</li>

Revision as of 22:18, 18 April 2013

This is an internal planning page.
Please see the published WCAG 2 FAQ.

Nav: EOWG wiki main page

Goals, etc.

  • clarify role of techniques, address misunderstandings
  • clarify issues with WCAG 2 ISO
  • focus on current issues, e.g., lower Is WCAG done and comparison to WCAG 1 sections

Note: consider along with update to WCAG Overview

WCAG 2 ISO draft

This is an internal planning page. Please see the published WCAG 2 FAQ. In the FAQ is information about ISO/IEC 40500 and WCAG 2.0.

{Q: [Tell me about] WCAG 2 ISO?}

WCAG 2.0 [is expected to be] approved as an ISO standard: ISO/IEC @@DIS 40500 Information technology -- W3C Web Content Accessibility Guidelines (WCAG) 2.0.

ISO 40500 is exactly the same as Web Content Accessibility Guidelines (WCAG) 2.0 from the W3C Web Accessibility Initiative (WAI), which is available online at http://www.w3.org/TR/WCAG/

For an overview of WCAG and links to supporting resources that provide practical advice for meeting WCAG 2.0, see the WCAG Overview.

{Adoption of} WCAG 2.0 as an ISO standard benefits countries and organizations that are more easily able to {adopt} ISO standards. Countries that previously adapted WCAG 2.0 may now be able to adopt WCAG 2.0 as is through the ISO document.

WCAG 2.0 is available in multiple languages from WCAG 2.0 Translations.

If you want more information on W3C and the ISO process, see W3C PAS FAQ.

Techniques

Issue: Some people wrongly think that:

  • the techniques are the basis for meeting WCAG, instead of the SC
  • you must use the sufficient techniques
  • you can only use the W3C sufficient techniques and not other ways to meet the SC
  • if you fail a test in a technique, you fail WCAG 2

Current coverage of Techniques:

Proposal for addressing the issue:

Draft Content:

Proper use of WCAG 2.0 Techniques and Failures from WCAG WG.


FAQ

Do I have to follow the Techniques to meet WCAG?

No. The Techniques document provides guidance that is "informative". The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard — not the techniques.

You do not have to use the sufficient techniques to meet WCAG. Web content can use other ways to meet the WCAG success criteria. Web content could even fail a particular technique test, yet still meet WCAG a different way. Also, content that uses some of the published techniques does not necessarily meet all WCAG success criteria.

The Techniques are not intended to be required. The only thing that is intended to be required is meeting the success criteria.

To learn more about the techniques, please see:

  • About the Techniques section of How to Meet WCAG 2.0: A customizable quick reference... [@@ is there a reason to point to the QuickRef? or do we only need to point to the Techniques?]
  • Sufficient and Advisory Techniques section of Techniques for WCAG 2.0.
  • [@@ do we only need to point to the Techniques? or is there a reason to also point to Understanding?]
QuickRef Draft:

About the Techniques

[@@ just started this, and will have other edits...]

All of the techniques are informative — you do not have to follow the techniques. The basis for determining conformance to WCAG 2.0 is the success criteria, not the techniques.

You do not have to use the sufficient techniques to meet WCAG. Web content can use other ways to meet the WCAG success criteria. Web content could even fail a particular technique test, yet still meet WCAG a different way. Also, content that uses some of the published techniques does not necessarily meet all WCAG success criteria.

The Techniques are not intended to be required. The only thing that is intended to be required is meeting the success criteria.

Anyone can submit new techniques at any time. If techniques are used other than those listed by the Working Group, then some other method for establishing the technique's ability to meet the success criteria would be needed.

In addition to the 'sufficient techniques', there are also advisory techniques that go beyond WCAG 2.0's requirements. Authors are encouraged to apply all techniques that they are able to, including the advisory techniques, in order to best address the needs of the widest possible range of users.

Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive language and learning areas. Authors are encouraged to seek relevant advice about current best practice to ensure that Web content is accessible, as far as possible, to this community.

See also Sufficient and Advisory Techniques. [@@suggest replacing with latest version link, not dated URI]

archived notes:

Questions: Do you think the right explanation is in those places? Does it need to be explained better? Or, are people just not finding it there?

Clarifying misunderstandings: Maybe we should refine a good explanation and then put it in the FAQ or elsewhere, and then do a promotional campaign just around that one issue - explaining the techniques... or while we're at it, see if there are other WCAG misunderstandings we want to clear up, too... (I'm imagining a short video explaining it, too - but that's wishlist.)

Some wording we drafted then deleted elsewhere: WCAG Techniques give specific guidance for developers on how to develop accessible web content. The techniques are "informative", that is, you do not have to use them. The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard, not the techniques. To learn more about techniques, see About the Techniques.




This is an internal planning page.
Please see the published WCAG 2 FAQ.