Accessibility Audits
Outcome
Section titled “Outcome”You will know how accessibility audits fit into a practical review workflow, how to remediate the most common findings, and where to look up the underlying WCAG guidance when you need a definitive answer.
What To Look For
Section titled “What To Look For”- Repeated accessibility failures across templates, which usually point to one shared fix
- High-impact issues on high-traffic pages, where the audience exposed to the problem is largest
- Findings that affect primary forms, navigation, or customer journeys
- Issues on pages that are linked from email campaigns, paid traffic, or external partners
Common Findings
Section titled “Common Findings”The table below covers the categories that come up most often in TMXIO accessibility audits. Each entry links to the WCAG quick reference for the exact success criterion.
| Issue | WCAG ref | How to fix |
|---|---|---|
| Images missing alt text | 1.1.1 Non-text Content | Add descriptive alt text, or mark purely decorative images with empty alt |
| Form fields without labels | 3.3.2 Labels or Instructions | Associate a visible label with each input; do not rely on placeholder text alone |
| Insufficient color contrast | 1.4.3 Contrast (Minimum) | Adjust foreground or background so the ratio meets at least 4.5:1 for body text |
| Non-descriptive link text | 2.4.4 Link Purpose (In Context) | Replace “click here” or “read more” with link text that explains the destination |
| Skipped heading levels | 1.3.1 Info and Relationships | Keep heading order logical; do not pick heading levels for visual size |
| Missing language attribute | 3.1.1 Language of Page | Set the page or site language at the document level |
| Keyboard-inaccessible controls | 2.1.1 Keyboard | Make every interactive element reachable and operable with the keyboard alone |
For anything not in this table, the full quick reference is the canonical source: WCAG 2.1 Quick Reference.
Remediation Flow
Section titled “Remediation Flow”-
Run the audit and sort findings so the highest-impact items are at the top.
-
Group findings by template, page type, or component. A single fix at the template level usually clears many entries in the report.
-
Pick a small batch to remediate this cycle. Closing a few categories well is more useful than touching every category briefly.
-
Make the fix, then re-run the audit on the affected pages to confirm the finding is gone.
-
Record the change in your team’s tracker so future audits can compare against it.
What Success Looks Like
Section titled “What Success Looks Like”- Accessibility work is prioritized by impact, not by audit row count
- Repeated template-level findings are fixed at the template, not patched page by page
- Lens, support, and audit findings reinforce each other rather than living in separate silos
- Each remediation pass leaves a record so progress is visible across cycles