This specification defines the authoring rules (author conformance requirements) for the use of [[[wai-aria-1.2]]] and [[[dpub-aria-1.0]]] attributes on [[HTML]] elements. This specification's primary objective is to define requirements for use with conformance checking tools used by authors (i.e., web developers). These requirements will aid authors in their development of web content, including custom interfaces and widgets, which make use of ARIA to complement or extend the features of the host language [[HTML]].
ARIA in HTML is an [[HTML]] specification module. Any HTML features, conformance requirements, or terms that this specification module makes reference to, but does not explicitly define, are defined by the [[HTML|HTML Standard]].
Since this specification become a W3C Recommendation on 09 December 2021, the following substantive additions and/or corrections have been proposed:
Reviewers of the document can identify candidate additions and/or corrections by their distinctive styling in the document:
Candidate corrections are marked in the document.
Candidate additions are marked in the document.
Authors MAY use the ARIA `role` and `aria-*` attributes to change the exposed meaning (semantics) of [=HTML elements=], in accordance with the requirements defined by [[wai-aria-1.2|WAI-ARIA]], except where ARIA features conflict with thestrong native semantics or are equal to theimplicit ARIA semantics of a given HTML element. Theimplicit ARIA semantics for the features of HTML are defined by the [[html-aam-1.0|HTML Accessibility API Mappings]] specification.
Any constraints for the use of ARIA features in HTML defined by this specification are intended to prevent authors from making assistive technology products report nonsensical user interface (UI) information that does not represent the actual UI of the document.
Authors MUST NOT use the ARIA `role` and `aria-*` attributes in a manner that conflicts with the semantics described in the [[[#docconformance]]] and [[[#docconformance-attr]]] tables. It is NOT RECOMMENDED for authors to set the ARIA `role` and `aria-*` attributes to values that match theimplicit ARIA semantics defined in either table. Doing so is unnecessary and can potentially lead to unintended consequences.
Through the use of ARIA, authors can specify semantics that go beyond the current capabilities of native HTML. This can be very useful, as it provides authors the opportunity to create widgets, or expose specific accessible states and properties to native HTML features which would not be possible by the use of HTML alone.
For instance, a `button` element has no native HTML feature to expose a "pressed" state. ARIA allows authors to extend the semantics of the element by specifying the `aria-pressed` attribute, allowing for an aural UI that will match the visual presentation of the control.
In the following example, a `button` element allows for a user to toggle the state of a setting within a web application. The `aria-pressed` attribute is used to augment the `button` element. When in the "pressed" state that information can be exposed to users of assistive technologies.
<button aria-pressed=true>...</button>
There are also situations where certain `aria-*` attributes are allowed for use on elements with specific `role`s, while the equivalent native attribute is currently not valid in HTML itself.
For instance, HTML has no direct concept of a disabled hyperlink (`a href` element). Constructs such as `<a href="..." disabled> ... </a>` are not valid, and will not be conveyed to assistive technologies.
ARIA diverges from HTML in this regard and does allow for an `aria-disabled` attribute to be specified on an element with an explicit `role=link`. If an author were to specify an `aria-disabled=true` on an HTML hyperlink, user agents would not functionally treat the hyperlink any differently (it would still be clickable/operable), however it would be exposed to assistive technologies as being in the disabled state.
Similarly, while native HTML `option` elements that are descendants of a `select` can only be set as being `selected`, elements with an explicit `option` role can not only allow the equivalent `aria-selected`, but also the `aria-checked` attribute, supporting widgets/constructs that go beyond the capabilities of a native `select` element.
Unfortunately, in these situations where ARIA and HTML have feature parity, but diverge in allowances, it can create for a misalignment in support, if not also user experiences. In situations where ARIA allows a feature not supported by HTML, it will often be in the author's and ultimately the user's best interest to instead implement as a fully custom ARIA widget.
In the following example, a hyperlink needs to be communicated as being in the disabled state. HTML does not allow for the use of the `disabled` attribute on a hyperlink, and using `aria-disabled=true` would communicate the hyperlink as being disabled to assistive technologies, but would not actually disable the element. The most effective way to both communicate and actually disable a hyperlink would be to remove the `href` from the [^a^] element, creating a placeholder. Then, ARIA can be applied to this placeholder link to communicate the element's intended role and state.
<a role=link aria-disabled=true>...</a>
ARIA is useful for revising or correcting the role of an element when a different role is necessary to expose to users. However, it is rarely in the user or author's best interest to try and use ARIA to override an interactive element, for instance a `button`, with a role generally exposed by a non-interactive element. For instance, a heading.
As an example, the following uses a `role=heading` on a [^button^] element. This is not allowed, because the `button` element has default functionality that conflicts with user expectations for the heading role.
<button role="heading">search</button>
An author would need to take additional steps to ensure the default functionality and presentation of the `button` was removed, and even doing so may still not be enough to fully supress the element's implicit features depending on how the user chooses to engage with the web page. E.g., by turning on Windows high contrast themes, or viewing the web page in a browser's reader mode.
The following example illustrates a [^button^] element which has also been provided an explicit `role=button`. Specifying this role is unnecessary, as a "button" element is already exposed with an implicit `button` role. In practice this particular instance of redundancy will likely not have unforeseen side effects, other than unnecessarily making the markup more verbose, and incorrectly signaling to other authors that this practice is useful. Please review the section [[[#side-effects]]] for an example of where specifying unnecessary roles can be problematic.
<!-- Avoid doing this! --> <button role="button">...</button>
Similarly, the following uses a `role=group` on a [^fieldset^] element, and a `role=Main` on a [^main^] element. This is unnecessary, because the `fieldset` element is implicitly exposed as a `role=group`, as is the `main` element implicitly exposed as a `role=main`. Again, in practice this will likely not have any unforeseen side effects to users of assistive technology, as long as the declaration of the `role` value uses [=ASCII lowercase=]. Please see [[[#case-sensitivity]]] for more information.
<!-- Avoid doing this! --> <fieldset role="group">...</fieldset> <!-- or this! --> <main role="Main">...</main>
The following uses a `role=list` on an [^ul^] element. As the `ul` element has an implicit role of `list`, explicitly adding the role would generally be considered redundant. However, some user agents suppress a list's implicit ARIA semantics if the list markers are removed from the visual presentation of the list items. Generally the redundant declaration of an element's implicit role would not be recommended, but in specific situations such as this, and where the role is necessary to expose, authors can explicitly add the role.
<!-- Generally avoid doing this! --> <ul role="list">...</ul>
The following uses a `role=button` on a [^summary^] element. This is unnecessary and can result in cross-platform issues. For instance, preventing the element from correctly exposing its state, and forcing the role of `button`, when it might otherwise be exposed with a platform or browser specific role.
<details> <!-- Avoid doing this! --> <summary role="button">more information</summary> ... </details>
[[[wai-aria-1.2]]] defines a number of roles which are not meant to be used by authors. Many of these roles are categorized asAbstract Roles which are explicitly stated as not to be used by authors. The following example illustrates the invalid use of an abstract `select` role, where an author likely meant to use the `combobox` role instead.
<!-- Do not do this! --> <div role="select" ...>...</div>
ARIA also defines a`generic` role which is meant to provide feature parity with a number of HTML elements that do not have more specific ARIA semantics of their own. For instance, HTML's [^div^] and [^span^] elements, among others. ARIA discourages authors from using the `generic` role as its intended purpose is for use by implementors of user agents.
In the following example, rather than using a `generic` role, authors are advised to use a `div` in place of the `article` element. If changing the HTML element is not possible, specifying a role of `presentation` or `none` would be acceptable alternaties to remove the implicit role of the `article`.
<!-- Avoid doing this! --> <article role="generic" ...>...</article>
Additionally, ARIA specifically mentions inConflicts with Host Language Semantics that if authors use both native HTML features for exposing states and properties as well as their ARIA counterparts, then the host language features take priority over the explicit ARIA attributes that are also used.
For instance, in the following example an author is using HTML's `input type=checkbox` and has specified an `aria-checked=true`. However, user agents are meant to ignore the `aria-checked` attribute. Instead user agents would expose the state based on the native features of the form control.
<!-- Do not do this! --> <input type="checkbox" checked aria-checked="false">
While ARIA can be used to alter the way HTML features are exposed to users of assistive technologies, these modifications do not change the underlying parsing and allowed content models of HTML. For instance, a [^div^] allows an author to specify any role on it. However, this does not mean that the element can then be used in a way that deviates from the rules HTML has defined for the element.
For instance, in the following example an author has specified a role of `link` on a `div` element. While HTML allows for a hyperlink (exposed as a `role=link`) to be a descendant of a `p` element, the HTML parser does not allow a `div` to be a descendant of a `p` element.
<!-- Do not do this! --> <p> ... <div role=link tabindex=0>...</div> ... </p>
The HTML parser will modify the above markup to be output as the following:
<!-- The previous example's markup will render as follows --> <p>...</p> <div role=link tabindex=0>...</div> ... <p></p> <!-- Instead of a div, use a span. Spans are allowed descendants of p elements! --> <p> ... <span role=link tabindex=0>...</span> ... </p>
While this specification indicates the allowed ARIA attributes that can be specified on each HTML element, this example illustrates that even if a role is allowed, the context in which it is used can still result in potential rendering and accessibility issues.
The following table provides normative per-element document conformance requirements for the use of ARIA markup in HTML documents. Additionally, it identifies theimplicit ARIA semantics that apply to [=HTML elements=]. Theimplicit ARIA semantics of these elements are defined in [[html-aam-1.0|HTML AAM]].
Each language feature (element) in a cell in the first column implies the ARIA semantics (role, states, and properties) given in the cell in the second column of the same row. The third cell in each row defines the ARIA `role` values and `aria-*` attributes which authors MAY specify on the element. Where a cell in the third column includes the termAny `role` it indicates that any `role` valueMAY be used on the element. However, it is NOT RECOMMENDED for authors to specify the implicit role of the element, the `generic` role, or a roledeprecated by ARIA on these elements. If a cell in the third column includes the termNo `role` it indicates that authors MUST NOT overwrite the implicit ARIA semantics, or native semantics of the HTML element.
[[wai-aria-1.2|WAI-ARIA]] identifies roles which haveprohibited states and properties. These roles do not allow certain WAI-ARIA attributes to be specified by authors. HTML elements which expose these implicit WAI-ARIA roles also prohibit authors from specifying these WAI-ARIA attributes.
Elements which are identified asNaming prohibited are those which authors MUST NOT specify an `aria-label` or `aria-labelledby` attribute, unless the element allows for its implicit role to be overwritten by an explicit WAI-ARIA role which allows naming from authors. For more information see [[[#docconformance-naming]]].
While setting an ARIA `role` and/or `aria-*` attribute that matches theimplicit ARIA semantics is NOT RECOMMENDED, in some situations explicitly setting these attributes can be helpful – for instance, for user agents that do not expose implicit ARIA semantics for certain elements.
While it is conforming to use [[[dpub-aria-1.0]]] `role` values as outlined in the following table, the use of these roles is not intended for implementation of websites. If using these role for purposes beyond the scope of the digital publishing industry, further manual testing will be necessary to ensure the intended experience is provided to users.
| HTML element | Implicit ARIA semantics(explicitly assigning these in markup is NOT RECOMMENDED) | ARIA role, state and property allowances |
|---|---|---|
| [^a^] with [^a/href^] | role=link | Roles:`button`,`checkbox`,`menuitem`,`menuitemcheckbox`,`menuitemradio`,`option`,`radio`,`switch`,`tab` or`treeitem`. ( DPub Roles:`doc-backlink`,`doc-biblioref`,`doc-glossref` or`doc-noteref` Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. It is NOT RECOMMENDED to use `aria-disabled="true"` on an `a` element with an `href` attribute. If a link needs to be programmatically communicated as "disabled",remove the `href` attribute. |
| [^a^] without [^a/href^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^abbr^] | No corresponding role | Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^address^] | role=group | Any `role`, though`group` is NOT RECOMMENDED. Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^area^] with [^area/href^] | role=link | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the`link` role. |
| [^area^] without [^area/href^] | role=generic | Roles:`button` or`link`. ( Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^article^] | role=article | Roles:`application`,`document`,`feed`,`main`,`none`,`presentation` or`region`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^aside^] | role=complementary | Roles:`feed`,`none`,`note`,`presentation`,`region` or`search`. ( DPub Roles:`doc-dedication`,`doc-example`,`doc-footnote`,`doc-glossary`,`doc-pullquote` or`doc-tip` Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^audio^] | No corresponding role | Role:`application` Global `aria-*` attributes and any `aria-*` attributes applicable to the`application` role. |
| autonomous custom element | Role exposed from author defined {{ElementInternals}} Otherwise | If role defined by `ElementInternals`,no `role` Otherwise,any `role`, though Naming Prohibited if exposed as the `generic` role, or if exposed as another role which prohibits naming. Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^b^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^base^] | No corresponding role | No `role` or `aria-*` attributes |
| [^bdi^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^bdo^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^blockquote^] | role=`blockquote` | Any `role`, though Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^body^] | role=generic | No `role` other than Otherwise,global `aria-*` attributes allowed for the `generic` role, with the exception that authors MUST NOT specify `aria-hidden=true` on the `body` element. |
| [^br^] | No corresponding role | Roles:`none` or`presentation` Authors MAY specify the`aria-hidden` attribute on the `br` element. Otherwise, no other allowed `aria-*` attributes. |
| [^button^] |
If the `button` is the first child of a `select` element, the element is `inert`. | Roles:`checkbox`,`combobox`,`gridcell`,`link`,`menuitem`,`menuitemcheckbox`,`menuitemradio`,`option`,`radio`,`separator`,`slider`,`switch`,`tab`, or`treeitem`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. If the `button` is the first child of a `select` element:No `role` or `aria-*` attributes |
| [^canvas^] | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^caption^] | role=`caption` | No `role` other than Otherwise,global `aria-*` attributes. |
| [^cite^] | No corresponding role | Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^code^] | role=`code` | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^col^] | No corresponding role | No `role` or `aria-*` attributes |
| [^colgroup^] | No corresponding role | No `role` or `aria-*` attributes |
| [^data^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^datalist^] | role=listbox | |
| [^dd^] | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the `definition` role. |
| [^del^] | role=`deletion` | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^details^] | role=group | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `group` role. |
| [^dfn^] | role=term | Any `role`, though Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^dialog^] | role=dialog | Role:`alertdialog`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the `dialog` role. |
| [^div^] | role=generic | If a direct child of a [^dl^] element, only`presentation` or`none`. Otherwise,any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^dl^] | No corresponding role | Roles:`group`,`list`,`none` or`presentation` Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^dt^] | No corresponding role | Role:`listitem` Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^em^] | role=`emphasis` | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^embed^] | No corresponding role | Roles:`application`,`document`,`img`,`image`,`none` or`presentation`. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^fieldset^] | role=group | Roles:`none`,`presentation` or`radiogroup`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^figcaption^] | No corresponding role | Roles:`group`,`none` or`presentation` Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^figure^] | role=figure | If the `figure` has a valid `figcaption` descendant: DPub Role:`doc-example`. Otherwise, if the `figure` has no `figcaption` descendant: Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^footer^] | If not a descendant of an `article`, `aside`, `main`, `nav` or `section` element, or an element with `role=article`, `complementary`, `main`, `navigation` or `region` then Otherwise, | Roles:`group`,`presentation` or`none`. (If not a descendant of an `article`, `aside`, `main`, `nav` or `section` element, or an element with `role=article`, `complementary`, `main`, `navigation` or `region`, then DPub Role:`doc-footnote` Naming Prohibited if exposed as `generic`. Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^form^] |
| Roles:`none`,`presentation` or`search`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. A `form` is not exposed as a landmark region unless it has been provided anaccessible name. |
| form-associated custom element | Role exposed from author defined {{ElementInternals}} Otherwise | If role defined by `ElementInternals`,no `role` Otherwise, form-related roles:`button`,`checkbox`,`combobox`,`listbox`,`progressbar`,`group`,`radio`,`radiogroup`,`searchbox`,`slider`,`spinbutton`,`switch` or`textbox`. ( Naming Prohibited if exposed as the `generic` role. Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| `h1 to h6` | role=heading, `aria-level` = the number in the element's tag name | Roles:`none`,`presentation` or`tab`. ( DPub Role:`doc-subtitle` Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^head^] | No corresponding role | No `role` or `aria-*` attributes |
| [^header^] | If not a descendant of an `article`, `aside`, `main`, `nav` or `section` element, or an element with `role=article`, `complementary`, `main`, `navigation` or `region` then Otherwise, | Roles:`group`,`none` or`presentation`. (If not a descendant of an `article`, `aside`, `main`, `nav` or `section` element, or an element with `role=article`, `complementary`, `main`, `navigation` or `region`, then Naming Prohibited if exposed as `generic`. Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^hgroup^] | role=group | Any `role`, though`group` is NOT RECOMMENDED. Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^hr^] | role=separator | Roles:`none` or`presentation`. ( DPub Role:`doc-pagebreak` Global `aria-*` attributes and any `aria-*` attributes applicable to the `separator` role. |
| [^html^] | role=generic | No `role` other than No `aria-*` attributes. |
| [^i^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^iframe^] | No corresponding role | Roles:`application`,`document`,`img`,`image`,`none` or`presentation`. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
[^img^] | If the `img` has non-empty [^img/alt^] (`alt="some text"`) or an accessible name is provided by another`img` naming method, or the `img` has no `alt` and has not been provided a name:role=img or image | Roles:`button`,`checkbox`,`link`,`math`,`menuitem`,`menuitemcheckbox`,`menuitemradio`,`meter`,`option`,`progressbar`,`radio`,`scrollbar`,`separator`,`slider`,`switch`,`tab` or`treeitem`. ( DPub Role:`doc-cover` Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^img^] with no accessible name | If the `img` has an empty `alt` ([^img/alt^]`=""`) and lacks any other`img` naming methods: If the `img`lacks an `alt` attribute and lacks any other`img` naming methods: | If the `img` has no `alt` attribute or accessible name:No `role` other than the If the `img` has an empty `alt=""` attribute and no `aria-label` or `aria-labelledby` attributes to provide it an accessible name:No `role` other than the No `aria-*` attributes except`aria-hidden="true"`. Otherwise, if the `img` has an author defined accessible name, see`img` with an accessible name. |
| `input type=button` | role=button | Roles:`checkbox`,`combobox`,`gridcell`,`link`,`menuitem`,`menuitemcheckbox`,`menuitemradio`,`option`,`radio`,`separator`,`slider`,`switch`,`tab`, or`treeitem`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| `input type=checkbox` | role=checkbox | Roles:`menuitemcheckbox`,`option` or`switch`;`button` if used with `aria-pressed`. ( AuthorsMUST NOT use the `aria-checked` attribute on `input type=checkbox` elements. Otherwise, anyglobal `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. The HTML [^input/checked^] attribute can be used instead of the `aria-checked` attribute for `menuitemcheckbox`, `option` or `switch` roles when used on `type=checkbox`. |
| `input type=color` | No corresponding role | Global `aria-*` attributes and `aria-disabled` attribute. |
| `input type=date` | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| `input type=datetime-local` | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| `input type=email` with no [^input/list^] attribute | role=textbox | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| `input type=file` | No corresponding role | Global `aria-*` attributes, `aria-disabled`, `aria-invalid` and `aria-required` attributes. |
| `input type=hidden` | No corresponding role | No `role` or `aria-*` attributes |
| `input type=image` | role=button | The following roles are allowed, but are NOT RECOMMENDED:`button`,`checkbox`,`gridcell`,`link`,`menuitem`,`menuitemcheckbox`,`menuitemradio`,`option`,`radio`,`separator`,`slider`,`switch`,`tab` or`treeitem`. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. If possible, authors SHOULD consider using a different HTML element which allows the specified role, such as the `button` element. |
| `input type=month` | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| `input type=number` | role=spinbutton | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `spinbutton` role. |
| `input type=password` | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| `input type=radio` | role=radio | Role:`menuitemradio`. ( AuthorsMUST NOT use the `aria-checked` attribute on `input type=radio` elements. Otherwise, anyglobal `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. The HTML [^input/checked^] attribute can be used instead of the `aria-checked` attribute for the `menuitemradio` role when used on `type=radio`. |
| `input type=range` | role=slider | No `role` other than Authors SHOULD NOT use the`aria-valuemax` or`aria-valuemin` attributes on `input type=range`. Otherwise, anyglobal `aria-*` attributes and any other `aria-*` attributes applicable to the `slider` role. |
| `input type=reset` | role=button | The following roles are allowed, but are NOT RECOMMENDED:`button`,`checkbox`,`combobox`,`gridcell`,`link`,`menuitem`,`menuitemcheckbox`,`menuitemradio`,`option`,`radio`,`separator`,`slider`,`switch`,`tab` or`treeitem`. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. If possible, authors SHOULD consider using a different HTML element which allows the specified role, such as the `button` element. |
| `input type=search`, with no [^input/list^] attribute | role=searchbox | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `searchbox` role. |
| `input type=submit` | role=button | The following roles are allowed, but are NOT RECOMMENDED:`button`,`checkbox`,`combobox`,`gridcell`,`link`,`menuitem`,`menuitemcheckbox`,`menuitemradio`,`option`,`radio`,`separator`,`slider`,`switch`,`tab` or`treeitem`. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. If possible, authors SHOULD consider using a different HTML element which allows the specified role, such as the `button` element. |
| `input type=tel`, with no [^input/list^] attribute | role=textbox | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| `input type=text` or with a missing or invalid `type`, with no [^input/list^] attribute | role=textbox | Roles:`combobox`,`searchbox` or`spinbutton`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| `input type=text`,`search`,`tel`,`url`,`email`, or with a missing or invalid `type`,with a [^input/list^] attribute | role=combobox | No `role` other than Authors SHOULD NOT use the `aria-haspopup` attribute on the indicated `input`s with a `list` attribute. Otherwise, anyglobal `aria-*` attributes and any other `aria-*` attributes applicable to the `combobox` role. |
| `input type=time` | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| `input type=url` with no [^input/list^] attribute | role=textbox | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| `input type=week` | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| [^ins^] | role=`insertion` | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^kbd^] | No corresponding role | Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^label^] | No corresponding role | If a `label` element is implicitly or explicitly associated with alabelable element thenno `role` Otherwise, if the `label` is not associted with an element thenany `role`, though Naming Prohibited if exposed as the `generic` role, or if exposed as another role which prohibits naming. Otherwise,global `aria-*` attributes. |
| [^legend^] | No corresponding role | Otherwise,global `aria-*` attributes. |
| [^li^] | If the `li` is a child of a list element (`ul`,`ol`,`menu`) Otherwise, if the `li` is not a child of a list element it is exposed as a | No `role` other than Otherwise,any `role` if the parent list element does not expose an implicit or explicit `list` role. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. Authors SHOULD NOT use the followingdeprecated DPub Roles:`doc-biblioentry`,`doc-endnote`. |
| [^link^] | No corresponding role | No `role` or `aria-*` attributes |
| [^main^] | role=main | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `main` role. |
| [^map^] | No corresponding role | No `role` or `aria-*` attributes |
| [^mark^] | No corresponding role | Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| `math` | role=math | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `math` role. |
| [^menu^] | role=list | Roles:`group`,`listbox`,`menu`,`menubar`,`none`,`presentation`,`radiogroup`,`tablist`,`toolbar` or`tree`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. Authors SHOULD NOT usedeprecated`directory` role. |
| [^meta^] | No corresponding role | No `role` or `aria-*` attributes |
| [^meter^] | role=`meter` | No `role` other than Authors SHOULD NOT use the`aria-valuemax` or`aria-valuemin` attributes on `meter` elements. Otherwise, anyglobal `aria-*` attributes and any other `aria-*` attributes applicable to the `meter` role. |
| [^nav^] | role=navigation | Roles:`menu`,`menubar`,`none`,`presentation` or`tablist`. ( DPub Roles:`doc-index`,`doc-pagelist` or`doc-toc` Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^noscript^] | No corresponding role | No `role` or `aria-*` attributes |
| [^object^] | No corresponding role | Roles:`application`,`document`,`img` or`image`. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^ol^] | role=list | Roles:`group`,`listbox`,`menu`,`menubar`,`none`,`presentation`,`radiogroup`,`tablist`,`toolbar` or`tree`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. Authors SHOULD NOT usedeprecated`directory` role. |
| [^optgroup^] | role=group | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `group` role. |
| [^option^] element that is in alist of options or that represents a suggestion in a [^datalist^] | role=option | No `role` other than Authors SHOULD NOT use the `aria-selected` attribute on the `option` element. Global `aria-*` attributes and any other `aria-*` attributes applicable to the `option` role. |
| [^output^] | role=status | Any `role`, though Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^p^] | role=`paragraph` | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^param^] | No corresponding role | No `role` or `aria-*` attributes |
| [^picture^] | No corresponding role | Authors MAY specify the`aria-hidden` attribute on the `picture` element. Otherwise, no other allowed `aria-*` attributes. |
| [^pre^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^progress^] | role=progressbar | No `role` other than Authors SHOULD NOT use the`aria-valuemax` attribute on `progress` elements. Otherwise, anyglobal `aria-*` attributes and any other `aria-*` attributes applicable to the `progressbar` role. |
| [^q^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^rp^] | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^rt^] | No corresponding role | Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^ruby^] | No corresponding role | Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^s^] | role=`deletion` | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^samp^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^script^] | No corresponding role | No `role` or `aria-*` attributes |
| [^search^] |
| Roles:`form`,`group`,`none`,`presentation` or`region`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^section^] |
Otherwise, | Roles:`alert`,`alertdialog`,`application`,`banner`,`complementary`,`contentinfo`,`dialog`,`document`,`feed`,`group`,`log`,`main`,`marquee`,`navigation`,`none`,`note`,`presentation`,`search`,`status` or`tabpanel`. ( DPub Roles:`doc-abstract`,`doc-acknowledgments`,`doc-afterword`,`doc-appendix`,`doc-bibliography`,`doc-chapter`,`doc-colophon`,`doc-conclusion`,`doc-credit`,`doc-credits`,`doc-dedication`,`doc-endnotes`,`doc-epigraph`,`doc-epilogue`,`doc-errata`,`doc-example`,`doc-foreword`,`doc-glossary`,`doc-index`,`doc-introduction`,`doc-notice`,`doc-pagelist`,`doc-part`,`doc-preface`,`doc-prologue`,`doc-pullquote`,`doc-qna`,`doc-toc` Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^select^] (with NO `multiple` attribute and NO `size` attribute having value greater than `1`) | role=combobox | Role:`menu`. ( Authors SHOULD NOT use the `aria-multiselectable` attribute on a `select` element. Otherwise, anyglobal `aria-*` attributes and any other `aria-*` attributes applicable to the `combobox` or `menu` role. |
| [^select^] (with a `multiple` attribute or a `size` attribute having value greater than `1`) | role=listbox | No `role` other than Authors SHOULD NOT use the `aria-multiselectable` attribute on a `select` element. Otherwise, anyglobal `aria-*` attributes and any other `aria-*` attributes applicable to the `listbox` role. |
| [^selectedcontent^] | role=generic | If used as a valid descendant of a `select` element:no `role` or `aria-*` attributes Otherwise,any `role` if the element is used outside of its intended context as a child of the `button` part of a customizable `select` element, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^slot^] | No corresponding role | No `role` or `aria-*` attributes |
| [^small^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^source^] | No corresponding role | No `role` or `aria-*` attributes |
| [^span^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^strong^] | role=`strong` | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^style^] | No corresponding role | No `role` or `aria-*` attributes |
| [^sub^] | role=`subscript` | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^summary^] | The exposed role of a `summary` element can vary depending on the user agent and assistive technology. | No `role` if the `summary` element is asummary for its parent details element. Global `aria-*` attributes, `aria-disabled`, and `aria-haspopup` attributes. Otherwise, if the `summary` element isnot asummary for its parent details element, authors MAY specifiyany `role`, and anyglobal `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^sup^] | role=superscript | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| `SVG` | `role=graphics-document` as defined bySVG AAM | Any `role`, though `graphics-document` is NOT RECOMMENDED. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^table^] | role=table | Any `role`, though Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^tbody^] | role=rowgroup | Any `role`, though Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^td^] |
No corresponding role if the ancestor `table` element is not exposed as a `role=table`, `grid` or `treegrid` | If the ancestor `table` element has `role=table`, `grid`, or `treegrid`,no `role` other than the following:
Otherwise, if the ancestor `table` element is not exposed as a `role=table`, `grid` or `treegrid`,any `role`. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^template^] | No corresponding role | No `role` or `aria-*` attributes |
| [^textarea^] | role=textbox | No `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the `textbox` role. |
| [^tfoot^] | role=rowgroup | Any `role`, though Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^th^] |
No corresponding role if the ancestor `table` element is not exposed as a `role=table`, `grid` or `treegrid` | If the ancestor `table` element has `role=table`, `grid`, or `treegrid`,no `role` other than the following:
Otherwise, if the ancestor `table` element is not exposed as a `role=table`, `grid` or `treegrid`,any `role`. Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^thead^] | role=rowgroup | Any `role`, though Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^time^] | role=time | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^title^] | No corresponding role | No `role` or `aria-*` attributes |
| [^tr^] | role=row | If the ancestor `table` element has `role=table`, `grid`, or `treegrid`,no `role` other than Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^track^] | No corresponding role | No `role` or `aria-*` attributes |
| [^u^] | role=generic | Any `role`, though Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^ul^] | role=list | Roles:`group`,`listbox`,`menu`,`menubar`,`none`,`presentation`,`radiogroup`,`tablist`,`toolbar` or`tree`. ( Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. Authors SHOULD NOT use thedeprecated`directory` role. |
| [^var^] | No corresponding role | Otherwise,global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
| [^video^] | No corresponding role | Role:`application` Global `aria-*` attributes and any `aria-*` attributes applicable to the `application` role. |
| [^wbr^] | No corresponding role | Roles:`none` or`presentation` Authors MAY specify the`aria-hidden` attribute on the `wbr` element. Otherwise, no other allowed `aria-*` attributes. |
The elements marked withNo corresponding role, in the second column of the table do not have anyimplicit ARIA semantics, but they do have meaning and this meaning may be represented in roles, states and properties not provided by ARIA, and exposed to users of assistive technology via accessibility APIs. It is therefore recommended that authors add a `role` attribute to a semantically neutral element such as a [^div^] or [^span^], rather than overriding the semantics of the listed elements.
Authors are encouraged to make use of the following documents for guidance on using ARIA in HTML beyond that which is provided here:
These features can be used to make accessibility tools render content to their users in more useful ways. For example, ASCII art, which is really an image, appears to be text, and in the absence of appropriate roles and properties would end up being rendered by screen readers as a nonsensical string of punctuation characters. Using the features described in this section, one can instead make the ATs skip the ASCII art and just read the caption:
<figure> <pre role="img" aria-label="ASCII Fish"> o .'`/ ' / ( O .-'` ` `'-._ .') _/ (o) '. .' / ) ))) >< < `\ |_\ _.' '. \ '-._ _ .-' '.) jgs `\__\ </pre> <figcaptionid="fish-caption"> Joan G. Stark, "<cite>fish</cite>". October 1997. ASCII on electrons. 28×8. </figcaption></figure>
Authors MAY use`aria-label` and`aria-labelledby` attributes to specifyaccessible names for elements which have an implicit or explicit ARIA role which allows naming from authors. [[[wai-aria-1.2]]] definesroles which allow naming from authors as well asroles where author naming is prohibited.
Authors MUST NOT specify `aria-label` or `aria-labelledby` on elements with implicit WAI-ARIA roles which cannot be named. HTML elements whose implicit WAI-ARIA roles prohibit naming from authors are identified in [[[#docconformance]]].
The following markup example demonstrates a selection of HTML elements with implicit ARIA roles that prohibit naming from authors.
<!-- DO NOT do the following! --> <p aria-label="...">...</p> <span aria-label="...">...<span> <code aria-label="...">...<code> <div aria-labelledby="...">...</div>
The following markup example demonstrates elements which have explicit WAI-ARIA roles which allow naming from authors. Due to the explicit roles specified on these elements, `aria-label` and `aria-labelledby` attributes are allowed.
<p role="link" tabindex="0" aria-label="...">...</p> <span role="button" tabindex="0" aria-label="...">...<span> <div role="article" aria-labelledby="...">...</div>
Unless otherwise stated, authors MAY use `aria-*` attributes in place of their HTML equivalents on HTML elements where the `aria-*` semantics would be expected. For example, authors MAY specify `aria-disabled=true` on a [^button^] element, while also implementing the necessary scripting to functionally disable the `button`, rather than the use `disabled` attribute.
As stated inWAI-ARIA's Conflicts with Host Language Semantics, when HTML elements useboth `aria-*` attributes and their host language (HTML) equivalents, user agents MUST ignore the WAI-ARIA attributes – the native HTML attributes with the sameimplicit ARIA semantics take precedence. For this reason, authors SHOULD NOT specify both the native HTML attribute and the equivalent `aria-*` attribute on an element. Please review each attribute for any further author specific requirements.
The following table represents HTML elements and their attributes which have `aria-*` attribute parity.
Each language feature (element and attribute) in a cell in the first column implies the ARIA semantics (states, and properties) given in the cell in the second column of the same row. The third cell in each row defines how authors can use the native HTML feature, along with requirements for using the `aria-*` attributes that supply the sameimplicit ARIA semantics.
| HTML feature | Implicit ARIA semantics | HTML feature and `aria-*` attribute author guidance |
|---|---|---|
| Any element where the [^input/checked^] attribute is allowed | `aria-checked="true"` | Use the `checked` attribute on any element that is allowed the `checked` attribute in HTML. Use the`indeterminate` IDL attribute to indicate the "mixed" state for`input type=checkbox` elements. Authors MUST NOT use the`aria-checked` attribute on any element where thecheckedness, or the indeterminate checked value of the element can be in opposition to the current value of the `aria-checked` attribute. Authors MAY use the `aria-checked` attribute on any other element with a WAI-ARIA role which allows the attribute. |
| Any element where the [^input/disabled^] attribute is allowed, including `option` [^option/disabled^] and `optgroup` [^optgroup/disabled^] | `aria-disabled="true"` | Use the `disabled` attribute on any element that is allowed the `disabled` attribute in HTML. Authors MAY use the`aria-disabled` attribute on any element that is allowed the `disabled` attribute in HTML, or any element with a WAI-ARIA role which allows the `aria-disabled` attribute. Authors SHOULD NOT use `aria-disabled="true"` on any element which also has a `disabled` attribute. Authors MUST NOT use `aria-disabled="false"` on any element which also has a `disabled` attribute. |
| Any element with a [^html-global/hidden^] attribute | `aria-hidden="true"` | Authors MAY use the`aria-hidden` attribute on any HTML element that allowsglobal `aria-*` attributes to be specified, with the exception of focusable elements and the`body` element. It is generally NOT RECOMMENDED for authors to use `aria-hidden="true"` on any element which also has the `hidden` attribute specified. However, authors MUST NOT use `aria-hidden="true"` on any element which also has the `hidden` attribute specified in the `until-found` state. A focusable element is any element which can be focused by use of keyboard or pointer device. Focusable elements are not always elements which can be tabbed to via a keyboard. For instance, an element with `tabindex="-1"` is focusable but is not a tabbable element. Using `aria-hidden="true"` on an element that has the `hidden` attribute is at best an unnecessary redundancy. At worst its usage can prevent access to the content if the `hidden` attribute's default UA style of `display: none` has been purposeuflly overwritten by an author or user style sheet. Finally, if the `hidden` attribute has the value of `until-found`, the use of `aria-hidden=true` will prevent this content from being discoverable to users of assistive technology when it is found via a browser's in-page find feature and visually rendered to users. |
| Any element where the [^input/placeholder^] attribute is allowed | `aria-placeholder="..."` | Use the `placeholder` attribute on any element that is allowed the `placeholder` attribute in HTML. Authors MAY use the`aria-placeholder` attribute on any element that is allowed the `placeholder` attribute in HTML, or any element with a WAI-ARIA role which allows the `aria-placeholder` attribute. Authors MUST NOT use the `aria-placeholder` attribute on any element which also has a `placeholder` attribute. |
| Any element where the `max` attribute is allowed: `meter` [^meter/max^], `progress` [^progress/max^], and `input` [^input/max^] | `aria-valuemax="..."` | Use the `max` attribute on any element that is allowed the `max` attribute in HTML. Authors MAY use the`aria-valuemax` attribute on any other element with a WAI-ARIA role which allows the `aria-valuemax` attribute. Authors SHOULD NOT use `aria-valuemax` on any element which allows the `max` attribute. Use the `max` attribute instead. Authors MUST NOT use `aria-valuemax` on any element which also has a `max` attribute. |
| Any element where the `min` attribute is allowed: `meter` [^meter/min^] and `input` [^input/min^] | `aria-valuemin="..."` | Use the `min` attribute on any element that is allowed the `min` attribute in HTML. Authors MAY use the`aria-valuemin` attribute on any other element with a WAI-ARIA role which allows the `aria-valuemin` attribute. Authors SHOULD NOT use `aria-valuemin` on any element which allows the `min` attribute. Use the `min` attribute instead. Authors MUST NOT use `aria-valuemin` on any element which also has a `min` attribute. |
| Any element which allows the `readonly` attribute: `input` [^input/readonly^], `textarea` [^textarea/readonly^] andform-associated custom element which allows [^form-associated custom elements/readonly^] | `aria-readonly="true"` | Use the `readonly` attribute on any element that is allowed the `readonly` attribute in HTML. Authors MAY use the`aria-readonly` attribute on any element with a WAI-ARIA role which allows the attribute. Authors SHOULD NOT use the `aria-readonly="true"` on any element which also has a `readonly` attribute. Authors MUST NOT use `aria-readonly="false"` on any element which also has a `readonly` attribute. |
Element with [^html-global/contenteditable^]`=true` or element without `contenteditable` attribute whose closest ancestor with a `contenteditable` attribute has `contenteditable="true"`. This is equivalent to the`isContentEditable` IDL attribute. | `aria-readonly="false"` | Authors MUST NOT set `aria-readonly="true"` on an element that has `isContentEditable="true"`. |
| Any element where the `required` attribute is allowed: `input` [^input/required^], `textarea` [^textarea/required^], and `select` [^select/required^] | `aria-required="true"` | Use the `required` attribute on any element that is allowed the `required` attribute in HTML. Authors MAY use the`aria-required` attribute on any element that is allowed the `required` attribute in HTML, or any element with a WAI-ARIA role which allows the `aria-required` attribute. Authors SHOULD NOT use the `aria-required="true"` on any element which also has a `required` attribute. Authors MUST NOT use `aria-required="false"` on any element which also has a `required` attribute. |
| Any element where the [^th/colspan^] attribute is allowed: `td` and `th` | `aria-colspan="..."` | Use the `colspan` attribute on any element that is allowed the `colspan` attribute in HTML. Authors SHOULD NOT use the `aria-colspan` attribute on any element which also has a `colspan` attribute. Authors MUST NOT use `aria-colspan` on any element which also has a `colspan` attribute, and the values of each attribute do not match. |
| Any element where the [^th/rowspan^] attribute is allowed: `td` and `th` | `aria-rowspan="..."` | Use the `rowspan` attribute on any element that is allowed the `rowspan` attribute in HTML. Authors SHOULD NOT use the `aria-rowspan` attribute on any element which also has a `rowspan` attribute. Authors MUST NOT use `aria-rowspan` on any element which also has a `rowspan` attribute, and the values of each attribute do not match. |
The ARIA Specification'sDeprecated Requirements section indicates that if an ARIA feature is marked as deprecated then authors are advised not to use said feature for new content.
The following roles and attributes are deprecated features of ARIA and DPub ARIA. Conformance checkers MUST warn authors about the deprecated status of these features. Whenever possible, authors are advised to use alternatives to deprecated features.
The `directory` role is marked for deprecation in [[wai-aria-1.2|WAI-ARIA 1.2]]. In reality, the `directory` role had no functional difference to an element with an implicit or explicit `list` role. Authors are advised to use one of HTML's native list elements, or an ARIA `list` instead.
The `doc-biblioentry` and `doc-endnote` roles are marked for deprecation in [[[dpub-aria-1.1]]], as they are not valid children for an element with an implicit or explicit role of `list`. Authors can use standard list and child `li` elements without the need for these roles.
The `aria-dropeffect` and `aria-grabbed` attributes were deprecated in [[wai-aria-1.1|WAI-ARIA 1.1]]. There is presently no feature in ARIA to replace their proposed functionality.
Authors SHOULD use [=ASCII lowercase=] for all `role` token values and any state or property attributes (`aria-*`) whose values aredefined as tokens.
While modern browsers treat the `role` or `aria-*` attribute values as [=ASCII case-insensitive=], not all assistive technologies will correctly parse these values.
To reduce interoperability issues, authors are strongly encouraged to use [=ASCII lowercase=] for `aria-*` and `role` attribute values. Further, authors are encouraged to rigorously test with different browser and assistive technology combinations to ensure that their content will be correctly exposed to their users.
Correct (conforming) examples:
<divrole="main">...</div> <a href="home/"aria-current="page">home</a>
Incorrect (non-conforming) examples:
<!-- DO NOT DO THE FOLLOWING --><divrole="MAIN">...</div><divrole="Main">...</div><a href="home/"aria-current="Page">home</a>
The following table maps (and extends) theKinds of content and allowed descendant information (defined in the [[HTML]] specification) to elements that have an equivalent `role`.
Column 1 links to the normative [[[wai-aria-1.2]]] definitions for each ARIA `role`. Column 2 identifies theKinds of content categories each `role` has when it is used on an HTML element. Column 3 indicates what kinds of HTML elements can be descendants of an element with an explicit `role` specified, often matching the HTML element with the sameimplicit role.
For example, a [^button^] element has an implicit `role=button`. In HTML a `button` element allows [=phrasing content=] as descendants, and does not allow [=interactive content=] or descendants with a `tabindex` attribute. Therefore, any elements specified with a `role=button` would follow the same descendant restrictions, and not allow any interactive content descendants, elements with a `tabindex` specified, or any elements with role values that are in the interactive content category (identified in column 3).
<!-- conformance checkers will report an error --><button> <divrole="button">...</div></button><divrole="button"> <button>...</button></div><divrole="link"> <textarea>...</textarea></div>
Additionally, there are certain roles which [[[wai-aria-1.2]]] has specified specific requirements for their allowed descendants. These have been identified in column 3 (Descendant allowances) by indicating to "Refer to the 'Required Owned Elements'" for those particular roles.
| Role | Kind of content | Descendant allowances |
|---|---|---|
| `alert` | [=Flow content=] | [=Flow content=] but with nomain element descendants. |
| `alertdialog` | [=Flow content=] | [=Flow content=] |
| `application` | [=Flow content=] | [=Flow content=] |
| `article` |
| [=Flow content=] but with nomain element descendants. |
| `banner` |
| [=Flow content=] but with nomain,header, orfooter element descendants. |
| `blockquote` |
| [=Flow content=] but with nomain element descendants. |
| `button` |
| [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `caption` | N/A | [=Flow content=] but with nomain ortable element descendants. |
| `cell` | N/A | [=Flow content=] but with nomain element descendants. |
| `checkbox` |
| [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `code` |
| [=Phrasing content=] |
| `columnheader` | N/A | [=Flow content=] but with nomain,header, orfooter element descendants. |
| `combobox` |
| [=Flow content=] but with nomain element descendants. |
| `complementary` |
| [=Flow content=] but with nomain element descendants. |
| `contentinfo` |
| [=Flow content=] but with nomain,header, orfooter element descendants. |
| `definition` |
| [=Phrasing content=] |
| `deletion` |
| [=Phrasing content=] |
| `dialog` | [=Flow content=] | [=Flow content=] |
| `directory` | [=Flow content=] | [=Flow content=] but with nomain element descendants. |
| `document` | [=Flow content=] | [=Flow content=] |
| `emphasis` |
| [=Phrasing content=] |
| `feed` | [=Flow content=] | [=Flow content=] but with nomain element descendants. |
| `figure` |
| [=Flow content=] but with nomain element descendants. |
| `form` |
| [=Flow content=], but with no [^form^] element descendants. |
| `generic` |
| [=Flow content=] |
| `grid` |
| Refer to the "Required Owned Elements" as defined for the ARIA`grid` role. |
| `gridcell` | [=Interactive content=] | [=Flow content=] but with nomain element descendants. |
| `group` |
| [=Flow content=] |
| `heading` |
| [=Phrasing content=] |
| `img` or `image` |
| [=Phrasing content=], but with no [=interactive content=] descendants. |
| `insertion` |
| [=Phrasing content=] |
| `link` |
| [=Flow content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `list` | [=Flow content=] | Refer to the "Required Owned Elements" as defined for the ARIA`list` role. |
| `listbox` |
| Refer to the "Required Owned Elements" as defined for the ARIA`listbox` role. |
| `listitem` | N/A | [=Flow content=] but with nomain element descendants. |
| `log` | [=Flow content=] | [=Flow content=], but with nomain element descendants. |
| `main` | [=Flow content=] | [=Flow content=], but with nomain element descendants. |
| `marquee` | [=Flow content=] | [=Flow content=], but with nomain element descendants. |
| `math` | [=Flow content=] | [=Flow content=] |
| `menu` |
| Refer to the "Required Owned Elements" as defined for the ARIA`menu` role. |
| `menubar` |
| Refer to the "Required Owned Elements" as defined for the ARIA`menubar` role. |
| `menuitem` | [=Interactive content=] | [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `menuitemcheckbox` | [=Interactive content=] | [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `menuitemradio` | [=Interactive content=] | [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `meter` |
| [=Phrasing content=], but with nometer element descendants. |
| `navigation` |
| [=Flow content=], but with nomain element descendants. |
| `none` | N/A | Transparent |
| `note` | [=Flow content=] | [=Flow content=], but with nomain element descendants. |
| `option` | [=Interactive content=] | [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `paragraph` |
| [=Phrasing content=] |
| `presentation` | N/A | Transparent |
| `progressbar` |
| [=Phrasing content=], but with noprogress element descendants. |
| `radio` |
| [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `radiogroup` |
| [=Flow content=] |
| `region` |
| [=Flow content=], but with nomain element descendants. |
| `row` | N/A | Refer to the "Required Owned Elements" as defined for the ARIA`row` role. |
| `rowgroup` | N/A | Refer to the "Required Owned Elements" as defined for the ARIA`rowgroup` role. |
| `rowheader` | N/A | [=Flow content=] but with nomain element descendants. |
| `scrollbar` | [=Interactive content=] | [=Phrasing content=] |
| `search` |
| [=Flow content=] but with nomain element descendants. |
| `searchbox` |
| [=Flow content=] but with nomain element descendants. |
| `separator` | [=Interactive content=] (if focusable) | [=Phrasing content=] |
| `slider` |
| [=Phrasing content=] |
| `spinbutton` |
| [=Flow content=] but with nomain element descendants. |
| `status` | [=Flow content=] | [=Flow content=] but with nomain element descendants. |
| `strong` |
| [=Phrasing content=] |
| `subscript` |
| [=Phrasing content=] |
| `superscript` |
| [=Phrasing content=] |
| `switch` |
| [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `tab` | [=Interactive content=] | [=Phrasing content=], but with no [=interactive content=] descendants, and no descendants with a `tabindex` attribute specified. |
| `table` |
| Refer to the "Required Owned Elements" as defined for the ARIA`table` role. |
| `tablist` |
| Refer to the "Required Owned Elements" as defined for the ARIA`tablist` role. |
| `tabpanel` | [=Flow content=] | [=Flow content=] |
| `term` | [=Phrasing content=] | [=Phrasing content=] |
| `textbox` | [=Interactive content=] | [=Flow content=] but with nomain element descendants. |
| `time` |
| [=Phrasing content=] |
| `timer` | [=Flow content=] | [=Flow content=] but with nomain element descendants. |
| `toolbar` | [=Flow content=] | [=Flow content=] but with nomain element descendants. |
| `tooltip` | [=Flow content=] | [=Phrasing content=] |
| `tree` | [=Flow content=] | Refer to the "Required Owned Elements" as defined for the ARIAtree role. |
| `treegrid` | [=Flow content=] | Refer to the "Required Owned Elements" as defined for the ARIAtreegrid role. |
| `treeitem` | [=Interactive content=] | [=Phrasing content=] |
Conformance checkers that claim support for checking ARIA in HTML documents MUST implement checks for the conformance requirements for use of the ARIA `role` and `aria-*` attributes on [=HTML elements=] as defined in this specification.
A conforming document MUST NOT contain any elements with author defined `role` or `aria-*` attributes with values other than those which, per this specification, authors MAY use on each [=HTML element=] in [[[#docconformance]]]. Conformance checkers SHOULD flag instances where authors are explicitly providing an element with a `role` which matches itsimplicit ARIA semantics as failures, as it is NOT RECOMMENDED for authors to explicitly set these roles.
A conformance checker MAY define their own terminology, and level or levels of severity, when surfacing document failures to conform to this specification.
This specification does not define the features of [[wai-aria-1.2]], [[dpub-aria-1.0]] or [[HTML]]. Rather it provides rules and guidance for conformance checkers that claim support for checking ARIA in HTML, as well as providing guidance to authors.
Therefore, there are no known privacy or security impacts of this specification, as it defines no new features to introduce potential concern.