-
Notifications
You must be signed in to change notification settings - Fork 161
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
Calendar keyboard navigation accessibility #6275
Comments
Actually, I don't see that in the spec.. Is this Tab behavior simply a side-effect of the date elements being focusable? |
Currently, we just let the browser handle the tabs as it would. I don'` know if this was intentional, I guess yes. There are some tweaks though that skip a disabled/non-visible date when tabbing. |
There has been no recent activity and this issue has been marked inactive. |
@radomirchev does "Next Milestone Draft" means that this issue is planned for the next milestone? |
@zdrawku it is a draft, not a final version. It is under consideration to be included in the next milestone. |
There has been no recent activity and this issue has been marked inactive. |
Is your
featurerequest related to a problem? Please describe.Related to #6272, after looking at the descriptions for calendar in the datepicker example:
"calendar that uses the grid pattern"
"as specified in the grid design pattern, only one button in the calendar grid is in the Tab sequence."
In other words, tab navigation through the calendar is supposed to allow you to jump through the prev/next buttons, the year/month pickers and the calendar grid itself. Right now the calendar handles the tab as it would cursor keys, which is super tedious.
Describe the solution you'd like
The tab navigation of the calendar should allow you to jump through the separate groups and have a single tab stop for the actual calendar grid.
Additional context
I realize this is a behavior change from the current implementation, but the way the spec describes the behavior seems very reasonable, so I'm logging this as an enhancement.
The text was updated successfully, but these errors were encountered: