Blog / WordPress /

A practical accessibility review for WordPress content editors

An editor writes a WordPress article with good headings, descriptive links and images. Then the published page shows heading levels that jump about, vague link text and an image with no useful alternative. It read well in the editor. Readers don’t see the editor. They see the rendered page.

An accessibility review for content editors should cover what editors can control: structure, language, links, images, media and how the content behaves in the theme. It doesn’t replace a technical audit. It does stop the same common barriers being published again and again.

Start in the rendered page

Review the public page at the same size and interaction conditions a reader might use. The block editor shows content structure, but the theme determines final contrast, spacing, focus visibility and responsive behaviour. Check the page on a narrow screen and zoom in. If it only works at one size, that needs attention.

Use a keyboard to move through links, buttons, menus and embedded controls. Confirm that the focus indicator is visible and that the order follows the content. If an interactive block can’t be reached or activated without a mouse, log it for the site owner. I wouldn’t ask an editor to publish around it.

Try a screen reader or the built-in accessibility inspection, but don’t lean on a tool alone. Automated checks catch some missing labels and contrast issues. They can’t decide whether a heading is meaningful or whether alt text conveys what the image is for.

Keep headings meaningful

Use headings to organise the article, not to make text appear larger. Start with a clear page title, then use sections that describe the content beneath them. Don’t pick a heading level just for how it looks. Styling belongs to the theme. Structure belongs to the content.

Read the outline without the paragraphs. Can a reader predict the content from the headings? If several sections are called “More information” or “Other details,” rewrite them to explain the topic. A useful heading helps someone scan and navigate, including a person using assistive technology.

Don’t skip levels for looks. A heading hierarchy needn’t be mechanically perfect in every odd layout, but arbitrary jumps make relationships harder to follow. If the editor can’t get the visual treatment without changing structure, ask for a reusable style from the theme. Don’t insert a heading just for size.

Use link text that describes the destination or action. A list of links read aloud as “click here” tells you nothing about where each goes. A descriptive phrase still fits naturally in the sentence. Just don’t stuff it with a keyword at the cost of clarity.

Check each destination and its purpose. A link should resolve to the intended page, and its wording should not promise information that the page does not contain. If it opens a document or starts a download, make that clear where a reader could otherwise be surprised.

Colour alone shouldn’t be what marks a link. The theme usually supplies the cues, but editors can inspect the result and flag links that blend into the paragraph. If they’re indistinguishable, that’s a design issue to escalate, not a reason to add awkward formatting.

Add alternative text with intent

Ask what role the image plays. If it conveys information not available in nearby text, write concise alternative text that communicates that information. If it is decorative or repeats adjacent text without adding meaning, use the appropriate empty alternative text setting when the WordPress workflow allows it.

Don’t paste the file name into the alt field, and don’t list every visual detail. I aim for equivalent information, not a catalogue entry. A chart may need a short alternative plus a nearby explanation of its important takeaway. A product image may need a concise description that distinguishes it from other variants, based on verified product facts.

Check captions and credit requirements too. A caption is visible to everyone and can add context; it does not automatically replace alternative text. Avoid placing important instructions only inside an image. If text in an image is essential, repeat it as accessible text nearby.

Review language and media

Use plain language and explain specialised terms. Keep paragraphs and lists structured. Do not create visual lists with manual symbols when WordPress offers a real list block. Use table headers correctly and avoid tables for layout. If a table is genuinely necessary, check that its structure remains understandable on mobile.

For video or audio, confirm that captions or transcripts are available where needed and that the player controls are operable. An embedded provider’s default controls won’t necessarily meet every requirement. Ask the responsible person to check the media before it’s published.

Check forms, buttons and calls to action within embedded blocks. Their labels should explain the action, and any instructions or errors should be perceivable. Content editors may not control the implementation, but they can report the exact page, block and observed barrier so a developer can reproduce it.

Make a repeatable pre-publication check

Create a short checklist inside the editorial workflow: meaningful headings, descriptive links, image alternatives, real lists, captions or transcripts, and a rendered keyboard check for interactive elements. Keep the checklist short enough to use, and pair each item with examples for your site’s content types.

Define escalation routes. An editor should know who to contact when a theme control is inaccessible, a block lacks a label or a table fails on mobile. Don’t make the editor invent a workaround that hides important information from some readers.

Review recurring issues with the WordPress team. If several editors make the same mistake, improve the component, template or guidance instead of relying on repeated correction. A small change to the publishing system can prevent a wider class of barriers.

Accessibility is part of whether a published page does its job for different readers. Open one recent WordPress article on the public site. Can you get through its structure and links without touching the mouse?