Accessibility
Automated WCAG 2.1 accessibility audits per page and component, with actionable issue reports.
What this module tests
The Accessibility module audits your web application's pages against WCAG 2.1 guidelines. Tests are generated for each page listed in your KB domains and run automatically with every test suite execution. Issues are reported with WCAG criterion, severity, affected element, and suggested fix.
- WCAG 2.1 Level AA — default compliance target
- WCAG 2.1 Level AAA — opt-in per project or domain
- Missing alt text, insufficient colour contrast, missing form labels
- Keyboard navigation and focus order issues
- ARIA attribute misuse
- Missing landmark regions, skip-navigation links
- Screen reader compatibility (announced element roles and states)
WCAG criteria tested
| Category | Criteria | Level |
|---|---|---|
| Perceivable | Alt text for images, captions for media, colour contrast ratio ≥ 4.5:1 | AA |
| Operable | Keyboard navigability, no keyboard traps, skip links, focus indicators | AA |
| Understandable | Form labels, error identification, language attribute on <html> | AA |
| Robust | Valid ARIA roles, states, and properties; compatible with assistive tech | AA |
| Enhanced contrast | Contrast ratio ≥ 7:1 | AAA |
Issue severity levels
Each accessibility issue is assigned a severity level:
- Critical — blocks access for users with disabilities (e.g. interactive element with no accessible name)
- Serious — significantly impairs usability (e.g. low colour contrast on body text)
- Moderate — creates friction but usable with workarounds
- Minor — best-practice improvements
KB scenario format for accessibility
# Accessibility scenario example
domain: checkout
scenarios:
- id: A11Y-CHK-001
title: "Checkout page passes WCAG 2.1 AA audit"
module: accessibility
steps:
- Navigate to /checkout while authenticated
- Wait for page to fully render
expected: >
Zero critical or serious accessibility violations.
All form fields have associated labels.
All interactive elements are keyboard-accessible.
Colour contrast meets WCAG AA minimum ratios.
Accessibility tests are non-destructive — they only read the DOM and computed styles, never modify the application. They run safely alongside other modules.
Viewing accessibility reports
After each run, the Accessibility tab in the run results view lists all violations grouped by page. Each violation shows:
- WCAG criterion (e.g. 1.4.3 Contrast)
- Affected element (CSS selector and rendered HTML snippet)
- Severity and impact description
- Suggested remediation
Reports can be exported as HTML or JSON from the run results page.