Skip to content
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

Accessibility not working on Month and Years dropdown #2587

Closed
tresorama opened this issue Nov 14, 2024 · 2 comments · Fixed by #2600
Closed

Accessibility not working on Month and Years dropdown #2587

tresorama opened this issue Nov 14, 2024 · 2 comments · Fixed by #2600

Comments

@tresorama
Copy link

tresorama commented Nov 14, 2024

Expected Behavior

On tab navigation we should be able to reach the "select", then on "enter / space" press we should open the "select" and moving between "options" with "arrows" press.

Actual Behavior

The "select" of the drop-down is hidden under the drop-down label ( that shows current selected option).
Because of this the "select" is not reachable with Tab navigation.

Example

https://daypicker.dev/docs/navigation#hidenavigation

Version Affected: 9.3.0

@gpbl
Copy link
Owner

gpbl commented Nov 16, 2024

Thank you for your feedback. It appears that the select is not receiving the focus outline, but it is actually focused.

To open the select element, you can press the “space” key when tabbing on it (after the "Next Month" button):

To resolve this issue, we need to apply a border as outline to the caption when the select element is focused. I believe the outline was working before, but it appears to have been removed for some reason.

@gpbl gpbl added the style label Nov 16, 2024
@tresorama
Copy link
Author

@gpbl great. I haven't checked that.
So it is a css issue at the end

@gpbl gpbl self-assigned this Nov 24, 2024
@gpbl gpbl linked a pull request Nov 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants