From 47e948f8326aca3f23d80bb569c433efe494b54d 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.
diff --git a/techniques/html/H4.html b/techniques/html/H4.html index 34fb55a12c..2bdc9c1ba3 100644 --- a/techniques/html/H4.html +++ b/techniques/html/H4.html @@ -6,7 +6,7 @@HTML and XHTML
The objective of this technique is to provide a logical tab order when the default tab - order does not suffice. Often, placing the + order does not suffice. Often, placing the interactive elements in an order that follows sequences and relationships within the content is sufficient and this technique is not necessary. It can be very easy to introduce usability bugs when setting the tab order explicitly.
diff --git a/techniques/html/H70.html b/techniques/html/H70.html index ad74d606a4..82767d4bc6 100644 --- a/techniques/html/H70.html +++ b/techniques/html/H70.html @@ -21,7 +21,7 @@This technique is appropriate when framesets are already used to organize the content of the page; other techniques are preferred for pages that are not already using framesets, because many people using assistive technology have trouble with frames . An - advisory technique about using noframes is available in Success Criterion 1.1.1.
+ advisory technique about using noframes is available in Success Criterion 1.1.1.In HTML5 the frame
element is marked as obsolete.
summary
would “break" this
transparency by calling attention to the table. A null summary
- (summary
="") on layout tables is acceptable. See F46 for details.
+ (summary
="") on layout tables is acceptable. See F46 for details.
doctype
.
For other resources, see Validating web
+ For other resources, see Validating web
pages.