Open siddhantantil39 opened 1 month ago
Thanks for the report @siddhantantil39!
@michaldudak, do you know what's the behaviour on Base UI's Select regarding this?
AFAIR @mui/base
did not place the aria-controls
attribute when its target doesn't exist. @atomiks, how does the new implementation handle this case?
@michaldudak yes, aria-controls
is not added to the trigger unless the popup is in the open
state
@michaldudak @atomiks, thanks. This means this will be fixed when we refactor Material UI's Select on top of Base UI's. This is one of the next projects we'll take on soon.
Hi @DiegoAndai, I'm also having this issue and I'm wondering if this wouldn't just be a matter of doing a similar change than the one from https://github.com/mui/material-ui/pull/30378/files?
Something like
aria-controls={listboxId}
-> aria-controls={open ? listboxId : ''}
on SelectInput.js
.
Steps to reproduce
Aria-controls references invalid id when not expanded mui select component
Link to live example: (required) Go to: https://mui.com/material-ui/react-select/
Steps:
It is also observed using access-assistant also.
PFA the ARC snapshot:
Current behavior
ARIA attribute value is incorrect is observed on the select component upon ADA Testing using automation tools such as ARC.
Expected behavior
Aria-control should refer to the id of the menu-item, in non-expanded state also.
Context
No response
Your environment
No response
Search keywords: select