- 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.
- 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 + 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 the implicit ARIA semantics defined in either table. + 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 the implicit 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 + 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.
@@ -252,8 +101,8 @@
- 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 + 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.
@@ -261,40 +110,40 @@- There are also situations where certain `aria-*` attributes are allowed for use on elements + 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. + 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 + 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 + 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. + 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 + 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 + 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.
@@ -318,16 +167,16 @@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 + 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 suppress the element's - implicit features depending on how the user chooses to engage with the web page. E.g., by turning on + 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 suppress 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" + 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 + 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.
@@ -350,7 +199,7 @@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 + 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`.
@@ -360,9 +209,9 @@<main role="main">...</main>
- The following uses a `role=list` on an [^ul^] element. As the `ul` element has an implicit role of `list`, + 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. + 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.
@@ -409,8 +258,8 @@- 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 + 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 alternatives to remove the implicit role of the `article`.
@@ -418,7 +267,7 @@Adhere to the rules of ARIA
<article role="generic" ...>...</article>
- Additionally, ARIA specifically mentions in Conflicts with Host Language Semantics + Additionally, ARIA specifically mentions in Conflicts 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.
@@ -443,12 +292,12 @@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. + allow a `div` to be a descendant of a `p` element.
<!-- Do not do this! -->
<p>
- ... <div role=link tabindex=0>...</div> ...
+ ... <div role=link tabindex=0>...</div> ...
</p>
@@ -457,10 +306,9 @@
<!-- The previous example's markup will render as follows -->
<p>...</p>
- <div role=link tabindex=0>...</div>
- ...
+ <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> ...
@@ -478,44 +326,42 @@
Document conformance requirements for use of ARIA attributes in HTML
- The following table provides normative per-element document conformance requirements for the
- use of ARIA markup in HTML documents. Additionally, it identifies the implicit ARIA semantics
- that apply to [=HTML elements=]. The implicit ARIA semantics of these elements are defined
+ The following table provides normative per-element document conformance requirements for the
+ use of ARIA markup in HTML documents. Additionally, it identifies the implicit ARIA semantics
+ that apply to [=HTML elements=]. The implicit 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.
+ 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 term Any `role`
- it indicates that any `role` value MAY 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 role
- deprecated by ARIA on these elements.
- If a cell in the third column includes the term No `role` it indicates
- that authors MUST NOT overwrite the implicit ARIA semantics, or native semantics of the HTML element.
+ it indicates that any `role` value MAY 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 role
+ deprecated by ARIA on these elements.
+ If a cell in the third column includes the term No `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 have
+ [[wai-aria-1.2|WAI-ARIA]] identifies roles which have
prohibited 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 as Naming 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
+ Elements which are identified as Naming 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 the implicit ARIA semantics
- is NOT RECOMMENDED, in some situations explicitly setting these attributes can be helpful – for instance,
+ 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.1]]] `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
+ 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.
|
- Roles: `button` @@ -667,10 +512,9 @@ - Otherwise, global `aria-*` attributes + Otherwise, global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. - |
||||
|
- If role defined by `ElementInternals`, + 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 + Otherwise, global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
@@ -789,9 +633,9 @@
-
+
+ No `role` other than + No `aria-*` attributes. + |
|||
|
- +
If a direct child of a [^dl^] element,
only `presentation`
or `none`. Otherwise,
any `role`, though - Otherwise, global `aria-*` attributes + Otherwise, global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
@@ -1194,7 +1033,7 @@
- If role defined by `ElementInternals`, + If role defined by `ElementInternals`, no `role` @@ -1426,11 +1265,11 @@
`switch`
or `textbox`. ( |
@@ -1455,7 +1294,7 @@
- No `role` other than @@ -1577,9 +1416,9 @@
Any `role`, though - Otherwise, global `aria-*` attributes + Otherwise, global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
@@ -1609,13 +1448,11 @@ ||
|
-
- [^img^]
-
+ [^img^]
|
- If the `img` has non-empty [^img/alt^] (`alt="some text"`) or an accessible name is provided by another
- `img` naming method,
+ 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 no accessible name:role=img or image
|
@@ -1625,26 +1462,20 @@
-
-
+
- If the `img` has an empty `alt` ([^img/alt^]`=""`) and lacks any other
- `img` naming methods:
+ If the `img` has an empty `alt` ([^img/alt^]`=""`) and lacks any other
+ `img` naming methods: |
-
No `role` other than the No `aria-*` attributes except `aria-hidden="true"`. - |
|
|---|---|---|---|---|
|
Roles:
- `checkbox`,
- `combobox`,
- `gridcell`,
+ `checkbox`,
+ `combobox`,
+ `gridcell`,
`link`,
`menuitem`,
`menuitemcheckbox`,
`menuitemradio`,
`option`,
- `radio`,
-
- `separator`,
- `slider`,
+ `radio`, `separator`,
+ `slider`,
`switch`,
`tab`,
- or `treeitem`.
+ or `treeitem`.
( - Global `aria-*` attributes + Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
@@ -1739,11 +1563,11 @@
-
-
+ - 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. - -+ 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. + |
|||
|
-
-
+ - 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. - -+ 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. + |
||||
|
-
-
+ - 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. - -+ 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`, + `input type=tel`, with no [^input/list^] attribute |
@@ -2095,7 +1913,7 @@
No `role` other than |
@@ -2116,7 +1934,7 @@
- If a `label` element is implicitly or explicitly associated with a + If a `label` element is implicitly or explicitly associated with a labelable element then no `role`
- Otherwise, if the `label` is not associated with an element then any `role`,
+ Otherwise, if the `label` is not associated with an element then any `role`,
though Naming Prohibited if exposed as the `generic` role, or if exposed as another role which prohibits naming. @@ -2269,7 +2087,7 @@- +Otherwise, global `aria-*` attributes. @@ -2281,40 +2099,36 @@
- If the `li` is a child of an element exposed as a `role=list`
- (e.g., `ul`, `ol`,
+ If the `li` is a child of an element exposed as a `role=list`
+ (e.g., `ul`, `ol`,
`menu`):
- Otherwise,
+ Otherwise,
| ||
|
- +
Any `role`, though - Otherwise, global `aria-*` attributes + Otherwise, global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
@@ -2800,9 +2608,9 @@
-
-
+
- Roles:
- `form`,
- `group`,
- `none`,
- `presentation` or
- `region`.
- ( - Global `aria-*` attributes - and any `aria-*` attributes applicable to the allowed roles. - -
+ Roles:
+ `form`,
+ `group`,
+ `none`,
+ `presentation` or
+ `region`.
+ ( + Global `aria-*` attributes + and any `aria-*` attributes applicable to the allowed roles. + |
|||
|
Otherwise,
`dialog`,
`document`,
`feed`,
- `group`,
+ `group`,
`log`,
`main`,
`marquee`,
@@ -2884,7 +2690,7 @@ role=region is also allowed,
+ (role=region is also allowed,
but NOT RECOMMENDED. role=generic SHOULD NOT be used.)
|
@@ -2939,8 +2745,8 @@
-
-
+ - No `role` if the `summary` element is a - summary for its parent details element. - -- Global `aria-*` attributes, - `aria-disabled`, and `aria-haspopup` attributes. - -- Otherwise, if the `summary` element is not a - summary for its parent details - element, authors MAY specify any `role`, and any - global `aria-*` attributes - and any `aria-*` attributes applicable to the allowed roles. - -+ No `role` if the `summary` element is a + summary for its parent details element. + ++ Global `aria-*` attributes, + `aria-disabled`, and `aria-haspopup` attributes. + ++ Otherwise, if the `summary` element is not a + summary for its parent details + element, authors MAY specify any `role`, and any + Global `aria-*` attributes + and any `aria-*` attributes applicable to the allowed roles. + |
|||
|
any `role`.- Global `aria-*` attributes + Global `aria-*` attributes and any `aria-*` attributes applicable to the allowed roles. |
@@ -3358,7 +3162,7 @@ ||||
|
-
-
+ - Roles: - `none` - or `presentation` - -- Authors MAY specify the `aria-hidden` attribute on the `wbr` element. - Otherwise, no other allowed `aria-*` attributes. - -+ Roles: + `none` + or `presentation` + ++ Authors MAY specify the `aria-hidden` attribute on the `wbr` element. + Otherwise, no other allowed `aria-*` attributes. + |
- No `role` other than listitem, which is NOT RECOMMENDED,
- if the parent list element has an implicit or explicit `list` role.
-
- Otherwise, any `role` if the parent list element does not expose an implicit or explicit `list` role. -
-- See `ul`, `ol`, or - `menu` for allowed roles for list elements. -
-
- Global `aria-*` attributes
+ No `role` other than listitem, which is NOT RECOMMENDED,
+ if the parent list element has an implicit or explicit `list` role.
+
+ Otherwise, any `role` if the parent list element does not expose an implicit or explicit `list` role. +
++ See `ul`, `ol`, or + `menu` for allowed roles for list elements. +
++ Global`aria-*` attributes and any `aria-*` attributes applicable to the allowed roles.
-Authors SHOULD NOT use the following deprecated DPub Roles: - `doc-biblioentry`, - `doc-endnote`. -
-Authors SHOULD NOT use the following deprecated DPub Roles: + `doc-biblioentry`, + `doc-endnote`. +
- The elements marked with No corresponding role, in the second column of - the table do not have any implicit 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 + The elements marked with No corresponding role, in the second column of + the table do not have any implicit 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.
<!-- DO NOT do the following! -->
<p aria-label="...">...</p>
-
<span aria-label="...">...<span>
-
<code aria-label="...">...<code>
-
<div aria-labelledby="...">...</div>
@@ -3620,9 +3416,7 @@
<p role="link" tabindex="0" aria-label="...">...</p>
-
<span role="button" tabindex="0" aria-label="...">...<span>
-
<div role="article" aria-labelledby="...">...</div>
@@ -3632,14 +3426,14 @@ - 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 + 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 in WAI-ARIA's Conflicts with Host Language Semantics, - when HTML elements use both `aria-*` attributes and their host language (HTML) equivalents, user agents MUST ignore the WAI-ARIA attributes – the - native HTML attributes with the same implicit ARIA semantics take precedence. For this reason, authors SHOULD NOT specify both the native HTML attribute + when HTML elements use both `aria-*` attributes and their host language (HTML) equivalents, user agents MUST ignore the WAI-ARIA attributes – the + native HTML attributes with the same implicit 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.
@@ -3681,16 +3475,14 @@
- 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 the checkedness, or the - indeterminate checked value of the element can be in opposition to the current value of the `aria-checked` attribute. -
-+ 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 the checkedness, 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.
@@ -3711,7 +3503,7 @@- Authors MAY use the `aria-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.
@@ -3731,13 +3523,13 @@
- Authors MAY use the `aria-hidden` attribute on any HTML element that allows - global `aria-*` attributes to + Authors MAY use the `aria-hidden` attribute on any HTML element that allows + Global `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 + 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 Hidden Until Found state.
- Authors MAY use the `aria-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.
@@ -3946,7 +3738,7 @@
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 compared to an element with an implicit or explicitly declared `list` role. Authors are advised to use one of HTML's native list elements, or an ARIA `list` role 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.
While modern browsers treat the `role` or `aria-*` attribute values as [=ASCII case-insensitive=], not all assistive technologies will correctly parse these values. @@ -4007,7 +3795,6 @@
<div role="main">...</div>
-
<a href="home/" aria-current="page">home</a>
@@ -4015,15 +3802,12 @@
<!-- DO NOT DO THE FOLLOWING -->
<div role="MAIN">...</div>
-
<div role="Main">...</div>
-
<a href="home/" aria-current="Page">home</a>
-
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.
-