Skip to content

Softening language around explicitly assigning implicit ARIA semantics #237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Aug 11, 2020
Merged

Softening language around explicitly assigning implicit ARIA semantics #237

Changes from all commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
cbd1e1f
Softening language around explicitly assigning implicit ARIA semantics
patrickhlauke Jul 25, 2020
b0d2725
Re-hardening to still use NOT RECOMMENDED normatively
patrickhlauke Jul 25, 2020
c135e3e
Change dash to comma
patrickhlauke Jul 30, 2020
ad55734
Merge branch 'gh-pages' into patrickhlauke-issue236
scottaohara Aug 10, 2020
a3bbf44
add examples
scottaohara Aug 10, 2020
59b977f
document formatting updates
scottaohara Aug 10, 2020
6de7837
remove list notes per new example provided
scottaohara Aug 10, 2020
dcc8894
cut down this text per the added examples which call this out.
scottaohara Aug 10, 2020
0ad16b1
note updates
scottaohara Aug 10, 2020
81b2e45
Add some fixes/corrections and extra button example
patrickhlauke Aug 10, 2020
c90e327
sentence update
scottaohara Aug 10, 2020
a78d2c1
additional wordsmithing
scottaohara Aug 10, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
105 changes: 65 additions & 40 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
ARIA in HTML is a [[HTML]] specification module. Any HTML features,
conformance requirements, or terms that this specification module makes
reference to, but does not explicitly define, are defined in the
[[HTML]] specification.
[[HTML|HTML specification]].
</p>
<p class="advisement">
This is a draft document and its contents are subject to change without
Expand All @@ -75,9 +75,10 @@ <h2 id="rules-wd">
<p>
Web developers MUST NOT use the ARIA `role` and `aria-*` attributes in
a manner that conflicts with the semantics described in the
[[[#docconformance]]] table. Web developers SHOULD NOT set the ARIA
`role` and `aria-*` attributes to values that match the <a>implicit
ARIA semantics</a> defined in the table.
[[[#docconformance]]] table. It is NOT RECOMMENDED for web developers
to set the ARIA `role` and `aria-*` attributes to values that match the
<a>implicit ARIA semantics</a> defined in the table. Doing so is unnecessary
and can potentially lead to unintended consequences.
</p>
<aside class="example">
The following uses a `role=heading` on a `button` element. This is not
Expand All @@ -87,6 +88,46 @@ <h2 id="rules-wd">
&lt;button role="heading"&gt;search&lt;/button&gt;
</pre>
</aside>

<aside class="example">
The following uses a `role=button` on a `button` element. This is unnecessary, as "button"
is already exposed as the implicit role for the element. In practice this redundancy will
likely not have any unforeseen side effects, other than unnecessarily making the markup more verbose, and incorrectly signaling to other developers that this practice is useful.
<pre class="HTML">
&lt;button role="button"&gt;...&lt;/button&gt;
</pre>
</aside>

<aside class="example">
The following uses a `role=group` on a `fieldset` element. This is unnecessary,
because the `fieldset` element is implicitly exposed as a `role=group`. Again,
in practice this will likely not have any unforeseen side effects.
<pre class="HTML">
&lt;fieldset role="group"&gt;...&lt;/fieldset&gt;
</pre>
</aside>

<aside class="example">
The following uses a `role=list` on an `ul` element. This is generally unnecessary,
because the `ul` element is implicitly exposed as a `role=list`. However, some user agents suppress a list's implicit ARIA semantics if list markers are removed. Authors can use `role=list` to reinstate the role if necessary, though this practice would generally not be recommended, otherwise.
<pre class="HTML">
&lt;ul role="list"&gt;...&lt;/ul&gt;
</pre>
</aside>

<aside class="example">
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 different role.
<pre class="HTML">
&lt;details>
&lt;summary role="button"&gt;more information&lt;/summary&gt;
...
&lt;/details>
</pre>
</aside>

</section>
<section>
<h2 id="docconformance">
Expand All @@ -96,24 +137,23 @@ <h2 id="docconformance">
The following table provides normative per-element document-conformance
requirements for the use of ARIA markup in HTML documents and describes
the <a>implicit ARIA semantics</a> that apply to <a data-cite=
"html/dom.html#elements">HTML elements</a> as defined in the HTML
Accessibility API Mappings 1.0 [[html-aam-1.0]] specification.
"html/dom.html#elements">HTML elements</a> as defined in the [[html-aam-1.0|HTML
Accessibility API Mappings 1.0]] specification.
</p>
<p>
Each language feature (element or attribute) in a cell in the first column
implies the ARIA semantics (any role, states, and properties) given in
the cell in the second column of the same row. The third cell in each
row defines which ARIA role values and aria-* attributes which MAY be
used. Where a cell in the third column includes the term
<dfn><strong>Any</strong> `role`</dfn> it indicates that any `role`
value apart from the <a>implicit ARIA semantics</a> `role` value, MAY
be used. If an cell in the third column includes the term <dfn><strong>No `role`</strong></dfn> it indicates that authors MUST NOT overwrite the implicit ARIA semantics, or native semantics of the HTML element.
Each language feature (element or attribute) in a cell in the first column implies the
ARIA semantics (any role, states, and properties) given in the cell in the second column
of the same row. The third cell in each row defines which ARIA role values and `aria-*`
attributes which MAY be used. Where a cell in the third column includes the term
<dfn><strong>Any</strong> `role`</dfn> it indicates that any `role` value apart from the
<a>implicit ARIA semantics</a> `role` value, MAY be used. If a cell in the third column
includes the term <dfn><strong>No `role`</strong></dfn> it indicates that authors MUST NOT
overwrite the implicit ARIA semantics, or native semantics of the HTML element.
</p>

<p class="note" id="aria-usage-note">
Setting an ARIA `role` and/or `aria-*` attribute that matches the
<span>implicit ARIA semantics</span> is unnecessary and is NOT
RECOMMENDED as these properties are already set by the browser.
While setting an ARIA `role` and/or `aria-*` attribute that matches the
<span>implicit ARIA semantics</span> is NOT RECOMMENDED, in some situations explicitly setting these attributes can be helpful. For instance, in user agents which lack specific implicit semantics.
</p>

<table class="simple">
Expand All @@ -126,10 +166,8 @@ <h2 id="docconformance">
</th>
<th>
<p id="implicit">
Implicit ARIA semantics -
</p>
<p>
SHOULD NOT be used
Implicit ARIA semantics
<small>(explicitly assigning these in markup is NOT RECOMMENDED)</small>
</p>
</th>
<th>
Expand Down Expand Up @@ -1176,7 +1214,8 @@ <h2 id="docconformance">
</td>
<td>
<p>
If not provided an author defined accessible name by other methods: <strong class="nosupport">No `role`</strong>, and <strong>no `aria-*` attributes</strong> except
If no author-defined accessible name is provided by other methods:
<strong class="nosupport">No `role`</strong>, and <strong>no `aria-*` attributes</strong> except
`aria-hidden`.
</p>
<p>
Expand Down Expand Up @@ -1800,11 +1839,6 @@ <h2 id="docconformance">
</td>
<td>
<code>role=<a href="#index-aria-list">list</a></code>
<p>
<strong>Note:</strong> some user agents suppress a list's
<a>implicit ARIA semantics</a> if list markers are removed.
Authors can use `role=list` to reinstate the role if necessary.
</p>
</td>
<td>
<p>
Expand Down Expand Up @@ -1923,11 +1957,6 @@ <h2 id="docconformance">
</td>
<td>
<code>role=<a href="#index-aria-list">list</a></code>
<p>
<strong>Note:</strong> some user agents suppress a list's
<a>implicit ARIA semantics</a> if list markers are removed.
Authors can use `role=list` to reinstate the role if necessary.
</p>
</td>
<td>
<p>
Expand Down Expand Up @@ -2599,7 +2628,8 @@ <h2 id="docconformance">
<code>role=<a href="#index-aria-cell">cell</a></code> if a
descendant of a `table` element.
</p>
<!--<p><code>role=<a href="#index-aria-cell">gridcell</a></code> if a descendant of a <code>table</code> elementwith <code>role=grid</code></p>-->
<!--<p><code>role=<a href="#index-aria-cell">gridcell</a></code> if a descendant
of a <code>table</code> element with <code>role=grid</code></p>-->
</td>
<td>
<p>
Expand Down Expand Up @@ -2686,11 +2716,6 @@ <h2 id="docconformance">
</td>
<td>
<code>role=<a href="#index-aria-list">list</a></code>
<p>
<strong>Note:</strong> some user agents suppress a list's
<a>implicit ARIA semantics</a> if list markers are removed.
Authors can use `role=list` to reinstate the role if necessary.
</p>
</td>
<td>
<p>
Expand Down Expand Up @@ -5290,8 +5315,8 @@ <h2>
Documents MUST NOT use any `role`
values with elements in the [[[#docconformance]]] table, other than the
corresponding role value (if any) as listed for that element in the
third column, other than those indicated in the second column, which
SHOULD NOT be used.
third column, other than those indicated in the second column (whose
explicit use in markup is NOT RECOMMENDED).
</p>
</section>

Expand Down