AnySurfer Audit Skill
Peteri3/anysurfer-audit-skill
Auditorias de acessibilidade web contra WCAG 2.2 AA e AnySurfer
Ver no GitHubSkill do Claude que avalia componentes web e designs (Figma/Penpot) contra a metodologia AnySurfer e critérios WCAG 2.2 AA. Realiza auditorias estruturadas de acessibilidade a partir de HTML, URLs, screenshots e descrições, identificando problemas de contraste, semântica, ARIA e conformidade legal belga.
Instalação
npx convez-ai Peteri3/anysurfer-audit-skill1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Validar acessibilidade de componentes web antes de deploy
- Avaliar designs no Figma/Penpot contra padrões de acessibilidade
- Verificar conformidade legal com regulamentações belgas (EAA)
- Auditar contraste de cores, hierarquia de headings e semântica ARIA
Veredito

Ferramenta prática para auditorias de acessibilidade em contexto belga, com suporte a múltiplos formatos de entrada (HTML, URLs, Figma). Limitação: análise estática sem teste em navegadores reais com tecnologia assistiva; eficácia depende fortemente do formato e completude do input (HTML auto-contido é ideal).
README
A tradução para o português deste README ainda está na fila.
AnySurfer Audit — Claude Skill
A Claude skill for evaluating web components and Figma/Penpot designs against the AnySurfer methodology and WCAG 2.2 AA criteria.
Unofficial. This skill is not a product of AnySurfer or Blindenzorg Licht en Liefde. It is a personal implementation based on publicly available WCAG 2.2 criteria and the publicly documented AnySurfer audit approach.
What does this skill do?
When you share a web component, Figma link, HTML fragment, or live URL in Claude and ask for an accessibility audit, this skill activates automatically and performs a structured evaluation based on:
- WCAG 2.2 success criteria (levels A and AA)
- AnySurfer label structure (minimum level A, target level AA)
- Belgian legal context (EAA, Royal Decree 05/09/2019, Flemish Governance Decree 2018)
Supported input types
| Input | What is evaluated |
|---|---|
| HTML/CSS/JS fragment | Semantics, ARIA, keyboard access, contrast |
| Figma or Penpot URL/screenshot | Colour contrast, focus states, touch target sizes, annotations |
| Live URL | Static evaluation via web fetch |
| Description or wireframe | Conceptual audit with recommendations |
Audit quality depends on input completeness
The depth and accuracy of the audit varies significantly depending on what Claude can actually read.
For the most complete audit — use a single self-contained HTML file with CSS in a <style> block and JS inline or in a <script> block. This gives Claude access to your actual colour values, font sizes, component structure, and interaction logic in a single pass, enabling full contrast calculations, semantic analysis, ARIA evaluation, and JS behaviour assessment.
External CSS files reduce audit quality. When a page links to an external stylesheet (<link rel="stylesheet" href="...">), Claude can fetch the HTML structure but cannot follow the stylesheet reference. Class names are visible but their computed values — colours, font sizes, spacing — are not. Contrast ratios cannot be calculated. To work around this, either paste your CSS into a <style> block, or share the CSS file separately alongside the URL.
Bootstrap and third-party CSS can be omitted. Claude has working knowledge of Bootstrap's default styles and accessibility patterns. Only your custom CSS is needed. Removing framework CSS significantly reduces file size without losing audit coverage.
Live URL audits are structural only. Fetching a live URL returns the HTML content but not the rendered styles. The audit covers semantics, heading hierarchy, ARIA attributes, landmark structure, link text, alt text, and form labels — but not contrast ratios or visual layout unless colours appear as inline styles.
JavaScript-driven components have inherent limits. Static analysis can identify missing ARIA attributes and flag patterns that are known to cause issues, but cannot verify runtime behaviour — focus management, live region updates, or dynamic state changes can only be confirmed through browser testing with real assistive technology.
File size guidelines
Claude's context window limits how much text can be processed in a single conversation. History already in the conversation counts toward this limit, so a fresh conversation always gives more headroom than a long one.
| Input size | Expectation |
|---|---|
| Single component or page section | No practical limit |
| Full page HTML + custom CSS (combined) | Works well up to ~100KB |
| Above 100KB combined | Split into separate audits per section, or strip irrelevant content (long body copy, repeated list items, data tables) |
| Large SPA with generated HTML | Audit individual components or views, not the full page output |
Stripping Bootstrap and other third-party CSS before sharing typically reduces file size by 80% and is always recommended. For large files, start a fresh conversation dedicated to the audit rather than continuing a long existing one.
Output
The audit report includes:
- Findings per WCAG principle (Perceivable / Operable / Understandable / Robust)
- Severity levels: 🔴 Critical · 🟠 Important · 🟡 Minor
- Estimated AnySurfer label status (Level A / AA)
- Colour contrast table
- Prioritised fix list
- Next steps towards the AnySurfer label
Installation
- Download the
anysurfer-audit.skillfile - In Claude, go to Settings → Skills
- Click Install from file and select the
.skillfile - The skill is active in your next conversation
Requires Claude Pro or higher with Skills access.
How to trigger this skill
This skill is intentionally scoped to AnySurfer and Belgian accessibility compliance. It does not activate on generic accessibility questions — those are handled by Claude's built-in accessibility-review skill, which avoids conflicts when both are installed simultaneously.
To activate this skill, do one of the following:
- Mention AnySurfer in your prompt — e.g. "Audit this component for AnySurfer", "Does this meet AnySurfer level AA?", "Check this design against the AnySurfer label criteria"
- Reference Belgian compliance — e.g. "Is this EAA compliant?", "Check this for Belgian accessibility law"
- Select the skill manually — In Claude, type
/to open the skill picker and selectanysurfer-auditdirectly
Generic prompts like "is this accessible?" or "check a11y" will route to the built-in accessibility skill, not this one. That is by design.
MCP design tool integrations
The skill supports direct integration with design tools via MCP connectors, enabling live inspection of design files rather than relying on screenshots or exports.
| Tool | Status | What it enables |
|---|---|---|
| Penpot | Tested | Reads fill colours, font sizes, component dimensions, layer names — full contrast and touch target audit from live file data |
| Figma | Available, untested | Exposes get_design_context, get_variable_defs, get_metadata, and get_screenshot — likely supports the same audit depth as Penpot once tested |
To use with Penpot: Install the Claude MCP plugin inside Penpot, keep it running while auditing, then select a board and prompt Claude with "Audit this for AnySurfer".
To use with Figma: Connect the Figma MCP in Claude Settings → Connectors, open your file in Figma, then prompt Claude with "Audit this for AnySurfer". The integration has not been formally tested against this skill yet — feedback welcome via GitHub issues.
Without a connected MCP tool, the skill falls back to screenshot or exported HTML analysis.
File structure
anysurfer-audit/
├── SKILL.md # Skill instructions and audit checklist
└── references/
├── wcag22-quick-ref.md # All WCAG 2.2 A/AA criteria with thresholds
└── anysurfer-context.md # Belgian legal framework and label process
Belgian context
This skill is particularly useful for:
- Belgian public sector organisations — WCAG 2.1 AA is legally required (Royal Decree 2019 + Flemish Governance Decree)
- Private sector — EAA compliance mandatory from 28 June 2025 for e-commerce, banking, transport, telecom, e-books and audiovisual services
- Web developers and agencies seeking to obtain or demonstrate the AnySurfer label to clients
Related standards and resources
- WCAG 2.2 — W3C
- AnySurfer — Blindenzorg Licht en Liefde
- EN 301 549 — European ICT accessibility standard
- European Accessibility Act (Directive EU 2019/882)
- Royal Decree 05/09/2019 — Belgian transposition of the Web Accessibility Directive
License
The WCAG criteria are based on the W3C Web Content Accessibility Guidelines, published under the W3C Document License. AnySurfer is a trademark of Blindenzorg Licht en Liefde vzw. This project has no official affiliation with AnySurfer or W3C.