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 from Survey #2313

Merged
merged 3 commits into from
Apr 19, 2022
Merged

Updates from Survey #2313

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4c9fefd
Updates from Survey
rachaelbradley Apr 19, 2022
0a6d2f0
survey updates
rachaelbradley Apr 19, 2022
c6aa150
updates from call
rachaelbradley Apr 19, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 25 additions & 9 deletions charter.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,22 +161,24 @@ <h1 id="title"><i class="todo">PROPOSED Accessibility Guidelines</i> Working Gro
<h2>Background</h2>
<section id="background-ag">
<h3>Motivation for Accessibility Guidelines Working Group (AG WG)</h3>
<p>Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. Web accessibility encompasses all disabilities that affect access to the Web, and also benefits people without disabilities. Accessible design improves overall user experience and satisfaction, especially in a variety of situations, across different devices, and for older users. It is essential that several different components of web development and interaction work together in order for the web to be accessible to people with disabilities. These components include content technologies, web content, web browsers and media players, assisitve technology, users, developers, authoring tools, and evaluation tools. Groups in the Web Accessibility Initiative work together to address accessibility for all the components.</p>
<p>Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. Web accessibility encompasses all disabilities that affect access to the Web, and also benefits older users and people without disabilities. Accessible design improves overall user experience and satisfaction, especially in a variety of situations, and across different devices. It is essential that several different components of web development and interaction work together in order for the web to be accessible to people with disabilities. These components include content technologies, web content, web browsers and media players, assisitve technology, users, developers, authoring tools, and evaluation tools. Groups in the Web Accessibility Initiative work together to address accessibility for all the components.</p>
<p>The Accessibility Guidelines Working Group describes the characteristics of accessible web content, in the form of guidance to content developers. It also describes support from other components needed for its advice to work, such as technologies, user agents, and authoring tools. Guidelines from this Working Group are widely used by developers and implementers, referenced in industry policy, and benefit all web users.</p>
</section>
<section id="background-focus">
<h3>Focus for the 2022 - 2024 Charter</h3>
<p>The goal of this 2022 - 2024 AG WG charter will be to put into wide (public) review one or more draft documents that demonstrate all major components of <a href="https://www.w3.org/TR/wcag-3.0/">W3C Accessibility Guidelines (WCAG) 3</a> and how they fit together. During this charter period, the WG will propose an approach for public review that addresses each of the <a href="https://w3c.github.io/silver/requirements/#requirements">WCAG 3 requirements</a> and known challenges. Examples of known challenges include:</p>
<ul>
<li>Rewriting existing guidelines in a reasonable amount of time,</li>
<li>Creating new guidelines for emerging technologies,  and</li>
<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>
</ul>
<p>Any requirement or challenge without a demonstrated solution 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 will work.</p>

<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>have a timeline for delivering WCAG 3, and </li>
<li>will have decided how the remaining parts of WCAG 3 will be delivered (all at once, in phases, or as modules.) </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>
</section>
<section id="scope" class="scope">
Expand All @@ -187,18 +189,19 @@ <h3>WCAG 3 </h3>
<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, and</li>
<li>At least one example of each type/category of testing,
<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>
<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 WCAG 3 will be published as a stand-alone resource, it will be made available either as a note or a working draft 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>
<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 topics such as third-party content, scoring, and accessibility statements are going to be part of WCAG 3, an initial version(s) will be made available for public review before the end of this charter. WCAG 3 may include an initial draft of guidelines for creating and serving third-party content. </p>
<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>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 Down Expand Up @@ -238,7 +241,20 @@ <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 disabilities, including accommodations for blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of these.</p>
<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:
<ul>
<li>indivudals 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 sensorty disorders and combinations of these.</li>
</ul>
</p>
<p class="draft-status"><b>Draft state:</b> Working Draft</p>
<p class="milestone"><b>Expected completion:</b> Q2 2026</p>
<p>
Expand Down