wcag_20_is_finalized.html 19.7 KB

Raw Blame History Permalink

<?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='' />
    <meta name="description" content="WCAG 2.0 was published today as a final Web Standard &quot;W3C Recommendation&quot;. Check out the official announcement, e-mail, press release, testimonials, and a personal reflection on WCAG. Here are some additional perspectives on a few points..." />
    <meta name="revision" content="$Id: wcag_20_is_finalized.html,v 1.53 2011/12/16 03:03:12 gerald 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>A New Era for Web Accessibility: WCAG 2.0 is Finalized - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2008/12/from_iran_with_love.html" title="From Iran, with love" />
   <link rel="next" href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html" title="A personal reflection on the WCAG 2.0 publication" />

   <!--
<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/2008/12/wcag_20_is_finalized.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/248"
    dc:title="A New Era for Web Accessibility: WCAG 2.0 is Finalized"
    dc:identifier="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html"
    dc:subject="Technology"
    dc:description="&lt;p&gt;&lt;a href=&quot;http://www.w3.org/TR/WCAG20/&quot;&gt;WCAG 2.0&lt;/a&gt; was published today as a final Web Standard &quot;W3C Recommendation&quot;. Check out the official &lt;a href=&quot;http://www.w3.org/News/2008#item210&quot;&gt;announcement&lt;/a&gt;, &lt;a href=&quot;http://lists.w3.org/Archives/Public/w3c-wai-ig/2008OctDec/0152.html&quot;&gt;e-mail&lt;/a&gt;, &lt;a href=&quot;http://www.w3.org/2008/12/wcag20-pressrelease.html&quot;&gt;press release&lt;/a&gt;, &lt;a href=&quot;http://www.w3.org/2008/12/wcag20-testimonial&quot;&gt;testimonials&lt;/a&gt;, and &lt;a href=&quot;http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html&quot;&gt;a personal reflection on WCAG&lt;/a&gt;. Here are some additional perspectives on a few points...&lt;/p&gt;"
    dc:creator="Shawn Henry"
    dc:date="2008-12-11T14:49:20+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/2008/12/from_iran_with_love.html">&laquo; From Iran, with love</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html">A personal reflection on the WCAG 2.0 publication &raquo;</a>
                     </p>

                        <h2 class="entry-header">A New Era for Web Accessibility: WCAG 2.0 is Finalized</h2>
                           <div class="entry-body">
                              <p><a href="http://www.w3.org/TR/WCAG20/">WCAG 2.0</a> was published today as a final Web Standard "W3C Recommendation". Check out the official <a href="http://www.w3.org/News/2008#item210">announcement</a>, <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2008OctDec/0152.html">e-mail</a>, <a href="http://www.w3.org/2008/12/wcag20-pressrelease.html">press release</a>, <a href="http://www.w3.org/2008/12/wcag20-testimonial">testimonials</a>, and <a href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html">a personal reflection on WCAG</a>. Here are some additional perspectives on a few points.</p>

<p>WCAG 2.0 is a significant improvement. It's better for website creators, it's better for people with disabilities, and many others, too. WCAG 2.0 met its goals: to apply to more advanced technologies; to be more precisely testable (with automated testing and human evaluation); and to be easier to use and understand.</p>

<p>WCAG 2.0 is designed to be a stable standard that is broadly applicable (including to non-W3C technologies), and to have along with it supporting documents that provide detailed guidance, explanations, and examples. These supporting documents will be updated periodically so we can incorporate new techniques, technologies, and best practices.</p>

<p>This WCAG 2.0 publication also comes with real-world examples of every requirement (success criteria). Gathering this "<a href="http://www.w3.org/WAI/GL/WCAG20/implementation-report/">implementation experience</a>" is now part of the <a href="http://www.w3.org/WAI/intro/w3c-process">W3C Process</a>.</p>

<p>Developers and designers will find WCAG 2.0 more flexible than 1.0. For example, scripting is not forbidden and is even included as techniques to enhance accessibility. And where WCAG 1.0 essentially did not allow flashing or other movement, WCAG 2.0 allows it within defined parameters that won't cause seizures.</p>

<p>WCAG 2.0 also defines better accessibility for people with disabilities (and thus more <a href="http://www.w3.org/WAI/bcase/soc.html#groups">benefits to others</a> as well, including <a href="http://www.w3.org/WAI/intro/wai-age-literature.php">older users</a>). For example, it has new requirements related to informing users of data entry errors. With the <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/intro.html#introduction-layers-techs-head">advisory techniques</a> it offers suggestions such as improving accessibility for people with cognitive/intellectual disabilities.</p>

<p>WAI and the WCAG Working Group actively worked with organizations around the world towards "<a href="http://www.w3.org/WAI/Policy/harmon">harmonization</a>"; that is, one shared international standard for web content accessibility, rather than different ones in different countries. And there are already plans for <a href="http://www.w3.org/2005/02/TranslationPolicy">Authorized Translations</a> of WCAG 2.0 in several languages.</p>

<p>WCAG was developed through the contributions of hundreds of people representing a wide range of interests and experiences. Thanks to careful review and comments from around the world, including from disability organizations, and the dedication of the WCAG Working Group, WCAG 2.0 improved with each Working Draft to become the mature standard published today.</p>

<p>Many individuals and organizations are endorsing WCAG 2.0. Will you add your voice to those supporting WCAG 2.0 and help spread the good news?</p>

<p>Over the next few weeks and months, we'll be providing additional material, such as presentations slides and policy transition support. We look forward to your suggestions for how we can make WCAG 2.0 materials easier to use. You can <a href="http://www.w3.org/WAI/WCAG20/comments/">send your comments to a publicly-archived list</a> or to a <a href="mailto:wai@w3.org">WAI internal-only list</a>; or participate in discussions on the <a href="http://www.w3.org/WAI/IG/#mailinglist">WAI Interest Group e-mail list</a>.</p>

<p>— Shawn Henry for <a href="http://www.w3.org/WAI/">W3C Web Accessibility Initiative (WAI)</a></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 December 11, 2008  2:49 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/mobile/">Mobile</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html#comments">Comments (11)</a>
                                 | <a href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-169885">
<p class="comment-meta" id="c169885">
<span class="comment-meta-author"><strong>Jon Dodd </strong></span>
<span class="comment-meta-date"><a href="#c169885">#</a> 2008-12-11</span>
</p>
<div class="comment-bulk">
<p>Congratulations to all that contributed.</p>

<p>I was teaching a course only today about WCAG 2.0 and it received good feedback as an advancement. </p>

<p>The question was raised about when this would be * the * offical standard - and I was pleased to announce that between the start and the end of the course it had made the leap to the one to officially cite and work towards! Great timing many thanks.</p>

<p>It is good to reassure those that do have an already accessible site that they have nothing to fear and only clarity to gain from using the new guidelines and techniques.</p>

<p>many thanks</p>

<p>Jon</p>

</div>
</div>


<div class="comment" id="comment-169889">
<p class="comment-meta" id="c169889">
<span class="comment-meta-author"><strong>Joshue O Connor </strong></span>
<span class="comment-meta-date"><a href="#c169889">#</a> 2008-12-12</span>
</p>
<div class="comment-bulk">
<p>Many congrats to the WAI team :-)</p>

</div>
</div>


<div class="comment" id="comment-169892">
<p class="comment-meta" id="c169892">
<span class="comment-meta-author"><strong>Shrirang </strong></span>
<span class="comment-meta-date"><a href="#c169892">#</a> 2008-12-12</span>
</p>
<div class="comment-bulk">
<p>Indeed great news.
Surely the flexibility in implementation options for gidelines will encourage designers and developers to be innovative in accessible manner.
thanks</p>

</div>
</div>


<div class="comment" id="comment-169900">
<p class="comment-meta" id="c169900">
<span class="comment-meta-author"><strong>Andrew Hart </strong></span>
<span class="comment-meta-date"><a href="#c169900">#</a> 2008-12-12</span>
</p>
<div class="comment-bulk">
<p>I know the WAI team has received a lot of criticism over the past few years for the significant delays in getting these standards polished off and released.  Let's hope that now these guidelines are available that those in the Web industry will pull behind them, taking the responsibility of getting <em>all</em> their staff familiar with, and working to these standards.</p>

<p>With luck this will put an end to the fragmented approach the industry has taken towards implementing accessibility in recent times, removing confusion (from both developers and clients alike) and building support for a single central standard.</p>

<p>Also, let's not lose sight of why we are all doing this: for those Web users with disabilities who need sites to be more accessible.  Hope these standards help to deliver the benefits that these users so badly need!</p>

</div>
</div>


<div class="comment" id="comment-170454">
<p class="comment-meta" id="c170454">
<span class="comment-meta-author"><strong>Daniel García Angulo </strong></span>
<span class="comment-meta-date"><a href="#c170454">#</a> 2008-12-18</span>
</p>
<div class="comment-bulk">
<p>I would like to express my personal gratitud to all thoes who contributud with their experiences, ideas, and work to this reference. It will make web pages world wide better.</p>

<p>Daniel García Angulo </p>

</div>
</div>


<div class="comment" id="comment-170712">
<p class="comment-meta" id="c170712">
<span class="comment-meta-author"><strong>David Horat </strong></span>
<span class="comment-meta-date"><a href="#c170712">#</a> 2008-12-23</span>
</p>
<div class="comment-bulk">
<p>Although I am currently finishing my Master Thesis on Accessibility and Usability applying WCAG 1.0, I will try to include some info about WCAG 2.0 because it seems far better than 1.0.</p>

<p>Good job!</p>

</div>
</div>


<div class="comment" id="comment-171031">
<p class="comment-meta" id="c171031">
<span class="comment-meta-author"><strong>Abby Van Buren </strong></span>
<span class="comment-meta-date"><a href="#c171031">#</a> 2008-12-31</span>
</p>
<div class="comment-bulk">
<p>I am looking forward to participating in the discussions on the WAI Interest Group e-mail list. Congratulations to all those who participated in the drafting process!</p>

</div>
</div>


<div class="comment" id="comment-171400">
<p class="comment-meta" id="c171400">
<span class="comment-meta-author"><strong>Hira Kumar Maharjan </strong></span>
<span class="comment-meta-date"><a href="#c171400">#</a> 2009-01-05</span>
</p>
<div class="comment-bulk">
<p>I specially thanks to WAI Team that they have done very nice job for disability people. I am from nepal and i have not seen any web site which meets WCAG standard. I would try to convince to my developer that, their framwork should compatible for disabiliy people too. </p>

</div>
</div>


<div class="comment" id="comment-171928">
<p class="comment-meta" id="c171928">
<span class="comment-meta-author"><strong>George Inglis </strong></span>
<span class="comment-meta-date"><a href="#c171928">#</a> 2009-01-14</span>
</p>
<div class="comment-bulk">
<p>The new guidelines are much clearer than version 1.0. It's obvious a lot of thoughtful work has gone into producing them. Congratulations to everyone involved. I feel confident version 2.0 will equip us with what we need to know to liaise with web developers confidently when we have our website redeveloped.</p>

</div>
</div>


<div class="comment" id="comment-173766">
<p class="comment-meta" id="c173766">
<span class="comment-meta-author"><strong>Doyle Burnett </strong></span>
<span class="comment-meta-date"><a href="#c173766">#</a> 2009-03-03</span>
</p>
<div class="comment-bulk">
<p>Hello to WCAG 2.0 members and all of the other folks who made 2.0 a reality.  Many individuals worked long and hard to to finalize a document that will carry web developers further into the future with regard to web site accessibility as they implement WCAG 2.0.  This was not an easy process and I am sorry that I took so long to comment to the larger group.  Nice job!  </p>

</div>
</div>


<div class="comment" id="comment-180819">
<p class="comment-meta" id="c180819">
<span class="comment-meta-author"><strong>Aliane </strong></span>
<span class="comment-meta-date"><a href="#c180819">#</a> 2009-04-12</span>
</p>
<div class="comment-bulk">
<p>Congratulations to the team and good job !!</p>

<p>Aliane</p>

</div>
</div>


  <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="4379" />
<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: 2011/12/16 03:03:12 $</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-2011
      <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>