-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MessageStrip]: Close button tooltip message is not according to design and no accessibleName is present. #9874
Comments
Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository. |
Hello @SAP/ui5-webcomponents-topic-rl , this inquiry looks more like a feature request. Please, consider if accessibleName is required here and/or the tooltip message should be different according to the "design" of the MessageStrip - "Information", "Positive", "Negative", "Warning" (currently, it is "Information Bar Close" for all designs). Regards, |
Hello, We will enrich the tooltip of the close button according to the spec, but in the specification there is no In this issue we will process the enrichment of the tooltip - including the Kind Regards, |
P1 BLI was created: FIORITECHP1-31872 |
🎉 This issue has been resolved in version v2.6.0-rc.0 🎉 The release is available on v2.6.0-rc.0 Your semantic-release bot 📦🚀 |
Describe the bug
Close button tooltip message is not according to design.
Same tooltip is shown for Design - "Information", "Positive", "Negative", "Warning
Tooltip: Information Bar Close
There is no accessibleName
Isolated Example
No response
Reproduction steps
Expected Behaviour
Tooltip message should be according to design.
accessibleName should be present. (It is good to have same accessibleName as tooltip otherwise Screen Reader will read both tooltip and accessibleName which usually will have same meaning in this case)
Screenshots or Videos
No response
UI5 Web Components for React Version
1.29.3
UI5 Web Components Version
1.24.7
Browser
Chrome, Edge, Firefox, Safari
Operating System
No response
Additional Context
No response
Relevant log output
No response
Organization
SuccessFactors
Declaration
The text was updated successfully, but these errors were encountered: