Issue Bug Closed

#107717Error message on failed login not announced

Michael Telgkamp 10/16/25, 09:33 updated 12/02/25, 12:04

Description

Once an invalid username or password has been entered, an error message is displayed, but not automatically read by the screenreader.

Reproduction steps

  1. Go to Backend login /typo3/login
  2. Enter incorrect username / password combination
  3. Submit Login Form
  4. Errormessage is shown

clipboard-202510161124-mnxt8.png

Impact

Users does not know why login to TYPO3 Backend is not successful.

Target group

visually impaired user, screen reader user

Severity

high

Frequency

less common

Definition of Done

WHEN I use a desktop screenreader (NVDA, JAWS, VoiceOver) AND
I enter an invalid password/username combination that trigger the alert
I HEAR the error message when it appears (BUT focus DOES NOT transfer automatically when the alert appears)
I HEAR it identifies itself as an alert

Recommended solution

Define an assertive aria live region for the error message.

References / WCAG 2.2 Reference

1.3.1h, 3.3.1, 3.3.3, 4.1.3

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/alert_role
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Guides/Live_regions

Reviews 3

Files 1

History 710

  1. René Pflamm commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-10-23T19:35:09+00:00" > 10/23/25, 19:35 </span>

    Applied in changeset commit:3568faf15bdb40b13c5a1ca14bf8d6ec6403b4fc.

  2. Sébastien Delcroix commented <span data-processor="relativetime" data-value="2025-10-24T09:09:38+00:00" > 10/24/25, 09:09 </span>

    Question : is backend login involves any kind of Javascript/XHR/Ajax in TYPO3v13 ? (doesn’t seem to on my DDEV instance as I write)

    If not, just adding the role=“alert” attribute is not useful because the whole page is reloaded. So screenreaders don’t announce something has changed on the page.

    This only works with live ARIA-live regions that get their content updated “live”.

  3. Benjamin Franzke commented <span data-processor="relativetime" data-value="2025-10-27T16:33:45+00:00" > 10/27/25, 16:33 </span>

    Sébastien Delcroix wrote in #note-5:
    > Question : is backend login involves any kind of Javascript/XHR/Ajax in TYPO3v13 ? (doesn’t seem to on my DDEV instance as I write)
    >
    > If not, just adding the role=“alert” attribute is not useful because the whole page is reloaded. So screenreaders don’t announce something has changed on the page.
    >
    > This only works with live ARIA-live regions that get their content updated “live”.

    Hey, there’s JavaScript involved, yes, but the page is indeed changed and the role=“alert” is rendered as static content.

    This works anyway (tested with NVDA, Narrator and VoiceOver), which actually aligns to the spec, as this make an exception for alerts:

    > The exception to this live region convention is alert, due to system accessibility notifications events required for the role. While an alert is a live region, its content is announced by assistive technology when the alert is rendered on the page and when the content changes.

    https://w3c.github.io/aria/#aria-live:~:text=spoken%20or%20brailled.-,The%20exception%20to%20this%20live%20region%20convention%20is%20alert%2C%20due%20to%20system%20accessibility%20notifications%20events%20required%20for%20the%20role.%20While%20an%20alert%20is%20a%20live%20region%2C%20its%20content%20is%20announced%20by%20assistive%20technology%20when%20the%20alert%20is%20rendered%20on%20the%20page%20and%20when%20the%20content%20changes.,-Characteristics%3A

  4. Sébastien Delcroix commented <span data-processor="relativetime" data-value="2025-10-27T17:44:58+00:00" > 10/27/25, 17:44 </span>

    Thanks for your answer.

    MDN page about “alert” role doesn’t mention this exception, and says that content must be changed (or revealed) with Javascript : https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/alert_role

    I have trouble about testing this role in VoiceOver, how do you proceed ?
    When I fail to log in, the page is reloaded and read by VoiceOver as usual, so the error message is read too but it’s not announced as an alert.

  5. Sébastien Delcroix commented <span data-processor="relativetime" data-value="2025-11-12T09:21:26+00:00" > 11/12/25, 09:21 </span>

    @mte_mscr As initial issuer, can I have your feedback about this ?