Tag: Accessibility - "Tag" is read out when interactive=false

[summer2200]

Describe the bug

When a non-interactive Tag is read out by screen reader, it's announcing "Tag [tag content]". Expected behavior should be just announcing the tag content without "Tag".

Isolated Example

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

Reproduction steps

1. Press Tab key to focus on the first timeline item, the tag was read out as "TagSingle Role"

Expected Behaviour

Should just read out the tag content without "Tag".

Screenshots or Videos

No response

UI5 Web Components for React Version

2.14.0

UI5 Web Components Version

2.14.0

Browser

Chrome

Operating System

MacOS

Additional Context

No response

Relevant log output

Organization

No response

Declaration

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

[Lukas742]

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.

[hinzzx]

Hi @UI5/ui5-team-ctr-rod , could you please check the issue with the ui5-tag component ?

The reporter expects the content of non-interactive ui5-tag component to be read out, without starting with "TAG" before.

[GerganaKremenska]

Hello @summer2200,

UI5 Web Components provide the prerequisites for screen reader support based on the HTML, ARIA, and WCAG standards. All screen readers that follow those standards should work fine. Nevertheless, there are deviations in the interpretation depending on the combination of browser and screen reader. UI5 Web Components focus on compliance with the standards, rely on automated checks for accessibility and manual tests with reference testing environments.

For Screen Reader Support, we recommend using JAWS 2025 + Chrome (latest), and for HTML/ARIA validation the recommended testing tool is Access Assistant. UI5 Web Components support other environments to the extent of providing a valid HTML and ARIA implementation following the WCAG standards.

When reporting issues with different testing environments, please ensure that the issue is not false positive, a real accessibility concern is present and there is an impact over the users. Therefore, we recommend to retest the issue using the mentioned reference testing tools and additionally with plain HTML.

In order to process the issue, we would like to have the following information provided:

Issue description:

• Reference to the suspected violated accessibility requirement (e.g. Web Content Accessibility Guidelines, WCAG 2.2, BITV 2.0, EN 301 549):
• Screen Reader:

NOTE: An non interactive tag can not be focused, it can only be read in virtual cursor mode. But the output is the same.

If a violated accessibility requirement can not be found, please close the issue.

Best Regards,
Gergana