diff --git a/techniques/html/H4.html b/techniques/html/H4.html index bfc7e44b00..69efb1e629 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 07c0079757..56996ef338 100644 --- a/techniques/html/H70.html +++ b/techniques/html/H70.html @@ -21,8 +21,8 @@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.
-In HTML5 the frame element is marked as obsolete.
In HTML5 the frame element is marked as obsolete.
summary attribute is not used or
                is null. The purpose of a layout table is simply to control the placement of content;
-               the table itself is “transparent" to the user. A summary would “break" this
-               transparency by calling attention to the table. A null summary
-                 (summary="") on layout tables is acceptable. See F46 for details.
+               the table itself is “transparent" to the user. A summary would “break" this
+               transparency by calling attention to the table. A null summary
+                 (summary="") on layout tables is acceptable. See F46 for details.
       
    doctype.
                
                 For other resources, see Validating web
+           For other resources, see Validating web
               pages.