wcag_techniques_learn_more.html 13 KB
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <style type="text/css" media="all">
    @import "/QA/2006/01/blogstyle.css";
    </style>
    <meta name="keywords" content='accessibility, Techniques, WCAG' />
    <meta name="description" content="Today W3C WAI published updated Techniques for WCAG 2.0 and Understanding WCAG 2.0... We encourage you to learn more about the stable WCAG 2.0 standard and the &quot;informative&quot; Techniques..." />
    <meta name="revision" content="$Id: wcag_techniques_learn_more.html,v 1.4 2012/01/16 04:06:09 mirror Exp $" />    
   <link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
   <link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />   
   <title>WCAG Techniques Updated - Learn about the informative guidance - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/12/w3c_tag_publishes_finding_on_i.html" title="W3C TAG Publishes Finding on Identifying Application State" />
   <link rel="next" href="http://www.w3.org/QA/2012/01/social_business_final_report_p.html" title="Social Business: Final Report Published with Next Steps for the W3C" />

   <!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
         xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
    rdf:about="http://www.w3.org/QA/2012/01/wcag_techniques_learn_more.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/457"
    dc:title="WCAG Techniques Updated - Learn about the informative guidance"
    dc:identifier="http://www.w3.org/QA/2012/01/wcag_techniques_learn_more.html"
    dc:subject=""
    dc:description="Today W3C WAI published updated Techniques for WCAG 2.0 and Understanding WCAG 2.0... We encourage you to learn more about the stable WCAG 2.0 standard and the &quot;informative&quot; Techniques..."
    dc:creator="Shawn Henry"
    dc:date="2012-01-03T19:22:55+00:00" />
</rdf:RDF>
-->

    <!-- <script type="text/javascript" src="http://www.w3.org/QA/mt.js"></script>-->

</head>
<body class="layout-one-column">
      <div id="banner">
      <h1 id="title">
	<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog
</h1>
    </div>
    
    <ul class="navbar" id="menu">
        <li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
        <li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
        <li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
        <li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
    </ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>


    <div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->

                     <p class="content-nav">
                        <a href="http://www.w3.org/QA/2011/12/w3c_tag_publishes_finding_on_i.html">&laquo; W3C TAG Publishes Finding on Identifying Application State</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2012/01/social_business_final_report_p.html">Social Business: Final Report Published with Next Steps for the W3C &raquo;</a>
                     </p>

                        <h2 class="entry-header">WCAG Techniques Updated - Learn about the informative guidance</h2>
                           <div class="entry-body">
                                       <p>Today W3C WAI published updated <a href="http://www.w3.org/TR/WCAG20-TECHS/">Techniques for WCAG 2.0</a> and <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/">Understanding WCAG 2.0</a>, following a <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2011AprJun/0041.html">public review period</a>. For background on the stable WCAG standard and this updated supporting material, read the <a href="http://www.w3.org/QA/2010/10/new_and_improved_wcag_20_techn.html">October 2010 blog post</a>.</p>
         <p><strong><a name="abouttech" id="abouttech"></a>About the  Techniques</strong></p>
         <p>First, understand that the basis for determining conformance to WCAG 2.0 is the <strong>success criteria</strong> from the <a href="http://www.w3.org/TR/WCAG20/">WCAG 2.0 standard</a> &mdash; not the techniques. The Techniques document provides guidance that is &quot;informative&quot;. You do not <strong>have</strong> 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, <strong>content that uses the published techniques does not necessarily meet all WCAG success criteria.</strong></p>
         <p>To learn more about the techniques, please see:</p>
         <ul>
            <li><a href="http://www.w3.org/WAI/WCAG20/quickref/#about-techs">About the Techniques section</a> of How to Meet WCAG 2.0: 
               A customizable quick reference...</li>
            <li><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/intro.html#introduction-layers-techs-head">Sufficient and Advisory Techniques section</a> of Understanding WCAG 2.0</li>
         </ul>
         <p><strong>About this Update</strong></p>
         <p>The updated documents published today include more coverage of non-W3C technologies (Flash, PDF, Silverlight), which will help developers who are using those technologies make their content more accessible. However, <strong>publication of techniques for a specific technology does not imply that the technology can be used in all cases to create  accessible content that meets WCAG 2.0.</strong> (For example, the <a href="http://www.w3.org/TR/WCAG20-TECHS/flash.html">Flash Techniques for WCAG 2.0</a> say: &quot;Flash accessibility support for assistive technology relies on use in Windows operating systems, using Internet Explorer 6 or later (with Flash Player 6 or later) or Mozilla Firefox 3 or later (with Flash Player 9 or later).&quot;) <strong>Developers need to be aware of the limitations of specific technologies  and ensure that they create content in a way that is accessible to all their potential users.</strong></p>
         <p>Changes in this update are highlighted in diff-marked versions at: <a href="http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/">Techniques for WCAG 2.0 (Diff)</a>, <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/">Understanding WCAG (Diff)</a>.</p>
         <p>(Note: The first links above go to the latest version of the documents. The &quot;dated&quot; versions of this update are: <a href="http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/">Techniques for WCAG 2.0 (dated URI)</a>, <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/">Understanding WCAG (dated URI)</a> The difference between these links are explained in <a href="http://www.w3.org/WAI/intro/linking.html">Referencing and Linking to WAI Guidelines and Technical Documents</a>.)</p>
         <p><strong>Help Develop Techniques</strong></p>
         <p class="listintro">Updating and expanding these WCAG supporting documents is on-going work, and we welcome your contributions.</p>
         <ul class="listafterpul">
            <li>You can send in your ideas for new techniques via the <a href="http://www.w3.org/WAI/GL/WCAG20/TECHS-SUBMIT/">Techniques for WCAG 2.0 submission form</a>.</li>
            <li>You can comment on what's already there  via the web form or e-mail listed in the <a href="http://www.w3.org/WAI/WCAG20/comments/"> Instructions for Commenting on WCAG 2.0 Documents</a>.</li>
            <li>You can actively <a href="http://www.w3.org/WAI/GL/participation.html">participate in the WCAG   Working Group</a>, writing and reviewing new techniques.</li>
         </ul>
         <p>And finally, a big thanks to the WCAG Working Group and everyone who is contributing to providing updated WCAG 2.0 Techniques!</p>

                           </div>
                           <div id="more" class="entry-more">
                              
                           </div>
                       <p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on January  3, 2012  7:22 PM in <br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2012/01/wcag_techniques_learn_more.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2012/01/wcag_techniques_learn_more.html#comments">Comments (0)</a>
                                 | <a href="http://www.w3.org/QA/2012/01/wcag_techniques_learn_more.html#trackback">TrackBacks (0)</a>
</p>





  <div class="comments-open" id="comments-open">
<h3 class="comments-open-header">Leave a comment</h3>

<div class="comments-open-moderated">
   <p>
   Note: this blog is intended to foster <strong>polite
   on-topic discussions</strong>. Comments failing these
   requirements and spam will not get published. Please,
   enter your real name and email address. Every
   individual comment is reviewed by the W3C staff.
   This may take some time, thank you for your patience.
   </p>
   <p>
   You can use the following HTML markup (a href, b, i, 
   br/, p, strong, em, ul, ol, li, blockquote, pre) 
   and/or <a href="http://daringfireball.net/projects/markdown/syntax">Markdown syntax</a>.</p>
</div>

<div id="comments-open-data">
<form method="post" action="http://www.w3.org/QA/sununga/beach.pl" id="comments-form">
<h4>Your comment</h4>
<div id="comments-open-text">
  <textarea id="comment-text" name="text" rows="20" cols="100"></textarea><br />
<label for="comment-text">Write your comment text here. Remember, keep the discussion on topic and courteous.</label>
</div>

<h4>About you</h4>
<div id="comment-form-name">
  <input type="hidden" name="static" value="1" />
<input type="hidden" name="entry_id" value="9307" />
<input type="hidden" name="__lang" value="en" /> 
<label for="comment-author">Your Name</label>
<input id="comment-author" name="author" size="30" value="" />
</div>
<div id="comment-form-email">
<label for="comment-email">Your Email Address</label>
<input id="comment-email" name="email" size="30" value="" />
</div>

<div id="comments-open-footer">
<input type="submit" accesskey="s" name="post" id="comment-submit" value="Submit" />

</div>
</form>
</div>
</div>



<p id="gentime">This page was last generated on $Date: 2012/01/16 04:06:09 $</p> 

      </div><!-- End of "main" DIV. -->

<address>

This blog is written by W3C staff and working group participants,<br />
&nbsp;and maintained by <a href="/People/CMercier/">Coralie Mercier</a>.<br />
Authorized parties may <a href="/QA/new">log in</a> to create a new entry.<br/>
<span id="poweredby">Powered by Movable Type, magpierss and a lot of Web Technology</span>
    </address>


    
    <p class="copyright">
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 1994-2012
      <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>&reg;
      (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
      <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
      <a href="http://www.keio.ac.jp/">Keio</a>),
      All Rights Reserved.
      W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
      <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
      and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
      rules apply. Your interactions with this site are in accordance
      with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
      <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
      statements.
    </p>

  </body>
</html>