An accessibility review for a routine WordPress edit starts with what changed. A new section needs a meaningful place in the heading structure. A replacement image needs an appropriate text alternative. A revised jump link needs to reach the intended section.
These checks belong partly in the editor and partly in the rendered page. The editor shows the content you control; the page also includes the theme, templates, plugins, and other elements that readers encounter.
Consider an ordinary revision to an established article: adding a preparation section, replacing its featured image, and updating a quick-navigation link. The workflow below follows those changes without turning a small edit into a full accessibility evaluation.
Start with the changes
Suppose a home-improvement article already contains an introduction, several main sections, and a short navigation list. You are adding “Prepare the room,” replacing a decorative featured photograph with a photograph showing a specific condition, and adding a navigation link to the new section.
Before editing, identify the questions those changes introduce:
- Does the new section belong alongside the existing main sections or inside one of them?
- What information does the replacement photograph contribute?
- Will the navigation link point to a unique, stable destination?
- Does the finished page still make sense in reading order and at a narrow width?
This keeps the review connected to the revision. If you also notice an unrelated barrier, record it separately rather than losing it—or allowing it to obscure the checks needed for this edit.
Place the new section in the heading structure
Open the Outline tab in WordPress’s Document Overview and review the article’s headings. The WordPress Heading block documentation describes this view and the controls for changing heading levels. Exact controls can vary with the installed version and editing environment.
If “Prepare the room” is a main section alongside “Choose materials” and “Plan the work,” it should normally use the same heading level. If it belongs inside a broader preparation section, it should be a subsection instead.
For an article whose template supplies the post title as an H1, a straightforward structure might be:
- H1: Planning an Interior Painting Project — supplied by the template
- H2: Choose materials
- H2: Prepare the room
- H3: Protect furniture and floors
- H3: Keep access routes clear
- H2: Plan the work
Do not add another body H1 just because the post title is absent from the content area. Many themes render the title separately. WordPress’s documentation notes that this behavior depends on the theme or template, so confirm the result rather than assuming it.
The editor’s Outline is useful for reviewing content structure, but it is not a complete account of every heading on the finished page. Preview the article and, where needed, inspect its headings using browser developer tools or an accessibility inspection tool. Check whether the template actually supplies the expected H1.
Choose heading levels for relationships, not font size. If the new H2 looks too large, that is a presentation question—not a reason to turn it into an H4. The broader principles are covered in heading hierarchy.
Review the replacement image by purpose
Changing an image can change its accessibility requirements even when its position stays the same.
Suppose the old featured image was an atmospheric room photograph. The replacement shows furniture grouped in the center of a room, with a clear route to the doorway. If the article uses that photograph to demonstrate preparation, the image now contributes information.
A suitable text alternative might be:
alt="Furniture grouped in the center of the room, leaving a clear route to the doorway"
The description communicates the relevant arrangement. It does not need to inventory every object or repeat the article title.
If the image serves only as visual decoration and adds nothing beyond the surrounding content, an empty alternative, alt="", may be appropriate. An empty alternative is different from a missing alt attribute.
Check how WordPress uses the image
A featured image may be rendered by the theme rather than an Image block. It may also appear in archive cards or other shared layouts. Do not assume that changing a Media Library field updates every existing use, or that every template outputs the image in the same way.
Check the relevant rendered placement:
- Does the image have the intended text alternative?
- Does the crop preserve the detail the article discusses?
- Is important information also explained in the article text?
- If the image is linked, does the link have a useful accessible name?
A linked image needs particular care. An empty alternative may suit a decorative image inside a link that also contains descriptive text. It can leave an image-only link unnamed if no other accessible label is provided.
For a more detailed treatment of these decisions, see accessible images and alternative text.
Check the revised jump link
For the new preparation section, add a unique HTML anchor to the heading, such as prepare-the-room. Link to it from the article’s navigation using #prepare-the-room.
In the Heading block’s HTML Anchor field, enter the identifier without the leading #. The link destination includes it:
<a href="#prepare-the-room">Prepare the room</a>
<h2 id="prepare-the-room">Prepare the room</h2>
Before replacing an existing anchor, consider whether other pages or saved links may already point to it. A wording change does not necessarily require changing the identifier.
Test the link in the rendered preview:
- Use Tab to reach the navigation link and confirm that its focus indicator is visible.
- Press Enter to activate it.
- Check that the intended section becomes visible and is not hidden beneath a fixed header.
- Continue navigating and check that the next steps remain understandable.
Scrolling to a heading and moving keyboard focus are related but not identical behaviors. A visual jump alone does not establish how navigation will continue. If keyboard or screen-reader behavior is unclear, record the observed result rather than adding untested focus scripts or ARIA attributes to the article.
Anchor jump links explains the underlying navigation pattern in more detail.
Review the rendered article
Use WordPress Preview to review the page outside the editing canvas. Check the affected section and its immediate surroundings, including the title, featured image, and quick navigation.
For this revision, a focused pass includes:
- Reading order: Does the introduction lead naturally into navigation and article content? Does the new section appear where its explanation belongs?
- Heading relationships: Does the rendered title and section structure match the intended hierarchy?
- Links: Does the changed link reach the correct destination, with wording that makes sense in context?
- Narrow layout: At a small viewport, does text remain readable without clipping or unnecessary horizontal scrolling? Does the image retain its relevant detail?
- Keyboard use: Can the changed interaction be reached and used, with visible focus?
If the revision replaces an embed rather than a jump link, test that affected interaction instead. For a video, this may include checking keyboard access to playback controls and the availability and usefulness of captions. Merely seeing the player load does not establish that readers can use it.
A preview may differ from the public page because of caching, permissions, or template behavior. After an authorized publication, confirm the changed area on the public page as part of the normal publishing check.
Hand off problems outside the article
Some findings belong to the theme, a shared template, or a plugin. A missing template title, an unnamed image-only link, or a fixed header covering anchor targets may not be safely repairable in article content.
A useful handoff describes the result and how to reproduce it:
On the article preview, activating “Prepare the room” from the quick navigation scrolls to the correct section, but the fixed site header covers the heading when the viewport is 375 CSS pixels wide. I reproduced this with keyboard activation in Firefox. The heading anchor is
prepare-the-room. I have not changed the theme or tested other templates.
Include the URL or preview reference, browser, relevant viewport or zoom setting, reproduction steps, expected result, and observed result. Add a screenshot or short recording when it clarifies the issue, but retain a written explanation.
Distinguish the observation from the suspected cause. “The heading is covered” is an observation; “the theme needs an offset adjustment” is a possible diagnosis.
If markup inspection or validation is needed, the HTML validation workflow explains how to trace findings to the responsible source layer. A clean validation report does not, by itself, establish accessibility.
Record what the review covered
A brief review note can preserve useful boundaries:
Reviewed the added section’s heading level, the replacement image’s purpose and rendered alternative text, and the revised jump link. Checked the affected area with a keyboard and at a narrow viewport. Recorded the fixed-header overlap for the maintainer. No full-page screen-reader evaluation or sitewide accessibility audit was performed.
This is more informative than marking the article “accessibility checked” without qualification.
A routine editorial review can catch meaningful barriers, but it does not establish that the page or website meets every accessibility requirement. Its purpose is narrower: understand what changed, check the consequences readers are likely to encounter, correct what is within the editor’s control, and give the next responsible person enough evidence to continue.