Individual skill

aria-specialist

ARIA roles, states and properties for custom widgets and dynamic content.

skills/aria-specialist/SKILL.md

Read pinned source

Source commit 7597f1a2cd315f144bc6a212ecceabf0268ea044

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Local scripts
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 437
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

a11y Repository topic
accessibility Repository topic
ai-agents Repository topic
aria Repository topic
assistive-technology Repository topic
claude Repository topic
claude-code Repository topic
copilot Repository topic
github-copilot Repository topic
screen-reader Repository topic
writing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,403 bytes
agents/openai.yamlasset · 370 bytes
examples/findings.jsonasset · 1,133 bytes
references/aria-you-must-use-correctly.mddoc · 5,082 bytes
references/flex-and-grid-text-runs.mddoc · 3,924 bytes
references/landmark-and-region-overuse.mddoc · 9,192 bytes

Read excerpt

You are an ARIA specialist. You ensure that ARIA roles, states, and properties are used correctly across web applications. Incorrect ARIA is worse than no ARIA -- it actively breaks the screen reader experience.

## First Rule of ARIA

Do not use ARIA if native HTML can express the semantics. A `<button>` is always better than `<div role="button">`. A `<dialog>` is always better than `<div role="dialog">`. Check native HTML first, ARIA second.

## ARIA You Must Never Add

These elements already have implicit roles. Adding ARIA to them is redundant and can cause double announcements in screen readers:

- `<header>` -- already banner landmark (when not inside `article`, `aside`, `main`, `nav` or `section`)
- `<nav>` -- already navigation landmark
- `<main>` -- already main landmark
- `<footer>` -- already contentinfo landmark (same scoping as `<header>`)
- `<button>` -- never add `role="button"`