Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Guide

How to Make a WordPress Site Accessible (WCAG Basics)

Short answer

To make a WordPress site accessible, aim for WCAG 2.2 AA, pick a theme with an accessibility-ready tag, add alt text to images, keep normal text contrast at 4.5:1, and make every menu, form and button work by keyboard. Then fix headings, links, forms and media, and re-check the site with a keyboard and an automated checker. Most small sites can finish the main fixes in a few hours spread over a week.

Key takeaways

  • WCAG 2.2 is the current W3C standard, with 13 guidelines under 4 principles and 3 levels: A, AA and AAA.
  • Aim for WCAG 2.2 AA, which needs 4.5:1 contrast for normal text and 3:1 for large text.
  • An accessibility-ready theme tag does not mean the theme meets WCAG AA on its own.
  • Every image needs alt text, and decorative images need empty alt text so screen readers skip them.
  • All controls must work by keyboard, with a visible focus style and targets at least 24 by 24 CSS pixels.

What does it mean to make a WordPress site accessible?

An accessible WordPress site is one that people with disabilities can perceive, operate and understand, including with a keyboard or a screen reader.

Accessibility covers visual, hearing, movement and cognitive needs. The WordPress Accessibility Team puts it simply: the goal is to make WordPress usable by as many people as possible, for reading pages and for creating and maintaining sites (WordPress Accessibility Team Handbook).

You do not need to rebuild your site to start. Most fixes are content and theme choices: alt text, contrast, headings, links, forms and keyboard access.

What standard should you aim for?

Aim for WCAG 2.2 AA, the level most sites and laws use as their target.

WCAG stands for Web Content Accessibility Guidelines. The W3C published WCAG 2.2 on 5 October 2023, with an update on 12 December 2024, as of November 2026 (WCAG 2 Overview).

WCAG 2.2 has 13 guidelines, organised under 4 principles: perceivable, operable, understandable, and compatibility with browsers and assistive tools. Each guideline has testable success criteria at 3 levels: A, AA and AAA.

WCAG 2.2 adds 9 success criteria to WCAG 2.1, including a minimum target size and focus rules. Content that meets WCAG 2.2 also meets WCAG 2.1 and WCAG 2.0, according to the W3C.

LevelWhat it meansWho should aim for it
ARemoves the most severe barriersEvery site, as a minimum
AACovers contrast, keyboard use, labels and moreMost sites, including yours
AAAThe strictest level, with higher contrastSome specialist sites, not a general target

Level AAA is not a realistic target for a whole site, and the W3C notes that even AAA content will not suit every person. Pick AA, fix the A and AA criteria that apply to your pages, and record what you checked.

How do you pick an accessible WordPress theme?

Pick a theme that carries the accessibility-ready tag, then check its keyboard support, focus style and contrast yourself.

Go to Appearance, then Themes, then Add New, and use the feature filter to find themes tagged accessibility-ready. A theme with that tag has passed the WordPress theme review team checks for keyboard access, skip links, headings, contrast and more.

The tag is a starting point, not a certificate. The WordPress Theme Handbook states that accessibility-ready does not mean the theme meets WCAG AA level, only that it reaches the minimum standards the theme review team has set (Accessibility in the Theme Handbook).

Check these 4 points before you commit to a theme:

  • Tab through the demo with no mouse and confirm you can reach every menu, button and link.
  • Confirm the focus outline stays visible and is not removed.
  • Check that body text contrast looks strong, not pale grey on white.
  • Confirm the theme has a skip link that jumps past the header to the main content.

If you change themes later, repeat the same 4 checks. A new theme can undo every fix your old theme handled. For help weighing free and paid options, see free vs premium WordPress themes.

How do you write alt text in WordPress?

Write short alt text that states the purpose of each image, and leave decorative images with empty alt text.

Alt text is a text alternative for an image. WCAG success criterion 1.1.1 requires every non-text item shown to a user to have a text alternative that serves the same purpose, except for pure decoration (Understanding 1.1.1 Non-text Content).

In WordPress, open Media, then Library, select an image, and fill in the Alternative Text field. For an image already in a post, select the image block and add the alt text in the block settings panel.

The WordPress Theme Handbook gives the same rule for theme images: non-decorative images in img elements should have an alt attribute, and decorative images should use an empty alt attribute, alt="", so screen readers skip them.

Follow these rules for each image:

  1. Describe what the image shows or does in one short sentence.
  2. If the image is a link, use the link destination as the alt text, such as the post title.
  3. Do not start with “image of” or repeat the caption word for word.
  4. For a chart, give the main finding in the alt text and put the full data in a table nearby.
  5. Leave logos and dividers with empty alt text when they add no information.

For a step-by-step method, see how to write alt text with AI in WordPress.

How do you fix colour contrast on your site?

Raise text contrast to at least 4.5:1 for normal text and 3:1 for large text, and check buttons and form borders at 3:1.

Contrast is the ratio between text colour and background colour. WCAG 2.2 success criterion 1.4.3 sets 4.5:1 for normal text and 3:1 for large text, where large means 18 point text or 14 point bold text (Understanding 1.4.3 Contrast Minimum).

The WordPress Theme Handbook applies the same numbers to themes: plain content text must meet the AA ratio of 4.5:1, and a link with no underline needs 3:1 contrast against the surrounding non-link text.

Non-text items have their own bar. WCAG 2.2 success criterion 1.4.11 requires user interface parts and meaningful graphics to reach at least 3:1 against adjacent colours, so input borders, icons and focus marks must stand out too.

Fix contrast in this order:

  1. Check body text, headings and footer text first, since they appear on every page.
  2. Darken pale grey text, which is the most common failure.
  3. Underline links in body text instead of relying on colour alone.
  4. Check buttons, form fields and icons against their backgrounds at 3:1.
  5. Re-check after any brand colour change, since one colour edit can break many pages.

The AAA level raises normal text to 7:1, but that is an extra goal, not the AA target. If a brand colour cannot reach 4.5:1, use a darker shade of it for text and keep the brand colour for large headings or decoration.

How do you make your site work by keyboard only?

Make every link, button, menu, form field and popup reachable and usable with Tab, Shift plus Tab, Enter and Space, with a visible focus mark at each stop.

WCAG 2.2 success criterion 2.1.1 requires all functionality to work through a keyboard interface, without timing limits on keystrokes, except for input that depends on the path of movement, such as freehand drawing (Understanding 2.1.1 Keyboard).

The WordPress Theme Handbook adds that all controls must work by keyboard on all screen sizes, including menu buttons, submenus, dialogs, modals and popups. It also says the default focus style must not be removed unless a clearer focus style replaces it.

Do this keyboard check on your home page, a post, a page with a form, and your menu on a phone-sized screen:

  1. Click the address bar, then press Tab and move through the page.
  2. Confirm you can see the focus mark at every stop.
  3. Open each menu and popup with Enter or Space, and close it the same way.
  4. Fill in and submit the form without touching the mouse.
  5. Confirm you never get stuck in a menu, slider or popup with no way out by keyboard.

If a control only works on hover or on click, replace it with a real button or link. A div styled to look like a button is not a button for keyboard users.

Make pointer targets at least 24 by 24 CSS pixels, with space around small targets so people do not tap the wrong one.

WCAG 2.2 success criterion 2.5.8 sets the AA minimum at 24 by 24 CSS pixels for pointer targets. The stricter AAA level, 2.5.5, uses 44 by 44 CSS pixels (Understanding 2.5.8 Target Size Minimum).

Small targets can still pass if they have enough space around them, so a 24 pixel circle centred on each small target must not touch another target. Inline links inside a sentence are exempt, since their size follows the line height.

Check your header icons, social icons, pagination links and close buttons first. Those are the controls most often built too small. Add padding to reach 24 pixels, or add space between neighbours, and re-check on a phone screen.

Use one H1 per page, headings in order without skipping levels, and link text that makes sense on its own.

Headings break content into logical parts. The WordPress Theme Handbook notes that screen reader users scan a page by its headings and jump to a section through its heading, so headings must follow a logical order and not be used for visual style alone.

For content that changes without a page reload, MDN's ARIA guides explain that ARIA live regions expose those changes so assistive technology can announce them.

In the block editor, set the page title as the H1, then use H2 for main sections and H3 for parts inside them. Do not jump from H2 to H4, and do not use a heading only to make text large or bold.

Link text needs the same care. The Theme Handbook says link text should describe the linked page even when read out of context, since some tools list all links on a page, and bare URLs should never be used as links.

  • Use “Read the WordPress backup guide” instead of “click here”.
  • Use “Download the 2026 price list (PDF)” instead of “download”.
  • Avoid repeating “Read more” on every card, since each link then sounds the same.
  • Keep link text short, and put the file type or size in the link when it matters.

Pages and posts serve different jobs in WordPress, and that choice shapes your heading plan. See posts vs pages in WordPress before you restructure a section.

How do you make forms accessible in WordPress?

Give every field a visible label, group related fields, show errors in words, and keep the tab order the same as the visual order.

The WordPress Theme Handbook states that all input fields must have a label, and a placeholder is not a replacement for a label. It also says to group related controls with a fieldset and legend, and to keep tab order matching visual order.

Error messages need the same care. The handbook says post-submission responses, including errors, should always be perceivable, and error text should make sense when read on its own.

Build each form with this checklist:

  1. Label every field with visible text, such as “Email address”.
  2. Mark required fields in words, not by colour alone.
  3. Put the error message next to the field and at the top of the form after submission.
  4. Do not use colour alone for an error; add text and an icon.
  5. Confirm the form can be finished and submitted by keyboard alone.

Forms collect personal data, so check your privacy and consent wording at the same time. See GDPR compliance for WordPress for the rules that apply to forms on your site.

How do you make videos, audio and moving content accessible?

Add captions to videos, a transcript for audio, and a way to pause or stop motion that starts on its own.

WCAG 2.2 requires a text alternative that at least names time-based media, and its media guideline adds captions for prerecorded video with sound. A transcript gives the same words in text for people who cannot hear the audio.

In WordPress, upload a captions file with the video block where your host or plugin supports it, and add a transcript below the video or as a linked page. For audio, place the transcript right after the player.

Motion needs a control too. Sliders, carousels and videos that play on their own should have a pause or stop button that works by keyboard. If a slider moves every few seconds, many readers cannot finish a slide before it changes.

Keep these 3 rules for media:

  • Never use sound alone to give key information, such as a success chime with no text.
  • Never flash content more than 3 times per second, since flashing can trigger seizures.
  • Do not hide the pause control behind a hover state that keyboard users cannot reach.

How do you check if your WordPress site is accessible?

Check it in 3 ways: an automated scan for common faults, a keyboard pass, and a screen reader pass on your main page types.

Automated checks catch missing alt text, low contrast and missing labels, but they miss many faults. The web.dev accessibility course covers automated testing, manual testing and assistive technology testing as separate steps, and treats them as a set (Learn Accessibility).

Run this check on your home page, one post, one page, your contact form and your checkout or signup page if you have one:

CheckHow to do itPass mark
Automated scanRun your checker on each page type and list every faultNo missing alt text, labels or contrast faults left
Keyboard passTab through each page with no mouseEvery control reachable, focus always visible
Text resizeRaise browser text size to 200%All text and controls still usable, with no overlap
Screen reader passListen to headings and links in orderHeadings in order, links make sense alone
Mobile passRepeat the keyboard and resize checks at phone widthMenus, forms and targets still work

The WordPress Theme Handbook sets the resize bar at 200%: all content and functions must stay available when text is resized to 200% of its size, with no overlap or two-way scrolling.

Fix faults in this order: keyboard traps first, then missing labels and alt text, then contrast, then headings and link text. Re-run the scan after each round of fixes, since one theme or plugin change can add new faults.

A theme and its plugins are only part of the result. The WordPress Accessibility Team notes that the tag and the theme are a wrapper, and your content decides much of the final result, so check real pages, not the theme demo alone. For the theme-versus-plugin split, see theme vs plugin in WordPress.

What mistakes should you avoid?

Avoid removing the focus outline, using colour alone, writing vague link text, and treating a plugin or a badge as proof of access.

These are the faults that recur most often on WordPress sites:

  • Removing outline: none with no replacement focus style, so keyboard users lose their place.
  • Using colour alone for errors, links or required fields.
  • Adding an accessibility plugin and assuming the site is now accessible, with no keyboard or screen reader check.
  • Writing “click here” or “read more” for every link.
  • Skipping heading levels or using headings for visual style.
  • Publishing images with no alt text, or with the file name as alt text.
  • Letting a slider, popup or cookie banner trap keyboard focus.

Fix one fault type across the whole site before moving to the next. That keeps the work in order and stops the same fault from returning in new posts.

Frequently asked questions

What is the difference between WCAG A, AA and AAA?

A is the lowest level and removes the most severe barriers, AA adds contrast, keyboard, label and other common rules, and AAA is the strictest level with higher contrast and extra rules. Most sites aim for AA, since AAA is not a realistic target for a whole site and some AAA rules do not fit every type of content.

Does an accessibility-ready theme make my site WCAG compliant?

No. The tag means the theme passed the WordPress theme review team checks for keyboard access, skip links, headings, contrast and more. It does not mean the theme meets WCAG AA on its own, and your content, plugins and settings can still add faults. Check real pages with a keyboard and a checker after you install the theme.

Do I need an accessibility plugin to make WordPress accessible?

No. Most fixes come from the theme, the content and the form settings: alt text, contrast, headings, labels and keyboard access. A plugin can help with a specific job, such as adding a skip link or a statement page, but it cannot fix vague link text, missing labels or a theme that traps keyboard focus.

How long does it take to make a small WordPress site accessible?

A small site with a few pages can finish the main fixes in a few hours spread over a week: pick or fix the theme, add alt text, fix contrast, label forms and check by keyboard. Larger sites take longer, since each page type, form and plugin needs its own check. Re-check after every theme or plugin change.

What should I put in an accessibility statement for my WordPress site?

State the standard you aim for, such as WCAG 2.2 AA, list the parts you have checked, note any known limits, and give a contact route for access problems. Keep the statement honest: do not claim full compliance for pages you have not checked, and update it when you fix faults or change the theme.

Can I check accessibility without a screen reader?

You can catch many faults without one: run an automated checker, tab through every page by keyboard, resize text to 200 percent, and check contrast ratios. A screen reader pass still matters, since it shows how headings and links sound in order. Use a free screen reader for a short pass on your main page types.

Sources

  1. WCAG 2 Overview W3C Web Accessibility Initiative
  2. Web Content Accessibility Guidelines (WCAG) 2.2 W3C
  3. Understanding Success Criterion 1.4.3: Contrast (Minimum) W3C Web Accessibility Initiative
  4. Understanding Success Criterion 2.5.8: Target Size (Minimum) W3C Web Accessibility Initiative
  5. Accessibility - Theme Handbook WordPress Developer Resources
  6. WordPress Accessibility Team Handbook Make WordPress Accessible
  7. Learn Accessibility web.dev
  8. ARIA guides MDN Web Docs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test