QSelect input now fails WCAG 2.0 A standards
See original GitHub issueDescribe the bug The changes introduced by #9983 cause QSelects to actively fail WCAG 2.0 A checks in axe-core now. Admittedly, the change is more accessible, but now fails standards checks whereas before it was less accessible but passed the check. 😃
The specific violations:
- Ensures ARIA attributes are allowed for an element’s role: ARIA attribute is not allowed: aria-multiselectable=“false”
- Likely Remedy:
aria-multiselectable
belongs on the element withrole="listbox"
- Likely Remedy:
- aria-labelledby or aria-label attribute does not exist, references elements that do not exist or references elements that are empty
- Likely Remedy: Should add
aria-label
similar to how QInput behaves.
- Likely Remedy: Should add
- Invalid ARIA attribute value: aria-activedescendant=“f_a1004b26-2180-4fad-8186-a3b48c387fe1_-1”
- Likely Remedy:
aria-activedescendant
must be a descendant of the element or in thearia-owns
comma-separated list. The current implementation puts the element withrole="listbox"
in thearia-owns
attr rather than the individual elements that haverole="option"
. Use comma-separated list ofrole="option"
items in thearia-owns
attribute. (This one is silly, the implementation here is cleaner, but this is what the spec says)
- Likely Remedy:
Codepen/jsFiddle/Codesandbox (required) Codepen doesn’t really describe the problem. The described violations occur when running Axe devtools on quasar.dev.
Expected behavior No accessibility violations.
Platform (please complete the following information): Quasar Version: 1.15.23
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:18 (7 by maintainers)
Top Results From Across the Web
Understanding Success Criterion 3.2.2 - W3C
Techniques and Failures for Success Criterion 3.2. 2 - On Input. Each numbered item in this section represents a technique or combination of...
Read more >Web Content Accessibility Guidelines (WCAG) 2.0 - W3C
(Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.) Time-Based Media: If non-text content is ...
Read more >WCAG 2 Overview | Web Accessibility Initiative (WAI) - W3C
Introduces the Web Content Accessibility Guidelines (WCAG) international standard, including WCAG 2.0, WCAG 2.1, and WCAG 2.2. WCAG documents explain how to ...
Read more >WCAG 2 FAQ | Web Accessibility Initiative (WAI) - W3C
Answers to some frequently asked questions (FAQ) about Web Content Accessibility Guidelines (WCAG).
Read more >F36: Failure of Success Criterion 3.2.2 due to ... - W3C
It is better to rely on the standard form behavior of the submit button and enter key. Examples. Failure Example 1: This failure...
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 FreeTop 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
Top GitHub Comments
Wow, very nice report. Let me digest it over the weekend and I’ll be back with news. Thank you.
Try “quasar”: “https://github.com/pdanpdan/quasar#quasar-pdan-v1.15.23-beta.3”