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
Describe the bug
It is not possible to navigate with keyboard navigation in the YearMonthPicker. When I click on the input field there is no way to use keyboard navigation to navigate through the calendar. This is not considered accessible and there is no way for the user to navigate to the calendar without first clicking on it. It works like a charm in the standard calendar with dates but not in MonthYearPicker.
To Reproduce
Steps to reproduce the behavior:
Use prop: showMonthYearPicker
Try to navigate with keyboard
Expected behavior
When calendar pops up the user should be able to navigate through the calendar with keyboard. In other words, when the input field is clicked on or selected, keyboard navigation should set focus on the calendar.
Desktop (please complete the following information):
OS: Windows 10/11
Browser: Chrome:latest / Firefox:latest
Additional context
Is there any solution to this applied in the repo or is it actually a bug?
The text was updated successfully, but these errors were encountered:
Describe the bug
It is not possible to navigate with keyboard navigation in the YearMonthPicker. When I click on the input field there is no way to use keyboard navigation to navigate through the calendar. This is not considered accessible and there is no way for the user to navigate to the calendar without first clicking on it. It works like a charm in the standard calendar with dates but not in MonthYearPicker.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When calendar pops up the user should be able to navigate through the calendar with keyboard. In other words, when the input field is clicked on or selected, keyboard navigation should set focus on the calendar.
Desktop (please complete the following information):
Additional context
Is there any solution to this applied in the repo or is it actually a bug?
The text was updated successfully, but these errors were encountered: