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 keyboard accessibility appears to be broken #3420

Open
sydk-adhoc opened this issue Jan 31, 2025 · 0 comments
Open

Dropdown keyboard accessibility appears to be broken #3420

sydk-adhoc opened this issue Jan 31, 2025 · 0 comments

Comments

@sydk-adhoc
Copy link

Describe the bug
From the documentation

When the Dropdown is open ...
If the same character is typed in succession, visual focus cycles among the options starting with that character.

This is not happening, AFAICT. We are experiencing this issue in MCT since upgrading to MGov CMSDS v10

To Reproduce
Steps to reproduce the behavior:

  1. Go to the CMSDS docs or Storybook for Dropdown, or, e.g., https://healthcare.gov/create-account (state dropdown)
  2. Use the keyboard, only, to navigate to a dropdown and open with the down arrow key
  3. Type any character that matches the beginning value of one of the options that has sibling options that start with the same character
  4. Focus goes to the first option that begins with that character
  5. Keep typing that character to cycle through the options (e.g., "M" for states that begin with "M")
  6. Does not cycle through options

Expected behavior
Cycles through options that begin with the same character

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • macOS Sequoia
  • Safari, Chrome, Firefox
  • Latest

Smartphone (please complete the following information):
N/A (no keyboard)

Additional context
Add any other context about the problem here.

@sydk-adhoc sydk-adhoc changed the title Dropdown keyboard accessibility is broken Dropdown keyboard accessibility appears to be broken Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant