wcag/techniques/about.html at 970cf66dc4329db13784c7159364e529e1599862 · w3c/wcag · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
<!DOCTYPE html>
<html lang="en">

<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <title>About WCAG Techniques | WAI | W3C</title>
    <link rel="stylesheet" href="https://w3.org/WAI/assets/css/style.css">
    <link rel="stylesheet" href="base.css">
</head>

<body dir="ltr">

    <div class="default-grid with-gap leftcol">
        <aside class="box nav-hack sidebar standalone-resource__sidebar ">
            <nav>
                <header class="box-h ">Page Contents</header>
                <div class="box-i">
                    <ul>
                      <li><a href="#aboutwcag">About WCAG</a></li>
                      <li><a href="#introduction">About Techniques</a></li>
                      <li><a href="#important">Important Additional Information</a></li>
                      <li><a href="#changelog">Change Log</a></li>
                      <li><a href="#acknowledgements">Acknowledgements</a></li>
                    </ul>
                </div>
            </nav>
        </aside>

        <main id="main" class="main-content standalone-resource__main">
           <h1>About WCAG Techniques</h1>
              <aside class="box">
                <header class="box-h">Summary</header>
                <div class="box-i">
                  <p><em>Techniques</em> are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet WCAG. Content can satisfy the normative requirements of WCAG success criteria even if it does not use any of the documented techniques. Similarly, common failure examples do fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that does satisfy the normative requirements. To start learning about WCAG, see the <a href="https://www.w3.org/WAI/intro/wcag">WCAG Overview</a>. For important information about techniques, see the <a class="understanding" href="../Understanding/understanding-techniques">Understanding Techniques for WCAG Success Criteria</a> section of Understanding WCAG.</p>
                </div>
              </aside>
          <section id="aboutwcag">
              <h2>About WCAG</h2>
              <p>Web Content Accessibility Guidelines (WCAG) provides requirements for making websites, applications, and other digital content accessible to people with disabilities. For an introduction to WCAG, supporting technical documents, and educational material, see <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">WCAG 2 Overview</a>.</p>

          <p>There are additional resources that help you understand and implement WCAG. These Techniques are one type of resource. Others are explained in the <a href="https://www.w3.org/WAI/standards-guidelines/wcag/docs/">WCAG 2 Documents</a>.</p>
          </section>
          <section id="introduction">
            <h2>About Techniques</h2>
              <p>The techniques provide guidance for web content  authors and evaluators on meeting WCAG success criteria. Techniques are examples of ways to meet WCAG.</p>
              <section id="updated">
              <h3>Updated periodically</h3>
              <p>WCAG 2 itself is a stable document that does not change. The techniques for WCAG are updated periodically to cover more current best practices and changes in technologies and tools.</p>
              </section>
              <section id="not-required">
              <h3>Techniques are not required</h3>
              <p>Techniques are informative—that means they are not required. The basis for determining conformance to WCAG 2 is the success criteria from the WCAG 2 standard—not the techniques.</p>
              <div class="note">
                <p>W3C cautions against requiring W3C's sufficient techniques. The only thing that should be required is meeting the WCAG 2 success criteria. To learn more, see: <a href="https://www.w3.org/WAI/standards-guidelines/wcag/faq/#techsnot">What would be the negative consequences of allowing <em>only</em> W3C's published techniques to be used for conformance to WCAG 2?</a> in the WCAG 2 FAQ</p>
              </div>
          	</section>
              <section id="quickref">
              <h3>WCAG Quick Reference</h3>
              <p><em>Techniques for WCAG 2</em> is not intended to be used as a stand-alone document. Instead, it is expected that content authors will usually use <a href="../quickref/">How to Meet WCAG 2: A customizable quick reference</a> to read the WCAG success criteria, and follow links from there to specific topics in Understanding WCAG 2 and to specific techniques.</p>
              </section>
              <section id="specifictech">
          	<h3>Techniques for specific technologies</h3>
              <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 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>
              </section>
            </section>
            <section id="important">
          	  <h2>Important Additional Information</h2>
              <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.</strong></p>
            </section>
            <section id="changelog">
                <h2>Change Log</h2>
                <p>For a detailed view of recent changes to the informative documents see the <a href="https://github.com/w3c/wcag/commits/">GitHub updates</a>.</p>
            </section>

        	<section id="acknowledgements">
        		<details>
	        		<summary><h2>Acknowledgements</h2></summary>
	        		<div data-include="../acknowledgements/ag-wg-active.html" data-include-replace="true"></div>
	        		<div data-include="../acknowledgements/ag-contributors.html" data-include-replace="true"></div>
	        		<div data-include="../acknowledgements/funders.html" data-include-replace="true"></div>
        		</details>
        	</section>

        </main>
        <a class="button button-backtotop" href="#top"><span><svg focusable="false" aria-hidden="true" class="icon-arrow-up " viewBox="0 0 26 28">
            <path d="M25.172 15.172c0 0.531-0.219 1.031-0.578 1.406l-1.172 1.172c-0.375 0.375-0.891 0.594-1.422 0.594s-1.047-0.219-1.406-0.594l-4.594-4.578v11c0 1.125-0.938 1.828-2 1.828h-2c-1.062 0-2-0.703-2-1.828v-11l-4.594 4.578c-0.359 0.375-0.875 0.594-1.406 0.594s-1.047-0.219-1.406-0.594l-1.172-1.172c-0.375-0.375-0.594-0.875-0.594-1.406s0.219-1.047 0.594-1.422l10.172-10.172c0.359-0.375 0.875-0.578 1.406-0.578s1.047 0.203 1.422 0.578l10.172 10.172c0.359 0.375 0.578 0.891 0.578 1.422z"></path></svg> Back to Top
        </span></a>
    </div>
    <script>
				var translationStrings = {}; /* fix WAI JS */
			</script>
    <script src="https://www.w3.org/WAI/assets/scripts/main.js"></script></body>

</html>