Evidence Center
Evidence, not just accessibility claims.
Accessibility Rocket releases are checked with automated scanners, HTML validation, launch-quality audits, and manual review. We publish what was tested, what passed, and what still depends on implementation.
What this evidence means
Release-output versions are tested directly. Framework component kits are reviewed at component level because final application output depends on routing, styling, content, integrations, and testing.
Release output tested
Used for HTML/CSS/JS, Astro, Eleventy, and SvelteKit static versions. The generated pages are tested directly.
Component patterns reviewed
Used for React, Vue, and Angular component kits. The components are reviewed, but final application output depends on integration and testing.
Automated accessibility
Three accessibility engines (axe-core, IBM Equal Access, and Pa11y's HTML_CodeSniffer) each catch issues the others miss, so we run all three. The Nu HTML Checker validates the markup underneath.
-
Nu HTML Checker
0 errors
HTML markup validation
Passing
View Nu HTML Checker log -
axe-core
0 violations
Automated scan via Playwright
Passing
View axe-core report -
IBM Equal Access
0 violations
Automated scan via Playwright
Passing
View IBM Equal Access report -
Pa11y CI
0 errors
HTML_CodeSniffer ruleset
Passing
View Pa11y CI report
Launch quality
Lighthouse audits accessibility, performance, best practices, and SEO on every release. The accessibility score is a useful signal, not a full WCAG conformance result.
-
Lighthouse Accessibility
100%
Launch quality check
Passing
View Lighthouse Accessibility report -
Lighthouse Performance
91%
Launch quality check
Passing
View Lighthouse Performance report -
Lighthouse Best practices
100%
Launch quality check
Passing
View Lighthouse Best Practices report -
Lighthouse SEO
100%
Launch quality check
Passing
View Lighthouse SEO report
Manual review
Automated scanners cannot verify keyboard flows, screen reader behavior, or editorial quality. These checks run on every release before ship.
-
Keyboard navigation
Completed
Tab order, focus, and traps reviewed
View keyboard review -
Screen reader smoke test
Completed
VoiceOver landmarks and announcements
View screen reader smoke test -
Reduced motion
Checked
Animations respect prefers-reduced-motion
View reduced motion review -
Content editor checklist
Completed
Copy, headings, and alt text reviewed
View content editor checklist
Important limitation
Automated checks help catch many issues early, but they do not determine full accessibility on their own. Final accessibility and legal conformance depend on content, implementation, integrations, and testing.
Known limitations
- Automated tools do not determine full accessibility on their own.
- Third-party scripts or embedded tools may introduce issues.
- User edits can break heading order, alt text, contrast, or form clarity.
- Framework integrations outside the tested release output need separate review.
- Final accessibility and legal conformance depend on content, implementation, integrations, and testing.
Want evidence included with your template?
Every Rocket Pack includes the relevant testing evidence and documentation for its release.