UI5 / UI5/webcomponents

[Dialog|A11Y]: Extra unexpected data is read by screenreaders inside Dialog window

Open
#13,562 7 comments 0 reactions 1 assignee View on GitHub

@unazko is already working on this.

Since Jun 11, 2026.

ACC bug documentation Medium Prio TOPIC B
Dominant language
TypeScript
Stars
1.8k
Forks
285
Avg merge
3d 2h
Merged PRs (30d)
59

Description

Bug Description

When a modal dialog is opened JAWS screen reader announces additional, irrelevant information such as "Header toolbar. To move through the toolbar use left or right arrow," which is not part of the modal dialog content. This can confuse users and detract from the intended user experience.

Image
Affected Component

Dialog

Expected Behaviour

Expected result:

Upon opening the modal dialog, JAWS should announce only the modal dialog content (e.g., modal title and the first interactive element). No information from outside the modal (such as toolbars or headers) should be announced.

WCAG/BP: 4.1.2 Name, Role, Value

Help links/Techniques: https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/examples/dialog/

Recommendation: According to MDN (https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/toolbar_role), a toolbar is a collection of commonly used program controls. A modal header containing a title and a close button does not fit this definition. role="toolbar" with aria-label="Header" misleads screen readers. It should be removed.

Isolated Example

No response

Steps to Reproduce
  1. open Dialog component
  2. launch screenreader
  3. navigate through Dialog window
    ...
Log Output, Stack Trace or Screenshots

No response

Priority

Medium

UI5 Web Components Version

2.22.0

Browser

Chrome, Edge, Firefox

Operating System

Windows 10\11

Additional Context

No response

Organization

SAP \ UDEx

Declaration
  • I’m not disclosing any internal or sensitive information.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.