Accessibility has moved from a nice-to-have to something with legal and commercial consequences in a growing number of markets. It is also one of the areas where WordPress sites fail quietly, because nothing visibly breaks. Our maintenance plans include accessibility checks for exactly that reason.
This guide covers what accessibility actually requires in practice, the failures we find most often on business sites, and why automated tools only get you part of the way.
Why This Matters Commercially
The legal picture varies by jurisdiction and is tightening in several. But the commercial argument stands on its own: a meaningful share of your audience has a permanent, temporary, or situational impairment. Someone with a broken wrist, someone on a phone in bright sunlight, and someone using a screen reader all benefit from the same work.
Accessible sites also tend to be better structured, which helps both search engines and the AI systems that increasingly summarise your content.
The Failures We Find Most Often
Across audits, the same handful of problems account for the majority of issues. None is difficult to fix once identified.
- Insufficient colour contrast: light grey body text on white is the single most common failure
- Missing or useless alt text: either absent entirely, or filled with a filename
- Unlabelled form fields: placeholder text is not a label and disappears on focus
- Keyboard traps: menus, modals, and sliders that cannot be escaped without a mouse
- No visible focus indicator: removed in CSS because a designer disliked the outline
- Broken heading order: headings chosen for size rather than structure
- Link text that says nothing: a page full of “click here” is unusable out of context
Why Overlay Widgets Are Not a Solution
Accessibility overlay plugins promise instant compliance from a single script. They do not deliver it. Overlays cannot fix underlying markup problems, they frequently interfere with the assistive technology a user already has configured, and they have been the subject of significant criticism from disabled users themselves.
Treat any product promising full compliance from one line of JavaScript with suspicion. The work is in the markup.
Testing Properly
What Automation Catches
Automated scanners reliably catch contrast failures, missing alt attributes, missing form labels, and invalid ARIA. They are genuinely useful and cost nothing to run. Run one across your key templates.
What Automation Misses
Automated tools typically catch only a portion of real issues. They cannot judge whether alt text is meaningful, whether focus order makes sense, or whether a custom component actually works with a screen reader. Those require manual testing.
The single most valuable test costs nothing: unplug your mouse and try to complete your main conversion path using only the keyboard. Most site owners discover a problem within a minute.
A Practical Starting Sequence
- Run an automated scan on your homepage, a service page, and your contact page
- Fix every contrast failure, since these are quick and affect everyone
- Add real alt text to images that convey information, and empty alt to decorative ones
- Attach proper labels to every form field, including search
- Restore visible focus styles if they were removed
- Complete a full keyboard-only pass of your main conversion path
- Check heading order reflects document structure rather than font size
Keeping It From Regressing
Accessibility is not a project you complete. Every new page, plugin, and design tweak can reintroduce problems. Building a short check into your publishing routine costs far less than a remediation project a year from now.
If you want a clear picture of where your site stands today, our free site audit covers accessibility alongside performance and security.
Get a free audit covering security, updates, backups, and performance gaps. Takes 60 seconds to request and costs nothing.
