This page is adapted for people with low vision

Logo de adapta tu web
Logo de adapta tu web

ACCESIBILIDAD ≠ OVERLAY · 28

Accessibility ≠ Overlay: an overlay cannot fix underlying problems

📅 October 2026   ·   ⏱ 7 min read

A panel offering contrast or text-size settings may help some people, but it does not prove that a website is accessible.

01. Appearance is not structure

A panel offering contrast or text-size settings may help some people, but it does not prove that a website is accessible.

02. Code and semantic errors

Buttons without accessible names, unlabelled fields and incorrect heading structures require changes to the underlying code.

03. Understandable content

Informative images need meaningful text alternatives. Instructions and links must be clear, not merely larger or higher contrast.

04. Keyboard navigation and focus

Menus, dialogs and forms must work with a keyboard, with visible focus and a logical navigation order.

05. Assistive technology

Screen readers, magnifiers and voice control interact with the real page. An extra layer must not interfere with them.

06. What to test

Use Tab, Shift+Tab and Enter, then try a screen reader and mobile device. Check whether essential tasks can be completed.

07. Fix the source

Audit against WCAG, combine automated and manual tests, and repair components, content and interactions at their source.

08. Conclusion

Accessibility is designed, developed, maintained and verified. An overlay is no substitute for that work.

W3C — WCAG 2.2 · Adapta tu Web

🧑‍🦯 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 BlindReader
  • Go to Withdrawal Button
  • 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.


Jump to sections

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 223 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.