TableExpandRow button fails IBM Equal Access A11y Checker
See original GitHub issueBrowser Chrome
Automated testing tool and ruleset Latest
Assistive technology used to verify IBM Equal Access A11y Checker
Detailed description
Failure is: An input element must have an associated visible label
<button type="button" class="bx--table-expand__button" aria-label="Expand current row">...</button>
The button is getting flagged by the tool.
What version of the Carbon Design System are you using? 10
- Screenshots or code
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
IBM Equal Access Toolkit
Create inclusive experiences with the provided tools and guidance. Tools. Gather the tools needed for your accessibility journey.
Read more >IBM Equal Access Toolkit Now Available to Develop ...
The Equal Access Toolkit and Checker are tools for developers and testers to use to embed accessibility directly into their workflow.
Read more >sitemap-questions-164.xml - Stack Overflow
... com/questions/1139050/how-to-ignore-duplicate-key-error-in-t-sql-sql-server ... ://stackoverflow.com/questions/6697461/check-if-all-table-rows-are-equal ...
Read more >IBM's new open-source tool helps developers make their apps ...
IBM's new tools are divided into two parts: a set of public guidelines called IBM Equal Access Toolkit and a Checker that identifies ......
Read more >IBM Equal Access Accessibility Checker version history
IBM Equal Access Accessibility Checker by IBM Accessibility ... Fix engine failure with an existing 'ace' object in ... Info button fix in...
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
Conferred with the team, and we agree with Josh that this issue should not apply to buttons. Will track this as a defect in the checker rules: https://github.com/IBMa/equal-access/issues/204
The aria-label was checked as part of a separate rule / success criteria, and that will continue to be checked.
Thanks for circling back with us @tombrunet and giving us some more background! Going to close this one out as fixed via https://github.com/IBMa/equal-access/pull/205