agentleFS
Sign inStart free
IndrajeetPatilIndrajeetPatil/effective-claude-code-usage/.agents/skills/check-accessibility/SKILL.md

check-accessibility

Skill1 starsChanged 11 days agoCC0-1.0View on GitHub

Audit the deck's accessibility with axe-core (just axe) and keep the a11y extension and accessibility.html working: what each provides, the disabled menu features, which states to inspect, headless runs and WCAG link cues. Use after changing slide markup, styles, HTML widgets, menus or the a11y setup, or when asked for an accessibility check.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. AgnosticUI/agnosticui★ 833same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Verify with just axe, which appends an "Accessibility Report" slide listing axe-core violations.

    line 13
  2. Very specific:

    Do not add axe to index.qmd: it belongs in _quarto-a11y.yml so the deployed deck never ships the axe-core payload.

    line 16
  3. Very specific:

    Keep accessibility.html for code scrolling, menu focus, and vertical-slide semantics.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Check accessibility

  • Verify with just axe, which appends an "Accessibility Report" slide listing axe-core violations. For headless checks, use just axe --no-browser --port 8891.
  • Do not add axe to index.qmd: it belongs in _quarto-a11y.yml so the deployed deck never ships the axe-core payload. -M axe:true cannot enable it, because the format: block in index.qmd takes precedence over CLI metadata.
  • The report alone does not exercise every state. Inspect all slides, revealed fragments, tab panels and menu panels in both presentation and native ?view=scroll modes. Fix actionable findings rather than filtering rules.
  • Links inside muted text need a non-colour cue (e.g. text-decoration: underline) to satisfy WCAG 1.4.1.

The a11y extension and accessibility.html

  • The a11y extension supplies zoom, focus indicators, link underlines, reduced motion, slide isolation, and screen-reader announcements. Install the latest directly from upstream with quarto add mcanouil/quarto-revealjs-a11y --no-prompt (in both justfile and CI). This extension is trusted; do not add version pins, vendoring, or checksum checks.
  • Version 0.2.3's slide-menu patch and settings menu introduce ARIA and contrast failures, so both are disabled in index.qmd.
  • Keep accessibility.html for code scrolling, menu focus, and vertical-slide semantics. This deck has no tabsets, but accessibility.html still ships the shared tabset keyboard handling: the file is copied verbatim across decks and kept in sync by hand, so never trim it locally.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free