<h2>Use blocks intentionally</h2>
<p>Headings should come from heading blocks, not bold paragraphs. Lists should be real lists.</p>
<h2>Plugin audit</h2>
<p>If an accessibility scan fails after installing a plugin, open a ticket with the vendor early—do not let bad markup linger across posts.</p>
<h2>Media library discipline</h2>
<p>Alt text belongs in the attachment fields your theme actually outputs. Train authors on meaningful descriptions.</p>


Editor habits, plugin hygiene, and theme checks that prevent common failures at scale.

WordPress Accessibility Basics

<h2>Structure</h2>
<ul>
<li>[ ] Logical heading order on key templates</li>
<li>[ ] One clear primary action per screen where possible</li>
<li>[ ] Skip link to main content on content-heavy pages</li>
</ul>
<h2>Media</h2>
<ul>
<li>[ ] Alt text for informative images; empty alt for decorative</li>
<li>[ ] Captions for spoken video; transcripts when audio-only matters</li>
</ul>
<h2>Forms</h2>
<ul>
<li>[ ] Visible labels or programmatic equivalents</li>
<li>[ ] Error messages tied to fields, not only color</li>
</ul>
<h2>Keyboard</h2>
<ul>
<li>[ ] Full task completion without a mouse</li>
<li>[ ] Visible focus on all interactive elements</li>
</ul>
<h2>Verification</h2>
<p>Run an automated scan on production-like URLs, then repeat the keyboard pass after fixes.</p>


A concise preflight list for designers, developers, and content owners before you flip DNS.

Accessibility Checklist Before Launching a Website

<p>This guide mirrors our blog article with a few extra notes for workshops:</p>
<ul>
<li>Map WCAG success criteria to your design system backlog.</li>
<li>Pair each release train with a short regression scan on templates.</li>
<li>Publish internal examples of good vs. bad patterns so authors copy the right thing.</li>
</ul>
<p>For deep dives, pair this guide with the issue library and platform-specific checklists.</p>


A slightly longer companion to the blog primer—useful for stakeholders who want talking points without reading the full spec.

WCAG Explained in Plain English (Guide)

<h2>Themes matter</h2>
<p>Pick accessible foundations, then customize carefully. Custom CSS can destroy focus rings and heading order.</p>
<h2>Apps are wildcards</h2>
<p>Test cart drawers, upsell modals, and reviews widgets with the same rigor as first-party sections.</p>
<h2>Operational rhythm</h2>
<p>Rescan before peak seasons. Compare public report URLs sprint over sprint so regressions do not sneak in.</p>


Theme-level habits, app risk, and content workflows that keep storefronts more inclusive.

Guides

Start here

By platform