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.

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

Suggested wording to address Issue #41 1 #589

Merged
merged 3 commits into from
Feb 1, 2022
Merged
Changes from all commits
Commits
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
7 changes: 4 additions & 3 deletions requirements/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -24,10 +24,11 @@
<section>
<h2 id="intro">Introduction</h2>
<p>People with disabilities can face problems using online content and applications. Disabilities can be permanent, temporary, or recurring limitations. </p>
<p>We need guidelines to: </p>
<p>We need guidance that: </p>
<ul>
<li>identify these barriers encountered by people with disabilities. </li>
<li>explain how to solve the problems they pose. </li>
<li>identifies the barriers encountered by people with disabilities,</li>
<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>
<section>
Expand Down