Sample deliverable
Northstar Checkout Accessibility Audit
This is the structure every audit follows; the delivery format is agreed before work begins. Northstar Checkout is a fictional product, so the findings are illustrative. Each finding is written so a developer can reproduce it without asking a follow-up question: what the defect is, exactly how to trigger it, what happens, what should happen instead, who it affects, and what to change.
- Version
- 1.0
- Issued
- July 12, 2026
- Target
- WCAG 2.2 Level A and AA
- Auditor
- Khushwant Parihar (CPACC, DHS Trusted Tester)
Demonstration disclosure
Northstar Checkout is a fictional product created solely to demonstrate the structure and evidence quality of an Accessibility.build audit report. It is not a client, an endorsement, or a conformance claim, and the findings below describe a product that does not exist.
Scope, test environments, and limitations
Scope
- Checkout entry page
- Delivery address form
- Payment method step
- Order review dialog
- Confirmation state
Test environments
- Chrome 128 with NVDA 2025.1 on Windows 11
- Safari 18 with VoiceOver on macOS 15
- Keyboard-only interaction across all five states
- Browser zoom to 400 percent and reflow at 320 CSS pixels
- axe-core 4.10 used as supporting evidence only
Limitations
- This sample covers five representative states, not every possible checkout configuration.
- No usability testing with disabled participants is represented in this fictional sample.
- Conformance cannot be claimed from a sample. A conformance claim requires every page in scope to be evaluated.
Methodology. Manual testing against WCAG 2.2 Level A and AA, carried out by a CPACC-certified auditor, with automated checks used only to surface candidates for manual review. Every finding below was reproduced by hand.
Report summary
Total findings
8
Across 5 audited states
Blocking
4
Critical and High, fix these first
WCAG criteria affected
14
Distinct success criteria failed
Severity distribution
- 2 Critical
- Blocks a disabled user from completing the task. No workaround.
- 2 High
- Task is completable but only with significant difficulty or guesswork.
- 3 Medium
- Creates friction or confusion; a workaround exists.
- 1 Low
- Minor inconsistency with limited practical impact.
Detailed findings
Showing 8 of 8 findings
| Expand | ID | Issue | Severity | Level | WCAG criteria | Location |
|---|---|---|---|---|---|---|
| NS-001 | Order review dialog does not keep keyboard focus within the modal | Critical | Level A | Payment step, order review overlay | ||
| NS-002 | Delivery date picker cannot be operated with a keyboard | Critical | Level A | Delivery address form, preferred delivery date | ||
| NS-003 | Address validation errors are not announced after submission | High | Level A | Delivery address form | ||
| NS-004 | Promotional code helper text falls below minimum contrast | High | Level AA | Payment step, promotional code field. Token reused site-wide. | ||
| NS-005 | Visible payment option text is not included in the accessible name | Medium | Level A | Payment step, payment method selection | ||
| NS-006 | Order summary requires horizontal scrolling at 400 percent zoom | Medium | Level AA | Order review step, summary table | ||
| NS-007 | Card number field does not declare its input purpose | Medium | Level AA | Payment step, card details fieldset | ||
| NS-008 | Checkout progress indicator conveys the current step by colour alone | Low | Level A | All checkout steps, header progress indicator |
The Excel export contains every column shown here plus the full reproduction steps, actual and expected results, and suggested resolution for each finding, on a Findings sheet with a Summary sheet alongside it. It exports whatever your current filters show, so you can hand a developer just the Critical rows if that is all they need.
Want this level of evidence for your product?
A real audit follows the same structure against your actual product, tested by hand with screen readers and a keyboard rather than scanned. You get the findings, the reproduction steps, and a prioritised remediation plan your developers can work straight from.