Skip to content

Commit

Permalink
link xrefs
Browse files Browse the repository at this point in the history
  • Loading branch information
Michael Cooper committed Jul 6, 2023
1 parent ca4c6cb commit 88f6e8d
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions guidelines/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -236,8 +236,9 @@ <h2>Approaches to conformance</h2>
<p>The proposed approaches can fit together in a variety of ways. We will be testing these approaches and others for <a>validity</a>, <a>reliability</a>, <a>sensitivity</a>, <a>adequacy</a>, <a>complexity</a> and <a>equity</a>. We welcome suggestions on ways to improve these approaches to better meet these criteria and concerns about how they might affect accessibility. The working group plans to select from or even replace these options based on feedback, prototyping, and testing. </p>
<p>There are two main approaches to evaluating accessibility that are promising. There are also detailed ideas that support these approaches. The two main approaches are: </p>
<ul>
<li><strong>Outcomes with tests</strong>: Outcomes are verifiable statements that allow testers to reliably determine if the content being evaluated satisfies the user needs identified in the Guideline. Outcomes are addressed in Section 3.3.1. Tests are addressed in Section 3.3.2. </li>
<li><strong>Assertions and procedures:</strong> <em>Assertions</em> are attributable statements by a person or organization that they followed a <em>procedure</em> to improve accessibility. Assertions are addressed in Section 3.4.1. </li>
<li><strong>Outcomes with tests</strong>: Outcomes are verifiable statements that allow testers to reliably determine if the content being evaluated satisfies the user needs identified in the Guideline. Outcomes are addressed in <a href="#outcomes">Section 3.3.1 Outcomes</a>. Tests are addressed in <a href="#testing-outcomes">Section 3.3.2 Testing Outcomes</a>. </li>
<li><strong>Assertions and procedures:</strong>
<em>Assertions</em> are attributable statements by a person or organization that they followed a <em>procedure</em> to improve accessibility. Assertions are addressed in <a href="#assertions">Section 3.4.1 Assertions</a>. </li>
</ul>
<p>There are additional ideas that support these two approaches and can be used or combined in many different ways. </p>
<ul>
Expand Down Expand Up @@ -322,7 +323,7 @@ <h5>Types of tests</h5>

<p>Most tests have prescribed ways to meet the test. In some cases, the ways to meet the test will change based on a specific condition being met (example: the language the content is written in).</p>

<p>Although content may satisfy all outcomes using quantifiable and qualitative tests, the content may not always be usable by people with a wide variety of disabilities. The assertions (see section 4.3 below) are designed to address this problem. </p>
<p>Although content may satisfy all outcomes using quantifiable and qualitative tests, the content may not always be usable by people with a wide variety of disabilities. The assertions (see <a href="#assertions">Section 3.4.1 Assertions</a>) are designed to address this problem. </p>

<section>
<h6>Quantifiable tests</h6>
Expand Down

0 comments on commit 88f6e8d

Please sign in to comment.