Skip to content

Commit

Permalink
Editorial fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
@iadawn
iadawn committed Dec 11, 2024
1 parent 40e04d9 commit 1fb3d2a
Show file tree
Hide file tree
Showing 3 changed files with 16 additions and 16 deletions.
24 changes: 12 additions & 12 deletions explainer/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@

<body>
<section id='abstract'>
<p>The Explainer for WCAG 3.0 accompanies the draft of [[[?WCAG3]]]. It provides an overview of the history and goals of WCAG 3. This document also describes the current thinking on the structure of the guidelines and the conformance model. The guidelines, conformance model, and related work are still evolving.</p>
<p>The Explainer for WCAG 3.0 accompanies the draft of [[[?WCAG3]]]. It provides an overview of the history and goals of WCAG 3.0. This document also describes the current thinking on the structure of the guidelines and the conformance model. The guidelines, conformance model, and related work are still evolving.</p>
<p>Information on the current schedule is included below with a link to a more detailed timeline.</p>
<p>See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">WCAG 3 Introduction</a> for more details about this work and links to WCAG technical and educational material.</p>
<p>See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">WCAG 3.0 Introduction</a> for more details about this work and links to WCAG technical and educational material.</p>
</section>
<section id='sotd'>
<p>This is an updated draft of the WCAG 3.0 Explainer. It is informative, not normative, and is not expected to become a W3C Recommendation. It provides background on [[[?WCAG3]]].</p>
Expand Down Expand Up @@ -45,15 +45,15 @@ <h2>Introduction</h2>
<section>
<h2>Goals</h2>
<p>The goal of WCAG is to provide information that can be used to improve the accessibility of products on a
variety of platforms. WCAG 3 will use a model that allows it to:</p>
variety of platforms. WCAG 3.0 will use a model that allows it to:</p>
<ul>
<li>address more disability needs than WCAG 2,</li>
<li>incorporate publishing requirements and emerging technologies such as web XR (augmented, virtual, and mixed reality) and voice input,</li>
<li>facilitate maintenance, so that the new model will be more enduring over time as technologies evolve, and</li>
<li>include additional information about the ways web technologies need to work with <a>authoring tools</a>, <a>user agents</a>, and <a>assistive technologies</a>.</li>
</ul>
<p>Additional goals for WCAG 3.0 are written in <a
href="https://www.w3.org/TR/wcag-3.0-requirements/">Requirements for WCAG 3</a>. These are based on the
href="https://www.w3.org/TR/wcag-3.0-requirements/">Requirements for WCAG 3.0</a>. These are based on the
<a href="https://www.w3.org/WAI/GL/task-forces/silver/wiki/Silver_Research_Archive">Silver research</a>, the
results from the <a href="https://www.w3.org/community/silver/draft-final-report-of-silver/">Silver Design
Sprint</a>, and input from the Accessibility Guidelines Working Group, the Silver Task Force, and the
Expand Down Expand Up @@ -142,7 +142,7 @@ <h2>Current Process for Creating WCAG 3.0</h2>
</ul>

<p>The working group aims to publish two new drafts each year. Each draft will include targeted questions for the
public to consider and respond to in order to advance the working draft. Content will evolve and there may be
public to consider. Responses will help advance the work. Content will evolve and there may be
changes to layout and style that are not yet reflected in all parts of the present release and will be reflected
in future releases.</p>
</section>
Expand Down Expand Up @@ -423,13 +423,13 @@ <h3>Only accessibility-supported ways of using technologies</h3>

<p>The intent is for the responsibility of testing with user-agents to vary depending on the level of conformance.</p>

<p>At the foundational level of conformance assumptions can be made by authors that methods and techniques provided by WCAG 3 work. At higher levels of conformance the author may need to test that a technique works, or check that available user-agents meet the requirement, or a combination of both.</p>
<p>At the foundational level of conformance assumptions can be made by authors that methods and techniques provided by WCAG 3.0 work. At higher levels of conformance the author may need to test that a technique works, or check that available user-agents meet the requirement, or a combination of both.</p>

<p>This approach means the working group will ensure that methods and techniques included do have reasonably wide and international support from user-agents, and there are sufficient techniques to meet each outcome.</p>

<p>The intent is that WCAG 3 will use a content-management-system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information.</p>
<p>The intent is that WCAG 3.0 will use a content-management-system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information.</p>

<p>An "accessibility support set" is used at higher levels of conformance to define which user-agents and assistive technologies you test with. It would be included in a conformance claim, and enables authors to use techniques that are not provided with WCAG 3.</p>
<p>An "accessibility support set" is used at higher levels of conformance to define which user-agents and assistive technologies you test with. It would be included in a conformance claim, and enables authors to use techniques that are not provided with WCAG 3.0.</p>

<p>An exception for long-present bugs in assistive technology is still under discussion.</p>

Expand All @@ -443,7 +443,7 @@ <h3>User-generated content</h3>
<p>User-generated content is content written by the public and customers. WCAG 3.0 may use different advice or steps for user-generated content to improve accessibility than for content created by the publisher. WCAG 3.0 proposes that organizations identify user-generated content and identify the steps taken to encourage accessibility. </p>
</details>
<div class="ednote">
<p>It remains to be determined how to address user-generated content that has accessibility issues; and to define what minimum thresholds might be acceptable. We expect WCAG 3 to provide this guidance within individual guidelines and outcomes and to support testing for conformance. The working group is looking at alternative requirements to apply to user-generated content guideline by guideline, and is seeking feedback on what would serve as reasonable requirements on how to best support accessibility in user-generated content with known (or anticipated) accessibility issues. </p>
<p>It remains to be determined how to address user-generated content that has accessibility issues; and to define what minimum thresholds might be acceptable. We expect WCAG 3.0 to provide this guidance within individual guidelines and outcomes and to support testing for conformance. The working group is looking at alternative requirements to apply to user-generated content guideline by guideline, and is seeking feedback on what would serve as reasonable requirements on how to best support accessibility in user-generated content with known (or anticipated) accessibility issues. </p>
<p>One example would be “alternative text”. The Authoring Tool Accessibility Guidelines (ATAG) has specific guidance for providing a mechanism for alternative text. The <a href="https://www.w3.org/TR/ATAG20/#gl_b23">ATAG 2.0 Guideline B.2.3</a> - “Assist authors with managing alternative content for non-text content” could be adapted to provide specific, guideline-related guidance for user generated alternative text. </p>
<p>The working group intends to more thoroughly address the contents and the location of an accessibility statement in a future draft.</p>
</div>
Expand All @@ -454,8 +454,8 @@ <h3>User-generated content</h3>
<li>uploaded photographs, or</li>
<li>uploaded videos or other multimedia.</li>
</ul>
<p>User-generated content is provided for publication by visitors where the content platform specifically welcomes and encourages it. User-generated content is content that is submitted through a user interface designed specifically for members of the public and customers. Use of the same user interface as an authoring tool for publication of content by agents of the publisher (such as employees, contractors, or authorized volunteers) acting on behalf of the publisher does not make that content user-generated content. The purpose of the user-generated content conformance section is to allow WCAG 3 outcomes and methods to require additional or different steps to improve the accessibility of user-generated content.</p>
<p>An important part of WCAG conformance is the specific guidance that is associated with individual WCAG 3 guidelines and outcomes. Not all WCAG 3 guidelines will have unique outcomes and testing for user-generated content. Unless user-generated content requirements are specified in a particular guideline, that guideline applies as written whether or not the content is user generated. </p>
<p>User-generated content is provided for publication by visitors where the content platform specifically welcomes and encourages it. User-generated content is content that is submitted through a user interface designed specifically for members of the public and customers. Use of the same user interface as an authoring tool for publication of content by agents of the publisher (such as employees, contractors, or authorized volunteers) acting on behalf of the publisher does not make that content user-generated content. The purpose of the user-generated content conformance section is to allow WCAG 3.0 outcomes and methods to require additional or different steps to improve the accessibility of user-generated content.</p>
<p>An important part of WCAG conformance is the specific guidance that is associated with individual WCAG 3.0 guidelines and outcomes. Not all WCAG 3.0 guidelines will have unique outcomes and testing for user-generated content. Unless user-generated content requirements are specified in a particular guideline, that guideline applies as written whether or not the content is user generated. </p>


<p>The web content publisher should identify all locations of user-generated content (such as commentary on hosted content, product descriptions for consumer to consumer for sale listings, and restaurant reviews) and perform standard accessibility evaluation analysis for each. If there are no accessibility issues, the user-generated content is fully conforming.</p>
Expand Down Expand Up @@ -569,7 +569,7 @@ <h2>Glossary</h2>
<p>The reproducibility and consistency of scores i.e. the extent to which they are the same when evaluations of the same resources are carried out in different contexts (different tools, different people, different goals, different time). This would be particularly useful to ensure that similar results are achieved by different testers. It would also be useful to see if different testers would select the same path or off-path decisions. Representative sampling tests also fit in this category.
<a href="https://www.w3.org/WAI/RD/wiki/Benchmarking_Web_Accessibility_Metrics.html">Benchmarking Web Accessibility Metrics</a>, Vigo, Lopes, O Connor, Brajnik, Yesilada 2011. </p>
</dd>
<dt><dfn>Semi-Automated evaluation</dfn></dt>
<dt><dfn>Semi-automated evaluation</dfn></dt>
<dd>
<p>Evaluation conducted using machines to guide humans to areas that need
inspection.</p>
Expand Down
2 changes: 1 addition & 1 deletion guidelines/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1351,7 +1351,7 @@ <h2>Conformance</h2>
<p>We are experimenting with different conformance approaches for WCAG 3.0. Once we have developed enough guidelines, we will test how well each works.</p>
</details>

<p>WCAG 3.0 will use a different conformance model than WCAG 2.2 in order to meet its requirements. Developing and vetting the conformance model is a large portion of the work AG needs to complete over the next few years. Drafts will include maturity models for public review and comment. </p>
<p>WCAG 3.0 will use a different conformance model than WCAG 2.2 in order to meet its requirements. Developing and vetting the conformance model is a large portion of the work AG needs to complete over the next few years.</p>

<p>AG is exploring a model based on Foundational Requirements, Supplemental Requirements, and Assertions.</p>

Expand Down
6 changes: 3 additions & 3 deletions requirements/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ <h3>WCAG 3.0 Scope</h3>
<p>WCAG 3.0 will have a broader scope than WCAG 2.x. The Web Content Accessibility Guidelines (WCAG) are scoped to Web and to Content. WCAG 3.0 is being designed to be able to include: </p>
<ul>
<li><strong>Disability Needs</strong>: An improved measurement and conformance structure that includes guidance for a broad range of disabilities. This includes particular attention to the needs of low vision and cognitive accessibility, whose needs don't tend to fit the true/false statement success criteria of WCAG 2.x.</li>
<li><strong>Emerging Technologies</strong>: Flexibility to include emerging technologies, such as augmented/virtual reality(AR/VR/XR) and voice assistants</li>
<li><strong>Emerging Technologies</strong>: Flexibility to include emerging technologies, such as augmented/virtual reality (AR/VR/XR) and voice assistants</li>
<li><strong>Support for the Technologies that Impact Accessibility</strong>: Advice for all levels of the accessibility technology stack who wish to support the WCAG 3.0 core Guidelines including: <ul>
<li><strong>digital content</strong>, including guidance currently addressed by WCAG 2.x;</li>
<li><strong>authoring tools</strong>, such as content management systems;</li>
Expand Down Expand Up @@ -111,9 +111,9 @@ <h4>Usability</h4>
</section>
<section id="opportunities_conformance">
<h4>Conformance Model</h4>
<p>There are several areas for exploration in how conformance can work. These opportunities may or may not be incorporated. They need to work together, and that interplay will be governed by the design principles</p>
<p>There are several areas for exploration in how conformance can work. These opportunities may or may not be incorporated. They need to work together, and that interplay will be governed by the design principles.</p>
<ul>
<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is best expressed as a true/false statement. Others far less so. There are needs of people with disabilities, especially cognitive and low vision disabilities, that are better captured by a different type of measurement. WCAG 3.0 can include guidance (provisions) that use different means of evaluation beyond just true/false performance or outcome statements, allowing for the inclusion of more accessibility guidance.</li>
<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is best expressed as a true/false statement. Others far less so. There are needs of people with disabilities, especially cognitive and low vision disabilities, that are better captured by a different type of measurement. WCAG 3.0 can include guidance (guidelines) that use different means of evaluation beyond just true/false performance or outcome statements, allowing for the inclusion of more accessibility guidance.</li>
<li><strong>Scope Options</strong>: WCAG 3.0 conformance could include web pages, web sites, page sections, individual components, and conformance based on a set of tasks as defined by the author of the site or application. A task-based assessment would allow flexibility for conformance of complex applications that go beyond component/tag assessment or full-page assessment.</li>
<li><strong>Accessibility Supported</strong>: As the technologies advance, the lines between content, user agents, and assistive technology will continue to shift and blur. Interoperability may be affected by any number of factors outside of the control of the author and publisher of digital content. WCAG 3.0 can include advice to user agents and assistive technology developers. WCAG 3 does not intend to make authors responsible for interoperability problems beyond a reasonable effort.</li>
</ul>
Expand Down

0 comments on commit 1fb3d2a

Please sign in to comment.