Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/aria-text
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid focusable descendants in role='text' elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
1 fixed19 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A test case the skill fixed. Same model, same prompt, with and without the skill.
An inline icon and label are grouped as `<span role="text"><svg aria-hidden="true"><path d="..."></path></svg> Updated yesterday</span>`. Does this markup violate accessibility guidelines?
| Checked | Without skill | With skill |
|---|---|---|
| Confirms this markup is compliant because no focusable descendants are present inside role="text" | Missed | Passed |
The instructions your model reads when the skill loads.
Using role="text" on a container forces screen readers to treat everything inside as a single string of text, which effectively hides any interactive elements from users who rely on assistive technology.
role="text" should not contain interactive children (links, buttons)role="text" only contains static text contentIdentify elements with role="text" and verify they do not contain any focusable elements like buttons, links, or inputs.
Remove role="text" from containers that have interactive children or move the interactive elements outside.
Explain how role="text" overrides the semantics of descendant elements, making interactive components inaccessible to screen reader users.
Review the rendered markup and interactive states that affect Avoid focusable descendants in role="text" elements. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/aria-text
test cases passed, vs 19 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.