You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>This publication has been funded in part with U.S. Federal funds from the Health and Human Services, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Health and Human Services or the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.</p>
Copy file name to clipboardExpand all lines: guidelines/index.html
+16-21
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@
16
16
<p>See <ahref="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">WCAG 3.0 Introduction</a> for an introduction and links to WCAG technical and educational material.</p>
17
17
</section>
18
18
<sectionid="sotd">
19
-
<p>This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for two Guidelines: Image alternatives and Keyboard Focus Appearance.</p>
19
+
<p>This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for three Guidelines: Clear meaning, Image alternatives, and Keyboard focus appearance.</p>
20
20
<p>To comment, <ahref="https://github.com/w3c/wcag3/issues/new">file an issue in the W3C wcag3 GitHub repository</a>. 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 <ahref="mailto:[email protected]?subject=WCAG%203.0%20public%20comment">[email protected]</a> (<ahref="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). In-progress updates to the guidelines can be viewed in the <ahref="https://w3c.github.io/wcag3/guidelines/">public editors’ draft</a>.</p>
21
21
</section>
22
22
<sectionclass="informative">
@@ -70,13 +70,13 @@ <h2>Introduction</h2>
70
70
<p>The purpose of this update is to demonstrate a potential structure for guidelines and indicate the current direction of the WCAG 3.0 conformance. Please consider the following questions when reviewing this draft:
71
71
<ul><li>What requirements are missing from this list to make web content accessible?</li>
72
72
<li>What research supports or refutes the requirements marked as needing additional research?</li>
73
-
<li>Three guidelines (<ahref="#clear-meaning">Clear meaning</a>, <ahref="#image-alternatives">Image alternatives</a>, and <ahref="#keyboard-focus-appearance">Keyboard Focus Appearance</a>) have moved from exploratory to developing and demonstrate a potential structure. Do the following make the guidelines easier to understand and use:
73
+
<li>Three guidelines (<ahref="#clear-meaning">Clear meaning</a>, <ahref="#image-alternatives">Image alternatives</a>, and <ahref="#keyboard-focus-appearance">Keyboard focus appearance</a>) have moved from exploratory to developing and demonstrate a potential structure. Do the following make the guidelines easier to understand and use:
74
74
<ul>
75
75
<li>Grouping related requirements and assertions?</li>
76
76
<li>Using a decision tree for foundational requirements?</li>
77
77
</ul>
78
78
</li>
79
-
<li>The organization of the decision trees in <ahref="#clear-meaning">Clear meaning</a> and <ahref="#keyboard-focus-appearance">Keyboard Focus Appearance</a> differ slightly. Does one seem clearer than the other?</li>
79
+
<li>The organization of the decision trees in <ahref="#clear-meaning">Clear meaning</a> and <ahref="#keyboard-focus-appearance">Keyboard focus appearance</a> differ slightly. Does one seem clearer than the other?</li>
80
80
<li>The conformance section explains the approach the Accessibilty Guidelines Working Group is considering for WCAG 3.0. While many details still need to be worked out, do you have constructive comments about the proposed approach for WCAG 3.0? </li>
<li>Is the <a>image</a> presented in a way that is available to user agents and assistive technology?
158
-
<ul><li>Yes, <a>image</a> must meet <ahref="#detectable-image">Image is programmatically determinable</a> AND the <a>accessibility support set</a> meets <ahref="#content-image">Equivalent text alternative is available for image that conveys content</a>. Stop.</li>
158
+
<ul><li>Yes, <a>image</a> must meet <ahref="#detectable-image">Image is programmatically determinable</a> AND the <a>accessibility support set</a> meets <ahref="#equivalent-text-alternative">Equivalent text alternative is available for image that conveys content</a>. Stop.</li>
159
159
<li>No, continue.</li></ul>
160
160
</li>
161
161
@@ -349,7 +349,7 @@ <h4>Clear meaning</h4>
349
349
<svgaria-hidden="true" class="i-info"><usexlink:href="img/icons.svg#i-info"></use></svg> How to meet Clear Meaning</a></p>
<p>For each item of ambiguous text, such as <a>non-literal text</a>, abbreviations and acronyms, <a>ambiguous numbers</a>, or text missing letters or diacritics:</p>
354
354
<ol>
355
355
<li>Is the text presented in a way that is available to <a>user agents</a>, including assistive technology (AT)?
<p>Testing scope that includes a series views that support a specified <a>user activity</a>. A task flow may include a subset of <a>items</a> in a <a>view</a> or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.</p>
1564
+
<p>Testing scope that includes a series views that support a specified user activity. A task flow may include a subset of <a>items</a> in a <a>view</a> or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.</p>
1565
1565
</dd>
1566
1566
<dtdata-status="developing"><dfn>Test</dfn></dt>
1567
1567
<dd>
1568
1568
<p>Mechanism to evaluate implementation of a <a>method</a>.</p>
1569
1569
</dd>
1570
+
<dt><dfn>Text</dfn></dt>
1571
+
<dd>
1572
+
<divclass="ednote">
1573
+
<p>To be defined.</p>
1574
+
</div>
1575
+
</dd>
1570
1576
<dt><dfn>User agent</dfn></dt>
1571
1577
<dd>
1572
1578
<divclass="ednote">
@@ -1583,7 +1589,7 @@ <h2>Glossary</h2>
1583
1589
</dd>
1584
1590
<dtdata-status="developing"><dfn>View</dfn></dt>
1585
1591
<dd>
1586
-
<p>Testing scope that includes all <a>content</a> visually and <a>programmatically</a> available without a <a>significant change</a>. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content, such as a modal dialog.</p>
1592
+
<p>Testing scope that includes all <a>content</a> visually and <a>programmatically</a> available without a significant change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content, such as a modal dialog.</p>
1587
1593
</dd>
1588
1594
<dt><dfn>Web technologies</dfn></dt>
1589
1595
<dd>
@@ -1624,23 +1630,12 @@ <h2>Change log</h2>
1624
1630
1625
1631
</section>
1626
1632
<sectionclass="appendix">
1627
-
<h2>Acknowledgements</h2>
1628
-
<sectionclass="appendix">
1629
-
<h3>Current Contributors</h3>
1633
+
<h2>Acknowledgements</h2>
1630
1634
<p>Additional information about participation in the Accessibility Guidelines Working Group (AG WG) can be found on the <ahref="https://www.w3.org/groups/wg/ag/">Working Group home page</a>.</p>
0 commit comments