raam-audit

Accessibility Skillset • v1.5.0

Agent skills for RAWeb, RAAM, and RAPDF, Luxembourg's official accessibility frameworks based on EN 301 549 and WCAG 2.1.

Compatible with skills.sh and the Agent Skills open standard. Works with Claude Code, Cursor, Gemini CLI, GitHub Copilot, and 30+ other AI coding agents.

---

Important: Always consider auditing your website by a human being. AI isn't ready to replace human evaluation, moreover on a topic as complex as accessibility. With or without skills, your AI is just a junior assistant with a lot of flaws. This skills set is only here as an experiment, and as guidelines to help your AI be better at accessibility, not perfect.

---

Available Skills

---

Installation

Via npx (recommended)

# Install the full skillset
npx skills add geoffreycrofte/luxembourg-accessibility-skillset

# Install globally (available in all projects)
npx skills add geoffreycrofte/luxembourg-accessibility-skillset -g

# Install a single skill
npx skills add geoffreycrofte/luxembourg-accessibility-skillset --skill raweb-code

Each skill is self-contained — its references/ and scripts/ ship inside the skill folder, so installing individual skills works out of the box.

Manual installation (Claude Code)

# Project-level
cp -r raweb-code raweb-audit raam-code raam-audit .claude/skills/

# User-level (all projects)
cp -r raweb-code raweb-audit raam-code raam-audit ~/.claude/skills/

Usage

A note on criterion numbers. RAWeb numbering is not WCAG numbering, and the two are easy to conflate — RAWeb 7.3 is keyboard operability; WCAG 2.1.1 is. Every criterion number cited by these skills is checked against the official data by validate-references.sh, because a wrong number in an audit report is worse than no number: it reads as authoritative and nothing contradicts it.

Web development • RAWeb

The raweb-code skill activates automatically when you write front-end web code. It provides:

• Inline accessible code patterns for all 17 RAWeb themes
• Code references for all 30 WAI-ARIA APG patterns, with dos and don'ts in vanilla HTML/CSS/JS, React, Angular, and Web Components — each don't explains the concrete failure it causes for a real user
• Decision tables for the patterns that are usually the wrong choice (role="menu" on site navigation, role="grid" on a read-only table, a treeview for a nav sidebar…)
• ARIA attribute/state and keyboard-interaction tables, rendered from the reference data so they can't go stale
• Pre-commit accessibility checklist
• Lookup commands for specific RAWeb criteria and test methodologies

Invoke explicitly with /raweb-code.

The raweb-audit skill reviews existing code against RAWeb. It provides:

• Theme-by-theme checklists covering every criterion in themes 1–13 (136/136), with each number and each description verified against the 304 official test methodologies — not against the criterion titles, which summarise and routinely under-state scope
• The 7 EN 301 549-only criteria that hide inside ordinary themes (4.14–4.18, 13.13, and 13.14 at Level A) called out explicitly — no WCAG-based scanner reports them, and nothing around them looks unusual enough to prompt a lookup
• Per-component audit scope — show <slug> states which RAWeb criteria a component must satisfy and why, with levels resolved live so they can't be stale
• A defect catalogue — code <slug> gives real production failure modes with their user impact, plus a manual test procedure that states explicitly what axe and Lighthouse will not catch for that pattern
• Structured report format with verdicts (C / NC / NA), severity classification, and WCAG cross-references
• A methodology step for the failure no scanner catches: checking the pattern itself is right, not just its implementation

Invoke explicitly with /raweb-audit.

Mobile development • RAAM

The raam-code skill activates when you write mobile app code. It provides:

• Platform-specific patterns for iOS (SwiftUI/UIKit), Android (Compose/XML), React Native, and Flutter
• Accessible component examples for all 15 RAAM themes
• Cross-platform accessibility API quick reference
• Pre-commit checklist covering screen reader, orientation, text scaling, and gesture requirements

Invoke explicitly with /raam-code. Audit with /raam-audit.

Lookup scripts

Standalone CLI tools for querying criteria and component patterns:

Scripts live inside each skill folder. From the repo root (or from the installed skill directory), invoke them like:

# RAWeb criteria (web) — script lives in raweb-code/scripts/ and raweb-audit/scripts/
./raweb-code/scripts/raweb-lookup.sh topics                       # List all 17 topics
./raweb-code/scripts/raweb-lookup.sh stats                        # Summary statistics
./raweb-code/scripts/raweb-lookup.sh criterion 11.1               # Specific criterion
./raweb-code/scripts/raweb-lookup.sh topic 11                     # All criteria in a topic
./raweb-code/scripts/raweb-lookup.sh methodology 11.1.1           # Test procedure
./raweb-code/scripts/raweb-lookup.sh level AA                     # All Level AA criteria
./raweb-code/scripts/raweb-lookup.sh search "form"                # Search by keyword
./raweb-code/scripts/raweb-lookup.sh glossary "text alternative"  # Glossary lookup

# WAI-ARIA APG component patterns
./raweb-code/scripts/raweb-component-lookup.sh list               # List all 30 patterns
./raweb-code/scripts/raweb-component-lookup.sh find "modal"       # Find pattern by keyword
./raweb-code/scripts/raweb-component-lookup.sh show dialog-modal  # Contract: criteria, keyboard, ARIA (markdown tables)
./raweb-code/scripts/raweb-component-lookup.sh show dialog-modal --plain   # Same, as terminal bullets
./raweb-code/scripts/raweb-component-lookup.sh code dialog-modal          # Code examples, all frameworks
./raweb-code/scripts/raweb-component-lookup.sh code dialog-modal react    # Just the React section
./raweb-code/scripts/raweb-component-lookup.sh roles "dialog"     # Find patterns by ARIA role

# Consistency check — fails if a skill cites a criterion or level that
# contradicts the official RAWeb data, or if a "Do" code example does not parse.
# Exit 1 on drift, so it can gate CI. Ships in every RAWeb skill.
./raweb-code/scripts/validate-references.sh
./raweb-audit/scripts/validate-references.sh

# Keep the -code and -audit skills' shared files identical. Each skill ships its
# own references/ and scripts/ so single-skill installs work; this is what stops
# those copies drifting apart.
./scripts/sync-skills.sh            # copy raweb-code → raweb-audit, raam-code → raam-audit
./scripts/sync-skills.sh --check    # exit 1 if they have diverged (CI gate)

# RAAM criteria (mobile) — script lives in raam-code/scripts/ and raam-audit/scripts/
./raam-code/scripts/raam-lookup.sh topics                         # List all 15 topics
./raam-code/scripts/raam-lookup.sh stats                          # Summary statistics
./raam-code/scripts/raam-lookup.sh criterion 9.1                  # Specific criterion
./raam-code/scripts/raam-lookup.sh topic 9