To verify accessibility fixes, re-run a Plexa Trust scan to clear automated findings, then manually test: tab through the site with keyboard only, check contrast with WebAIM, run WAVE or axe on key pages, and test with VoiceOver or NVDA on forms and navigation. Document results and fix anything still failing.
Automated scans catch many issues but not everything. A short manual test pass after fixing findings ensures keyboard, screen reader, and contrast fixes actually work for real users. This guide is the verification checklist.
Check your website
See how your site handles how to test and verify accessibility fixes — free, no account needed.
Business impact
Shipping accessibility fixes without verifying them risks false confidence — and leaving blockers in checkout or contact flows. A 20-minute test pass after each round of fixes prevents regressions and supports compliance documentation.
Why this happens
Layer automated and manual testing: (1) Plexa Trust re-scan for trust/accessibility findings. (2) axe DevTools or WAVE on homepage, form, checkout. (3) Keyboard-only walkthrough. (4) Screen reader on navigation and one form. (5) Contrast checker on brand colours. Automated tools catch ~30–50% of issues; manual catches the rest.
How to confirm the issue
With Plexa Trust: run a free scan before and after fixes — compare finding counts. Use the scan as your regression baseline.
Step-by-step fix
Re-scan with Plexa Trust and note which accessibility findings remain.
Run WAVE or axe DevTools on homepage, contact form, and one inner page.
Keyboard-test: Tab through entire flow, activate buttons with Enter/Space.
Screen reader test: VoiceOver or NVDA on menu and one form submission.
Contrast-check buttons, links, and footer text.
Log remaining issues, fix, and repeat until clean.
Platform-specific fixes
All sites
Free tools for manual verification.
Install axe DevTools browser extension.
Install WAVE extension for visual feedback.
NVDA (Windows) or VoiceOver (Mac: Cmd+F5) for screen reader test.
WebAIM Contrast Checker for colour pairs.
CI / development
Add axe-core or pa11y to CI for regression catching on key URLs.
Run on staging before production deploy.
How to verify the fix
Test the same pages you scan — homepage, forms, checkout.
Re-scan after every accessibility fix batch before closing the task.
Keep a simple checklist document for compliance records.
Common mistakes
Relying only on automated scans and never keyboard-testing.
Testing only desktop and ignoring mobile screen readers.
Fixing homepage only while inner pages still fail.
Frequently asked questions
Do automated tools catch everything?
No. They catch roughly 30–50% of WCAG issues. Manual keyboard and screen reader testing is essential.
What is the fastest verification?
Plexa Trust re-scan plus a keyboard Tab-through of your main user journey.
Which pages should I test?
Homepage, primary contact/signup/checkout form, and your highest-traffic landing page.
How often should I test?
After any theme redesign, form change, or accessibility fix batch. Quarterly for stable sites.
Is Plexa Trust enough for WCAG compliance?
It catches many automated checks; full WCAG conformance still needs manual testing and possibly an audit.
What is WAVE?
A free browser extension that visualises accessibility issues on the page.
Can I pay for a full audit?
Yes — for legal compliance or VPAT needs, hire a certified accessibility auditor after fixing automated findings.
How do I document testing?
Screenshot scan results, note test date, pages tested, tools used, and issues resolved.
Think you've fixed it?
Run a free scan to verify the issue is resolved. Upgrade to Pro on Plexa Trust for the full audit, monitoring alerts, and score history.
Verify with a free scan