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

Def fixes #721

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Def fixes #721

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2c1863f
link technique to term
Jul 24, 2023
a181d5c
remove unused term
Jul 24, 2023
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
4 changes: 1 addition & 3 deletions guidelines/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,7 @@ <h3>Outcomes and methods</h3>
<section>
<h3>Outcomes</h3>
<p>Outcomes are verifiable statements that allow testers to reliably determine if the content being evaluated satisfies the user needs identified in the Guideline. All outcomes and assertions that relate to a Guideline will be listed together to encourage adoption of higher levels of accessibility. </p>
<p>Each outcome is associated with at least one <a>method</a>. Methods are informative and kept in how to documents. Each method contains techniques for meeting the outcome, examples, resources, and <a>sets of tests</a> for evaluating the outcome. Methods can apply to a specific technology, such as HTML, or can be more generic where the advice applies no matter what technology, such as the methods supporting the Clear Language guideline. </p>
<p>Each outcome is associated with at least one <a>method</a>. Methods are informative and kept in how to documents. Each method contains <a>techniques</a> for meeting the outcome, examples, resources, and <a>sets of tests</a> for evaluating the outcome. Methods can apply to a specific technology, such as HTML, or can be more generic where the advice applies no matter what technology, such as the methods supporting the Clear Language guideline. </p>

<p>Outcomes are written so that testers can determine the accessibility of technologies based solely on the outcome, even when methods do not yet exist for those technologies.</p>
</section>
Expand Down Expand Up @@ -654,8 +654,6 @@ <h2>Glossary</h2>
experience. [=Semi-automated evaluation=] allows machines to guide humans
to areas that need inspection. The emerging field of testing conducted via
machine learning is not included in this definition.</p></dd>
<dt><dfn data-lt="Best Practice|Best Practices">Best Practice</dfn></dt>
<dd><p>Methods which are not required and meet a higher requirement than methods required to conform to Bronze. </p></dd>
<dt><dfn data-lt="Complex">Complexity</dfn></dt>
<dd>
<p>Complexity refers to the resources required to accomplish the conformance testing. These could be crawler time, or time for human judgment testing. This would be a useful metric to have to answer the question of how much time WCAG 3 takes to test as compared to WCAG 2. <a href="https://www.w3.org/WAI/RD/wiki/index.php?title=Benchmarking_Web_Accessibility_Metrics">Benchmarking Web Accessibility Metrics</a>, Vigo, Lopes, O Connor, Brajnik, Yesilada 2011. </p>
Expand Down