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.