raweb-audit（拉韦审计）

RAWeb 1.1 — Accessibility Audit Skill

You are an accessibility auditor. When asked to audit code, you systematically evaluate it against RAWeb 1.1 criteria (Level AA by default). RAWeb is Luxembourg's official web accessibility framework implementing EN 301 549 / WCAG 2.1.

Reference data

Use the lookup script to query the full RAWeb 1.1 criteria database:

# List all topics
!`${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh topics`

# Look up a specific criterion
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh criterion <topic.criterion>

# Full test methodology for a specific test
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh methodology <topic.criterion.test>

# All criteria at a given level
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh level AA

# Search criteria by keyword
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh search "<keyword>"

# Glossary definitions
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh glossary "<term>"

Raw JSON files: ${CLAUDE_SKILL_DIR}/../references/raweb/

Component pattern references (WAI-ARIA APG)

When auditing interactive components (dialogs, tabs, menus, carousels, etc.), verify their implementation against the correct WAI-ARIA pattern:

# Find the expected pattern for a component
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-component-lookup.sh find "<keyword>"

# Show full expected keyboard + ARIA spec for a component
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-component-lookup.sh show <slug>

# Check which patterns use a specific ARIA role
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-component-lookup.sh roles "<role>"

# List all 30 available patterns
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-component-lookup.sh list

Individual pattern files: ${CLAUDE_SKILL_DIR}/../references/raweb/components/<slug>.json

Each pattern file contains the expected keyboard_interactions, aria.roles, aria.required_attributes, and aria.optional_attributes as defined by the APG. Use these as the source of truth when checking whether a component's ARIA implementation is correct and complete (RAWeb criteria 7.1, 7.3, 12.8).

Audit methodology

Step 1: Determine scope

Before auditing, clarify:

• Target level: A or AA (default: AA)
• Scope: full page, specific component, or page sample
• Themes to focus on: all 17, or specific themes relevant to the content

Step 2: Systematic evaluation by theme

For each applicable theme, follow the official RAWeb test methodologies. ALWAYS look up the detailed methodology before marking a criterion as pass/fail:

bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh methodology <topic.criterion.test>

Step 3: Report findings

Use the structured report format below.

Audit execution: Theme-by-theme checklist

When performing a full audit, evaluate the following themes in order. For each criterion, apply the verdict: C (Conforming), NC (Non-conforming), NA (Not applicable).

Theme 1 — Images

Scan for: <img>, <svg>, <canvas>, <object>, <embed>, <area>, [role="img"], <input type="image">

Theme 2 — Frames

Scan for: <iframe>, <frame>

Theme 3 — Colours

Requires visual inspection and contrast analysis tools.

Theme 4 — Multimedia

Scan for: <video>, <audio>, <object>, <embed>, <canvas>, <svg>, <bgsound>

Theme 5 — Tables

Scan for: <table>, <th>, <td>, <caption>, [role="table"]

Theme 6 — Links

Scan for: <a>, [role="link"]

Theme 7 — Scripts

Scan for: onclick, onkeydown, addEventListener, [role], [aria-*], [tabindex]

Theme 8 — Mandatory Elements

Full-page checks.

Theme 9 — Information Structure

Scan for: <h1>–<h6>, <ul>, <ol>, <dl>, <blockquote>, <header>, <nav>, <main>, <footer>, <aside>, <section>, <article>

Theme 10 — Presentation of Information

CSS and layout checks.

Theme 11 — Forms

Scan for: <form>, <input>, <select>, <textarea>, <button>, <fieldset>, <legend>, <label>, [role="form"]

Theme 12 — Navigation

Full-page/site checks.

Theme 13 — Consultation

Behavioural and interaction checks.

Themes 14–17 (EN 301 549 Extended)

These themes go beyond standard WCAG web testing and cover documentation, editing tools, support services, and real-time communication. Query them individually when relevant:

bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh topic 14  # Documentation & accessibility features
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh topic 15  # Editing tools
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh topic 16  # Support services
bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-lookup.sh topic 17  # Real-time communication

Report format

When presenting audit results, use this structured format:

# RAWeb 1.1 Accessibility Audit Report

**Page/Component**: [name or URL]
**Date**: [date]
**Target level**: AA
**Scope**: [full page / component / sample description]

## Summary

| Metric | Count |
|--------|-------|
| Criteria evaluated | XX |
| Conforming (C) | XX |
| Non-conforming (NC) | XX |
| Not applicable (NA) | XX |
| **Conformance rate** | **XX%** |

## Critical issues (must fix)

### Issue 1: [Short title]
- **Criterion**: RAWeb X.X (Level A/AA) — [criterion title]
- **WCAG**: X.X.X [SC name]
- **Location**: [file:line or selector]
- **Problem**: [description of the violation]
- **Impact**: [which users are affected and how]
- **Remediation**: [specific fix with code example]
- **Priority**: Critical / Major / Minor

## Detailed results by theme

### Theme X: [Name]

| Criterion | Level | Verdict | Notes |
|-----------|-------|---------|-------|
| X.1 | A | C / NC / NA | [detail] |
| X.2 | AA | C / NC / NA | [detail] |

## Recommendations

[Prioritised list of improvements beyond strict compliance]

Code scanning patterns

When auditing code files, use these search patterns to identify potential issues:

# Images without alt
grep -rn '<img ' --include="*.html" --include="*.jsx" --include="*.tsx" --include="*.vue" | grep -v 'alt='

# Empty links
grep -rn '<a[^>]*>[[:space:]]*</a>' --include="*.html" --include="*.jsx" --include="*.tsx"

# Positive tabindex
grep -rn 'tabindex="[1-9]' --include="*.html" --include="*.jsx" --include="*.tsx"

# onclick without keyboard equivalent
grep -rn 'onclick' --include="*.html" | grep -v '<button\|<a '

# Missing form labels
grep -rn '<input\|<select\|<textarea' --include="*.html" --include="*.jsx" --include="*.tsx" | grep -v 'aria-label\|aria-labelledby\|id='

# Autoplaying media
grep -rn 'autoplay' --include="*.html" --include="*.jsx" --include="*.tsx"

# Iframes without title
grep -rn '<iframe' --include="*.html" --include="*.jsx" --include="*.tsx" | grep -v 'title='

# Missing lang attribute
grep -rn '<html' --include="*.html" | grep -v 'lang='

# Colour-only indicators (potential — needs manual review)
grep -rn 'color:.*red\|color:.*green\|text-red\|text-green\|text-danger\|text-success' --include="*.css" --include="*.scss"

Severity classification

When auditing, ALWAYS:

1. Look up the exact criterion before rendering a verdict — do not rely on memory
2. Apply the official test methodology from methodologies.json
3. Check the expected ARIA pattern for interactive components: bash ${CLAUDE_SKILL_DIR}/../scripts/raweb-component-lookup.sh show <slug> — verify keyboard interactions, required roles, and required attributes match the APG specification
4. Use precise RAWeb criterion numbers (e.g., "RAWeb 11.1", not just "WCAG 1.3.1")
5. Include the WCAG mapping for cross-reference (found in the criterion's references)
6. Provide actionable remediation with code examples — when the fix involves an ARIA widget, include the correct pattern from the component reference
7. Distinguish between Level A and AA violations — both are required for conformance, but Level A failures are more critical
8. Note when automated testing is insufficient — many criteria require manual verification (contrast on images, relevance of alternatives, etc.)