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.

🧑‍🦯 Blind Reader
Intent narrator ready.

Accessibility guide

This is a functional summary, not a literal reading.

Go to primary goal Jumps to the main action area (form, list or contact).

Page type: article. The main goal seems to be: to inform you.

There are 13 sections you can jump to.

Before continuing:

  • Handle cookies/consent Reason: Detecté un aviso relacionado con cookies/consentimiento. — Recommended route: Contenido principal

Go by goals

Choose what you want to do. I will explain it, then ask before jumping.

  • Handle cookies/consent Important: this may block navigation.
  • Go to article content
  • Go to comments
  • Go to end of article
  • Back to News / Blog
  • Previous post
  • Next post
  • Go to Home
  • Go to About
  • Go to Products
  • Go to BlindReader
  • Go to Withdrawal Button
  • Go to Intent Flow
  • Go to Services
  • Go to Blog
  • Go to Contact
  • Go to Español
  • Go to Català
  • Go to Polski
  • Go to Română
  • Go to Italiano
  • Go to Français
  • Go to Svenska
  • Go to Deutsch
  • Go to Nederlands
  • Go to Português
Goal options
Confirmation mode

Choose how often I should ask before jumping.



Learning scope (only for “first time”)

Site: remember this goal across the whole site. Page: remember per URL.


Guided navigation

The guide announces one section at a time.

How it works: Start guide announces the first key section and scrolls to it. Next moves to the following section. To move focus to the section, use Go to current section. Stop exits.

Status: Guide inactive

Go to current section This link updates as the guide advances.

This article has approximately 438 words.

Moves focus to the start of the content, skipping menus and secondary elements.

About Blind Reader

Blind Reader is an accessibility assistant that analyzes each page and narrates its purpose, key sections and recommended actions — designed for screen reader users.

Compatible page builders: Works with any WordPress theme or builder: Divi, Elementor, Gutenberg, WPBakery, Avada and others. It reads the real content of the page, not the builder markup.

Does it interfere with your content? It does not change your texts or your design. It only adds an accessible panel and fixes technical accessibility attributes (for example, names of buttons without text) so that screen readers announce them correctly.

How does it work? It analyzes the page structure (headings, links, forms, landmarks) and generates a functional summary. The guide and goals help navigate without having to scan the whole page.

Keyboard shortcut: Press Alt + G to jump directly to the first goal.