Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid using deprecated ARIA roles. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
63
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/aria-deprecated-role/SKILL.mdUsing deprecated roles can lead to inconsistent behavior across different browsers and screen readers as they transition to newer standards.
Search the codebase for deprecated ARIA roles like directory or abstract roles that shouldn't be used in HTML.
Update deprecated ARIA roles to their modern recommended equivalents or use native HTML elements.
Explain the risks of using deprecated ARIA roles and the benefits of moving to modern ARIA standards.
Review the rendered markup and interactive states that affect Avoid using deprecated ARIA 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-deprecated-role
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.