question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Accessibility: no way to clear the selection with a keyboard

See original GitHub issue

Caveat: I’m not an accessibility expert so perhaps there is an alternative mechanism available to clear selections. But the usual way (tabbing to the clear button) is not working.

Reproduction Steps

  1. open NVDA
  2. visit https://react-select.com/
  3. tab to any select example that has a selected item and that is clearable (at the time of this writing the first example satisfies these conditions)
  4. tab again

Expected Behavior

I would expect Step 4 to focus the “X” that clears the selected option.

Actual Behavior

You can’t focus the clear button.

Proposed Solution

Make the clear div a button tag.

Am I Willing To Submit A PR For This?

Yes, absolutely. The company I work for has budget for fixing a11y issues in the open source libraries we use or that we are considering using.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:9

github_iconTop GitHub Comments

1reaction
dgreene1commented, Jul 29, 2022

On second thought, @Rall3n i just re-read the combo box authoring spec and it refers to the popup button or children of the popup. The clear button is neither of those things. So can you clarify why it would break the spec to make clear tab-able?

Note: The popup indicator icon or [popup indicator] button (if present), the popup, and the popup descendants are excluded from the page Tab sequence.

1reaction
dgreene1commented, Jul 29, 2022

@Rall3n I agree to the spec but it’s just sad for the user that it’s a bit confusing. I concede though because following specs allows us to provide a common mental model for users so they can “port” their experiences from one application to another.

FYI, your links to the authoring guide above are stale or wrong so I have it here: https://www.w3.org/WAI/ARIA/apg/patterns/combobox/

thank you for the insight.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Keyboard Accessibility - WebAIM
Keyboard accessibility is one of the most important aspects of web accessibility. Many users with motor disabilities rely on a keyboard.
Read more >
Windows keyboard shortcuts for accessibility - Microsoft Support
Additional accessibility keyboard shortcuts ; Left Alt + left Shift + Num lock. Turn Mouse Keys on or off ; Shift five times....
Read more >
Keyboard - Accessibility - MDN Web Docs - Mozilla
To be fully accessible, a web page must be operable by someone using only a keyboard to access and control it. This includes...
Read more >
Use accessibility shortcuts - Android Accessibility Help
On your device, open the Settings app. Tap Accessibility. Select the app that you want to use with a shortcut. Select the shortcut...
Read more >
Keyboard-Only Navigation for Improved Accessibility
Keyboard users must be able to access all interactive elements, not just the main navigation or in-line links. This means that form elements ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found