What is the accessibility-a11y skill?
The accessibility-a11y skill is a SKILL.md from the Mindrally/skills collection, converted from Cursor rules. It tells your coding agent to follow WCAG, prefer semantic HTML, use ARIA only where needed, keep focus visible, support keyboard use and respect reduced motion and contrast preferences.
accessibility-a11y is one of more than 265 skills in the Mindrally/skills repo, which converts Cursor rules into SKILL.md files. This one tells an agent to follow WCAG so interfaces work for people with visual, auditory, motor and cognitive disabilities.
It is a guideline list, not a scanner. The skill sets the standards the agent writes code to, from semantic landmarks and form labels to contrast ratios and keyboard handling.
What changes in your agent's output
- Real elements such as button, nav, main and header instead of generic divs, with heading levels that do not skip
- Labels tied to inputs with for and id, fieldset and legend for groups, and clear error messages
- ARIA used only where native HTML is not enough, for example aria-label, aria-expanded, aria-live and aria-current
- Contrast targets of 4.5 to 1 for normal text and 3 to 1 for large text
- Visible focus styles, logical tab order and no keyboard traps
Testing guidance is included too: Lighthouse and axe-core in automation, screen readers such as NVDA, JAWS and VoiceOver, keyboard only passes and browser zoom at 200 percent. For a source level audit with a fixed report format, see fixing-accessibility.
Who it is for
Best for
- Developers building new interfaces who want accessibility rules active from the first prompt
- Teams moving from Cursor rules to the SKILL.md format
- Projects that also want automated checks in CI
Not for
- A formal conformance report. The skill names WCAG but lists guidelines, not success criteria
- Running audits itself. It does not include scripts or a scanner
- Deep per component review. accessibility-per-component is a closer fit
Use it with UiChemy
After you convert a design or AI build to WordPress with UiChemy, check the Elementor or Gutenberg result against the same rules: heading order, alt text, labels and keyboard focus.
How to install Accessibility A11y Skill: WCAG Rules for AI Agents
git clone https://github.com/Mindrally/skills.gitThe repo README describes a separate command line installer for picking single skills from the collection.Clone the repo
Run the command above. The skill is the accessibility-a11y folder at the repo root, holding one SKILL.md.
Copy the folder
Copy accessibility-a11y into ~/.claude/skills/ for all projects, which the README names for Claude Code, or into your own agent's skills directory.
Use it while building
Ask your agent to build or review a component and to apply the accessibility rules.
Check that it loaded
Ask your agent to create a form with a modal dialog. It should use labeled inputs, a real button, visible focus styles and keyboard handling, and mention reduced motion where animation appears.
Key features
- Semantic structureUse header, main, footer, nav, article, section and aside, buttons for actions, landmarks for screen reader navigation and a heading hierarchy that never skips levels.
- Form accessibilityAssociate labels with inputs, group related controls with fieldset and legend, use suitable input types and treat placeholders as hints, not labels.
- ARIA when neededPrefer native elements, add aria-label for unlabeled controls, aria-describedby for context, aria-live for dynamic updates and aria-hidden for decoration.
- Common ARIA patternsrole button only when a non-button must act as one, aria-expanded for collapsibles, aria-current page for navigation and aria-labelledby for visible labels.
- Color and contrastText contrast of 4.5 to 1, or 3 to 1 for large text, never color alone to carry meaning, and testing with color blindness simulators.
- Focus managementVisible focus indicators on every interactive element, outlines never removed without a replacement, logical tab order and managed focus when content changes.
- Keyboard navigationEverything works by keyboard, tabindex 0 or negative one only, Enter and Space on buttons, arrow keys in complex widgets and no keyboard traps.
- Images and mediaDescriptive alt text, empty alt for decoration, captions for video, transcripts for audio and link text that is not click here.
- User preferencesRespect prefers-reduced-motion, prefers-color-scheme and prefers-contrast, support text resizing to 200 percent and touch targets of at least 44 by 44 pixels.
- Testing guidanceLighthouse and axe-core in CI, manual runs with NVDA, JAWS or VoiceOver, keyboard only navigation, browser zoom and testing with disabled users where possible.
Frequently asked questions
What is the accessibility-a11y skill?
It is a SKILL.md from the Mindrally/skills repo that gives a coding agent WCAG based guidance for building inclusive interfaces. It covers semantic HTML, ARIA, contrast, focus, keyboard navigation, alt text, user preferences and testing, converted from a Cursor rules file.
How do I install the accessibility-a11y skill?
Clone Mindrally/skills and copy the accessibility-a11y folder into your agent's skills directory. The README names ~/.claude/skills/ as the global Claude Code location. It also documents a command line installer for choosing single skills from the repo.
Does accessibility-a11y check my code automatically?
No. It is guidance for the agent, not a scanner, and it has no scripts. It does recommend running Lighthouse and axe-core in automation and adding checks to CI, so pair it with those tools to catch what rules alone miss.
Which contrast ratios does the skill use?
It states a minimum of 4.5 to 1 for normal text and 3 to 1 for large text. It also says never to use color as the only way to convey information and to provide icons, patterns or text alongside it.
Is accessibility-a11y a Cursor rule or an agent skill?
The repo says its skills were converted from Cursor rules, which were coding guidelines in .cursorrules files, into the SKILL.md format. The README says the installer places them in Claude Code and more than 70 other agents.
How is it different from fixing-accessibility?
This skill is a broad set of WCAG guidelines the agent follows while writing code. fixing-accessibility is a ranked rule list with a review mode that quotes the exact snippet and proposes a minimal fix, so it suits auditing a file.
Is the accessibility-a11y skill free?
Yes. The Mindrally/skills repo is released under the Apache-2.0 license. The skill is a single text file in a folder, so there is nothing to purchase and nothing to run besides copying it into your agent.
What else should I add for accessibility work?
web-accessibility-skill and accessibility-testing cover other angles, including a WCAG 2.2 quick reference. Combine them with real screen reader and keyboard checks, since no rule file replaces testing on a rendered page.


