Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use only allowed ARIA attributes for each role. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-14 | ✗→✓ | ▲ Improved | 20% | 0% |
| case-06 | ✓→✗ | ▼ Worse | 5% | 0% |
| case-09 | ✓→✗ | ▼ Worse | 22% | 0% |
| case-13 | ✓→✗ | ▼ Worse | 13% | 0% |
| case-20 | ✓→✗ | ▼ Worse | 3% | 0% |
Invalid ARIA attributes are ignored by screen readers or may cause them to misinterpret the element's purpose, leading to a broken experience for users with disabilities.
Verify that all ARIA attributes used on elements are valid for their assigned WAI-ARIA roles.
Remove or correct ARIA attributes that are not supported by the element's current ARIA role.
Explain why using only role-supported ARIA attributes is necessary for proper screen reader communication.
Review the rendered markup and interactive states that affect Use only allowed ARIA attributes for each role. 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/en/rules/accessibility/aria-allowed-attr
Other measured skills in the registry, with their headline benchmark lift.