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

Requirements editorial changes #619

Merged
merged 11 commits into from
Mar 21, 2024
Merged

Requirements editorial changes #619

Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
3e2d7b1
#297 typo
jspellman Mar 31, 2022
6b863d1
#298 plus additional minor rewording
jspellman Mar 31, 2022
2f3dbac
#299
jspellman Mar 31, 2022
2631965
#300 remove "the"
jspellman Mar 31, 2022
9c8913f
#296
jspellman Mar 31, 2022
128fd67
#295 punctuation in lists
jspellman Mar 31, 2022
7a2f1bf
#295
jspellman Mar 31, 2022
1880f99
#293
jspellman Mar 31, 2022
38871a6
#292 - singular guidelines
jspellman Mar 31, 2022
7f06e6c
#290 - abstract plain language
jspellman Mar 31, 2022
5010559
Update requirements/index.html
alastc Feb 20, 2024
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
78 changes: 39 additions & 39 deletions requirements/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,11 @@
</head>
<body>
<section id="abstract">
<p>The Requirements for WCAG 3.0 document is the next phase in the development of the next major upgrade to accessibility guidelines that will be the successor to Web Content Accessibility Guidelines (WCAG) 2 series. The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to incubate the needs, requirements, and structure for the new accessibility guidance. To date, the group has: </p>
<p>The Requirements for W3C Accessibility Guidelines (WCAG) 3.0 documentation is the next phase of development of the next major upgrade to accessibility guidelines. WCAG 3.0 will be the successor to the Web Content Accessibility Guidelines (WCAG) 2 series. The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to incubate the needs, requirements, and structure for the new accessibility guidance. To date, the group has: </p>
<ol>
<li>Researched accessibility guidance needs</li>
<li>Developed problem statements and opportunities to improve accessibility guidance</li>
<li>Received input from industry leaders for directions to proceed</li>
<li>Researched accessibility guidance needs.</li>
<li>Developed problem statements and opportunities to improve accessibility guidance.</li>
<li>Received input from industry leaders for directions to proceed.</li>
<li>Drafted these high-level requirements for the next phase of the project, the prototyping and public input. </li>
</ol>
</section>
Expand All @@ -30,32 +30,32 @@ <h2 id="intro">Introduction</h2>
<li>explains what causes these barriers and who they impact, and</li>
<li>suggests how the problems they pose can be solved.</li>
</ul>
<p>The Web Content Accessibility Guidelines (WCAG) 2.0 were designed to be technology neutral, and has stayed relevant for over 10 years. The Authoring Tool Accessibility Guidelines (ATAG) 2.0 has been implemented in the open source authoring tool communities (chiefly Wordpress and Drupal) with little known uptake in commercial authoring tools. UAAG 2.0 offers useful guidance to user agent developers and has been implemented on an individual success criterion basis. There is no known user agent that has implemented all of UAAG 2.0. </p>
<p>Web Content Accessibility Guidelines (WCAG) 2.0 was designed to be technology neutral, and has stayed relevant for over 10 years. Authoring Tool Accessibility Guidelines (ATAG) 2.0 has been implemented in the open source authoring tool communities (chiefly Wordpress and Drupal) with little known uptake in commercial authoring tools. User Agent Accessibility Guidelines (UAAG) 2.0 offers useful guidance to user agent developers and has been implemented on an individual success criterion basis. There is no known user agent that has implemented all of UAAG 2.0. </p>
<section>
<h3>Comparison to WCAG 2.x Requirements</h3>
<p>WCAG 3.0 builds on the<a href="https://www.w3.org/TR/wcag2-req/"> WCAG 2.0 Requirements of 2006</a>. The WCAG 2.0 requirements are:</p>
<ol>
<li>Ensure that requirements may be applied across technologies</li>
<li>Ensure that the conformance requirements are clear</li>
<li>Design deliverables with ease of use in mind</li>
<li>Write to a more diverse audience</li>
<li>Clearly identify who benefits from accessible content</li>
<li>Ensure that the revision is "backwards and forward compatible"</li>
<li>Ensure that requirements may be applied across technologies.</li>
<li>Ensure that the conformance requirements are clear.</li>
<li>Design deliverables with ease of use in mind.</li>
<li>Write to a more diverse audience.</li>
<li>Clearly identify who benefits from accessible content.</li>
<li>Ensure that the revision is "backwards and forward compatible".</li>
</ol>
<p>WCAG 3.0 wishes to advance the WCAG 2.0 Requirements of:</p>
<ol>
<li>applied across technologies</li>
<li>clear conformance</li>
<li>ease of use</li>
<li>diverse audience</li>
<li>identify who benefits</li>
</ol>
<ul>
<li>applied across technologies,</li>
<li>clear conformance,</li>
<li>ease of use,</li>
<li>diverse audience, and</li>
<li>identify who benefits.</li>
</ul>
<p>WCAG 3.0 does not want to advance the WCAG 2.0 requirement: &quot;Ensure that the revision is 'backwards and forward compatible'&quot; . The intention is to include WCAG 2.x content, but migrate it to a different structure and conformance model. </p>
<p>The <a href="https://w3c.github.io/wcag/wcag21/requirements/">WCAG 2.1 Requirements</a> are very specific to WCAG 2.1 and will <em>not</em> be advanced by WCAG 3.0. WCAG 3.0 plans to migrate the content of WCAG 2.1 to WCAG 3.0, but the WCAG 2.1 Requirements document referred to structural requirements which are specific to WCAG 2.x. </p>
<p>The WCAG 2.1 Requirements are: </p>
<ol>
<li>Define a clear conformance model for WCAG 2.1/dot.x releases</li>
<li>Ensure the conformance structure utilizes the WCAG 2.0 A / AA / AAA model </li>
<li>Define a clear conformance model for WCAG 2.1/dot.x releases.</li>
<li>Ensure the conformance structure utilizes the WCAG 2.0 A / AA / AAA model. </li>
</ol>
</section>
<section>
Expand All @@ -65,12 +65,12 @@ <h3>WCAG 3.0 Scope</h3>
<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>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>
<li><strong>user agents</strong>, such as browsers and media players</li>
<li><strong>assistive technologies</strong>, such as screen readers, screen magnifiers, and assistants for memory, organization, or simplification</li>
<li><strong>software and web applications</strong>, including mobile apps</li>
<li><strong>operating systems</strong> and other platforms who may want advice for features to better support people with disabilities</li>
<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>
<li><strong>user agents</strong>, such as browsers and media players;</li>
<li><strong>assistive technologies</strong>, such as screen readers, screen magnifiers, and assistants for memory, organization, or simplification;</li>
<li><strong>software and web applications</strong>, including mobile apps; and</li>
<li><strong>operating systems</strong> and other platforms who may want advice for features to better support people with disabilities.</li>
</ul>
</li>
</ul>
Expand All @@ -80,7 +80,7 @@ <h3>WCAG 3.0 Scope</h3>
<h3>Silver Task Force Research</h3>
<p class="ednote">Introductory text about the research efforts undertaken, with pointers to methodology and results</p>
<p>The research done in 2017-2018 by the Silver Task Force, the Silver Community Group, and the <a href="https://rawgit.com/w3c/silver/master/prototypes/ConformancePrototype/index.html#research-partners">research partners</a> was used to identify the key problem statements related to the current accessibility guidelines (WCAG 2.x, ATAG 2.0 and UAAG 2.0). See the <a href="https://docs.google.com/presentation/d/1POs7orJ4ALB0bq5_vyo4v8RxDcr-5ctwD1noVgpXuJc/edit#slide=id.gc6f73a04f_0_0">Silver Research Summary slides</a> for more detailed information. These problem statements were used to identify the opportunities for WCAG 3.0 to address that will improve accessibility guidance. </p>
<p>During the year of WCAG 3.0 research, a recurring theme was the popularity and quality of the guidance in WCAG 2.0. Most of the opportunities identified in the research were improvements in the structure and presentation accessibility guidance to improve usability, to support more disability needs, and to improve maintenance. </p>
<p>A recurring theme identified in the year of WCAG 3.0 research was the popularity and quality of the WCAG 2.0 guidance. Most of the opportunities identified in the research were improvements in the structure and presentation of accessibility guidance to improve usability, support more disability needs, and improve maintenance. </p>
</section>
<section>
<h3>Large and Dynamic Sites</h3>
Expand All @@ -98,10 +98,10 @@ <h3 id="problem_statements">Opportunities for WCAG 3.0 </h3>
<h4>Usability</h4>
<ul>
<li><strong>Readable</strong>: When guidelines are easier to read and understand, users – especially people in the development cycle who are less technical – are more likely to implement accessibility. When all audiences are considered in the language and terminology used in the guidelines, the likelihood increases that they will: <ul>
<li>reach a larger audience</li>
<li>be better understood</li>
<li>be easier to translate</li>
<li>be interpreted as easier to implement</li>
<li>reach a larger audience,</li>
<li>be better understood,</li>
<li>be easier to translate, and</li>
<li>be interpreted as easier to implement.</li>
</ul>
</li>
<li><strong>On-ramp for Beginners</strong>: When beginning users can develop understanding and mastery of the accessibility guidance, this leads to faster and greater acceptance of accessibility. This also creates the opportunity to convince developers and project managers to include accessibility at the beginning of a project instead of the end. </li>
Expand All @@ -111,11 +111,11 @@ <h4>Usability</h4>
</section>
<section id="oppotunities_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. Then 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 quite clear and measurable. Others, far less so. There are needs of people with disabilities, especially cognitive and low vision disabilities that are not well served by guidance that can only be measured by pass/fail statement. Multiple means of measurement, in addition to pass/fail statements, allow inclusion of more accessibility guidance.</li>
<li><strong>Task-Based Assessment</strong>: Moving away from strictly web pages and web sites as a collection of web pages, WCAG 3.0 could set the scope of conformance as a comprehensive set of tasks as defined by the author of the site or application. A properly marked up button doesn't help anything if the user can't complete the task at hand. Task-based assessment allows flexibility for conformance of complex applications that are not conducive to component/tag assessment or full-page assessment.</li>
<li><strong>Accessibility Supported</strong>: As the technologies evolve, the interoperability of content, user agents, and assistive technology will continue to 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. Authors are not responsible for interoperability problems beyond a reasonable effort.</li>
<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is quite clear and measurable. Others, far less so. Some needs of people with disabilities, especially cognitive and low vision disabilities, are not well served by guidance that can only be measured by a true/false statement. If we allow multiple means of measurement, in addition to true/false statements, then we may include new accessibility guidance that benefits groups that may have been underserved in the past.</li>
<li><strong>Task-Based Assessment</strong>: Moving away from strictly web pages and web sites as a collection of web pages, WCAG 3.0 could set the scope of conformance as a comprehensive set of tasks defined by the author of the site or application. A properly marked up button doesn't help anybody if the user can't complete the task at hand. Task-based assessment allows flexibility for the conformance of complex applications that are not conducive to component/tag assessment or full-page assessment.</li>
<li><strong>Accessibility Supported</strong>: As technologies evolve, the interoperability of content, user agents, and assistive technology will continue to 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. Authors are not responsible for interoperability problems beyond a reasonable effort.</li>
</ul>
</section>
<section id="oppotunities_maintenance">
Expand Down Expand Up @@ -198,7 +198,7 @@ <h3>Scope</h3>
<h2>Change Log</h2>
<section>
<h3 id="changes-before-the-first-public-working-draft">Changes Prior to First Public Working Draft</h3>
<ul>
<ol>
<li>Moved the Opportunity for Evolving Technologies to Maintenance; added new opportunity for Flexibility in the Conformance section; and minor grammar corrections. (9 July 2018) </li>
<li>Added headings to individual requirements (25 June 2018)</li>
<li>Added section on Comparison to WCAG 2.x (25 June 2018)</li>
Expand All @@ -214,16 +214,16 @@ <h3 id="changes-before-the-first-public-working-draft">Changes Prior to First Pu
<li>Clarify the broader definition of "disabilities" based on input from public comments and group discussion. The definition sentence in the Introduction paragraph is a proposal for group discussion. </li>
<li>Change "future" to "unanticipated" in Requirements #2 and add subsequent sentence. </li>
<li>Change the Requirements Intro paragraph to remove the specific sentence on conformance and pass/fail tests and give greater context on the source of the Requirements. </li>
</ul>
</ol>
<h3 id="changes-before-the-second-requirements-draft">Changes Prior to Second Version of Requirements</h3>
<ul>
<ol>
<li>New requirements for Readability, Regulatory Environment, Motivation, and Scope. </li>
<li>Added paragraph explaining the differences between Design Principles and Requirements as a result of requests from the AGWG face-to-face meeting of 11 and 12 March 2019. </li>
<li>Added new Design Principles and Requirements and changed wording of existing Design Principles and Requirements based on feedback from AGWG in Q1 and Q2 2019 </li>
<li>Added a new Scope section to the Introduction that clarifies that WCAG 3.0 plans to address Authoring Tools, User agents and Apps. (26 April 2019)</li>
<li>Reworded Technology Neutral to bring it more in line with the original WCAG 2.0 Requirements wording. (26 April 2019)</li>
<li>changed Design Principle 9 to more clearly show that there will not be a hierarchy of disabilities and that when there is no research, how we will address that. </li>
</ul>
</ol>
</section>
</section>
<section class="appendix">
Expand Down