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
Current Behavior
Observed Behavior:
This SPAN is focusable but lacks a role attribute.
Affected Component
ui5-dialog
Expected Behaviour
Ensure that proper textual descriptions are provided for custom components within the application.
In general textual descriptions for information is provided via the alt attribute for images or title attribute for non image elements. After the name, developers can indicate the role of the element and then the state of the element should be provided. ARIA should also be used to indicate the control's role and state. For example, for a div or span element that represents a button, the role of "button" should be used, for elements that simulate links the role should be "link".
For anchors and buttons the onclick event handles both keyboard and mouse clicking. For elements other than button or anchor, both onclick and keyboard event handlers will need to be used. The keyboard event handler such as onKeyUp will receive all key up events and thus must be modified to only trigger on the enter or space key for buttons or the enter key for anchors.
Bug Description
The accessibility team has created an issue for
udex-modal
which uses aui5-dialog
https://github.tools.sap/sapudex/digital-design-system/issues/1018
Current Behavior
Observed Behavior:
This SPAN is focusable but lacks a role attribute.
Affected Component
ui5-dialog
Expected Behaviour
Ensure that proper textual descriptions are provided for custom components within the application.
In general textual descriptions for information is provided via the alt attribute for images or title attribute for non image elements. After the name, developers can indicate the role of the element and then the state of the element should be provided. ARIA should also be used to indicate the control's role and state. For example, for a div or span element that represents a button, the role of "button" should be used, for elements that simulate links the role should be "link".
For anchors and buttons the onclick event handles both keyboard and mouse clicking. For elements other than button or anchor, both onclick and keyboard event handlers will need to be used. The keyboard event handler such as onKeyUp will receive all key up events and thus must be modified to only trigger on the enter or space key for buttons or the enter key for anchors.
Isolated Example
No response
Steps to Reproduce
Steps to reproduce
• Login the application using the URL: https://udextest.z6.web.core.windows.net/a11y/index.html?path=/docs/about-introduction--docs
• Navigate to the side navigation menu and select ‘Accessibility Testing’
• Expand the ‘Modal’ and select ‘Dropdown’
• Activate the button ‘Modal with Dropdown’
Log Output, Stack Trace or Screenshots
Priority
Low
UI5 Web Components Version
1.24.8
Browser
Chrome
Operating System
No response
Additional Context
Brief description
ACC- 264.3(Level A)Unified Digital Experience (UDEx)-Storybook_Modal with Dropdown_Dialog Custom controls does not provide proper textual na.docx
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: