From 2c1863f87ee440cf0e87484b49e1ef100c09b21f Mon Sep 17 00:00:00 2001 From: Michael Cooper Date: Mon, 24 Jul 2023 09:41:32 -0400 Subject: [PATCH 1/2] link technique to term --- guidelines/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/index.html b/guidelines/index.html index 85a30e95..bb91ca0a 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -298,7 +298,7 @@

Outcomes and methods

Outcomes

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.

-

Each outcome is associated with at least one method. Methods are informative and kept in how to documents. Each method contains techniques for meeting the outcome, examples, resources, and sets of tests 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.

+

Each outcome is associated with at least one method. Methods are informative and kept in how to documents. Each method contains techniques for meeting the outcome, examples, resources, and sets of tests 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.

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.

From a181d5cd385e17330bd084d25078a7cb154764c6 Mon Sep 17 00:00:00 2001 From: Michael Cooper Date: Mon, 24 Jul 2023 09:42:14 -0400 Subject: [PATCH 2/2] remove unused term --- guidelines/index.html | 2 -- 1 file changed, 2 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index bb91ca0a..f8d08375 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -654,8 +654,6 @@

Glossary

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.

-
Best Practice
-

Methods which are not required and meet a higher requirement than methods required to conform to Bronze.

Complexity

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. Benchmarking Web Accessibility Metrics, Vigo, Lopes, O Connor, Brajnik, Yesilada 2011.