-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
[Select] Pointer Cancellation (WCAG 2.5.2) failure #45301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @stormojm, thanks for opening the issue. You're absolutely right. The Select from Base UI follows this behavior:
I'm marking this issue as "ready to take" in case someone wants to tackle it. |
Hi @aarongarciah I would like to work on this. Thanks in advance. |
@yermartee feel free to work on it |
@stormojm or @aarongarciah Could you please attach the video of the issue you're observing, and simplify more on the expected behavior, so that I could get clear understanding before I start working on it? |
@Ashish-619 I made a video, but I don't have the ability to capture my mouse clicks visually. Screen.Recording.2025-02-26.at.10.48.27.PM.movIn the video, current MUI documentation is on the left, and the base-ui documentation is on the right. The behavior as specified before:
|
Hey @Ashish-619 are you working on this? |
Hey @yermartee you can work if you want, I've not understood the problem exactly. |
Steps to reproduce
Steps:
Current behavior
Currently the Select component is failing the WCAG 2.5.2 success criterion, which requires functionality to be operated using a single pointer. In this case the combination of "No Down-event" and "Up reversal".
Currently the menu opens up on the mouse down, and it remains open even if moving away and releasing the mouse.
Expected behavior
A key aspect to meeting the Pointer Cancellation criteria is providing a way to easily undo or abort the functionality. So I would expect one of two behaviors:
It is also how apps like Github and Microsoft Teams work for their select-like operations.
Context
This was identified in as a accessibility concern for users of our software.
Your environment
Currently on MUI5, but in process of upgrading, but issue remains in Mui6.npx @mui/envinfo
System:
OS: macOS 15.3
Binaries:
Node: 22.14.0 - /private/var/folders/jv/xsd25_n518v97x_98dbjbmn40000gp/T/xfs-d414690d/node
npm: 10.9.2 - ~/.local/state/fnm_multishells/44298_1739490378994/bin/npm
pnpm: Not Found
Browsers:
Chrome: 133.0.6943.98
Edge: 133.0.3065.59
Safari: 18.3
npmPackages:
@emotion/react: 11.9.0
@emotion/styled: 11.13.0
@mui/core-downloads-tracker: 5.16.7
@mui/material: 5.16.7
@mui/private-theming: 5.16.6
@mui/styled-engine: 5.16.6
@mui/styles: 5.16.7
@mui/system: 5.16.7
@mui/types: 7.2.21
@mui/utils: 5.16.6
@mui/x-date-pickers: 7.24.1
@mui/x-internals: 7.24.1
@types/react: ^17.0.80 => 17.0.80
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
styled-components: 5.3.0
typescript: ~5.5.4 => 5.5.4
Search keywords: select wcag pointer cancellation
The text was updated successfully, but these errors were encountered: