You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a ui5-button with a badge (via slot="badge"), screen readers correctly read the full visual content including the badge (e.g., “Emphasized Tag Warning 999+.”). However, when an accessible-name is set on the button, the screen reader only reads the value of the accessible-name, and the badge content is ignored.
Affected Component
ui5-button
Expected Behaviour
When accessible-name is used, it should still be possible to include the badge content in what the screen reader announces.
Bug Description
When using a ui5-button with a badge (via slot="badge"), screen readers correctly read the full visual content including the badge (e.g., “Emphasized Tag Warning 999+.”). However, when an accessible-name is set on the button, the screen reader only reads the value of the accessible-name, and the badge content is ignored.
Affected Component
ui5-button
Expected Behaviour
When accessible-name is used, it should still be possible to include the badge content in what the screen reader announces.
Isolated Example
https://sap.github.io/ui5-webcomponents/nightly/packages/main/test/pages/Button.html
Steps to Reproduce
1.Open the example and find a button with a badge
2.Set accessible-name attribute to the button
3.It does not announce the badge anymore
...
Log Output, Stack Trace or Screenshots
No response
Priority
Medium
UI5 Web Components Version
2.9.0
Browser
Chrome
Operating System
Mac
Additional Context
Organization
SAP
Declaration
The text was updated successfully, but these errors were encountered: