Agent skill

Accessibility A11y Skill: WCAG Rules for AI Agents

A skill that gives your coding agent a WCAG minded rule set for semantic HTML, ARIA, contrast, focus, keyboard support, media alternatives and user preference queries.

Install
git clone https://github.com/Mindrally/skills.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

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.