#109137Optimize Flash Message
Description
Steps to reproduce
Log in to the TYPO3 backend.
Trigger or navigate to a backend view where system / info / warning / error messages (“flash messages”, status messages) are displayed (e.g. after saving a backend-user record by chnages username).
Use a screen reader (e.g. NVDA) to navigate to the messages section.
Inspect how each message is announced (including icon, text content, and any headings or structural information).
Current result
Each message includes an icon indicating the level of severity (e.g. info, success, warning, error), but these icons are hidden from assistive technologies.
The only remaining distinction between different message types is their background color and/or visual styling.
There is no programmatic information about the criticality or severity of the message, such as a textual severity indicator (“Information”, “Warning”, “Error”) that is exposed to assistive technologies.
The message container/section does not provide a heading that groups and identifies the area as “Messages”, “Notifications”, or similar.
As a result, screen reader users cannot reliably distinguish between different levels of messages or quickly understand that they are in a message/notification area.
Expected result
Each message exposes its severity level programmatically, not just via color or purely visual cues.
Screen reader users receive clear information about the level of the message, e.g. “Information”, “Success”, “Warning”, “Error”, in addition to the actual message text.
The message area is structured with a heading (e.g. a visually hidden heading) that clearly identifies the section as system messages or notifications.
The information about criticality and structure is available on the code level (e.g. via text, headings, or text alternatives), in line with BITV / WCAG requirements.
Impact
Affects blind and visually impaired users as well as users with certain cognitive disabilities who rely on explicit text and structure instead of color alone.
Without programmatically exposed severity information, users may miss critical warnings or errors, or misinterpret a message’s importance.
This violates BITV / WCAG 2.1 criterion 1.4.1 (Use of Color), as color is currently the only way to distinguish the criticality of messages, and the information is not redundantly conveyed in text or accessible attributes.
The lack of a heading for the messages section also impacts perception and navigation of the area, making it harder to find and understand notifications.
Recommended solution (for context, not a separate section in Forge)
As a quick fix, include the severity level as visually hidden text within each message, e.g.:html
{Severity}
where the severity level is taken from the message data.
As a more robust improvement, expose the severity level as a heading for each message (e.g.
Warning
followed by the message text), with styling as needed (including visually hidden, if appropriate).Add a heading for the overall messages area (e.g.
System messages
), so that assistive technologies can identify the section.Definition of done
Each backend message (info, success, warning, error, etc.) exposes its severity level in a programmatically accessible way (e.g. via visible or visually hidden text and/or heading), not relying solely on color or icon styling.
The messages area has a heading (visible or visually hidden) that clearly identifies the section as messages/notifications.
Screen reader testing (at least one common screen reader + browser combination) confirms that:
The severity level of each message is announced.
The messages section can be identified as a logical region or section with a heading.
The visual appearance of messages remains unchanged or only minimally adjusted, without regressions in layout or styling.
The implementation aligns with BITV / WCAG 2.1 criterion 1.4.1 (Use of Color) and improves structural clarity for assistive technologies.
Acceptance criteria
Each message contains a textual representation of the severity level (e.g. “Information”, “Success”, “Warning”, “Error”), either as visible text or as visually hidden text that is still announced by screen readers.
The messages area includes a heading (e.g. “System messages” or “Notifications”), which may be visually hidden but is exposed to assistive technologies.
Color is no longer the only means of distinguishing message criticality; the same information is available in text or accessible markup.
Screen reader testing confirms that:
The severity level is announced together with the message.
The messages section is discoverable via heading navigation.
No regressions occur in the appearance and behavior of messages for sighted users.
An accessibility review confirms that the implementation satisfies BITV Prüfschritt 9.1.4.1 (Use of Color) for this component.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.