[Messagebox|A11y]: screen reader does not announce message content on open (VoiceOver macOS, TalkBack Android)

[chengjun2621]

Bug Description

When a messagebox opens, VoiceOver (macOS) and TalkBack (Android) only announce the focused button label (e.g. "OK") — the message content is never read.

TalkBack + Chrome (Android):

VoiceOver + Chrome (macOS):

Note:JAWS and NVDA + Chrome (Windows) announce the message content correctly.

Affected Component

MessageBox

Expected Behaviour

When a MessageBox opens and focus moves to the confirm button, the screen reader should announce both the button label and the message content

Isolated Example

No response

Steps to Reproduce

1. Enable VoiceOver (macOS) or TalkBack (Android) with Chrome
2. Open link https://ui5.github.io/webcomponents-react/v2/?path=/story/modals-popovers-messagebox--with-custom-actions
3. Click the OpenMessageBox button

Log Output, Stack Trace or Screenshots

No response

Priority

Medium

UI5 Web Components Version

2.22.1

Browser

Chrome

Operating System

macOS, Android

Additional Context

No response

Organization

SAP

Declaration

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

[IlianaB]

Hello @UI5/ui5-team-ctr-rod,
I am forwarding this issue to you, because Dialog content is not read out on macOS with VoiceOver (tested by colleague and as stated by @chengjun2621). The message is read out with JAWS on Windows.
Playground sample: here

Regards,
Iliana

[chengjun2621]

Hi team,

This issue was reported by the customer. Could you share the estimated implementation schedule? We will upgrade to the latest release after the issue is fixed.

Thanks,
Jun

[kskondov]

Hello @chengjun2621 ,
The behavior is reproducible with plain HTML using the standard WAI-ARIA dialog pattern (role="alertdialog" + aria-describedby). Check this example. When focus moves to a button inside the dialog, VoiceOver does not announce the dialog's description — this contradicts the ARIA spec but is a vendor-specific bug.
Since UI5 Web Components follows web standards rather than working around individual screen reader vendor bugs, we should not add non-standard mechanisms (i.e. aria-live regions) to the Dialog component. Therefore I am closing this issue.

Best Regards,
Konstantin