Landmark regions can also be used as targets for "skip links" and by browser extensions to enhanced keyboard navigation.
- This section explains how HTML5 sectioning elements and ARIA landmark roles
+ This section explains how HTML sectioning elements and ARIA landmark roles
are used to make it easy for assistive technology users to understand the meaning of the layout of a page.
-
HTML5 Sectioning Elements
+
HTML Sectioning Elements
- Several HTML5 sectioning elements automatically create ARIA landmark regions.
+ Several HTML sectioning elements automatically create ARIA landmark regions.
So, in order to provide assistive technology users with a logical view of a page,
- it is important to understand the effects of using HTML5 sectioning elements.
- More information on HTML5 element role mapping.
+ it is important to understand the effects of using HTML sectioning elements.
+ [[HTML-ARIA]] contains more information on HTML element role mapping.
-
Default landmark roles for HTML5 sectioning elements
+
Default landmark roles for HTML sectioning elements
-
HTML5 Element
+
HTML Element
Default Landmark Role
@@ -3419,12 +3419,12 @@
Banner
-
HTML5 Techniques
+
HTML Techniques
-
The HTML5 header element defines a banner landmark when its context is the body element.
+
The HTML header element defines a banner landmark when its context is the body element.
- The HTML5 header element is not considered a banner landmark when it is descendant of any of following elements (see HTML Accessibility Mappings [[HTML-AAM]]):
+ The HTML header element is not considered a banner landmark when it is descendant of any of following elements (see HTML Accessibility Mappings [[HTML-AAM]]):
article
aside
@@ -3437,7 +3437,7 @@
HTML5 Techniques
ARIA Techniques
-
If the HTML5 header element technique is not being used, a role="banner" attribute should be used to define a banner landmark.
+
If the HTML header element technique is not being used, a role="banner" attribute should be used to define a banner landmark.
@@ -3463,13 +3463,13 @@
Complementary
-
HTML5 Technique
+
HTML Technique
-
Use the HTML5 aside element to define a complementary landmark.
+
Use the HTML aside element to define a complementary landmark.
ARIA Technique
-
If the HTML5 aside element technique is not being used, use a role="complementary" attribute to define a complementary landmark.
+
If the HTML aside element technique is not being used, use a role="complementary" attribute to define a complementary landmark.
@@ -3498,13 +3498,13 @@
Contentinfo
-
HTML5 Techniques
+
HTML Techniques
-
The HTML5 footer element defines a contentinfo landmark when its context is the body element.
+
The HTML footer element defines a contentinfo landmark when its context is the body element.
- The HTML5 footer element is not considered a contentinfo landmark when it is descendant of any of following elements (see HTML Accessibility Mappings [[HTML-AAM]]):
+ The HTML footer element is not considered a contentinfo landmark when it is descendant of any of following elements (see HTML Accessibility Mappings [[HTML-AAM]]):
article
aside
@@ -3517,7 +3517,7 @@
HTML5 Techniques
ARIA Technique
-
If the HTML5 footer element technique is not being used, a role="contentinfo" attribute should be used to define a contentinfo landmark.
+
If the HTML footer element technique is not being used, a role="contentinfo" attribute should be used to define a contentinfo landmark.
@@ -3556,9 +3556,9 @@
Form
-
HTML5 Techniques
+
HTML Techniques
-
The HTML5 form element defines a form landmark when it has an accessible name (e.g. aria-labelledby, aria-label or title).
+
The HTML form element defines a form landmark when it has an accessible name (e.g. aria-labelledby, aria-label or title).
ARIA Technique
@@ -3589,13 +3589,13 @@
Main
-
HTML5 Technique
+
HTML Technique
-
Use the HTML5 main element to define a main landmark.
+
Use the HTML main element to define a main landmark.
ARIA Technique
-
If the HTML5 main element technique is not being used, use a role="main" attribute to define a main landmark.
+
If the HTML main element technique is not being used, use a role="main" attribute to define a main landmark.
@@ -3617,13 +3617,13 @@
Navigation
-
HTML5 Technique
+
HTML Technique
-
Use the HTML5 nav element to define a navigation landmark.
+
Use the HTML nav element to define a navigation landmark.
ARIA Technique
-
If the HTML5 nav element technique is not being used, use a role="navigation" attribute to define a navigation landmark.
+
If the HTML nav element technique is not being used, use a role="navigation" attribute to define a navigation landmark.
@@ -3648,13 +3648,13 @@
Region
-
HTML5 Technique
+
HTML Technique
-
The HTML5 section element defines a region landmark when it has an accessible name (e.g. aria-labelledby, aria-label or title).
+
The HTML section element defines a region landmark when it has an accessible name (e.g. aria-labelledby, aria-label or title).
ARIA Technique
-
If the HTML5 section element technique is not being used, use a role="region" attribute to define a region landmark.
+
If the HTML section element technique is not being used, use a role="region" attribute to define a region landmark.
@@ -3676,8 +3676,8 @@
Search
-
HTML5 Technique
-
There is no HTML5 element that defines a search landmark.
+
HTML Technique
+
There is no HTML element that defines a search landmark.
ARIA Technique
@@ -5384,7 +5384,7 @@
Keyboard Navigation Between Components (The Tab Sequence)
As explained in section , all interactive UI components need to be reachable via the keyboard. This is best achieved by either including them in the tab sequence or by making them accessible from a component that is in the tab sequence, e.g., as part of a composite component. This section addresses building and managing the tab sequence, and subsequent sections cover making focusable elements that are contained within components keyboard accessible.
- The HTML tabindex and SVG tabindex attributes can be used to add and remove elements from the tab sequence.
+ The [[HTML]] tabindex and [[SVG2]] tabindex attributes can be used to add and remove elements from the tab sequence.
The value of tabindex can also influence the order of the tab sequence, although authors are strongly advised not to use tabindex for that purpose.