WordPress Accessibility Audit Checklist: WCAG Checks for Blogs and Publishers
WordPress accessibilityWCAGwebsite auditsblog designinclusive design

WordPress Accessibility Audit Checklist: WCAG Checks for Blogs and Publishers

TThemes.news Editorial Team
2026-11-20
8 min read

Use this WCAG-oriented WordPress accessibility checklist to audit themes, plugins, content, forms, media, keyboard use, and responsive layouts.

A WordPress accessibility audit helps you find barriers that automated scans alone can miss. This practical checklist covers WCAG-oriented checks for keyboard use, headings, contrast, links, forms, images, focus states, media, responsive layouts, and screen readers, with a repeatable review schedule for blogs and publishers.

Overview

Website accessibility means designing and maintaining a site that can be used by people with different vision, hearing, mobility, cognitive, and learning needs. For a WordPress blog, accessibility is shaped by more than the article editor. The active theme, block patterns, plugins, advertising components, forms, media players, and custom code can all affect the experience.

Use this WordPress accessibility checklist as a practical quality-control process rather than a one-time certification exercise. The goal is to identify barriers, record where they occur, fix the underlying pattern, and test again. Automated testing is useful for finding obvious issues, but it cannot reliably judge whether every image alternative is meaningful, whether link text makes sense in context, or whether a page is understandable when read in sequence.

When reviewing a site, use the Web Content Accessibility Guidelines (WCAG) as a reference framework, while treating any legal or organizational requirement as a matter for qualified, current advice in your location. Keep a record of the date tested, WordPress and theme versions, plugins involved, page templates reviewed, and unresolved issues.

What to track

1. Keyboard navigation and focus

Disconnect the mouse and try to use the site with a keyboard. You should be able to reach the skip link, logo, navigation, search, article links, comment controls, forms, media controls, menus, dialogs, and footer links. The tab order should follow a sensible visual order, and you should be able to close menus, pop-ups, and dialogs without becoming trapped.

  • Check that a visible focus indicator appears around the active control.
  • Confirm that focus is not hidden behind a sticky header, cookie notice, or advertising unit.
  • Test mobile navigation and any menu opened with a button.
  • Look for keyboard traps in sliders, embedded content, search overlays, and modal windows.

2. Heading structure and page landmarks

Review the heading outline of the homepage, category pages, author pages, and several article templates. Use one clear page title where appropriate, then organize sections in a logical hierarchy. Do not choose a heading level only because its visual styling looks attractive. A theme should let editors style headings independently from their structural level.

Check whether the page has identifiable navigation, main content, complementary content, and footer regions. Repeated elements such as sidebar widgets should have useful labels or headings. Remove empty headings and avoid using bold paragraphs as substitutes for headings.

3. Color, contrast, and non-color cues

Check body text, headings, metadata, buttons, navigation links, form labels, placeholder text, and text placed over images. Text should remain distinguishable from its background in normal and high-contrast viewing conditions. Also check borders, icons, charts, error messages, and links: color should not be the only way to communicate a state or difference.

Review the theme's color controls in both light and dark modes if the site supports them. Test links inside paragraphs, where an underline or another clear visual treatment may be important for recognition.

Link text should describe its destination or purpose. Repeated phrases such as “Read more” can be difficult to interpret when a visitor navigates through links out of context, so consider labels that identify the article or action. Buttons should describe an action, such as “Open search” or “Submit comment,” rather than relying on an icon alone.

Check that icons have accessible names, controls announce their expanded or collapsed state, and touch targets have enough space to use comfortably. Test menus, accordions, carousels, sharing tools, newsletter sign-ups, and any membership or subscription features.

5. Images and alternative text

Inspect featured images, inline images, logos, icons, infographics, and decorative backgrounds. A meaningful image should have alternative text that conveys its purpose in the article. Decorative images should not create unnecessary repetition for screen-reader users. If an infographic contains essential information, provide that information in nearby text or a fuller alternative.

Do not use the media library's filename as a substitute for useful alternative text. For editorial workflows, add an image review step before publication and make the responsibility clear to the person entering the image.

6. Forms, errors, and comments

Every form field should have a visible, programmatically associated label. Instructions should explain required formats, and required fields should not be identified by color alone. Submit a search form, newsletter form, contact form, login form, and comment form using only a keyboard.

Deliberately trigger an error. The message should identify what went wrong, explain how to correct it, and remain associated with the relevant field. Check whether focus moves to the error summary or another helpful location without disorienting the user.

7. Audio, video, and moving content

Video should provide captions when spoken information matters. Audio content may need a transcript, and video may need an audio description or equivalent text for important visual information. Check that autoplay is off or controllable, moving content can be paused, and animated elements do not create distracting or harmful effects.

8. Responsive layouts and readability

Test pages at narrow and wide viewport sizes, with increased browser text size where possible. Look for clipped text, overlapping controls, horizontal scrolling, disappearing focus states, low-contrast mobile menus, and content that becomes difficult to follow when columns stack.

Accessibility and readability often improve together. Use descriptive subheadings, short paragraphs, meaningful lists, consistent spacing, and plain language. The blog readability checklist can support this part of the review.

Theme-versus-plugin troubleshooting

Observed problemLikely area to inspectUseful next step
Headings or landmarks are inconsistent across templatesTheme, template, or block patternCompare the homepage, archive, and single-post templates; correct the reusable source.
Focus disappears or menus trap the keyboardTheme navigation or JavaScript pluginTest with plugins disabled in a staging environment, then isolate the component.
Form fields lack labels or errors are unclearForm or newsletter pluginReview field settings and test the generated markup and error flow.
Contrast changes in buttons, pop-ups, or adsTheme settings, ad code, or third-party embedRecord the exact component and review its styling at each display state.
Images repeat titles or have empty alternativesEditorial process or media settingsInspect the content entry workflow and correct the image purpose.

Change one variable at a time where possible. If a plugin appears responsible, confirm the result on a staging copy before changing production functionality.

Cadence and checkpoints

A repeatable audit is more useful than an occasional large review. Use a light monthly check for the site’s most important templates and a fuller quarterly review for the entire publishing system.

  • Before launching a new theme: test the homepage, archives, article page, navigation, search, forms, and responsive layouts.
  • After a theme or major plugin update: repeat keyboard, focus, contrast, form, and media checks, especially where the update changes front-end output.
  • Before publishing a new template: review headings, landmarks, links, image alternatives, and mobile behavior.
  • Monthly: sample new posts, featured images, newsletter forms, comments, ads, and embedded media.
  • Quarterly: run automated scans, perform manual keyboard testing, use a screen reader for representative journeys, and review unresolved issues.
  • After a reported barrier: reproduce it using the reporter’s steps where possible, record the affected device or assistive technology, fix the pattern, and retest.

Keep a simple worksheet with these columns: date, URL or template, issue, user impact, severity, suspected cause, owner, planned fix, verification date, and status. This turns an accessibility audit into a manageable publishing task rather than an unstructured list of warnings.

How to interpret changes

Prioritize barriers that prevent someone from accessing navigation, reading content, completing a form, controlling media, or understanding an error. A single issue affecting a shared theme component may be more important than several isolated article-level warnings because it can appear across many URLs.

Do not treat a clean automated report as proof that a site is fully accessible. Automated tools can flag missing labels, suspicious contrast, duplicate IDs, or structural problems, but a human still needs to judge meaning, order, clarity, and operability. Combine at least three perspectives:

  1. Automated testing: use it to find repeatable code and markup issues.
  2. Manual keyboard testing: use it to verify focus, order, controls, and traps.
  3. Assistive-technology testing: use a screen reader or other relevant technology to check names, roles, states, headings, landmarks, forms, and reading order.

When a score changes, compare the affected template and release history before assuming the problem is site-wide. A contrast warning may come from a new block style; a missing label may be limited to one plugin form; a broken heading outline may have been introduced by a reusable pattern. Fix the source pattern, then sample several pages to confirm that the repair propagates.

When to revisit

Revisit this WordPress accessibility checklist at least monthly for new content and quarterly for a broader website accessibility audit. Return immediately after changing WordPress themes, adding or replacing plugins, introducing a new ad or membership component, changing color schemes, rebuilding navigation, publishing a new template, or receiving an accessibility report.

Set a recurring calendar reminder and keep the last audit record beside your release notes. Review the guidance and testing tools periodically rather than assuming a previous result remains current; WCAG guidance, WordPress accessibility features, browser behavior, themes, and plugins can change. A six-month editorial review is a practical point for checking the checklist itself, while a release-triggered review is better for catching regressions.

To complete the next audit, choose five representative URLs: the homepage, an archive, a standard article, a form page, and a page with embedded media. Test each with the mouse disconnected, inspect headings and contrast, verify images and links, submit forms, resize the viewport, and perform a short screen-reader pass. Log every finding, fix shared components first, and retest the same journeys. If a theme change is planned, pair this process with the guide to changing a WordPress theme without losing SEO or site functionality so accessibility is included in the release plan rather than added afterward.

Related Topics

#WordPress accessibility#WCAG#website audits#blog design#inclusive design
T

Themes.news Editorial Team

Editorial Team

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.