● Communauté
geoffreycrofte
⚡ Instantané
luxembourg-accessibility-skillset
par geoffreycrofte · geoffreycrofte/luxembourg-accessibility-skillset
Six skills covering Luxembourg's RAWeb (136 web criteria) and RAAM (108 mobile criteria) accessibility standards — both code generation and audit.
A skillset that makes Claude Code conform to Luxembourg's official accessibility frameworks: RAWeb 1.1 for web (HTML/CSS/JS across 17 themes) and RAAM 1.1 for mobile (iOS SwiftUI/UIKit, Android Compose/XML, React Native, Flutter). Each has a -code and -audit sub-skill. RAPDF is planned. All criteria target Level AA conformance and align with EN 301 549 and WCAG 2.1.
Pourquoi l'utiliser
Fonctionnalités clés
- raweb-code + raweb-audit — RAWeb 1.1, 136 criteria, 17 themes
- raam-code + raam-audit — RAAM 1.1, 108 criteria, 15 themes, multi-framework mobile
- Default Level AA conformance aligned with EN 301 549 and WCAG 2.1
- Works with 30+ AI coding agents via the Agent Skills standard
- Author is a recognized accessibility practitioner (geoffreycrofte)
Démo en direct
Aperçu en pratique
luxembourg-accessibility-skillset-skill.replay
▶ prêt
Cas d'usage
Usages concrets : luxembourg-accessibility-skillset
Quand l'utiliser : You have a deadline and need a structured audit before publication.
Déroulement
-
Point at the code
Use raweb-audit to evaluate src/pages/contact.tsx against all 17 themes. Level AA.✓ Copié
→ Per-criterion pass/fail with line references
-
Fix the failures
For each failed criterion, apply the raweb-code pattern to fix it.✓ Copié
→ Diffs that resolve specific criteria without new regressions
Résultat : An RAWeb-conformant page with a paper trail of what changed.
Pièges
- Fixing a11y by hand can break existing semantics — Always re-run raweb-audit after edits — criteria interact
Quand l'utiliser : New feature — don't want to bolt a11y on later.
Déroulement
-
Describe the screen
Use raam-code — SwiftUI login screen with form, errors, and biometric option. RAAM Level AA.✓ Copié
→ Code with proper accessibility labels, traits, dynamic type, VoiceOver hints
-
Self-audit
Now raam-audit this same file. Anything missed?✓ Copié
→ Clean report or small residual fixes
Résultat : Accessible-by-default mobile code that passes a later audit.
Combinaisons
Associez-le à d'autres MCPs pour un effet X10
luxembourg-accessibility-skillset-skill +
githubOpen a PR that applies audit fixes with per-criterion commits for traceability
Run raweb-audit, fix the failures, and open a PR with one commit per criterion.✓ Copié
luxembourg-accessibility-skillset-skill +
filesystemAudit and fix a whole src/ tree in one pass
Audit every .tsx file under src/pages and fix everything that fails RAWeb AA.✓ Copié
Coût et limites
Coût d'exécution
- Quota d'API
- None
- Tokens par appel
- Audits can be large on big files — budget accordingly
- Monétaire
- Free — skills are local files
- Astuce
- Audit file-by-file rather than whole repo if you hit context limits.
Sécurité
Permissions, secrets, portée
Stockage des identifiants : No credentials — pure prompts
Sortie de données : None — code stays local
- Level AA is the default; AAA criteria are not covered by this skillset.
Dépannage
Erreurs courantes et correctifs
Wrong trigger keywords — audit runs for the wrong standard
Be explicit: 'raam-audit' (mobile) vs 'raweb-audit' (web).
Alternatives
luxembourg-accessibility-skillset vs autres
| Alternative | Quand l'utiliser | Compromis |
|---|
| axe-core / Lighthouse | You want browser-runtime WCAG checks | Runtime vs source-level; no Luxembourg-specific framing |
| Deque skills | You want enterprise-grade a11y tooling with reporting dashboards | Paid; not an agent skill |