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
Access Assistant reports following - This DIV is focusable but lacks a role attribute. (Please see the attached pictures).
If we follow the Accessibility Best Practice - adding a role helps provide context, making it clear to users relying on screen readers what kind of interactive element they are encountering. However it is not possible to assign role attribute to the focusable div. If we pass down interactive prop to the CardHeader, this will assign the role="Button" to the focusable DIV, which makes the header clickable, and also changes the way the header looks and behaves on hover.
Affected Component
ui5-card-header
Expected Behaviour
We should be able to assign the role=<anyRole> attribute to the focusable div element.
shakogele01
changed the title
[CardHeader]: The focusable DIV lacks a role attribute.
[ui5-card-header]: The focusable DIV lacks a role attribute.
Dec 12, 2024
Bug Description
Access Assistant reports following -
This DIV is focusable but lacks a role attribute.
(Please see the attached pictures).If we follow the Accessibility Best Practice - adding a
role
helps provide context, making it clear to users relying on screen readers what kind of interactive element they are encountering. However it is not possible to assignrole
attribute to the focusable div. If we pass downinteractive
prop to the CardHeader, this will assign therole="Button"
to the focusable DIV, which makes the header clickable, and also changes the way the header looks and behaves on hover.Affected Component
ui5-card-header
Expected Behaviour
We should be able to assign the
role=<anyRole>
attribute to the focusable div element.Isolated Example
https://js-xw5smpxh.stackblitz.io/
Steps to Reproduce
Log Output, Stack Trace or Screenshots
No response
Priority
Medium
UI5 Web Components Version
2.5.0
Browser
Chrome, Safari
Operating System
MacOS
Additional Context
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: