ACCESIBILIDAD ≠ OVERLAY · 41
Headings that help screen reader users find their way
📅 16 November 2026 · ⏱ 2 min read
You want to check a product’s returns policy before purchasing. You open the product page and bring up your screen reader’s heading list. If ‘Delivery and returns’ is merely styled in bold, it may be absent from that list. A semantic heading makes the section discoverable.
01. Plan the hierarchy
Use the product name as the page heading and organise the main sections as level-two headings. ‘Delivery times’ and ‘How to return a product’ can sit at level three under ‘Delivery and returns’. Return to level two for a peer section such as ‘Reviews’. Style each level with CSS and check what Divi actually outputs.
02. Write headings for the list
‘More information’ tells you little when it appears in several places. ‘Return deadline’ explains what the section is for before you read it. Open the published page and check the list of headings on desktop and mobile. Make sure there are no duplicate controls or headings from an inactive layout.
03. How Blind Reader helps
Blind Reader uses headings and other page cues to summarise the structure and guide people to sections. It works alongside their existing screen reader. On a product page, a semantic ‘Delivery and returns’ heading gives both tools a useful signal. A visual overlay can resize the words. Heading markup communicates their role.
04. Test the shopping task
Open the heading list, find ‘Delivery and returns’ and read the following paragraph. Check the announced levels, order and link to the relevant policy. Repeat with the Blind Reader guide and after changing the Divi template. WCAG 2.2 criterion 1.3.1 covers structure and relationships conveyed by presentation. WCAG 2.2 · 1.3.1
05. Run a comparison in the editor
In a copy of the page, style ‘Delivery and returns’ as a bold paragraph and put the policy below it. Check the heading list in the preview. Change the paragraph to a level-two heading and check again. Select the new heading and see whether you can read the policy from that point. If it takes you elsewhere, check where the heading sits in the published layout.
06. Retest when the template changes
Try a product with multiple variations and one without reviews. Conditional sections change the outline, so check that the remaining headings still describe the page. If the mobile policy is inside an accordion, test the button and its expanded state. Save the product URLs and expected heading sequence so the next editor can repeat the test.

