Accessibility assessment
Clear findings.
Practical next steps.
GatekeeperQA: PASS
Prepared 2026-09-25 20:18:13 UTC
Executive summary
1 page(s) requested. 0 scan error(s). 0 confirmed rule violation(s), affecting 0 element occurrence(s). 0 rule check(s) need manual review (0 listed element occurrence(s)).
No confirmed automated violations were found in the scanned page state. Manual testing is still needed.
Confirmed findings by severity
Counts represent affected elements per rule; an element may appear under more than one rule. Manual-review items are counted separately.
Scope and method
Playwright and axe-core evaluated the initially loaded pages using WCAG 2.1/2.2 A/AA rule tags. Linked pages, authenticated journeys and interactions were not tested.
- http://127.0.0.1:62243/
Automated checks cover only part of accessibility. PASS is a configured gate result, not WCAG or Section 508 certification. Manual review is required.
Tester overview
What to fix first
Start with scan errors, then critical and serious findings. Counts below are element occurrences, not unique elements. Review shared components before fixing each page separately.
No confirmed automated findings to prioritize. Complete the manual checks before drawing a broader conclusion.
Why this gate result?
Quality gate: FAIL on serious, critical; WARN on minor, moderate, unknown. Unresolved checks cause WARN; scan errors or missing pages cause FAIL. No severity threshold exceeded. 0 scan error(s). Expected 1 pages; received 1.
Page-by-page coverage
| Scanned page | Run | Confirmed occurrences | Review checks |
|---|---|---|---|
| Page 1: http://127.0.0.1:62243/ | Completed | 0 | 0 |
Completed describes scan execution, not accessibility conformance. Review checks are unresolved automated checks, not completed human testing. Evidence and suggested fixes follow for each page.
Findings and remediation
Page 1: http://127.0.0.1:62243/
Checks needing manual review: 0
No confirmed automated violations recorded for this page.
Manual testing checklist
Use this as a starting point, not a complete accessibility audit. These checks have not been completed by the scanner. Record the tester, date, page state, result and evidence separately.
- Keyboard: reach and operate links, buttons, menus and forms without a mouse; check for keyboard traps.
- Focus: confirm the focus indicator stays visible and moves in a meaningful order.
- Screen reader: check headings, control names, instructions and error announcements.
- Zoom and reflow: enlarge text and test a narrow viewport for lost content or overlapping controls.
- Page states: check dialogs, validation errors and important user journeys that the initial-page scan did not exercise.
Recommended next steps
- Resolve execution errors, then address critical and serious confirmed findings.
- Review each unresolved check with a person; an unresolved result is not a confirmed failure or pass.
- Test keyboard navigation, focus order, screen-reader use and complete user journeys.
- Repeat the scan after fixes and retain the report alongside manual test evidence.
This report is automated test evidence. It is not a WCAG certification, legal opinion or completed VPAT/ACR.