Screen reader still reads tabbing instructions when `tabSelectsValue` prop is false
See original GitHub issueReact-select still reads the tabbing instruction (“press Tab to select the option and exit the menu”) when tabSelectsValue
is set to false
.
Example with tabSelectsValue={false}
https://codesandbox.io/s/zxvkolx6wp
Solution:
Only include that part of the screen reader instructions if tabSelectsValue
is true
(default).
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Screen reader reads it all, but does not tab to it - Stack Overflow
props.orderSummary.totalShippingDiscount)} that sits outside any HTML element, not sure how to deal with that. – user8359832. Sep ...
Read more >react-select-fixed-v2/HISTORY.md - UNPKG
Disabled options are now focusable and announced by screen-readers but not ... and `aria-label` props are still available and retain their functionality.
Read more >Use a screen reader to change the indentation and spacing ...
This article is part of the Microsoft 365 screen reader support content set where you can find more accessibility information on our apps....
Read more >aria-selected - Accessibility - MDN Web Docs - Mozilla
The aria-selected attribute indicates the current "selected" state for gridcell , option , row and tab roles.
Read more >Creating Accessible React Native Apps (2022) - Shopify
For a full understanding of how to use these tools to test app accessibility, you can read my post Mobile Screen Reader Testing....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’re hoping to merge and release the attached PR that fixes this issue as part of 3.2. We don’t have an ETA at the moment, but my guess is that it will happen sometime in the next month.
@bladey Any plans to merge this PR? We are looking forward for this fix.