Accessibility #2684
Replies: 2 comments 1 reply
-
I would love to improve the accessibility. Some features like date ranges can be in worse state in terms accessibility than the calendar in general. Is there an issue filed on the date range accessibility? If not, you can go ahead and create one. It shouldn't be too hard to improve. |
Beta Was this translation helpful? Give feedback.
-
Hi, I just cloned the project to improve accessibility. There are several things to fix, but what worries me most is the instantiation. By having the datepicker instantiate on an input, this doesn't give the correct role for a screen reader user to press it. An input expects to have write behavior. This is the initial thing. It should be some element like a button or with role="button" (doesn't apply to input), that allows to open the calendar. Also, when you press tab and get to the datepicker, it shouldn't open automatically. This interrupts the typical navigation flow of a screen reader. It should only open with an explicit keyboard action. My opinion is that the input that stores the date should be of type hidden and the datepicker trigger should be a button. I still can't think of how this change could be implemented without it being such a big breacking change. The calendar container should have role="dialog" and we should do something to move quickly through the days as if it were a table, this isn't complicated. We should also add some missing aria attributes, like when a day is selected or when a day is disabled. More things are missing, but that would be the start. What do you think? Screen reader user and blind developer here |
Beta Was this translation helpful? Give feedback.
-
Hi,
Accessibility (a11y) has become an important topic these days. Flatpickr is a wonderful date picker and I think it could become even greater if we could fix some accessibility issue and add documentation on how it should interact with keyboards navigation ans screen-reader. I've searched in issues and tried to set my mind on what it needs to be done. Maybe if we could set a road map regarding accessibility.
In my particular case I'm using inline calendar with dateRange. Keyboard navigation is almost useless (or unclear to me how it should be used).
I'm just starting this discussion to get your feelings about accessibility and get some ideas on how we should work toward improving Flatpickr.
Beta Was this translation helpful? Give feedback.
All reactions