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

Dropdown needs to be Accessible #157

Closed
Johnne25 opened this issue Jan 29, 2021 · 6 comments
Closed

Dropdown needs to be Accessible #157

Johnne25 opened this issue Jan 29, 2021 · 6 comments
Labels
stale Stale issue with no response or lack of info

Comments

@Johnne25
Copy link

So far this is one of the better dropdown menu implementations I have seen.
I would be fantastic if you could make it a bit more accessible (used with keyboard only).

So far I haven't been able to get it to function correctly without using the mouse.

Here is what would be nice to have fixed:

  1. Tabbing into the dropdown doesn't show the cursor in the input area.
  2. Pressing the down arrow does open the dropdown, however you can not navigate the dropdown list (using up and down arrows).
  3. Pressing enter does select the item.
  4. Once into the control, you can not tab out of it.
@sanusart
Copy link
Owner

  1. It is bu design and constrains of being able to skip the field. Tapping down will.
  2. it does navigate with both, arrows and tabs
  3. What is wrong with that?
  4. Escape

@Johnne25
Copy link
Author

Johnne25 commented Feb 8, 2021

Ok.
#1. I will agree with. Not a big deal.
#2. I have tried and once I press the down arrow to open the dropdown list I can not navigate to it. Pressing TAB or all the arrow keys does nothing.
#3. Sorry, it was to indicate pressing ENTER does work correctly, wasn't an issue.
#4. Ok, pressing ESC does work.

So, only #2 doesn't work for me.

@sanusart
Copy link
Owner

sanusart commented Feb 8, 2021

May I ask the browser kind and Operating system to debug number 2?

@Johnne25
Copy link
Author

Johnne25 commented Feb 8, 2021

The backend is running on a Windows 2019 machine (node.js).
The frontend is running on a Mac (node.js).
The browser is running on a Mac Big SURR Beta 3 (same as the frontend server).
The browser is the latest version of Chrome.

@sanusart
Copy link
Owner

Unfortunately I was not able to reproduce. Same env described just the stable, latest version of big sur.

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issue with no response or lack of info label Jun 2, 2021
@stale stale bot closed this as completed Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issue with no response or lack of info
Projects
None yet
Development

No branches or pull requests

2 participants