WordPress Development
How to Make Your WordPress Site Accessible: A WCAG Compliance Guide
Over 1 billion people have a disability that affects how they use the web. Here is how to make your WordPress site accessible to everyone — and why it matters for SEO and legal compliance.
Web accessibility means building websites that can be used by everyone — including people with visual, auditory, motor, or cognitive disabilities. Beyond being the right thing to do, accessibility is increasingly a legal requirement in many countries and a confirmed ranking signal for Google. Here is how to make your WordPress site accessible.
Why WordPress accessibility matters
- Over 1 billion people globally have some form of disability — that is a significant portion of any target audience
- Legal requirements — the ADA (USA), AODA (Canada), and EN 301 549 (EU) require public-facing websites to meet accessibility standards
- SEO benefit — many accessibility improvements (alt text, heading structure, descriptive links) also improve how Google understands your content
- Better usability for everyone — captions help people in noisy environments; clear navigation helps users with slow connections or older devices
WCAG guidelines — what they are
The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility, published by the W3C. WCAG 2.1 Level AA is the benchmark referenced by most legal frameworks.
| WCAG principle | What it means | WordPress example |
|---|---|---|
| Perceivable | Content must be perceivable by all users | Images have alt text; videos have captions |
| Operable | UI must be operable by all input methods | Site navigable by keyboard alone; no keyboard traps |
| Understandable | Content and UI must be understandable | Clear headings; consistent navigation; readable font sizes |
| Robust | Content must work with assistive technologies | Semantic HTML; proper ARIA labels; valid markup |
Step 1 — Choose an accessible WordPress theme
Accessibility starts with your theme. A poorly coded theme can make compliance nearly impossible to achieve through plugins or content alone. Look for themes that advertise WCAG 2.1 AA compliance:
Step 2 — Fix the most common accessibility issues
Image alt text
Every meaningful image must have descriptive alt text that conveys its content to screen reader users. Decorative images (backgrounds, spacers) should have empty alt attributes (alt="") so screen readers skip them.
- In WordPress, add alt text in the Media Library or in the image block’s Alt Text field
- Describe what the image shows, not what it is (‘A bar chart showing 40% growth in Q3’ not ‘Chart’)
- Product images: describe the product as a customer would want to know (‘Red leather Oxford shoe, size 10’)
- Do not start alt text with ‘Image of’ or ‘Photo of’ — screen readers already announce it as an image
Heading structure
Headings create a navigable outline of your page for screen reader users. The correct hierarchy is: one H1 per page (the page title), H2s for major sections, H3s for subsections. Never skip heading levels (H1 to H3 without H2).
Colour contrast
Text must have sufficient contrast against its background. WCAG 2.1 AA requires a contrast ratio of 4.5:1 for normal text and 3:1 for large text. Test your theme’s text/background combinations using the WebAIM Contrast Checker (webaim.org/resources/contrastchecker/).
Keyboard navigation
All functionality must be operable via keyboard alone — no mouse required. Test by pressing Tab to move through your site and Enter to activate links and buttons. Every interactive element must be reachable and visibly focused.
Step 3 — Accessibility plugins for WordPress
Automated accessibility overlays (like UserWay or accessiBe) have been publicly criticised by disability advocates as inadequate for compliance. They can help some users but do not fix underlying code issues. Proper accessibility requires fixing the source HTML, CSS, and content — not adding a widget on top.
Step 4 — Test your accessibility
Install the Accessibility Checker plugin or use the WAVE tool (wave.webaim.org). Automated tools catch approximately 30–40% of WCAG issues — they are a starting point, not a comprehensive audit.
Put your mouse aside. Navigate your entire site using Tab, Shift+Tab, Enter, and arrow keys. Every link, button, and form field must be reachable and usable.
On Mac, use VoiceOver (Cmd+F5). On Windows, use NVDA (free download). Navigate your site and listen to how it is announced. You will quickly discover missing alt text, unclear link labels, and heading issues.
Use the WebAIM Contrast Checker or Chrome DevTools’ accessibility panel to verify all text meets the 4.5:1 contrast ratio requirement.
Use the W3C HTML Validator (validator.w3.org). Invalid HTML often causes unexpected behaviour with assistive technologies.
Need your WordPress site audited or built for accessibility?
Simple Automation Solutions conducts WordPress accessibility audits and builds WCAG-compliant sites for organisations worldwide.
Frequently asked questions
Is my WordPress site legally required to be accessible?+
It depends on your location and business type. In the USA, the ADA applies to businesses open to the public — courts have increasingly ruled that websites qualify as ‘places of public accommodation’. In the EU, the European Accessibility Act (effective June 2025) requires most businesses to meet EN 301 549 (which references WCAG 2.1 AA). Consult a legal advisor for specific guidance on your obligations.
Does WordPress itself meet accessibility standards?+
WordPress core is developed with accessibility as a stated goal — the WordPress Accessibility Team reviews new features against WCAG guidelines before release. However, the themes and plugins you install on top of WordPress determine how accessible your specific site is. A poorly coded theme can undermine WordPress’s own accessibility efforts.
How long does a WordPress accessibility audit take?+
A basic automated audit and report takes 1–2 hours. A comprehensive manual audit covering WCAG 2.1 AA — including keyboard testing, screen reader testing, and content review — typically takes 8–24 hours depending on site size and complexity. Remediation time depends on the severity and number of issues found.
