Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Improve a WordPress site’s accessibility by checking both its theme and the content you publish, fixing barriers in structure, navigation, images, forms, and media, then testing with automated tools and people-friendly manual checks. An “accessibility-ready” theme is a useful starting point, not a guarantee of WCAG conformance for the finished site.
What accessibility means for a WordPress site
Accessibility means people can perceive, operate, understand, and reliably use your site, including with keyboards and assistive technology. In practice, ask whether information depends only on sight, sound, or color; whether every control can be operated without a mouse; whether page structure and instructions make sense; and whether browsers and assistive technologies can interpret the content.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
WordPress Absolute Beginner's Guide | $6.79 | Buy on Amazon |
| 2 |
|
WordPress Absolute Beginner's Guide | $23.99 | Buy on Amazon |
WordPress says it aims to make the Admin and bundled themes fully compliant with WCAG 2.2 AA “where possible,” while acknowledging that some features may have known issues. Its coding standards expect new and updated WordPress code to conform to WCAG 2.2 Level AA. These goals apply to WordPress project code, not automatically to every site built with WordPress, its third-party themes, plugins, and user-created content. See WordPress’s accessibility statement and its Accessibility Coding Standards.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Start with the theme, but do not stop there
When choosing a theme from the WordPress.org directory, the accessibility-ready tag indicates that it has met the Theme Review Team’s baseline requirements. It is not a WCAG AA certification: WordPress’s Theme Handbook explicitly says that “Accessibility Ready” does not mean a theme meets WCAG AA. The tag also cannot ensure that your content, plugin combination, or customizations are accessible. Review the Theme Handbook’s accessibility guidance and the current accessibility-ready requirements when comparing themes.
#1 Best Overall
Check plugins as well as themes. Current theme requirements say themes must not recommend or require inaccessible plugins, but the site owner still needs to assess the plugins actually installed and how they behave with the site’s content and configuration.
Improve page structure, navigation, and controls
- Use a meaningful heading hierarchy. Give each page a clear main heading and organize sections in a logical order. Avoid choosing heading levels just to change text size.
- Make links understandable out of context. Use descriptive link text rather than phrases such as “click here” or “read more” without a clear subject. In text, distinguish links with underlining or another non-color cue.
- Provide a skip link and useful landmarks. A skip-to-content link lets keyboard users bypass repeated navigation. Landmarks should identify page regions meaningfully so assistive-technology users can move between them.
- Check keyboard operation. Use Tab and Shift+Tab to reach controls, Enter or Space to activate them where appropriate, and arrow keys when a component expects them. Confirm that focus remains visible and follows a sensible order through navigation menus, dialogs, and interactive blocks.
- Label form fields and controls. Each field needs a programmatic label, not merely placeholder text. Controls should expose an accessible name, role, and state. Explain errors in text and make it possible to identify and correct the affected field.
These checks align with the current WordPress accessibility-ready requirements, which also address ambiguous link text, screen-reader text, and controls.
Make images, color, text, and media usable
- Write useful alternative text. For an informative image, describe its relevant purpose or information in context. Decorative images should not generate redundant spoken descriptions; depending on how an image is added, leave its alternative text empty or mark it decorative.
- Do not rely on color alone. Links and other distinctions should remain apparent without color perception. Check text and interface-control contrast. The WordPress Theme Handbook gives a 4.5:1 contrast ratio for plain content text in its discussion of theme guidance; check the applicable WCAG criterion for the particular content and control rather than treating that figure as a universal rule.
- Provide alternatives for media. Use captions for spoken video content and transcripts where appropriate for audio and video. Make sure meaningful information conveyed visually is available in another form.
- Allow text enlargement and reflow. Increase text size and inspect narrower screens to see whether content, controls, or functionality disappear, overlap, or require avoidable horizontal scrolling. Check that text-spacing changes do not break the layout.
- Make transient content accessible. Do not hide essential information behind hover-only behavior. Content revealed on hover should also be available on keyboard focus and remain usable while someone moves to it. Avoid unexpected changes of context, and warn users when a link opens a new tab or window.
The Theme Handbook distinguishes informative and decorative images and discusses contrast; the current requirements also cover media, reflow, text spacing, hover and focus content, and context changes.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTest the finished site in more than one way
Automated scanners such as axe or WAVE can flag likely issues quickly, but a clean scan is not proof that a site fully conforms to WCAG. Combine scanning with hands-on checks of real pages and interactions. WordPress’s theme testing guidance recommends varied content and screen sizes and identifies keyboard navigation, screen-reader compatibility, and ARIA use as testing concerns.
- Choose representative pages. Include a typical page or post, navigation, forms, pages with informative images or media, and pages using interactive blocks or plugin features.
- Run an automated scan. Use a tool such as axe or WAVE on those pages. Review the flagged element and context; automated findings can need human interpretation, and scans cannot identify every usability barrier.
- Navigate with a keyboard. Starting at the top of each page, use Tab and Shift+Tab to reach interactive elements. Check focus visibility, order, skip-link behavior, menus, forms, and any dialogs or custom controls.
- Try a screen reader. Check that headings, landmarks, links, field labels, control states, and image alternatives communicate the structure and purpose needed to use the page.
- Vary the viewing conditions. Inspect more than one screen size and enlarge text or change text spacing. Confirm that content remains available and usable.
- Track and retest fixes. Record barriers, prioritize those that block access to important content or tasks, then repeat the relevant checks after changes to content, themes, plugins, or custom components.
What changed in WordPress theme requirements
On May 6, 2026, WordPress’s accessibility team announced an update to accessibility-ready requirements. The updated material provides clearer titles, repeatable step-by-step pass/fail tests, and a standard way to document testing. It also clarifies that WCAG evaluates content and does not apply directly to a theme as a wrapper around content. The requirements now address topics including reflow and text spacing, unexpected context changes, hover and focus content, accessibility statements, and plugin recommendations. Read the announcement alongside the live requirements when evaluating a theme.
When to get additional help
If keyboard or screen-reader checks reveal barriers in custom components, complex forms, or essential user journeys that you cannot resolve confidently, consider an independent accessibility audit or remediation specialist. A focused review can help identify the underlying causes and verify fixes; it does not remove the need to maintain accessible content and retest changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
