-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #148 from w3c/editorial-updates-nov-24
Fixes during meeting Nov 26
- Loading branch information
Showing
6 changed files
with
27 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| <section id="enabling-funders"> | ||
| <h2>Enabling funders</h2> | ||
| <h3>Enabling funders</h3> | ||
| <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> | ||
| </section> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 4 additions & 3 deletions
7
guidelines/acknowledgements/previous-notable-contributors.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,8 @@ | ||
| <section> | ||
| <h2>Previous notable contributors:</h2> | ||
| <h3>Previous notable contributors:</h3> | ||
| <ul> | ||
| <li>Shawn Lauriat (Editor 2021-2023)</li> | ||
| <li>Wilco Fiers (Project Manager 2021-2023)</li>l | ||
| <li>Michael Cooper, Staff Editor 2021-2023 (W3C)</li> | ||
| <li>Shawn Lauriat, Editor 2021-2023 (Google, Inc.)</li> | ||
| <li>Wilco Fiers, Project Manager 2021-2023 (Deque Systems, Inc.)</li> | ||
| </ul> | ||
| </section> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -16,7 +16,7 @@ | |
| <p>See <a href="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> | ||
| </section> | ||
| <section id="sotd"> | ||
| <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> | ||
| <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> | ||
| <p>To comment, <a href="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 <a href="mailto:[email protected]?subject=WCAG%203.0%20public%20comment">[email protected]</a> (<a href="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). In-progress updates to the guidelines can be viewed in the <a href="https://w3c.github.io/wcag3/guidelines/">public editors’ draft</a>.</p> | ||
| </section> | ||
| <section class="informative"> | ||
|
|
@@ -70,13 +70,13 @@ <h2>Introduction</h2> | |
| <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: | ||
| <ul><li>What requirements are missing from this list to make web content accessible?</li> | ||
| <li>What research supports or refutes the requirements marked as needing additional research?</li> | ||
| <li>Three guidelines (<a href="#clear-meaning">Clear meaning</a>, <a href="#image-alternatives">Image alternatives</a>, and <a href="#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: | ||
| <li>Three guidelines (<a href="#clear-meaning">Clear meaning</a>, <a href="#image-alternatives">Image alternatives</a>, and <a href="#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: | ||
| <ul> | ||
| <li>Grouping related requirements and assertions?</li> | ||
| <li>Using a decision tree for foundational requirements?</li> | ||
| </ul> | ||
| </li> | ||
| <li>The organization of the decision trees in <a href="#clear-meaning">Clear meaning</a> and <a href="#keyboard-focus-appearance">Keyboard Focus Appearance</a> differ slightly. Does one seem clearer than the other?</li> | ||
| <li>The organization of the decision trees in <a href="#clear-meaning">Clear meaning</a> and <a href="#keyboard-focus-appearance">Keyboard focus appearance</a> differ slightly. Does one seem clearer than the other?</li> | ||
| <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> | ||
| </ul></p> | ||
|
|
||
|
|
@@ -145,7 +145,7 @@ <h4>Image alternatives</h4> | |
| </div> | ||
|
|
||
| <details class="decision-tree"> | ||
| <summary>Which foundational provision applies?</summary> | ||
| <summary>Which foundational requirements apply?</summary> | ||
|
|
||
| <p>For each <a>image</a>: | ||
| <ol> | ||
|
|
@@ -155,7 +155,7 @@ <h4>Image alternatives</h4> | |
| </li> | ||
|
|
||
| <li>Is the <a>image</a> presented in a way that is available to user agents and assistive technology? | ||
| <ul><li>Yes, <a>image</a> must meet <a href="#detectable-image">Image is programmatically determinable</a> AND the <a>accessibility support set</a> meets <a href="#content-image">Equivalent text alternative is available for image that conveys content</a>. Stop.</li> | ||
| <ul><li>Yes, <a>image</a> must meet <a href="#detectable-image">Image is programmatically determinable</a> AND the <a>accessibility support set</a> meets <a href="#equivalent-text-alternative">Equivalent text alternative is available for image that conveys content</a>. Stop.</li> | ||
| <li>No, continue.</li></ul> | ||
| </li> | ||
|
|
||
|
|
@@ -349,7 +349,7 @@ <h4>Clear meaning</h4> | |
| <svg aria-hidden="true" class="i-info"><use xlink:href="img/icons.svg#i-info"></use></svg> How to meet Clear Meaning</a></p> | ||
| </aside> | ||
| <details class="decision-tree"> | ||
| <summary>Which foundational provision applies?</summary> | ||
| <summary>Which foundational requirements apply?</summary> | ||
| <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> | ||
| <ol> | ||
| <li>Is the text presented in a way that is available to <a>user agents</a>, including assistive technology (AT)? | ||
|
|
@@ -446,7 +446,7 @@ <h4>Keyboard Focus Appearance</h4> | |
| </div> | ||
|
|
||
| <details class="decision-tree"> | ||
| <summary>Which foundational provision applies?</summary> | ||
| <summary>Which foundational requirements apply?</summary> | ||
| <p>For each focusable item: | ||
| <ol> | ||
|
|
||
|
|
@@ -1561,12 +1561,18 @@ <h2>Glossary</h2> | |
| </dd> | ||
| <dt data-status="developing"><dfn>Task flow</dfn></dt> | ||
| <dd> | ||
| <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> | ||
| <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> | ||
| </dd> | ||
| <dt data-status="developing"><dfn>Test</dfn></dt> | ||
| <dd> | ||
| <p>Mechanism to evaluate implementation of a <a>method</a>.</p> | ||
| </dd> | ||
| <dt><dfn>Text</dfn></dt> | ||
| <dd> | ||
| <div class="ednote"> | ||
| <p>To be defined.</p> | ||
| </div> | ||
| </dd> | ||
| <dt><dfn>User agent</dfn></dt> | ||
| <dd> | ||
| <div class="ednote"> | ||
|
|
@@ -1583,7 +1589,7 @@ <h2>Glossary</h2> | |
| </dd> | ||
| <dt data-status="developing"><dfn>View</dfn></dt> | ||
| <dd> | ||
| <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> | ||
| <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> | ||
| </dd> | ||
| <dt><dfn>Web technologies</dfn></dt> | ||
| <dd> | ||
|
|
@@ -1624,23 +1630,12 @@ <h2>Change log</h2> | |
|
|
||
| </section> | ||
| <section class="appendix"> | ||
| <h2>Acknowledgements</h2> | ||
| <section class="appendix"> | ||
| <h3>Current Contributors</h3> | ||
| <h2>Acknowledgements</h2> | ||
| <p>Additional information about participation in the Accessibility Guidelines Working Group (AG WG) can be found on the <a href="https://www.w3.org/groups/wg/ag/">Working Group home page</a>.</p> | ||
| <div data-include="acknowledgements/current-contributors.html" data-include-replace="true"></div> | ||
| </section> | ||
| <section class="appendix"> | ||
| <h3>Prior Notable Contributors</h3> | ||
| <div data-include="acknowledgements/previous-notable-contributors.html" data-include-replace="true"></div> | ||
| </section> | ||
| <section class="appendix"> | ||
| <h3>Prior Contributors</h3> | ||
| <div data-include="acknowledgements/previous-contributors.html" data-include-replace="true"></div> | ||
| <div data-include="acknowledgements/research-partners.html" data-include-replace="true"></div> | ||
| </section> | ||
| <section> | ||
| <h3>Funders</h3> | ||
| <div data-include="acknowledgements/funders.html" data-include-replace="true"></div> | ||
| </section> | ||
| </body> | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters