Guide
2026-02-14
WordPress Accessibility Basics
Editor habits, plugin hygiene, and theme checks that prevent common failures at scale.
When to use this guide
When you manage blocks, themes, or plugins on WordPress and need CMS-aware context for the same rules the scanner shows.
Who this is for
Site builders and developers maintaining WordPress sites.
WordPress
Skips levels
Page title
Subsection (styled as heading but wrong level)
Logical sequence
H1 Page title
H2 Section
H3 Subsection
Do not rely on bold paragraphs for structure.
WordPress
No associated label
Placeholder is not a replacement for a label.
Label linked to field
Placeholders are not labels—check shortcodes and builders.
Scan while you read
Paste a public URL. You get a shareable report. Fix issues, deploy, then rescan the same URL to compare results.
Use blocks intentionally
Headings should come from heading blocks, not bold paragraphs. Lists should be real lists.
Plugin audit
If an accessibility scan fails after installing a plugin, open a ticket with the vendor early—do not let bad markup linger across posts.
Media library discipline
Alt text belongs in the attachment fields your theme actually outputs. Train authors on meaningful descriptions.
What to do after this
Keep the scan, fix, rescan loop going
Ship a fix, then run another scan on the same URL. Each run gets its own report link so you can compare before and after.
Open scan