Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

updates through jeanne in survey #2348

Merged
merged 6 commits into from May 3, 2022
Merged

updates through jeanne in survey #2348

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ace1a67
updates through jeanne in survey
rachaelbradley May 3, 2022
734d833
typo
rachaelbradley May 3, 2022
5548128
updates from meeting
rachaelbradley May 3, 2022
5dff0af
updates from meeting
rachaelbradley May 3, 2022
476a38a
typo
rachaelbradley May 3, 2022
2339066
updated functional needs link
May 3, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
26 changes: 7 additions & 19 deletions charter.html
View file
Open in desktop
Expand Up @@ -171,12 +171,12 @@ <h3>Focus for the 2022 - 2024 Charter</h3>
<li>Rewriting existing guidelines,</li>
<li>Adding guidance to address known gaps in WCAG 2,</li>
<li>Creating new guidelines for emerging technologies,and</li>
<li>Complex conformance challenges, such as third-party content, website conformance, scoring, accessibility statements, etc.</li>
<li>Complex conformance challenges, such as third-party content, scoring, accessibility statements, etc.</li>
</ul>

<p>Any requirement or challenge without a demonstrated solution that has AG WG consensus by the end of the next charter will be excluded from WCAG 3. These solutions won’t be complete at the end of this charter period, but they will have enough breadth of developed material so that reviewers can understand the intended scope of WCAG 3 as a whole, and have enough depth to understand how conformance evaluations for WCAG 3 can work.</p>
<p>By the end of the 2022 - 2024 charter AG WG will: </p><ul>
<li>Know what will and will not be part of WCAG 3,</li>
<li>Know what will and will not be part of WCAG 3,</li>
<li>have a timeline for delivering WCAG 3, and </li>
<li>have decided how the remaining parts of WCAG 3 will be delivered (all at once, in phases, or as modules.) </li>
</ul> In the case of phases or modules, AG WG will have the scope and requirements of those phases or modules defined for the next charter period. </section>
Expand All @@ -185,23 +185,23 @@ <h3>Focus for the 2022 - 2024 Charter</h3>
<h2>Scope</h2>
<section id="scope-wcag3">
<h3>WCAG 3 </h3>
<p>The primary objective of the AG WG during this charter period is to publish a <a href="https://www.w3.org/2021/Process-20211102/#wide-review">wide review draft</a> of WCAG 3. The goal is to get broad support for the scope and direction of WCAG 3 and work out how the <a href="https://w3c.github.io/silver/requirements/">requirements for WCAG 3</a> can be met, including better coverage across disabilities, and be easier to maintain, so that the new framework will be more durable as technologies evolve. This wide review of WCAG 3 will include the following:</p>
<p>The primary objective of the AG WG during this charter period is to publish one or more <a href="https://www.w3.org/2021/Process-20211102/#wide-review">wide review draft(s)</a> of WCAG 3. The goal is to get broad support for the scope and direction of WCAG 3 and work out how the <a href="https://w3c.github.io/silver/requirements/">requirements for WCAG 3</a> can be met, including better coverage across disabilities, and be easier to maintain, so that the new framework will be more durable as technologies evolve. These wide review(s) of WCAG 3 will include the following:</p>
<ul>
<li>A preliminary set of guidelines (not including outcomes or methods),</li>
<li>A representative set of outcomes worked out in detail, along with all methods and documentation necessary to understand and test those outcomes,</li>
<li>At least one example of each type/category of testing,
</li><li>A conformance model, and</li>
<li>An approach on testing emerging technologies.</li>
</ul>
<p>WCAG 3 will not be brought to Recommendation during this charter period. Results of the wide review will determine scope and timeline for further work in the following charter period. Deliverables and timelines for WCAG 3 are further precised in the <a href="https://github.com/w3c/silver/wiki">WCAG 3 project plan</a>.</p>
<p>WCAG 3 will not be brought to Recommendation during this charter period. Results of the wide review(s) will determine scope and timeline for further work in the following charter period. Deliverables and timelines for WCAG 3 are further precised in the <a href="https://github.com/w3c/silver/wiki">WCAG 3 project plan</a>.</p>
<section id="scope-wcag3-additional">
<h4>Additional WCAG 3 Publications</h4>
<p>AG WG will explore options for publishing WCAG 3 in stages or as modules. If any part of the initial WCAG 3 will be published as a stand-alone resource, a draft will be made available within this charter period. If a transitional document between WCAG 2.2 and WCAG 3 is to be created, a first draft of it will be published by the end of the charter.</p>
</section>
</section>
<section id="scope-wcag3-conformance">
<h4>WCAG 3 Conformance Model</h4>
<p>In this charter period, AG WG will define the scope of the conformance model for WCAG 3. If any part of the initial WCAG 3 recommendation will be published as a stand-alone resource, a draft will be made available within this charter period.</p>
<p>In this charter period, AG WG will define a working conformance model for WCAG 3. If any part of the initial WCAG 3 recommendation will be published as a stand-alone resource, a draft will be made available within this charter period.</p>
<p>While there will be no normative guidance for stand-alone user agents or authoring tools, WCAG 3 may include guidelines for embedded user agents and authoring tools such as an online video player built with JavaScript and HTML, or online blogging service.</p>
</section>
<section id="scope-other">
Expand All @@ -213,7 +213,7 @@ <h3>Non WCAG 3 Scope</h3>
<li>performs secondary research, and engages with primary researchers, to understand better the needs of specific user groups (such as <a href="https://www.w3.org/groups/wg/ag/publications">Accessibility Requirements for People with Low Vision</a>, <a href="https://www.w3.org/groups/wg/ag/publications">Cognitive Accessibility User Research</a>),</li>
<li>conducts gap analyses against deployed features to identify accessibility guidance needs (such as <a href="https://www.w3.org/groups/wg/ag/publications">Cognitive Accessibility Roadmap and Gap Analysis</a>, <a href="https://www.w3.org/groups/wg/ag/publications">Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile</a>),</li>
<li>develops Accessibility Conformance Testing (ACT) Rules Format 1.1, to keep ACT rules compatible with WCAG 3, and enable writing rules that have proven difficult to write under version 1.0,</li>
<li>provides evaluation guidance and test materials to support verfiication of conformance to normative guidance (such as <a href="https://www.w3.org/groups/wg/ag/publications">Accessibility Conformance Testing (ACT) Rules Format 1.0</a>),</li>
<li>provides evaluation guidance and test materials to support verification of conformance to normative guidance (such as <a href="https://www.w3.org/groups/wg/ag/publications">Accessibility Conformance Testing (ACT) Rules Format 1.0</a>),</li>
<li>develops supplemental guidance, beyond that in the normative guidance, that describes enhanced accessibility for certain scenarios (such as <a href="https://www.w3.org/groups/wg/ag/publications">Making Content Usable for People with Cognitive and Learning Disabilities</a>), and</li>
<li>maintains errata for content developed by predecessor groups (such as <a href="https://www.w3.org/TR/ATAG20/">Authoring Tool Accessibility Guidelines 2.0</a>).</li>
</ul>
Expand Down Expand Up @@ -242,19 +242,7 @@ <h3> Normative Specifications </h3>
<a href="#">W3C Accessibility Guidelines (WCAG) 3.0</a>
</dt>
<dd>
<p>This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. It supports a wide set of user needs, uses new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3.0 supports this evolution by focusing on users’ functional needs. Following these guidelines will make content more accessible to people with a wide range of functional needs, including individuals:
</p><ul>
<li>individuals without vision and with partial vision,</li>
<li>without hearing and with partial hearing,</li>
<li>without movement or dexterity and with partial dexterity,</li>
<li>without speech and with partial speech,</li>
<li>with limited attention,</li>
<li>with limited language and literacy,</li>
<li>with limited learning,</li>
<li>with limited memory, </li>
<li>with limited executive functions,</li>
<li>as well as sensory disorders and combinations of these.</li>
</ul>
<p>This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. It supports a wide set of user needs, uses new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3.0 supports this evolution by focusing on users’ functional needs. Following these guidelines will make content more accessible to people with a wide range of <a href="https://w3c.github.io/fast/#functional-needs">functional needs</a>.</p>

<p class="draft-status"><b>Draft state:</b> Working Draft</p>
<p class="milestone"><b>Expected completion:</b> Q2 2026</p>
Expand Down