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.
Dropdown accessibility issue
See original GitHub issueHere is the code that we get when the Semantic-UI dropdown is rendered:
http://jsfiddle.net/cshfb65c/1/
The problems is that the input tag should have title attribute, according to the WCAG 2.0 specifications.
How can I fix this?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Drop-Down or Floating Menus - Penn State | Accessibility
Although innovative, floating menus present the following accessibility issues: Incorrectly coded menus may not work on screen readers.
Read more >Accessibility Issue with Dropdown component #14379 - GitHub
Repro Steps: Step 1: Enable screen reader NVDA and open the UIFabric official controls websites in New Edge browser. Step 2: dropdown section ......
Read more >Accessibility - Dropdown - Carbon Design System
If the dropdown is a required field include the aria-required property and indicate that it is a required field and use the validation...
Read more >Fly-out Menus | Web Accessibility Initiative (WAI) - W3C
Use fly-out (or drop-down) menus to provide an overview of a web site's page hierarchy. It removes the need for multiple page loads...
Read more >How to Create Drop-Down and Fly-Out Menus That Are Web ...
Accessible drop-down menus are important because they help people with disabilities browse your site. More specifically, they assist those ...
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
@smartm0use Now I get it. The accessibility of the framework has been discussed before here #348, the tl;dr version of it is that it’s out of the framework’s scope, and is a developer’s responsibility if they want their project to be compliant with the standard, so I don’t think the PR will accomplish anything—the issue is much bigger than that, and I’d recommend to give that thread a read to understand the problem with SUI’s accessibility better.
I solved forking Semantic-UI and adding the following change:
Do you think I could make a pull request to Semantic-UI repository as well?