/ Каталог / Песочница / luxembourg-accessibility-skillset
← Все серверы ↗ GitHub
● Сообщество geoffreycrofte ⚡ Сразу

luxembourg-accessibility-skillset

автор 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.

▶ Смотреть демо 📦 Установить 💡 Сценарии

Зачем использовать

Ключевые функции

Живое демо

Как выглядит на практике

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.

Поток
  1. 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
  2. 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.

Поток
  1. 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
  2. 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 — эффект x10

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 0
raweb-audit file path or code block Before submission or PR review 0
raam-code screen intent + framework (SwiftUI/Compose/RN/Flutter) Writing new mobile screens 0
raam-audit file path or code block + framework Pre-release mobile audit 0

Стоимость и лимиты

Во что обходится

Квота 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

Устранение неполадок

Частые ошибки и исправления

Wrong trigger keywords — audit runs for the wrong standard

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

Альтернативы

luxembourg-accessibility-skillset в сравнении

АльтернативаКогда использоватьКомпромисс
axe-core / LighthouseYou want browser-runtime WCAG checksRuntime vs source-level; no Luxembourg-specific framing
Deque skillsYou want enterprise-grade a11y tooling with reporting dashboardsPaid; not an agent skill

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills