[BUG]: Accessibility checker reports 4.1.2 violation while it seems correct
See original GitHub issueProject
accessibility-checker-engine, ruleId: Rpt_Aria_RequiredParent_Native_Host_Sematics
Description
Hello,
The accessibility checker is finding a bug with the carbon-react-component Tab:

However, when I look at the element, I saw that the element with tab role is a child of the ul element with role="tablist"

Steps to reproduce
Steps for reproducing need investigation.
Thank you in advance for any help!
Issue Analytics
- State:
- Created a year ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Technique H64 interpreted as 4.1.2 requiring descriptive ...
I'd say yes. SC 4.1.2 is not about the name being meaningful, but about the name being programmatically determinable. I.e. if the visual...
Read more >Create and verify PDF accessibility, Acrobat Pro
To add bookmarks to the document, select Bookmarks on the Accessibility Checker panel, and choose Fix from the Options menu. In the Structure ......
Read more >Web Content Accessibility Guidelines (WCAG) 2.1 - W3C
While WCAG 2.0 remains a W3C Recommendation, the W3C advises the use of WCAG 2.1 to maximize future applicability of accessibility efforts. The ......
Read more >Beware False Negatives - Adrian Roselli
Automated accessibility testing tools are rightly wary of giving false positives. You don't want to flag something as an error in a test...
Read more >Introduction & Information details for the WaaT Tool - accessible
WaaT supports developers and designers and accessibility analyzer in test ... and the corresponding HTML source code (where the violation appears) are ...
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

@shunguoy I see. So it sounds like this is still a violation. Would this still fall under the 4.1.2: Name, Role, Value wcag guideline?
This seems to be working now, @gcattan can you please re-test this on our next release with preview rules. The new release should be available later this week.