.spec-table{width:100%;border-collapse:collapse;font-size:13px;margin:12px 0}
.spec-table th{text-align:left;padding:8px 12px;background:#F3F4F6;font-weight:700;font-size:11px;text-transform:uppercase;letter-spacing:.04em;color:#6B7280;border-bottom:2px solid #E5E7EB}
.spec-table td{padding:8px 12px;border-bottom:1px solid #F3F4F6;vertical-align:top;line-height:1.5}
.related-pages{margin-top:32px;padding-top:20px;border-top:1px solid #E5E7EB}
.related-pages h3{font-size:13px;font-weight:700;text-transform:uppercase;letter-spacing:.06em;color:#6B7280;margin-bottom:10px}

# Accessibility testing

Accessibility testing validates that Petrel meets WCAG 2.2 AA requirements. Testing must occur at design, development, and acceptance stages — not only at the end of a release cycle.
## Testing tools

Tool
Purpose
When to use
Accessibility Insights for Windows
UI Automation tree inspection, automated checks
Development and acceptance
Windows Colour Contrast Analyser
Contrast ratio measurement on-screen
Design and development
Microsoft Narrator
Built-in Windows screen reader
Development and acceptance
NVDA (free)
Screen reader widely used by accessibility testers
Acceptance testing
Windows Magnifier
Test at up to 1600% magnification
Development
## Acceptance criteria

A feature is considered accessible when all of the following are true:

- All text meets 4.5:1 contrast ratio (3:1 for large text)
- All interactive controls are reachable by Tab
- All interactive controls have visible focus indicators
- All controls have descriptive accessible names
- Status and error messages do not rely on colour alone
- No keyboard traps exist outside of modal dialogs
- The application functions at 150% display scaling without clipping
- Accessibility Insights Fast Pass returns no critical failures


## Testing checklist by stage

**Design stage:** Run Figma Colour Contrast plugin. Review tab order annotation. Verify accessible name specifications for all icon controls.

**Development stage:** Run Accessibility Insights Fast Pass. Test keyboard-only operation. Verify AutomationPeer implementations for custom controls. Test at 150% scaling.

**Acceptance stage:** Screen reader walkthrough with Narrator. Full keyboard navigation test. Contrast check on final render. Scaling test at 100% and 150%.

### Related pages

Colour and contrast
Keyboard and focus
Custom controls