Check whether ARIA attributes, which describe interface elements to assistive technology, are supported by each element’s role. Review rendered HTML and interactive states, identify invalid combinations, and suggest removals or corrections to support accurate screen reader interpretation.
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.
Checks whether the ARIA attributes attached to interface elements are supported by those elements’ roles. ARIA provides information about an element’s meaning and state to assistive technology. Different roles allow different attributes, so the review identifies unsupported combinations and recommends removing or correcting them. It helps make the information a browser passes to assistive technology meaningful and consistent with the element’s role.
Use it when reviewing interactive controls, shared components, or a design system. It starts with the meaning built into native HTML elements, then examines the HTML actually rendered and the states that occur during interaction. Where needed, it also checks keyboard operation, focus movement, and the names read aloud by assistive technology, pointing to the specific elements with problems.
There are no special notes.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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/rules/accessibility/aria-allowed-attr
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.