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

Keyboard accessibility #32

Open
freaksauce opened this issue Apr 4, 2019 · 3 comments
Open

Keyboard accessibility #32

freaksauce opened this issue Apr 4, 2019 · 3 comments
Labels
📦 backlog ⚡️ feature New feature or request

Comments

@freaksauce
Copy link

freaksauce commented Apr 4, 2019

Describe the bug
The datepicker appears to be impossible to use with keyboard which makes it totally inaccessible.

To Reproduce
Steps to reproduce the behavior:

  1. Try to tab into the component
  2. Click on a date and attempt to navigate to another day or control with tabs and arrow keys

Expected behavior
In order for people who can only use keyboard or assisted devices to use the component it must not be reliant on mouse events only.

Desktop (please complete the following information):

  • OS: macOS Mojave
  • Browser Chrome
  • Version 73.x
@y0c
Copy link
Owner

y0c commented Apr 4, 2019

Thank you for your feedback.
i 'll update this feature in next release :)

@y0c y0c added ⚡️ feature New feature or request 📦 backlog labels Apr 4, 2019
@Aams1000
Copy link

Aams1000 commented Jun 29, 2019

I second this. For example, say one wants to change a date in the RangeDatePicker from 2018-01-01 to 2019-01-01. The user should be able to edit the text field and press enter, triggering the appropriate calendar onChange functions. Right now the enter key does nothing--one must navigate all twelve months by mouse.

I really like this library, but the lack of such functionality makes me question whether I should keep using it--such navigation by mouse is quite a pain.

Thanks!

@y0c
Copy link
Owner

y0c commented Jun 29, 2019

@Aams1000 Thank for your interest, i haven't been able to proceed because I've been busy lately, but I'm going to go ahead with it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 backlog ⚡️ feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants