The Complete Accessibility Checklist for WordPress Content Editors

Maintaining a fully accessible WordPress website is not just a technical responsibility—it’s an ongoing content discipline. If you manage or publish posts, your decisions directly impact whether people using screen readers, keyboard navigation, or other assistive technologies can fully engage with your content.

This guide is designed as a practical, repeatable reference for anyone creating or editing posts in WordPress. Use it as a checklist every time you publish.


1. Use Proper Heading Structure

Headings are not just visual—they define the structure of your page for assistive technologies.

Best practices:

  • Use one H1 per page (usually the post title).
  • Use H2s for main sections, H3s for subsections, and so on.
  • Never skip heading levels (don’t jump from H2 to H4).
  • Do not use headings purely for styling.

Why it matters:
Screen reader users rely on headings to navigate content quickly.


2. Always Add Descriptive Alt Text to Images

Every meaningful image must include alternative text.

Best practices:

  • Describe the purpose of the image, not just what it looks like.
  • Keep it concise but informative.
  • Leave alt text empty ("") only for decorative images.

Examples:

  • Bad: “image1.jpg”
  • Better: “Nurse assisting an elderly patient with home care visit”

Avoid vague links like “click here” or “read more.”

Best practices:

  • Make link text descriptive and meaningful out of context.
  • Indicate if a link opens in a new tab or downloads a file.

Examples:

  • Bad: “Click here for the report”
  • Better: “Download the 2025 Annual Accessibility Report (PDF)”

4. Ensure Sufficient Color Contrast

Text must be readable against its background.

Best practices:

  • Maintain a contrast ratio of at least 4.5:1 for normal text.
  • Avoid using color alone to convey meaning (e.g., “items in red are required”).
  • Test buttons, links, and overlays as well.

5. Use Lists Properly

Lists help structure content clearly.

Best practices:

  • Use bulleted or numbered list blocks instead of manually typing dashes or numbers.
  • Keep list items concise and parallel in structure.

6. Make Tables Accessible

Tables should only be used for data, not layout.

Best practices:

  • Use table headers (th) for column and/or row headings.
  • Include a clear header row.
  • Avoid complex merged cells when possible.

7. Provide Accessible Media

Audio and video content must be usable by everyone.

Best practices:

  • Add captions to all videos.
  • Provide transcripts for audio content.
  • Ensure media players are keyboard accessible.

8. Use Clear and Simple Language

Accessibility includes cognitive accessibility.

Best practices:

  • Write in plain language.
  • Use short paragraphs and sentences.
  • Avoid jargon or explain it when necessary.

9. Avoid Using Text Inside Images

Text embedded in images cannot be read by screen readers.

Best practices:

  • Use real text instead of image-based text whenever possible.
  • If unavoidable, replicate the text in the alt description.

10. Ensure Keyboard Accessibility

Some users navigate without a mouse.

Best practices:

  • Make sure all interactive elements (links, buttons, forms) are reachable via keyboard.
  • Avoid embedding content that traps focus (e.g., poorly implemented iframes).

Buttons and links serve different purposes.

Best practices:

  • Use buttons for actions (e.g., submit, open modal).
  • Use links for navigation.
  • Avoid using generic containers styled as clickable elements without proper roles.

12. Label Forms Clearly

Forms are one of the most common accessibility failure points.

Best practices:

  • Every input must have a visible label.
  • Use placeholder text only as a supplement, not a replacement.
  • Provide clear error messages and instructions.

13. Avoid Auto-Playing Content

Unexpected motion or sound can create barriers.

Best practices:

  • Do not autoplay videos or audio.
  • Avoid animations that cannot be paused or stopped.
  • Respect reduced motion preferences.

14. Use ARIA Sparingly and Correctly

ARIA attributes can improve accessibility—but only when used properly.

Best practices:

  • Do not add ARIA roles unless necessary.
  • Never override native HTML semantics without a strong reason.
  • If you don’t understand ARIA, rely on standard WordPress blocks instead.

15. Test Your Content Before Publishing

Even experienced editors make mistakes.

Checklist before publishing:

  • Navigate your post using only the keyboard.
  • Scan headings for logical order.
  • Check all images for alt text.
  • Verify link text clarity.
  • Review contrast visually.

16. Use Accessibility Plugins Carefully

Tools can help, but they are not a substitute for good content practices.

Best practices:

  • Treat plugins as support, not a fix-all solution.
  • Manually verify anything flagged or “auto-corrected.”

17. Maintain Consistency Across Posts

Accessibility is easier when patterns are consistent.

Best practices:

  • Follow the same heading and formatting patterns across all posts.
  • Reuse accessible blocks and templates.
  • Avoid introducing one-off styles or structures.

Final Pre-Publish Checklist

Before you hit publish, confirm:

  • Headings are structured correctly
  • All images have appropriate alt text
  • Links are descriptive
  • Color contrast is sufficient
  • Lists and tables use proper markup
  • Media includes captions or transcripts
  • Content is clear and readable
  • No critical functionality requires a mouse
  • Forms (if present) are fully labeled

Closing Thoughts

Accessibility is not a one-time task—it’s a habit. The more consistently you apply these practices, the more natural they become. A truly accessible site is the result of many small, deliberate decisions made at the content level.

Use this guide every time you create a post, and you’ll not only meet accessibility standards—you’ll create a better experience for every user.

More Articles
  • A tranquil scene of Canadian Geese flying in formation against a clear sky in Decatur, Alabama.

    How to Migrate a Magento Commerce Website to WordPress and WooCommerce: A Step-by-Step Guide

    If your Magento Commerce website has become expensive to maintain, difficult to customize, or more complex than your business needs, you’re not alone. Many businesses are making the move to WordPress and WooCommerce to reduce costs, simplify website management, and gain greater flexibility for content marketing and SEO. A successful migration requires more than simply…

  • Close-up of a bright yellow disabled symbol on textured asphalt, indicating accessibility.

    Website Accessibility Review Workflow

    Version: 1.0Standard: WCAG 2.2 AAAudience: Web Developers, QA Testers, UI Designers Phase 1 – Automated Accessibility Scan Goal: Find common accessibility issues before manual testing. Checklist ☐ Run an accessibility scan on every page template. ☐ Review all reported errors. ☐ Fix high-impact issues first: ☐ Re-run scan until no critical issues remain. Recommended Tools…

  • accessible parking spot comparing ADA rules to WCAG rules

    What Is the Industry Standard Website Scanner for WCAG Compliance?

    If you’re trying to make your website accessible, one of the first questions you’ll probably ask is: “What’s the industry-standard scanner for WCAG compliance?” The short answer is: there isn’t just one. While several excellent accessibility scanners exist, no automated tool can certify that a website is fully compliant with the Web Content Accessibility Guidelines…