ACCESIBILIDAD ≠ OVERLAY · 43

Announce what changes when a product goes into the basket

📅 18 November 2026   ·   ⏱ 2 min read

You activate ‘Add to basket’ with a screen reader. The counter changes and a green message appears, while the screen reader says nothing. Pressing again could add a second item. The shop needs to communicate the result while you stay on the button.

01. Say what happened

‘Blue jacket added. One item in your basket’ names the product and confirms the outcome. A bare number leaves people guessing. If the operation fails, explain what happened and how to proceed. Keep the feedback visible so it can be checked again.

02. Keep focus in place

For routine feedback, create a role="status" region before it is needed and update its text after the server confirms the operation. Use urgent alerts for incidents that need immediate attention. If a dialogue requires a decision, manage focus using the dialogue pattern and test where it returns on close.

03. Test repeat updates

A counter, toast and mini basket can update together and announce the same thing several times. Listen for duplicated or conflicting messages. Add the same item twice and check that the new quantity is announced. On slow connections, distinguish a pending operation from a confirmed result.

04. Test with assistive technology

Add an item, change its quantity and remove it using the keyboard and a screen reader. Check failures as well. Blind Reader offers guided basket review by voice in WooCommerce, PrestaShop and Odoo. Test both tools together for repeat announcements. WCAG 2.2 criterion 4.1.3 covers status messages conveyed without moving focus. WCAG 2.2 · 4.1.3

05. An example status region

Place the empty container in the page from the start. After the server confirms the action, set its message with textContent. Keep the same node for later updates and listen to the result with your usual screen reader.

<div id="cart-status" role="status"></div>
document.getElementById("cart-status").textContent =
  "Blue jacket added. One item in your basket.";
🧑‍🦯 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 12 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 347 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.