Skill not invoked — Claude uses generic WCAG advice

Name the sub-skill explicitly ('raweb-audit', 'raam-code'). Plain WCAG prompts won't route to RAWeb.

SKILL.md frontmatter wrong in one sub-skill

Each sub-skill has its own SKILL.md; inspect the specific folder.

freemcplab / 디렉터리 / 플레이그라운드 / luxembourg-accessibility-skillset

← 모든 서버 ↗ GitHub

● 커뮤니티 geoffreycrofte ⚡ 바로 사용

luxembourg-accessibility-skillset

Name: luxembourg-accessibility-skillset (Claude Skill)
Author: geoffreycrofte

제작: 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.

▶ 데모 보기 📦 설치 💡 사용 사례

왜 쓰나요

핵심 기능

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)

라이브 데모

실제 사용 모습

luxembourg-accessibility-skillset-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: luxembourg-accessibility-skillset

Audit a public-sector website against RAWeb before a submission deadline

👤 Luxembourg agencies and vendors required to meet RAWeb ⏱ ~90 min intermediate

언제 쓸까: You have a deadline and need a structured audit before publication.

흐름

Point at the code

Use raweb-audit to evaluate src/pages/contact.tsx against all 17 themes. Level AA.✓ 복사됨

→ Per-criterion pass/fail with line references
Fix the failures

For each failed criterion, apply the raweb-code pattern to fix it.✓ 복사됨

→ Diffs that resolve specific criteria without new regressions

결과: An RAWeb-conformant page with a paper trail of what changed.

함정

Fixing a11y by hand can break existing semantics — Always re-run raweb-audit after edits — criteria interact

함께 쓰기: github · filesystem

Generate accessible mobile screens (SwiftUI / Compose) from the start

👤 Mobile engineers building for Luxembourg public sector ⏱ ~45 min intermediate

언제 쓸까: New feature — don't want to bolt a11y on later.

흐름

Describe the screen

Use raam-code — SwiftUI login screen with form, errors, and biometric option. RAAM Level AA.✓ 복사됨

→ Code with proper accessibility labels, traits, dynamic type, VoiceOver hints
Self-audit

Now raam-audit this same file. Anything missed?✓ 복사됨

→ Clean report or small residual fixes

결과: Accessible-by-default mobile code that passes a later audit.

조합

다른 MCP와 조합해 10배 효율

luxembourg-accessibility-skillset-skill + github

Open 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.✓ 복사됨

luxembourg-accessibility-skillset-skill + filesystem

Audit and fix a whole src/ tree in one pass

Audit every .tsx file under src/pages and fix everything that fails RAWeb AA.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
raweb-code	component intent + pattern (form / table / nav / modal)	Writing new web code
raweb-audit	file path or code block	Before submission or PR review
raam-code	screen intent + framework (SwiftUI/Compose/RN/Flutter)	Writing new mobile screens
raam-audit	file path or code block + framework	Pre-release mobile audit

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Audits can be large on big files — budget accordingly
금액: Free — skills are local files
팁: Audit file-by-file rather than whole repo if you hit context limits.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials — pure prompts

데이터 외부 송신: None — code stays local

Level AA is the default; AAA criteria are not covered by this skillset.

문제 해결

자주 발생하는 오류와 해결

Wrong trigger keywords — audit runs for the wrong standard

Be explicit: 'raam-audit' (mobile) vs 'raweb-audit' (web).

대안