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 Include required ARIA attributes for roles. 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-01 | ✗→✓ | ▲ Improved | 4% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | 112% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | 160% | 0% |
| case-04 | ✓→✓ | ＝ Same ✓ | 67% | 0% |
| case-05 | ✓→✓ | ＝ Same ✓ | 119% | 0% |
Certain ARIA roles are incomplete without their required attributes, preventing assistive technologies from correctly communicating the element's state or value.
aria-valuenow for sliders are presentVerify that all ARIA roles have their mandatory attributes as defined by the WAI-ARIA specification.
Add the missing required ARIA attributes to elements with specific roles (e.g., aria-valuenow for role="slider").
Explain how required ARIA attributes provide critical state information that screen readers need to function correctly.
Review the rendered markup and interactive states that affect Include required ARIA attributes for roles. 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-required-attr
Other measured skills in the registry, with their headline benchmark lift.