The example uses JavaScript in the "accToggle.js" file to store the initial pre-enhanced version of the web page, created solely from the HTML in the source code, so that it can act as a "conforming alternate version" for any later enhanced versions of the web page; and inserts a toggle link into all enhanced versions of the web page which allows a user to revert the web page back to the stored pre-enhanced "Conforming Alternate Version". Note: The "sayhello.js" file is simply there as an example payload external file, and is to be replaced by any other external scripts which are desired.
-The script in the acctoggle.js file stores the pre-enhanced version - assigning the version the url postfix #accessible. Clicking the "WCAG 2.0 conforming alternate version" link (inserted as the first child of the body element in any enhanced versions) changes the url to include the postfix "#accessible" which then resets the html located in the body element and the head element to pre-enhanced code. The pre-enhanced state can be reached from the link, or directly from a url typed into the browser. In addition, a link is inserted into the pre-enhanced "Conforming Alternate Version" which allows the user to re-enhance the web page (something which can also be done using the web browser's back button).
The script in the acctoggle.js file stores the pre-enhanced version - assigning the version the url postfix #accessible. Clicking the "WCAG 2 conforming alternate version" link (inserted as the first child of the body element in any enhanced versions) changes the url to include the postfix "#accessible" which then resets the html located in the body element and the head element to pre-enhanced code. The pre-enhanced state can be reached from the link, or directly from a url typed into the browser. In addition, a link is inserted into the pre-enhanced "Conforming Alternate Version" which allows the user to re-enhance the web page (something which can also be done using the web browser's back button).
window.onload = function(event) {
@@ -56,7 +56,7 @@ acctoggle.js JavaScript:
var nel = document.createElement("a");
nel.id = "acctoggle";
nel.setAttribute("href", "#accessible");
- nel.innerHTML = "WCAG 2.0 conforming alternate version";
+ nel.innerHTML = "WCAG 2 conforming alternate version";
document.body.insertBefore(nel, document.body.firstChild);
// payload
@@ -122,7 +122,7 @@ Tests
Procedure
- Check enhanced versions of the web page contain a link to the "Conforming Alternate Version".
- - Check that the alternate version is a conforming alternate version of the original page and that it conforms to WCAG 2.0 at the claimed conformance level.
+ - Check that the alternate version is a conforming alternate version of the original page and that it conforms to WCAG 2 at the claimed conformance level.
For Flash movies that automatically start playing sound after loading:
The word "technology" is widely used to cover everything from the stone tools used by early humans to contemporary digital devices such as cell phones. But in WCAG 2.0, the word technology is used in a more restricted way: it means a mechanism for encoding instructions to be rendered, played or executed by user agents, including markup languages, data formats, and programming languages used in producing and delivering Web content.
+The word "technology" is widely used to cover everything from the stone tools used by early humans to contemporary digital devices such as cell phones. But in WCAG 2, the word technology is used in a more restricted way: it means a mechanism for encoding instructions to be rendered, played or executed by user agents, including markup languages, data formats, and programming languages used in producing and delivering Web content.
All technologies that present live audio-only information
The objective of this technique is to provide a transcript or script if the live audio content is following a set script. Because it is prepared in advance, the script can be more accurate and complete than live transcription. However, the script will not be synchronized with the audio as it plays. Live audio should not deviate from the script for this technique.
-With this technique, a link to the transcript or script is provided and should conform to WCAG 2.0 and could either be included at another location on the same web page or at another URI.
+With this technique, a link to the transcript or script is provided and should conform to WCAG 2 and could either be included at another location on the same web page or at another URI.
<link rel="glossary" href="https://www.w3.org/TR/WCAG20/#glossary">
Authors can replace the default link text by providing an /Alt entry
for the Link tag. When the Link tag has an /Alt entry, screen readers ignore the value of any visible text objects in the Link tag and use the /Alt entry value for the link text.
The simplest way to provide context-independent link text that complies - with the WCAG 2.0 success criteria is to create them when authoring + with the WCAG 2 success criteria is to create them when authoring the document, before conversion to PDF. In some cases, it may not be possible to create the links using the original authoring tool. When editing PDF documents with Adobe Acrobat Pro, the best way to create accessible links is to use the Create Link command.
Authors should make sure that the alternate text makes sense in context of the screen text before and after the link.
diff --git a/understanding/20/accessibility-support-documenting.html b/understanding/20/accessibility-support-documenting.html index 8d8f885fe3..b379946f4a 100644 --- a/understanding/20/accessibility-support-documenting.html +++ b/understanding/20/accessibility-support-documenting.html @@ -9,7 +9,7 @@The documentation of accessibility support for uses of a web technology provides - the information needed to determine whether it is possible to satisfy the WCAG 2.0 + the information needed to determine whether it is possible to satisfy the WCAG 2 Success Criteria for a particular environment.
diff --git a/understanding/20/meaningful-sequence.html b/understanding/20/meaningful-sequence.html index 9889507cfe..553f892597 100644 --- a/understanding/20/meaningful-sequence.html +++ b/understanding/20/meaningful-sequence.html @@ -62,7 +62,7 @@The objective of this guideline is to ensure that content that is marked as conforming - to WCAG 2.0 avoids the types of flash that are most likely to cause seizure when viewed + to WCAG 2 avoids the types of flash that are most likely to cause seizure when viewed even for a second or two.
diff --git a/understanding/20/understanding-metadata.html b/understanding/20/understanding-metadata.html index 26224999a1..550d2a5f38 100644 --- a/understanding/20/understanding-metadata.html +++ b/understanding/20/understanding-metadata.html @@ -8,7 +8,7 @@This section discusses metadata techniques that can be employed to satisfy WCAG 2.0 +
This section discusses metadata techniques that can be employed to satisfy WCAG 2 success criteria. For more information about metadata see resources below.
diff --git a/understanding/20/unusual-words.html b/understanding/20/unusual-words.html index d7c4193fbe..5da78703cc 100644 --- a/understanding/20/unusual-words.html +++ b/understanding/20/unusual-words.html @@ -73,8 +73,8 @@