Skip to content

Working group name #4269

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

Closed
wants to merge 3 commits into from
Closed

Working group name #4269

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
41da97d
Change occurrences of AGWG to AG WG
mbgower Mar 7, 2025
fb80240
Update index.html
mbgower Mar 7, 2025
50321e4
Update index.html
mbgower Mar 7, 2025
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
10 changes: 5 additions & 5 deletions conformance-challenges/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ <h3>Problem Statement</h3>
to have website assessments so they can understand whether the site meets
their accessibility fitness criteria. To aid in this assessment, the
<a href="https://www.w3.org/WAI/GL/"> Accessibility Guidelines Working Group
(AGWG)</a> of the <a href="http://www.w3.org">World Wide Web Consortium
(AG WG)</a> of the <a href="http://www.w3.org">World Wide Web Consortium
(W3C)</a> developed the <a href="https://www.w3.org/TR/WCAG21/">Web Content
Accessibility Guidelines (WCAG</a>), containing
both a rich set of success criteria to meet the needs of people with
Expand Down Expand Up @@ -158,7 +158,7 @@ <h3>Silver Research Findings</h3>

<p>Working
over many years, the Silver Task Force of the Accessibility Guidelines Working
Group (AGWG) and the Silver Community Group collaborated with researchers on
Group (AG WG) and the Silver Community Group collaborated with researchers on
questions that the Silver Groups identified. This research was used to develop
11 problem statements that needed to be solved for Silver. The conformance-related Silver generated Problem Statements are included as originally submitted for this document below in <a href="#Appendix-C">Appendix C</a>.</p>
<aside>
Expand Down Expand Up @@ -415,7 +415,7 @@ <h2>Challenge #5: Accessibility Supported</h2>
<q>This topic raises the question of how many
or which assistive technologies must support a Web technology in order
for that Web technology to be considered <q>accessibility supported.</q> The
WCAG Working group and the W3C do not specify which or how many
AG Working Group and the W3C do not specify which or how many
assistive technologies must support a Web technology in order for it to
be classified as accessibility supported. This is a complex topic and
one that varies both by environment and by language.</q></p>
Expand Down Expand Up @@ -1150,7 +1150,7 @@ <h3>Success Criteria Needing Special Treatment in Non-Accessibility Supported En

<section class="appendix silver" id="Appendix-C">
<h2>Challenges of Conformance as identified from Silver Research</h2>
<p>Now known as <a href="https://www.w3.org/WAI/wcag3">W3C Accessibility Guidelines (WCAG 3.0)</a>, this iteration of W3C accessibility guidance was conceived and designed to be research-based. Working over many years, the Silver Task Force of the Accessibility Guidelines Working Group (AGWG) and the Silver Community Group collaborated with researchers on questions that the Silver Groups identified. This research was used to develop 11 problem statements that needed to be solved for Silver. The detailed problem statements include the specific problem, the result of the problem, the situation and priority, and the opportunity presented by the problem. The problem statements were organized into three main areas: Usability, Conformance, and Maintenance. The section following is taken from the <a href="https://www.w3.org/community/silver/draft-final-report-of-silver/#h.n2wcg0gauz5x">Conformance sections of the Silver Design Sprint Final Report</a> and the <a href="https://www.w3.org/WAI/GL/task-forces/silver/wiki/Problem_Statements#Conformance_Model">Silver Problem Statements</a>. Details of the research questions and the individual reports are in <a href="https://www.w3.org/WAI/GL/task-forces/silver/wiki/Silver_Research_Archive">Research Archive of Silver wiki</a>.</p>
<p>Now known as <a href="https://www.w3.org/WAI/wcag3">W3C Accessibility Guidelines (WCAG 3.0)</a>, this iteration of W3C accessibility guidance was conceived and designed to be research-based. Working over many years, the Silver Task Force of the Accessibility Guidelines Working Group (AG WG) and the Silver Community Group collaborated with researchers on questions that the Silver Groups identified. This research was used to develop 11 problem statements that needed to be solved for Silver. The detailed problem statements include the specific problem, the result of the problem, the situation and priority, and the opportunity presented by the problem. The problem statements were organized into three main areas: Usability, Conformance, and Maintenance. The section following is taken from the <a href="https://www.w3.org/community/silver/draft-final-report-of-silver/#h.n2wcg0gauz5x">Conformance sections of the Silver Design Sprint Final Report</a> and the <a href="https://www.w3.org/WAI/GL/task-forces/silver/wiki/Problem_Statements#Conformance_Model">Silver Problem Statements</a>. Details of the research questions and the individual reports are in <a href="https://www.w3.org/WAI/GL/task-forces/silver/wiki/Silver_Research_Archive">Research Archive of Silver wiki</a>.</p>
<p>The following is shown as originally presented by the Silver task force, Key conclusions have been folded into specific enumerated challenges as appropriate.</p>
<section>
<h3>Silver Research Problem Statements</h3>
Expand Down Expand Up @@ -1211,7 +1211,7 @@ <h4>Themes from Research</h4>
<section id="testing-constraints">
<h4>Constraints on What is Strictly Testable</h4>
<p><strong>Specific problem</strong>: Certain success criteria are quite clear and measurable, like color contrast. Others, far less so. The entire principle of understandable is critical for people with cognitive disabilities, yet success criteria intended to support the principle are not easy to test for or clear on how to measure. As a simple example, there is no clear, recent or consistent definition – within any locale or language – on what <q>lower secondary education level</q> means in regard to web content. Language and text content is also not the only challenge among those with cognitive and learning disabilities. Compounding this, most of the existing criteria in support of understanding are designated as AAA, which relatively few organizations attempt to conform with.</p>
<p><strong>Result of problem</strong>: The requirement for valid and reliable testability for WCAG success criteria presents a structural barrier to including the needs of people with disabilities whose needs are not strictly testable. Guidance that WCAG working group members would like to include cannot be included. The needs of people with disabilities – especially intellectual and cognitive disabilities – are not being met.</p>
<p><strong>Result of problem</strong>: The requirement for valid and reliable testability for WCAG success criteria presents a structural barrier to including the needs of people with disabilities whose needs are not strictly testable. Guidance that AG Working Group members would like to include cannot be included. The needs of people with disabilities – especially intellectual and cognitive disabilities – are not being met.</p>
<p><strong>Situation and Priority</strong>: Of the 70 new success criteria proposed by the Cognitive Accessibility Task Force to support the needs of people with cognitive and intellectual disabilities, only four to six (depending on interpretation) were added to WCAG 2.1 and only one is in level AA. The remainder are in level AAA, which is rarely implemented. This means user needs are not met.</p>
<p><strong>Opportunity</strong>: Multiple research projects and audience feedback have concluded that simpler language is desired and needed for audiences of the guidelines. Clear but flexible criteria with considerations for a wider spectrum of disabilities helps ensure more needs are met.</p>
</section>
Expand Down
4 changes: 2 additions & 2 deletions requirements/22/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ <h2>Introduction</h2>
explains how to make Web content accessible to people with disabilities. Since the release of WCAG 2.0 in December
2008 and the release of WCAG 2.1 in June 2018, these standards have been widely adopted and implemented. As a
result of feedback from implementers, ongoing changes in technologies, and responding to the need for regular
updates in accessibility content standards, the Accessibility Guidelines Working Group (AGWG) is pursuing the
updates in accessibility content standards, the Accessibility Guidelines Working Group (AG WG) is pursuing the
development of WCAG 2.2.</p>
<p>The underlying goal of WCAG 2.2 requirements are the same as for WCAG 2.0 and WCAG 2.1 – to promote accessibility
of Web content. WCAG 2.2 must satisfy additional requirements addressed in this document including:</p>
Expand Down Expand Up @@ -194,7 +194,7 @@ <h3>Example </h3>
</section>
<section>
<h2>Success Criterion Acceptance Criteria</h2>
<p>These requirements are provided as guidance to the WCAG Working Group as it works to define new Success Criteria in WCAG 2.2. The Working Group will use the <a href="https://www.w3.org/WAI/GL/wiki/WCAG_2.2_working_process">WCAG 2.2 working process</a> to prioritize mature proposals review and ensure completeness before acceptance.</p>
<p>These requirements are provided as guidance to the AG Working Group as it works to define new Success Criteria in WCAG 2.2. The Working Group will use the <a href="https://www.w3.org/WAI/GL/wiki/WCAG_2.2_working_process">WCAG 2.2 working process</a> to prioritize mature proposals review and ensure completeness before acceptance.</p>
<section>
<h3>Success Criterion Characteristics</h3>
<p>Success criteria should:</p>
Expand Down