From 8740a5cc32a714b5baf09376f0b793941ec1502f Mon Sep 17 00:00:00 2001
From: "Patrick H. Lauke" The Accessibility Guidelines Working Group and the W3C do not specify which or how much support by assistive
technologies there must be for a particular use of a web technology in order for it
- to be classified as accessibility supported. (See Level of Assistive Technology Support Needed for "Accessibility Support".)
+ to be classified as accessibility supported. (See Level of Assistive Technology Support Needed for "Accessibility Support".)
Web technologies can be used in ways that are not accessibility supported as long
@@ -100,7 +100,7 @@
One way for authors to locate uses of a technology that are accessibility supported
would be to consult compilations of uses that are documented to be accessibility supported.
- (See Understanding Accessibility-Supported Web Technology Uses.) Authors, companies, technology vendors, or others may document accessibility-supported
+ (See Understanding Accessibility-Supported Web Technology Uses.) Authors, companies, technology vendors, or others may document accessibility-supported
ways of using web content technologies. However, all ways of using technologies in
the documentation would need to meet the definition of accessibility-supported Web
content technologies above.
diff --git a/guidelines/terms/20/conforming-alternate-version.html b/guidelines/terms/20/conforming-alternate-version.html
index dd597a83fe..6f29f26f73 100644
--- a/guidelines/terms/20/conforming-alternate-version.html
+++ b/guidelines/terms/20/conforming-alternate-version.html
@@ -64,6 +64,6 @@
the preferences is accessibility supported.
Refer to Understanding Text Alternatives for more information. +
Refer to Understanding Text Alternatives for more information.