ACCESIBILIDAD ≠ OVERLAY · 39

Form errors people can recover from

📅 12 November 2026   ·   ⏱ 6 min read

You choose a date, fill in your details and select ‘Book’. A red outline appears around the email field while your screen reader stays silent. To finish the booking, you need to know what happened, where to make the correction and whether the next attempt went through.

01. Make the error reach the person

An asynchronous response can leave focus on ‘Book’ while messages appear further up the page. An error summary gives people a way to discover the outcome and find the affected fields. An announced inline message may suffice for a short form. Where several fields fail, links in a summary let people choose which correction to make first.

02. Give a concrete next step

‘Invalid details’ sends people looking through the whole form. ‘Email address: enter an address in a format such as name@example.com’ identifies the field and describes the expected input. Ask for a date if none was selected. If a slot has sold out, say so and let the person choose another. Retain the other details where safe, so a correction leads straight to another attempt.

03. Distinguish an invalid value from a service failure

An incomplete email address and an unresponsive server call for different actions. For an incomplete address, point to the field and show the expected format. If the server fails to respond, marking a valid address as wrong would lead people to change information they entered correctly. Explain that the submission could not be confirmed and offer a way to try again. If the booking might already have been recorded, give the person a way to check its status before submitting again. They can then decide whether to wait or retry without risking an accidental duplicate.

04. Decide where focus goes after submission

In a booking form with several sections, you can move focus to an error summary at the start of the form. Use a heading that explains that some information needs attention, and link to each affected field. Activate a link with Enter and press Tab again. Scrolling the control into view is only part of the journey. Check where focus lands and what the screen reader announces when it arrives. For a single error with a reliably announced inline message, keeping focus in place can give the person more control over what to do next.

05. Give people time to finish typing

An email address looks incomplete while someone is still entering it. Announcing an error at every keystroke can compete with what the screen reader is already saying. Choose a sensible point for validation, such as a submission attempt. Once a field has been flagged, clear the error state when its corrected value has been validated. If you use a live region for an asynchronous response, test when the region is created and when its content changes. Listen to the result with assistive technology, especially where the form plugin also has an announcement of its own.

06. Keep the booking details available

Someone correcting an email address should still have access to the date, party size and preferences they selected. If a slot becomes unavailable during the correction, explain what has changed and provide the relevant choices again. Put format instructions beside the field before submission, particularly when the requirement is hard to guess. Placeholder text disappears as soon as people type and can leave them without the example they need to fix a value. A visible label and a description associated with the control let them find the information again when they return.

07. How Blind Reader helps

An overlay that only changes the appearance leaves the error unannounced. Blind Reader announces errors in real time in compatible forms, including Contact Form 7, Gravity Forms and WPForms. It works alongside the person’s screen reader. In the booking example, it can bring the validation feedback to the person immediately after they select ‘Book’. The form’s wording guides the correction. Test that the integrated message is heard once and the field is reachable by keyboard.

08. Check the integration on the booking page

Trigger a simple error using your usual combination of browser and screen reader. Note what is announced when you activate ‘Book’, which element keeps or receives focus and what you hear when you enter the field. Repeat with Blind Reader enabled and compare the spoken message with the text on screen. If two components announce the same text, decide which integration should deliver the announcement. Run the test again at higher zoom to check that the message stays visible near the field and that a fixed header leaves the destination in view when you follow a summary link.

09. Test recovery through to confirmation

WCAG 2.2 criteria 3.3.1 and 3.3.3 cover textual identification of detected errors and suggestions where known and appropriate. Associate feedback with its field, for example using aria-describedby, and mark validated invalid fields with aria-invalid. If you focus a summary, check that its links lead to the controls. Try a missing field, two simultaneous errors and a server rejection. Correct the inputs and resubmit. Verify that the success message is also perceptible with the keyboard and a screen reader.

W3C guidance · WCAG 2.2 · 3.3.1 · WCAG 2.2 · 3.3.3

10. Record a result the team can reproduce

Include the form URL, test inputs, keys pressed, expected message and observed result. For example, leave the email address blank, activate ‘Book’, listen for the error, navigate to the field and enter a valid address. Check that the other values remain available and that you can perceive the confirmation after resubmitting. Record the version of the form plugin and the Blind Reader configuration if they are relevant. Repeat the journey after changes to the form or theme. The record lets you verify the same barrier even when colours or layout change, and gives the person fixing the issue a clear starting point.

11. Check what happens if the second attempt fails

After correcting the email address, submit with a date the server will reject. Check that the earlier message clears and the new message describes the current problem. When the booking succeeds, the confirmation should indicate that the reservation is complete and provide the information the person needs to refer to it later. Try both outcomes without leaving the keyboard.

🧑‍🦯 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 18 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 1077 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.