| Rule ID |
Role 4 |
| Definition |
article element must only have role semantics of region, article (default), main, document or application. NOTE: Deprecated in favor of HTML 3 a more general rule on role restrictions based on ARIA in HTML specification. |
| Purpose |
- The
article element has role restrictions as part of its definition in the W3C HTML5 Specification.
- The
article element can be primarily be used to identify news paper or magazine articles, a list or nested messages in a comment or discussion list.
- The
article element might also be used to identify static text and image content in a web application using the region or document role.
- The
article element might also be used to identify a section of form controls and widgets in a web application using the region or application role.
|
| Mappings |
-
HTML4 Legacy Techniques
(Recommended)
-
HTML5 and ARIA Techniques
(Recommended)
|
| WCAG Success Criteria |
1.3.1 Info and Relationships (Level A, Primary Success Criterion)
Other Related Success Criterion:
|
| Rule Category |
Styling/Content |
| Scope |
Element |
| Target Resources |
article element
|
| Techniques |
- If the content of the
article element is primarily form controls and/or widgets use role="application" on the article element.
- If the content of the
article element is used as the container for the main content of the page use role="main" on the article element or preferably change the element to a main element.
- If the content of the
article element is used as the container for a message in nested discussion list, comment to a blog, or as a magazine/news story use role="article" on the article element.
- If the content of the
article element is used as a sub-section of another landmark use role="region" with an accessible name to identify the sub-section.
- If the content of the
article element does not meet any of the other techniques do not use the role attribute.
|
| Informational Links |
|