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

Various updates to requirements doc #732

Merged
merged 9 commits into from
Apr 2, 2024
Merged

Various updates to requirements doc #732

Changes from 3 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
2b9dc29
Various updates to requirements doc
WilcoFiers Feb 13, 2024
6fe5655
Tweaks to the Conformance Model section
WilcoFiers Feb 13, 2024
d3772af
Update requirements/index.html
alastc Feb 13, 2024
564d8fe
Update requirements/index.html
alastc Feb 13, 2024
4d22aee
Update requirements/index.html
alastc Feb 29, 2024
cba6b0f
Update requirements/index.html
alastc Mar 21, 2024
d9294bd
Update requirements/index.html
alastc Mar 21, 2024
4698a4b
Merge branch 'main' into wcag3-req-wilco
alastc Mar 21, 2024
a3fc75d
Update requirements/index.html
alastc Mar 26, 2024
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
11 changes: 5 additions & 6 deletions requirements/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,9 +113,9 @@ <h4>Usability</h4>
<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>
<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 best expressed as a pass/fail 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 multiple means of measurement, in addition to pass/fail statements, allowing inclusion of more accessibility guidance.</li>
alastc marked this conversation as resolved.
Show resolved Hide resolved
<li><strong>Other Scope Options</strong>: In addition to web pages conformance, WCAG 3.0 could include web sites conformance, conformance of page sections and individual components, and conformance based on 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>
alastc marked this conversation as resolved.
Show resolved Hide resolved
<li><strong>Accessibility Supported</strong>: As the technologies advances, the lines between content, user agents, and assistive technology will continue to shift and blur. WCAG 3 will require that authors make a reasonable effort to ensure their content is accessible with the user agents and assistive technologies of their users. WCAG 3.0 can include advice to user agents and assistive technology developers.</li>
alastc marked this conversation as resolved.
Show resolved Hide resolved
</ul>
</section>
<section id="opportunities_maintenance">
Expand Down Expand Up @@ -216,9 +216,8 @@ <h3>Technology Neutral</h3>
</section>
<section>
<h3>Readability</h3>
<p>The core guidelines are understandable by a non-technical audience. Text and presentation are usable and understandable through the use of plain language, structure, and design. They link to instruction videos, illustrations, and how-to where available. Creation of new videos and illustrations are outside the scope of this project at this time.
</p>
</section>
<p>The core guidelines are understandable by a non-technical audience. Where technical guidance is necessary, a plain language alternative of summary will be provided. Text and presentation are usable and understandable through the use of plain language, structure, and design. They link to instruction videos, illustrations, and how-to where available. Creation of new videos and illustrations are outside the scope of this project at this time.</p>
alastc marked this conversation as resolved.
Show resolved Hide resolved
</section>
<section>
<h3>Regulatory Environment</h3>
<p>The Guidelines provide broad support, including</p>
Expand Down
Loading