Skip to content

Commit 4dbf1a4

Browse files
scottaoharascottaohara
authored
finish command guidance
update the first column which had copied the `contenteditable` content to the correct `command` related content. update the allowances for aria-expanded to only be applicable to the toggle/show/hide popover states - since that's where the implicit conflict would come into play. other wording fixes for the attribute table cleanup that i was doing in this PR as well - for better/worse since that arguably should have been another PR... but the work is done so here it is...
1 parent 9901033 commit 4dbf1a4

File tree

1 file changed

+28
-35
lines changed

1 file changed

+28
-35
lines changed

‎index.html‎

Lines changed: 28 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -3655,23 +3655,15 @@ <h3 id="docconformance-attr">
36553655
<tr id="att-command" tabindex="-1">
36563656
<th>
36573657
<p>
3658-
Element with [^html-global/contenteditable^]`=true`
3659-
or
3660-
element without `contenteditable` attribute whose closest
3661-
ancestor with a `contenteditable` attribute has
3662-
`contenteditable="true"`.
3663-
</p>
3664-
<p class="note">
3665-
This is equivalent to the <a data-cite="html/interaction.html#dom-iscontenteditable">`isContentEditable`</a>
3666-
IDL attribute.
3658+
Any element where the <a data-cite="html/form-elements.html#attr-button-command">`command`</a> attribute is allowed
36673659
</p>
36683660
</th>
36693661
<td>
36703662
`aria-expanded="..."`, `aria-details`
36713663
</td>
36723664
<td>
36733665
<p>
3674-
Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `command` attribute.
3666+
Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `command` attribute in the <strong>Toggle popover</strong>, <strong>Show popover</strong> or <strong>Hide popover</strong> state. E.g., `command=toggle-popover`, `command=show-popover` or `command=hide-popover`.
36753667
</p>
36763668
<p>
36773669
Authors MAY use `aria-details` to modify whether or how the element exposes a details relationship
@@ -3703,9 +3695,7 @@ <h3 id="docconformance-attr">
37033695
<tr id="att-disabled" tabindex="-1">
37043696
<th>
37053697
Any element where the [^input/disabled^]
3706-
attribute is allowed, including
3707-
`option` [^option/disabled^] and
3708-
`optgroup` [^optgroup/disabled^]
3698+
attribute is allowed
37093699
</th>
37103700
<td>
37113701
`aria-disabled="true"`
@@ -3732,16 +3722,16 @@ <h3 id="docconformance-attr">
37323722
Authors MUST NOT use `aria-hidden="true"` on any element which also has the `hidden` attribute specified in the `until-found` state.
37333723
</p>
37343724
<p>
3735-
Authors MAY use the <a data-cite="wai-aria-1.2#aria-hidden">`aria-hidden`</a> attribute on any HTML element that allows
3725+
Authors MAY use the <a data-cite="wai-aria-1.2#aria-hidden">`aria-hidden`</a> attribute on an element that allows
37363726
<a data-cite="wai-aria-1.2#global_states">global `aria-*` attributes</a> to
37373727
be specified, with the exception of focusable elements. The attribute MUST NOT be used on the <a href="#el-body">`body`</a> and <a href="#el-html">`html`</a> elements.
37383728
</p>
37393729
<div class="note">
3740-
A focusable element is any element which can be focused by use of keyboard or pointer device. Focusable elements are not always elements which
3730+
A focusable element is an element which can be focused by use of keyboard or pointer device. Focusable elements are not always elements which
37413731
can be tabbed to with a keyboard. For instance, an element with `tabindex="-1"` is focusable but is not a tabbable element.
37423732
</div>
37433733
<div class="note">
3744-
Using `aria-hidden="true"` on an element that has the `hidden` attribute is at best an unnecessary redundancy. At worst its usage can
3734+
Using `aria-hidden="true"` on an element that has the `hidden` attribute is at best an unnecessary redundancy. At worst, its usage can
37453735
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.
37463736
Additionally, if the `hidden` attribute has the value of `until-found`, the use of `aria-hidden=true` will prevent this content from being discoverable to
37473737
users of assistive technology when it is found via a browser's in-page find feature and visually rendered to users.
@@ -3757,7 +3747,7 @@ <h3 id="docconformance-attr">
37573747
</td>
37583748
<td>
37593749
<p>
3760-
Authors MUST NOT use the `aria-placeholder` attribute on any element which also has a `placeholder` attribute.
3750+
Authors MUST NOT use the `aria-placeholder` attribute on an element which also has a `placeholder` attribute.
37613751
</p>
37623752
</td>
37633753
</tr>
@@ -3770,10 +3760,10 @@ <h3 id="docconformance-attr">
37703760
</td>
37713761
<td>
37723762
<p>
3773-
Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `popovertarget` attribute.
3763+
Authors MUST NOT use the `aria-expanded` attribute on an element which also has a `popovertarget` attribute.
37743764
</p>
37753765
<p>
3776-
Authors MAY use `aria-details` to modify whether or how the element exposes a details relationship
3766+
Authors MAY use `aria-details` to modify whether or how an element exposes a details relationship
37773767
with its associated `popover` or other relevant elements.
37783768
</p>
37793769
</td>
@@ -3787,10 +3777,11 @@ <h3 id="docconformance-attr">
37873777
</td>
37883778
<td>
37893779
<p>
3790-
Authors SHOULD NOT use `aria-valuemax` on any element which allows the `max` attribute. Use the `max` attribute instead.
3780+
Authors SHOULD NOT use `aria-valuemax` on an element which allows the `max` attribute.
3781+
Use the `max` attribute instead.
37913782
</p>
37923783
<p>
3793-
Authors MUST NOT use `aria-valuemax` on any element which also has a `max` attribute.
3784+
Authors MUST NOT use `aria-valuemax` on an element which also has a `max` attribute.
37943785
</p>
37953786
</td>
37963787
</tr>
@@ -3803,10 +3794,11 @@ <h3 id="docconformance-attr">
38033794
</td>
38043795
<td>
38053796
<p>
3806-
Authors SHOULD NOT use `aria-valuemin` on any element which allows the `min` attribute. Use the `min` attribute instead.
3797+
Authors SHOULD NOT use `aria-valuemin` on an element which allows the `min` attribute.
3798+
Use the `min` attribute instead.
38073799
</p>
38083800
<p>
3809-
Authors MUST NOT use `aria-valuemin` on any element which also has a `min` attribute.
3801+
Authors MUST NOT use `aria-valuemin` on an element which also has a `min` attribute.
38103802
</p>
38113803
</td>
38123804
</tr>
@@ -3819,59 +3811,60 @@ <h3 id="docconformance-attr">
38193811
</td>
38203812
<td>
38213813
<p>
3822-
Authors SHOULD NOT use the `aria-readonly="true"` on any element which also has a `readonly` attribute.
3814+
Authors SHOULD NOT use the `aria-readonly="true"` on an element which also has a `readonly` attribute.
38233815
</p>
38243816
<p>
3825-
Authors MUST NOT use `aria-readonly="false"` on any element which also has a `readonly` attribute.
3817+
Authors MUST NOT use `aria-readonly="false"` on an element which also has a `readonly` attribute.
38263818
</p>
38273819
</td>
38283820
</tr>
38293821
<tr id="att-required" tabindex="-1">
38303822
<th>
3831-
Any element where the `required` attribute is allowed: `input` [^input/required^], `textarea` [^textarea/required^], and `select` [^select/required^]
3823+
Any element where the `required` attribute is allowed
38323824
</th>
38333825
<td>
38343826
`aria-required="true"`
38353827
</td>
38363828
<td>
38373829
<p>
3838-
Authors SHOULD NOT use the `aria-required="true"` on any element which also has a `required` attribute.
3830+
Authors SHOULD NOT use the `aria-required="true"` on an element which also has a `required` attribute.
38393831
</p>
38403832
<p>
3841-
Authors MUST NOT use `aria-required="false"` on any element which also has a `required` attribute.
3833+
Authors MUST NOT use `aria-required="false"` on an element which also has a `required` attribute.
38423834
</p>
38433835
</td>
38443836
</tr>
38453837
<tr id="att-colspan" tabindex="-1">
38463838
<th>
3847-
Any element where the [^th/colspan^] attribute is allowed: `td` and `th`
3839+
Any element where the [^th/colspan^] attribute is allowed
38483840
</th>
38493841
<td>
38503842
`aria-colspan="..."`
38513843
</td>
38523844
<td>
38533845
<p>
3854-
Authors SHOULD NOT use the `aria-colspan` attribute on any element which also has a `colspan` attribute.
3846+
Authors SHOULD NOT use `aria-colspan` on an element which allows the `colspan` attribute.
3847+
Use the `colspan` attribute instead.
38553848
</p>
38563849
<p>
3857-
Authors MUST NOT use `aria-colspan` on any element which also has a `colspan` attribute.
3850+
Authors MUST NOT use `aria-colspan` on an element which also has a `colspan` attribute.
38583851
</p>
38593852
</td>
38603853
</tr>
38613854
<tr id="att-rowspan" tabindex="-1">
38623855
<th>
3863-
Any element where the [^th/rowspan^] attribute is allowed:
3864-
`td` and `th`
3856+
Any element where the [^th/rowspan^] attribute is allowed
38653857
</th>
38663858
<td>
38673859
`aria-rowspan="..."`
38683860
</td>
38693861
<td>
38703862
<p>
3871-
Authors SHOULD NOT use the `aria-rowspan` attribute on any element which also has a `rowspan` attribute.
3863+
Authors SHOULD NOT use the `aria-rowspan` attribute on an element which allows the `rowspan` attribute.
3864+
Use the `rowspan` attribute instead.
38723865
</p>
38733866
<p>
3874-
Authors MUST NOT use `aria-rowspan` on any element which also has a `rowspan` attribute.
3867+
Authors MUST NOT use `aria-rowspan` on an element which also has a `rowspan` attribute.
38753868
</p>
38763869
</td>
38773870
</tr>

0 commit comments

Comments
 (0)