[MultiCombobox]: there are no announcements for languages other than English

[raoakash01]

Bug Description

Describe the bug

we have an accessibility bug that we do not get announcements for the options for languages other English.

Affected Component

MultiCombobox

Expected Behaviour

we should get the proper announcements for whatever language it is available.

Isolated Example

https://stackblitz.com/edit/github-ddtqnziq-qsgndmzz?file=src%2FApp.tsx

Steps to Reproduce

1. Render a simple multicombobox with a few items with different languages.
2. Use Jaws for accessibility
3. Navigate between the options using keyboard
   ...

Log Output, Stack Trace or Screenshots

JAWS.AKASH-2-2.mp4

Priority

None

UI5 Web Components Version

2.21.0

Browser

Chrome

Operating System

Windows

Additional Context

No response

Organization

SAP LABs

Declaration

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

[LidiyaGeorgieva]

Hello @UI5/ui5-team-ctr-ril , please have a look at this issue.
The same behavior is reproducible with plain HTML here https://stackblitz.com/edit/js-lszsnfw5?file=index.js,index.html - the text of the list items with Chinese text is not read out by Jaws and NVDA.
I didn't find any similar issue in the "Accessibility Status Overview for UI5 Web Components" page for teh MultiComboBox.

Regards,
Lidiya

[ivoplashkov]

Hello,

Thank you for reporting this issue.

We investigated the behavior and were able to reproduce it not only with our component but also with a plain native HTML example containing Chinese text. The same behavior occurs with both JAWS and NVDA, which suggests that it is not caused by our component implementation.

For example, the issue is reproducible with a simple HTML structure such as:

• Hello
• 你好

During our testing, VoiceOver announced the Chinese text correctly, while JAWS and NVDA exhibited the same behavior as reported, even without our component being involved.

Based on these findings, we do not see evidence that the issue originates from our component. The behavior appears to be related to how the specific screen reader and speech synthesis configuration handle Chinese text.

Best regards,
Ivaylo

[github-actions]

This issue has been closed. To reopen, just leave a comment!