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
Since ARIA 1.1, separator has a superclass of widget if focusable (it looks like it's the only ARIA roles that can have different superclasses).
I'm not sure if it's possible to somehow add this, or if this library assumes that each aria role only has one superclass chain.
There's also a separate issue that aria-valuenow is a required prop if the separator is focusable (see also: #230 (comment)), but again, I don't know you'd be able to add that into the current code-base.
Looks like there's also an issue in w3c/aria#1348 that suggests making a separate role="resizer" to avoid separator acting differently depending on whether it's focusable or not.
The text was updated successfully, but these errors were encountered:
See also #547 (comment) which seems relevant to discussion r.e. superclasses with constraints (in this other case for the form role conditional having a superclass of landmark depending on whether the form is named).
Since ARIA 1.1,
separator
has a superclass ofwidget
if focusable (it looks like it's the only ARIA roles that can have different superclasses).I'm not sure if it's possible to somehow add this, or if this library assumes that each aria role only has one superclass chain.
There's also a separate issue that
aria-valuenow
is a required prop if theseparator
is focusable (see also: #230 (comment)), but again, I don't know you'd be able to add that into the current code-base.Looks like there's also an issue in w3c/aria#1348 that suggests making a separate
role="resizer"
to avoidseparator
acting differently depending on whether it's focusable or not.The text was updated successfully, but these errors were encountered: