You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The native disabled attribute is still supported on <fieldset>, which is a group.
There is still a rule in aria-disabled that it applies to all focusable descendants. Perhaps this rule could go away, but it is probably still useful for listbox, menu, menubar, rowheader, and columnheader.
The text was updated successfully, but these errors were encountered:
In looking to address Sarah's comment, and re-reviewing the initial issue, I think I missed the mark on what needed to be called out here. So, this revision is an attempt to simplify/clarify what I was trying to say before (that a link should not inherit the disabled state from a parent element).
This also removes the word "focusable" , as per the original issue a `<div role=textbox>` should still be communicated as being in the disabled state if a descendant of a `role=group aria-disabled=true`.
Note: that the alternative here is to instead move forward with Aaron's issue #1632, and remove the allowance for a `group` to be marked as disabled. The caveat I see here is that since `group` is allowed in a `listbox` and `menu`, a `group` should probably still be allowed to be marked as disabled in these contexts... so that's tricky.
The native disabled attribute is still supported on
<fieldset>
, which is a group.There is still a rule in aria-disabled that it applies to all focusable descendants. Perhaps this rule could go away, but it is probably still useful for listbox, menu, menubar, rowheader, and columnheader.
The text was updated successfully, but these errors were encountered: