Why accessibility overlays don't work
Overlay widgets promise WCAG compliance in one line of JavaScript. Here is what they actually change, why disabled users object to them, and what to do instead.
The European Accessibility Act and your WordPress site
The EAA deadline was June 2025, not next year. What the Act actually requires, who it covers, and what to do if you have only just heard about it.
How to write alt text that actually helps
Alt text is the most common accessibility failure on WordPress sites and the one automation cannot do for you. A practical guide with real examples.
WordPress colour contrast: finding and fixing every failure
What the 4.5:1 ratio actually means, why contrast checkers disagree with each other, and how to fix failures in WordPress without redesigning.
Heading levels in WordPress, and why they matter
Screen reader users navigate by headings. Here is what a correct heading structure looks like, what breaks it in WordPress, and how to fix it.
'Click here' and other link text that fails WCAG
Screen reader users pull up a list of every link on the page. If yours all say 'read more', that list is useless. How to write link text that works out of context.
Test your WordPress site with a keyboard in 20 minutes
The single most valuable accessibility test, it needs no tools, and automated checkers cannot do it for you. A step-by-step walkthrough.
Making an Elementor site accessible: seven things that break
Elementor does not make a site inaccessible on its own, but it makes several specific mistakes easy. Here is what to check and how to fix each one.
Gutenberg and accessibility: what core blocks get right and wrong
The block editor produces cleaner markup than most page builders. It still lets you build an inaccessible page. What to watch, block by block.
Accessible forms in WordPress: labels, errors and focus
Forms are where accessibility failures cost money, because a form nobody can complete is a sale nobody makes. The four things that matter most.
WCAG 2.2 AA for WordPress: a checklist you can finish
The Level AA criteria that actually come up on WordPress sites, what each one means in practice, and which can be checked automatically.
The 24-pixel rule: WCAG 2.2 target size on WordPress
A new WCAG 2.2 criterion that catches almost every WordPress theme. What 24 by 24 actually requires, the exceptions, and how to fix it without redesigning.
How to write an accessibility statement that is true
Most accessibility statements are a paragraph of reassurance that claims more than the site delivers. What to put in one that is honest and actually useful.
What automated accessibility testing cannot find
Automated checks settle part of WCAG and no tool can tell you the rest. Knowing exactly where the line falls is what stops a clean report becoming false confidence.
Your first WordPress accessibility audit, in order
A first scan on an unchecked site returns hundreds of findings. Here is the order of work that clears most of them fastest, without wasting a day.
How to choose a WordPress accessibility plugin
The first decision is whether to use an overlay, and the answer is no. After that it comes down to what you want the plugin to do: patch your theme, check pages as you write them, or scan the whole site and fix the code.
Fixing accessibility without breaking your theme
Where to put accessibility fixes in WordPress so they survive a theme update, a plugin change, and the next developer who touches the site.
Introducing WOWStudio Accessibility Remediation
A free WordPress plugin that finds, fixes and documents WCAG issues at the code level — real, reviewable fixes, and not an overlay.
How we build fast, accessible WordPress sites
Performance and accessibility aren't a final polish pass — they're decisions you make from the first line. Here's how we approach both.