⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v1.6.0

raam-audit

geoffreycrofte@geoffreycrofte⭐ 33 stars· last commit 12d ago· 0 open issues

>

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 33 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Accessibility Skillset • v1.6.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

SkillFrameworkDescriptionStatus
raweb-codeRAWeb 1.1Write accessible web code (HTML/CSS/JS)✅ Ready
raweb-auditRAWeb 1.1Audit web code against RAWeb criteria✅ Ready
raam-codeRAAM 1.1Write accessible mobile apps (iOS/Android/RN/Flutter)✅ Ready
raam-auditRAAM 1.1Audit mobile apps against RAAM criteria✅ Ready
rapdf-codeRAPDFGenerate accessible PDFs🔜 Planned
rapdf-auditRAPDFAudit PDFs against RAPDF criteria🔜 Planned

Installation

Claude Code plugin

/plugin install luxembourg-accessibility --marketplace geoffreycrofte/luxembourg-accessibility-skillset

On Claude Code versions older than 2.1.275, add the marketplace first:

/plugin marketplace add geoffreycrofte/luxembourg-accessibility-skillset
/plugin install luxembourg-accessibility@luxembourg-accessibility-skillset

The plugin installs all four skills. Updates arrive with /plugin marketplace update luxembourg-accessibility-skillset.

Via npx (any compatible agent)

# 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/

Claude.ai and the Claude desktop app

Zip the skill folder you need (one zip per skill), then upload it in Settings → Capabilities → Skills:

git archive --format=zip --prefix=raweb-code/ -o raweb-code.zip HEAD:raweb-code

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

# First-pass scan of source files for common defects (raweb-audit only).
# Every hit is a lead to confirm against the criterion's tests, not a verdict.
./raweb-audit/scripts/raweb-scan.sh src/

# Consistency check — fails if a skill cites a criterion or level that
# contradicts the official RAWeb data, or if a "Do" code example does

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • raam-audit/SKILL.md7.8 KBupstream ↗
    ---
    name: raam-audit
    description: >
      Audit mobile applications (iOS and Android) against RAAM 1.1 (Luxembourg Mobile
      Accessibility Assessment Framework). Use when reviewing existing mobile app code
      for accessibility compliance, generating audit reports, checking conformance
      levels, or preparing for Luxembourg accessibility certification. Covers all 15
      themes with platform-specific test procedures. Default target: Level AA.
    metadata:
      author: Geoffrey Crofte
      version: 1.5.0
      raam-version: "1.1"
      wcag-version: "2.1"
      en301549-version: "3.2.1"
      license: CC-BY-4.0
      repository: https://github.com/geoffreycrofte/luxembourg-accessibility-skillset
      reference: https://github.com/accessibility-luxembourg/ReferentielAccessibiliteMobile
      reference-license: CC-BY-3.0-LU
    allowed-tools: Bash Read Grep
    ---
    
    # RAAM 1.1 — Mobile Accessibility Audit Skill
    
    You are a mobile accessibility auditor. When asked to audit code, you systematically
    evaluate it against **RAAM 1.1** criteria (Level AA by default). RAAM is Luxembourg's
    official mobile accessibility framework implementing EN 301 549 v3.2.1 / WCAG 2.1.
    
    ## Reference data
    
    ```bash
    # List all topics
    !`${CLAUDE_SKILL_DIR}/scripts/raam-lookup.sh topics`
    
    # Look up a specific criterion
    bash ${CLAUDE_SKILL_DIR}/scripts/raam-lookup.sh criterion <topic.criterion>
    
    # Full test methodology (iOS & Android steps)
    bash ${CLAUDE_SKILL_DIR}/scripts/raam-lookup.sh methodology <topic.criterion>
    
    # All criteria at a given level
    bash ${CLAUDE_SKILL_DIR}/scripts/raam-lookup.sh level AA
    
    # Search criteria by keyword
    bash ${CLAUDE_SKILL_DIR}/scripts/raam-lookup.sh search "<keyword>"
    
    # Glossary definitions
    bash ${CLAUDE_SKILL_DIR}/scripts/raam-lookup.sh glossary "<term>"
    ```
    
    Raw JSON files: `${CLAUDE_SKILL_DIR}/references/`
    
    ---
    
    ## Audit methodology
    
    ### Step 1: Determine scope
    
    Before auditing, clarify:
    - **Platform**: iOS, Android, or both (cross-platform frameworks like React Native/Flutter count as both)
    - **Target level**: A or AA (default: AA)
    - **Scope**: full app, specific screen, or specific component
    - **Themes to focus on**: all 15, or specific themes relevant to the content
    
    ### Step 2: Systematic evaluation by theme
    
    For each applicable theme, follow the official RAAM test methodologies.
    ALWAYS look up the methodology before rendering a verdict — methodologies contain
    **platform-specific steps** for both iOS and Android:
    
    ```bash
    bash ${CLAUDE_SKILL_DIR}/scripts/raam-lookup.sh methodology <topic.criterion>
    ```
    
    ### Step 3: Report findings
    
    Use the structured report format below.
    
    ---
    
    ## Audit execution: Theme-by-theme checklist
    
    For each criterion, apply: **C** (Conforming), **NC** (Non-conforming), **NA** (Not applicable).
    
    ### Theme 1 — Graphic Elements (9 criteria)
    Scan for: image components, icons, decorative elements, content descriptions, accessibility labels.
    
    | Check | Criteria | Level |
    |-------|----------|-------|
    | Decorative graphics hidden from AT | 1.1 | A |
    | Informative graphics have text alternatives | 1.2 | A |
    | Text alternatives are relevant | 1.3 | A |
    | CAPTCHA graphics describe nature/function | 1.4 | A |
    | CAPTCHA has non-graphic alternative | 1.5 | A |
    | Complex graphics have detailed descriptions | 1.6 | A |
    | Detailed descriptions are relevant | 1.7 | A |
    | Text graphics have styled-text alternatives | 1.8 | AA |
    | Graphics with captions are correctly grouped | 1.9 | AA |
    
    **Code patterns to scan:**
    
    ```bash
    # iOS: images without accessibility labels
    grep -rn 'Image(' --include="*.swift" | grep -v 'accessibilityLabel\|accessibilityHidden\|decorative'
    
    # Android: images without content descriptions
    grep -rn 'Image(' --include="*.kt" | grep -v 'contentDescription'
    grep -rn 'ImageView' --include="*.xml" | grep -v 'contentDescription\|importantForAccessibility'
    
    # React Native: images without labels
    grep -rn '<Image' --include="*.tsx" --include="*.jsx" | grep -v 'accessibilityLabel\|accessible={false}'
    ```
    
    ### Theme 2 — Colours (4 criteria)
    Requires visual inspection and contrast tools.
    
    | Check | Criteria | Level |
    |-------|----------|-------|
    | Information not conveyed by colour alone | 2.1 | A |
    | Text contrast ≥ 4.5:1 / 3:1 (large) | 2.2 | AA |
    | Non-text element contrast ≥ 3:1 | 2.3 | AA |
    | Contrast replacement mechanism accessible | 2.4 | AA |
    
    **Code patterns to scan:**
    ```bash
    # Hardcoded colours that may have contrast issues
    grep -rn '#[0-9a-fA-F]\{6\}\|rgb(' --include="*.swift" --include="*.kt" --include="*.xml" --include="*.tsx"
    
    # iOS: check for semantic/adaptive colours
    grep -rn 'UIColor\|Color(' --include="*.swift" | grep -v 'semantic\|system\|primary\|label'
    ```
    
    ### Theme 3 — Multimedia (18 criteria)
    Scan for: video/audio players, media components.
    
    | Check | Criteria | Level |
    |-------|----------|-------|
    | Audio-only has text transcript | 3.1 | A |
    | Audio transcript is relevant | 3.2 | A |
    | Video-only has alternative | 3.3 | A |
    | Video-only alternative is relevant | 3.4 | A |
    | Synchronised media has alternative | 3.5 | A |
    | Synchronised media alternative is relevant | 3.6 | A |
    | Synchronised media has captions | 3.7 | A |
    | Captions are relevant and synchronised | 3.8 | A |
    | Video has audio description | 3.9 | AA |
    | Audio description is relevant | 3.10 | AA |
    | Media has adjacent identifying text | 3.11 | A |
    | Auto-playing audio ≤ 3s or controllable | 3.12 | A |
    | Player has play/pause/mute controls | 3.13 | A |
    | Caption/AD toggles at same level as play | 3.14 | AA |
    | Captions preserved on transmit/convert | 3.15 | AA |
    | AD preserved on transmit/convert | 3.16 | AA |
    | Captions are customisable | 3.17 | AA |
    | Captions key features preserved | 3.18 | AA |
    
    ### Theme 4 — Tables (5 criteria)
    
    | Check | Criteria | Level |
    |-------|----------|-------|
    | Complex table has title | 4.1 | A |
    | Complex table has summary | 4.2 | A |
    | Simple table has title | 4.3 | A |
    | Table headers correctly associated | 4.4 | A |
    | Table data cells associated with headers | 4.5 | A |
    
    ### Theme 5 — Interactive Components (5 criteria)
    
    | Check | Criteria | Level |
    |-------|----------|-------|
    | Components keyboard/switch accessible | 5.1 | A |
    | Components have accessible names | 5.2 | A |
    | Accessible names include visible text | 5.3 | A |
    | Context changes announced to AT | 5.4 | AA |
    | Component states exposed to AT | 5.5 | A |
    
    **Code patterns to scan:**
    ```bash
    # Custom interactive elements missing accessibility
    grep -rn 'onTap\|onClick\|onPress' --include="*.swift" --include="*.kt" --include="*.tsx" | grep -v 'accessibilityLabel\|contentDescription\|accessibilityRole'
    
    # Missing state announcements
    grep -rn 'isExpanded\|isSelected\|isEnabled\|isChecked' --include="*.swift" --include="*.kt" | grep -v 'accessibilityValue\|stateDescription\|accessibilityState'
    ```
    
    ### Theme 6 — Mandatory Elements (2 criteria)
    
    | Check | Criteria | Level |
    |-------|----------|-------|
    | Screen has a title announced by AT | 6.1 | A |
    | App language is identifiable by AT | 6.2 | A |
    
    **Code patterns to scan:**
    ```bash
    # iOS: screens without navigation title
    grep -rn 'struct.*View.*:.*View' --include="*.swift" | head -20
    grep -rn 'navigationTitle\|title =' --include="*.swift"
    
    # Android: activities without labels
    grep -rn '<activity' --include="*.xml" | grep -v 'android:label'
    ```
    
    ### Theme 7 — Information Structure (2 criteria)
    
    | Check | Criteria | Level |
    |-------|----------|-------|
    | Headings use correct semantics | 7.1 | A |
    | Significant elements use proper semantics | 7.2 | A |
    
    **Code patterns to scan:**
    ```bash
    # iOS: text styled as heading but missing trait
    grep -rn '\.font(.title\|\.font(.headline\|\.font(.subhead' --include="*.swift" | grep -v 'isHeader\|accessibilityAddTraits'
    
    # Android: styled headings without semantics
    grep -rn 'headlineMedium\|headlineSmall\|titleLarge' --include="*.kt" | grep -v 'heading()'
    ```
    
    ### Theme 8 — Presentation of Information (7 criteria)
    
    | Check | Criteria | Level |
    |-------|----------|-------|
    | Content usable at 200% system text size | 
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/geoffreycrofte-luxembourg-accessibility-skillset-raam-audit.md

// REPO STATS

33 stars
0 open issues
Last commit: 12d ago