Skip to content

Commit

Permalink
Updated from the comments in #44
Browse files Browse the repository at this point in the history
  • Loading branch information
alastc committed Mar 21, 2024
1 parent 3f44414 commit c561429
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions requirements/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -200,12 +200,13 @@ <h2 id="requirements">Requirements</h2>
<p>Previous W3C Accessibility Guidelines described how to make web pages accessible to people with disabilities. These guidelines provided a flexible framework that has kept the guidelines relevant for 10 years. Changing technology and changing needs of people with disabilities has shown areas where they could be improved. The requirements are drawn from the research performed by WCAG 3.0 to improve the guidelines, and the suggestions from the Silver Design Sprint. </p>
<p>The WCAG 3.0 Requirements are high level and will be expanded and refined as Silver members move through the prototyping process.</p>
<section>
<h3>Broad disability support</h3>
<h3>Broader disability support</h3>
<p>The guidance includes requirements that are not available in WCAG 2.x. Some guidance may use true/false verification but other guidance will use other ways of measuring and/or evaluating where appropriate so that more needs of people with disabilities may be included (for example: rubrics, sliding scale, task-completion, user research with people with disabilities, and more). This approach includes particular attention to people whose needs may better be met with a broad testing strategy, such as people with low vision, limited vision, or cognitive and learning disabilities.</p>
</section>
<section>
<h3>Flexible maintenance and extensibility</h3>
<p>The informative documentation uses a process that is easy to update and maintain. The process of developing the guidance includes experts who review the guidelines to check they will work for emerging technologies and interactions.</p>
<p>The informative documentation uses a process that is easy to update and maintain.
The process of developing the guidance includes experts who review the guidelines to check they will work for emerging technologies and interactions.</p>
</section>
<section>
<h3>Multiple ways to display</h3>
Expand All @@ -229,11 +230,11 @@ <h3>Regulatory Environment</h3>
</section>
<section>
<h3>Motivation</h3>
<p>The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility.</p>
<p>The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a conformance model that enables organizations to demonstrate when a greater effort is made to improve accessibility.</p>
</section>
<section>
<h3>Scope</h3>
<p>The guidelines provide guidance for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. Our intent is to provide guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.</p>
<p>WCAG 3 will provide guidance and a conformance model suitable for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. The scope of the associated informative materials will include guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.</p>
</section>
</section>
<section class="appendix" id="changelog">
Expand Down

0 comments on commit c561429

Please sign in to comment.