- The following are common mistakes that are considered failures of this Success Criterion by the WCAG Working Group. + The following are common mistakes that are considered failures of this Success Criterion by the Accessibility Guidelines Working Group.
diff --git a/_includes/understanding/intro/techniques.html b/_includes/understanding/intro/techniques.html index 4fbe2a572b..b6f45703b9 100644 --- a/_includes/understanding/intro/techniques.html +++ b/_includes/understanding/intro/techniques.html @@ -1,6 +1,6 @@Each numbered item in this section represents a technique or combination of techniques - that the WCAG Working Group deems sufficient for meeting this Success Criterion. + that the Accessibility Guidelines Working Group deems sufficient for meeting this Success Criterion. A technique may go beyond the minimum requirement of the criterion. There may be other ways of meeting the criterion not covered by these techniques. For information on using other techniques, see Understanding Techniques for WCAG Success Criteria, diff --git a/understanding/20/reading-level.html b/understanding/20/reading-level.html index 26c90be58c..225c19906c 100644 --- a/understanding/20/reading-level.html +++ b/understanding/20/reading-level.html @@ -137,7 +137,7 @@
According to the Open Society Mental Health Initiative, the concept of Easy to Read cannot be universal, and it will not be possible to write a text that will suit the abilities of all people with literacy and comprehension problems. Using the clearest - and simplest language appropriate is highly desirable, but the WCAG Working Group + and simplest language appropriate is highly desirable, but the Accessibility Guidelines Working Group could not find a way to test whether this had been achieved. The use of reading level is a way to introduce testability into a Success Criterion that encourages clear writing. Supplementary content can be a powerful technique for people with some classes of diff --git a/understanding/20/unusual-words.html b/understanding/20/unusual-words.html index e2cb48fe00..e1a07ad269 100644 --- a/understanding/20/unusual-words.html +++ b/understanding/20/unusual-words.html @@ -89,7 +89,7 @@
The inclusion of a product or vendor name in the list below does not constitute an - endorsement by the Web Content Accessibility Guidelines Working Group or the Web Accessibility + endorsement by the Accessibility Guidelines Working Group or the Web Accessibility Initiative of the World Wide Web Consortium. This list is provided simply for convenience and to give users an idea of what resources may be available
diff --git a/understanding/conformance.html b/understanding/conformance.html index 8559cb484a..a936bc80d6 100644 --- a/understanding/conformance.html +++ b/understanding/conformance.html @@ -642,7 +642,7 @@Each numbered item in this section represents a technique or combination of techniques - that the WCAG Working Group deems sufficient for meeting this success criterion. However, it is + that the Accessibility Guidelines Working Group deems sufficient for meeting this success criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see , particularly the "Other Techniques" section. diff --git a/understanding/understanding-techniques.html b/understanding/understanding-techniques.html index c4b3322563..620e56559b 100644 --- a/understanding/understanding-techniques.html +++ b/understanding/understanding-techniques.html @@ -100,7 +100,7 @@
The WCAG Working Group encourages people to submit new techniques so that they can be considered for inclusion in updates of the Techniques for WCAG {{ versionDecimal }} document. Please submit techniques for consideration to the WCAG repository on GitHub.
+The Accessibility Guidelines Working Group encourages people to submit new techniques so that they can be considered for inclusion in updates of the Techniques for WCAG {{ versionDecimal }} document. Please submit techniques for consideration to the WCAG repository on GitHub.