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
This is an interesting question. I'm going to reach out to the ARIA working group. The ARIA spec doesn't allow separators between options, but I'm wondering if they should, since those are allowed for menuitems. I'm curious what the reasoning is for allowing separators between menuitems, but not anything else.
BTW the way to address this issue is to use groups. Those should get announced and counted correctly.
A related question came up today about using a separator in a tablist. It seems NVDA and VoiceOver ignore them in counting the number of options. I'm not sure whether that is because of the separator role, because the option had no accessible name, or something else. We'll need to test this.
straker
added
spec
Waiting for a related spec to make a change before adopting in axe-core
rules
Issue or false result from an axe-core rule
and removed
ungroomed
Ticket needs a maintainer to prioritize and label
labels
Nov 17, 2023
Product
axe-core
Product Version
No response
Latest Version
Issue Description
Expectation
Accessibility tests to pass.
An item with role=separator should be acceptable as a child of an element with role=listbox.
Actual
Accessibility test fails aria-required-children test.
Error:
Fix any of the following:
Element has children which are not allowed (see related nodes)
Element has no aria-busy="true" attribute
Related node:
li[role="separator"]
How to Reproduce
html sample:
The text was updated successfully, but these errors were encountered: