raam-audit（内存审计）

RAAM 1.1 — Mobile Accessibility Audit Skill

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

Reference data

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

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

# Full test methodology (iOS & Android steps)
bash ${CLAUDE_SKILL_DIR}/../scripts/raam-lookup.sh methodology <topic.criterion>

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

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

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

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

Audit methodology

Step 1: Determine scope

Before auditing, clarify:

• Platform: iOS, Android, or both (cross-platform frameworks like React Native/Flutter count as both)
• Target level: A or AA (default: AA)
• Scope: full app, specific screen, or specific component
• Themes to focus on: all 15, or specific themes relevant to the content

Step 2: Systematic evaluation by theme

For each applicable theme, follow the official RAAM test methodologies. ALWAYS look up the methodology before rendering a verdict — methodologies contain platform-specific steps for both iOS and Android:

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

Step 3: Report findings

Use the structured report format below.

Audit execution: Theme-by-theme checklist

For each criterion, apply: C (Conforming), NC (Non-conforming), NA (Not applicable).

Theme 1 — Graphic Elements (9 criteria)

Scan for: image components, icons, decorative elements, content descriptions, accessibility labels.

Code patterns to scan:

# iOS: images without accessibility labels
grep -rn 'Image(' --include="*.swift" | grep -v 'accessibilityLabel\|accessibilityHidden\|decorative'

# Android: images without content descriptions
grep -rn 'Image(' --include="*.kt" | grep -v 'contentDescription'
grep -rn 'ImageView' --include="*.xml" | grep -v 'contentDescription\|importantForAccessibility'

# React Native: images without labels
grep -rn '<Image' --include="*.tsx" --include="*.jsx" | grep -v 'accessibilityLabel\|accessible={false}'

Theme 2 — Colours (4 criteria)

Requires visual inspection and contrast tools.

Code patterns to scan:

# Hardcoded colours that may have contrast issues
grep -rn '#[0-9a-fA-F]\{6\}\|rgb(' --include="*.swift" --include="*.kt" --include="*.xml" --include="*.tsx"

# iOS: check for semantic/adaptive colours
grep -rn 'UIColor\|Color(' --include="*.swift" | grep -v 'semantic\|system\|primary\|label'

Theme 3 — Multimedia (18 criteria)

Scan for: video/audio players, media components.

Theme 4 — Tables (5 criteria)

Theme 5 — Interactive Components (5 criteria)

Code patterns to scan:

# Custom interactive elements missing accessibility
grep -rn 'onTap\|onClick\|onPress' --include="*.swift" --include="*.kt" --include="*.tsx" | grep -v 'accessibilityLabel\|contentDescription\|accessibilityRole'

# Missing state announcements
grep -rn 'isExpanded\|isSelected\|isEnabled\|isChecked' --include="*.swift" --include="*.kt" | grep -v 'accessibilityValue\|stateDescription\|accessibilityState'

Theme 6 — Mandatory Elements (2 criteria)

Code patterns to scan:

# iOS: screens without navigation title
grep -rn 'struct.*View.*:.*View' --include="*.swift" | head -20
grep -rn 'navigationTitle\|title =' --include="*.swift"

# Android: activities without labels
grep -rn '<activity' --include="*.xml" | grep -v 'android:label'

Theme 7 — Information Structure (2 criteria)

Code patterns to scan:

# iOS: text styled as heading but missing trait
grep -rn '\.font(.title\|\.font(.headline\|\.font(.subhead' --include="*.swift" | grep -v 'isHeader\|accessibilityAddTraits'

# Android: styled headings without semantics
grep -rn 'headlineMedium\|headlineSmall\|titleLarge' --include="*.kt" | grep -v 'heading()'

Theme 8 — Presentation of Information (7 criteria)

Code patterns to scan:

# Fixed font sizes that won't scale
grep -rn 'fontSize.*=.*[0-9]' --include="*.swift" | grep -v '\.sp\|\.body\|\.title\|\.headline'
grep -rn 'textSize.*=.*"[0-9]' --include="*.xml" | grep 'dp"' # should be sp, not dp

# Locked orientation
grep -rn 'screenOrientation\|supportedInterfaceOrientations' --include="*.xml" --include="*.swift" --include="*.kt"

Theme 9 — Forms (12 criteria)

Code patterns to scan:

# Form fields without labels
grep -rn 'TextField\|TextInput\|EditText\|OutlinedTextField' --include="*.swift" --include="*.kt" --include="*.tsx" --include="*.xml" | grep -v 'label\|accessibilityLabel\|contentDescription\|hint'

# Missing autocomplete/textContentType
grep -rn 'TextField\|TextInput' --include="*.swift" --include="*.kt" --include="*.tsx" | grep -v 'textContentType\|autoComplete\|autofill\|AutofillType'

Theme 10 — Navigation (4 criteria)

Theme 11 — Consultation (16 criteria)

Code patterns to scan:

# Small touch targets
grep -rn 'frame(width:\|\.size(' --include="*.swift" | grep -E '[0-9]{1,2}[^0-9]' | grep -v '4[4-9]\|[5-9][0-9]\|[1-9][0-9]{2}'

# Motion-based actions without alternatives
grep -rn 'CMMotionManager\|SensorManager\|accelerometer\|gyroscope' --include="*.swift" --include="*.kt" --include="*.tsx"

# Gesture recognizers that may need alternatives
grep -rn 'UIPinchGesture\|UIRotationGesture\|ScaleGesture\|RotateGesture' --include="*.swift" --include="*.kt"

Themes 12–15 (EN 301 549 Extended)

Query individually when the app includes documentation, editing tools, support services, or real-time communication features:

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

Report format

# RAAM 1.1 Mobile Accessibility Audit Report

**Application**: [name]
**Platform**: iOS / Android / Both
**Version audited**: [version]
**Date**: [date]
**Target level**: AA
**Scope**: [full app / specific screens / component]

## Summary

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

## Testing environment

| | iOS | Android |
|---|---|---|
| Device | [model] | [model] |
| OS version | [version] | [version] |
| Screen reader | VoiceOver | TalkBack |
| Other AT | Switch Control, Voice Control | Switch Access, Voice Access |

## Critical issues (must fix)

### Issue 1: [Short title]
- **Criterion**: RAAM X.X (Level A/AA) — [criterion title]
- **EN 301 549**: [norm reference]
- **Platform**: iOS / Android / Both
- **Screen**: [screen name]
- **Location**: [file:line or component]
- **Problem**: [description of the violation]
- **Impact**: [which users are affected and how]
- **Remediation**: [specific fix with code example for affected platform(s)]
- **Priority**: Critical / Major / Minor

## Detailed results by theme

### Theme X: [Name]

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

## Recommendations

[Prioritised list of improvements beyond strict compliance]

Severity classification

When auditing, ALWAYS:

1. Look up the exact criterion before rendering a verdict — do not rely on memory
2. Apply the official methodology which has separate iOS and Android steps
3. Use RAAM criterion numbers (e.g., "RAAM 9.1", not just "WCAG 1.3.1")
4. Include the EN 301 549 norm reference for cross-reference
5. Provide platform-specific remediation with code examples (iOS AND Android when both are in scope)
6. Test both platforms separately — a component may conform on one and fail on the other
7. Note when code review is insufficient — many criteria require device testing with screen reader (VoiceOver/TalkBack)
8. Check both orientations — portrait and landscape
9. Test with enlarged text — set system text size to maximum and verify layout