Skip to content

Slash command

Accessibility audit

Checks interface changes for the accessibility failures that actually lock people out - not the ones a linter already caught.

About

Checks interface changes for the accessibility failures that actually lock people out - not the ones a linter already caught.

Files in v1.0.0

  • replicamd.plugin.json2464 B
  • skills/accessible-by-default.md2504 B

Contributes

{
  "commands": [
    {
      "id": "diff",
      "title": "Audit the diff for accessibility problems",
      "prompt": "Read the working diff and look only at what it does to people who are not using a mouse and a pair of working eyes.\n\nCheck, in this order:\n1. Can every new control be reached with Tab, and is the focus visible when it lands there? A `focus:outline-none` with nothing replacing it is a blocker, not a nit.\n2. Does every icon-only control have an accessible name? An icon with no label is silence to a screen reader.\n3. Are new interactive elements real buttons and links, or divs with click handlers? A div does not respond to Enter or Space and is not announced as actionable.\n4. Does anything convey meaning by colour alone - a red border, a green dot, a coloured row?\n5. Are new dialogs labelled, focus-trapped, and dismissible with Escape?\n6. Do new images and icons have alt text, or are they correctly marked decorative?\n\nFor each finding name the file, the line, and who it breaks for - \"a keyboard user cannot reach the delete button\" rather than \"missing tabindex\". Skip anything the project's linter already enforces; repeating it wastes the review. If the diff has no user-facing surface, say so instead of padding the list."
    },
    {
      "id": "page",
      "title": "Walk one screen for accessibility",
      "prompt": "Pick the screen I name and walk it the way someone would who cannot use a mouse.\n\nTab from the top and write down the order you land in. Say where focus disappears, where it jumps somewhere unexpected, and where you can see no focus ring at all. Then read the page as a screen reader would: list the landmarks, the heading levels in order, and every control that announces as nothing or as \"button\".\n\nReport it as a walk-through, in the order you hit each problem, with the fix for each one. End with the single change that would help the most - not a ranked list of everything."
    }
  ],
  "skills": [
    "skills/accessible-by-default.md"
  ]
}

Versions

  • v1.0.07/26/2026 · 2 files

Install

Install in ReplicaMD

Nothing happened? ReplicaMD may not be installed yet - or open it first, then Settings → Plugins and install by id.

Plugin id:

a11y-audit

Bundle endpoint:

https://replicamd.nl/api/registry/plugins/a11y-audit/download
Author
Ardjun Debi - Tewarie @ardjun
Latest
v1.0.0
License
MIT
Installs
0
accessibilityfrontendreviewdesign