Skip to content

Commit

Permalink
take understanding and techniques index out of respec
Browse files Browse the repository at this point in the history
  • Loading branch information
Michael Cooper committed Sep 4, 2018
1 parent d46b1fe commit e9b8f46
Show file tree
Hide file tree
Showing 2 changed files with 60 additions and 16 deletions.
38 changes: 30 additions & 8 deletions techniques/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,21 +2,43 @@
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="UTF-8"/>

<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"/>

<title>Techniques for WCAG 2.1</title>
<script src="../biblio.js" class="remove"></script>
<script src="respec-config.js" class="remove"></script>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
<link rel="stylesheet" type="text/css" href="../css/sources.css" class="remove"/>
<link rel="stylesheet" type="text/css" href="../css/additional.css" class="remove"/>
<link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/2016/base"/>
<link rel="stylesheet" type="text/css" href="techniques.css"/>
</head>
<body>
<div class="head">
<a href="https://www.w3.org/" class="logo">
<img alt="W3C" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72" height="48"/>
</a>
<h1 id="title" class="title p-name">Techniques for WCAG 2.1</h1>

<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2017-2018

<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>).

<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
rules apply.
</p>
<hr title="Separator for header"/>
</div>
<section id="abstract">
<h2>Abstract</h2>
<p>This <em>Techniques for WCAG 2.1</em> document provides guidance for web content authors and evaluators on meeting <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines (WCAG) 2.1</a> success criteria. It is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.1. For an introduction to WCAG, supporting technical documents, and educational material, see <a href="https://www.w3.org/WAI/intro/wcag">Web Content Accessibility Guidelines (WCAG) Overview</a>.</p>
<p>Techniques are informative—that means they are not required. The basis for determining conformance to WCAG 2.1 is the success criteria from the <a href="https://www.w3.org/TR/WCAG21/">WCAG 2.1 standard</a>—not the techniques. <strong>For important information about techniques, please see the <a href="https://www.w3.org/WAI/WCAG21/Understanding/understanding-techniques.html">Understanding Techniques for WCAG Success Criteria</a> section of Understanding WCAG 2.1.</strong></p>
<p><em>Techniques for WCAG 2.1</em> is not intended to be used as a stand-alone document. Instead, it is expected that content authors will usually use <a href="https://www.w3.org/WAI/WCAG21/quickref/">How to Meet WCAG 2.0: A customizable quick reference</a> to read the WCAG success criteria, and follow links from there to specific topics in Understanding WCAG 2.0 and to specific techniques.</p> </section>
<section id="sotd">
<h2>Status of This Document</h2>
<p>This is the official version of "Understanding WCAG 2.1", and is referenced by <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines 2.1</a>. This resource is maintained as needed to update interpretive guidance and reference techniques to meet the guidelines.</p>
<p>To comment, <a href="https://github.com/w3c/wcag/issues/new">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> WCAG 2.1 GitHub repository</a>. Although the proposed Success Criteria in this document reference issues tracking discussion, the Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to <a href="mailto:public-agwg-comments@w3.org?subject=WCAG%202.1%20public%20comment">public-agwg-comments@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). </p>
</section>
<section id="introduction">
Expand All @@ -36,10 +58,10 @@ <h2>Introduction to Techniques for WCAG 2.1</h2>
<p>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.1 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. </p>
<p><strong>For important information about techniques, please see the <a class="understanding" href="../Understanding/understanding-techniques">Understanding Techniques for WCAG Success Criteria</a> section of Understanding WCAG 2.1.</strong></p>
</section>
<section>
<nav id="toc">
<h2>Techniques</h2>
<div data-include="toc.html" data-include-replace="true"></div>
</section>
</nav>
<div data-include="../acknowledgements.html" data-include-replace="true">
<p>Acknowledgements</p>
</div>
Expand Down
38 changes: 30 additions & 8 deletions understanding/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,20 +2,42 @@
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="UTF-8"/>

<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"/>

<title>Understanding WCAG 2.1</title>
<script src="../biblio.js" class="remove"></script>
<script src="respec-config.js" class="remove"></script>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
<link rel="stylesheet" type="text/css" href="../css/sources.css"/>
<link rel="stylesheet" type="text/css" href="../css/additional.css"/>
<link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/2016/base"/>
<link rel="stylesheet" type="text/css" href="understanding.css"/>
</head>
<body>
<div class="head">
<a href="https://www.w3.org/" class="logo">
<img alt="W3C" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72" height="48"/>
</a>
<h1 id="title" class="title p-name">Understanding WCAG 2.1</h1>

<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2017-2018

<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>).

<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
rules apply.
</p>
<hr title="Separator for header"/>
</div>
<section id="abstract">
<h2>Abstract</h2>
<p>Understanding WCAG 2.1 is a guide to understanding and using <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines (WCAG) 2.1</a> [[WCAG21]]. It is part of a set of documents that support WCAG 2.1. Please note that the contents of this document are informative (they provide guidance), and not normative (they do not set requirements for conforming to WCAG 2.1). See <a href="https://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a> for an introduction to WCAG, supporting technical documents, and educational material.</p>
</section>
<section id="sotd">
<h2>Status of This Document</h2>
<p>This is the official version of "Understanding WCAG 2.1", and is referenced by <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines 2.1</a>. This resource is maintained as needed to update interpretive guidance and reference techniques to meet the guidelines.</p>
<p>To comment, <a href="https://github.com/w3c/wcag/issues/new">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> WCAG GitHub repository</a>. Although the proposed Success Criteria in this document reference issues tracking discussion, the Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to <a href="mailto:public-agwg-comments@w3.org?subject=WCAG%202.1%20public%20comment">public-agwg-comments@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). </p>
</section>
<section class="informative introductory" id="intro">
Expand Down Expand Up @@ -69,10 +91,10 @@ <h3>Techniques for WCAG 2.1</h3>

</section>

<section>
<nav id="toc">
<h2>Understanding Pages</h2>
<div data-include="toc.html" data-include-replace="true"></div>
</section>
</nav>
<div data-include="../acknowledgements.html" data-include-replace="true">
<p>Acknowledgements</p>
</div>
Expand Down

0 comments on commit e9b8f46

Please sign in to comment.