Accessibility Audits & Remediation (WCAG)
Accessibility Audits & WCAG Remediation
We audit and fix accessibility issues to align your WordPress site with WCAG 2.2 AA. Expect clear findings, prioritized fixes, component-level guidance, and training so improvements stick release after release.
Why accessibility with WP Support BC
Keyboard, forms, focus, semantics, color/contrast, target size, & error prevention.
Screen readers (NVDA/VoiceOver), keyboard paths, and automated checks (axe, WAVE).
Issue IDs, severity, WCAG references, code-level repro & fix examples for your stack.
Design/dev training, checklists, and regression QA for future releases.
What we audit & fix
Headings, landmarks (header/nav/main), lists, tables, labels, and ARIA roles.
Tab order, visible focus, traps, shortcuts, bypass blocks, and modals/menus.
Contrast ratios, reflow/zoom, captions/transcripts, images of text, motion.
Input purpose, labels/aria-describedby, validation hints, and error prevention.
Deliverables
| Item | Description |
|---|---|
| Audit report | WCAG-mapped issues with severity, repro steps, screenshots, and code-level fix notes. |
| Remediation | We implement fixes in theme/plugins or pair with your devs; PRs & change logs included. |
| Reusable components | Accessible patterns for menus, dialogs, tabs, carousels, and forms. |
| Docs & training | Checklists, contribution guide, and short training for design/dev/QA teams. |
| Statement/VPAT (optional) | Accessibility statement and assistance with ACR/VPAT where required. |
Accessibility — FAQs
We align with WCAG 2.2 Level AA. If your policy requires a different level, we’ll scope accordingly.
Manual testing with keyboard and screen readers (NVDA/VoiceOver), supported by automated audits (axe/WAVE) and code review.
Yes. We submit PRs to themes/plugins, create accessible components, and document patterns for future releases.
We can draft an Accessibility Statement and support ACR/VPAT preparation where procurement requires it.