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
The 'Clear' button in the input field is not accessible via keyboard navigation, and its type button is not announced by screen readers.
Affected Component
Input
Expected Behaviour
Keyboard is the prerequisite for support of assistive technologies to enable users with disabilities to read and operate software applications, hence all the UIs must be accessible with keyboard.
With screen reader enabled, UI elements type for all the UIs should be communicated to the user.
Isolated Example
No response
Steps to Reproduce
No response
Log Output, Stack Trace or Screenshots
No response
Priority
None
UI5 Web Components Version
2.7.0
Browser
Chrome
Operating System
No response
Additional Context
No response
Organization
No response
Declaration
I’m not disclosing any internal or sensitive information.
The text was updated successfully, but these errors were encountered:
AlekseiSch
changed the title
[Input][A11y]: Clear button is not navigable from the keyboard, type button is not communicated to the user.
[Input][A11y]: Clear button is not navigable from the keyboard, type button is not communicated to the user
Mar 5, 2025
Bug Description
Observed Behavior:
Switch
showClearIcon
to true, type something in the input field.https://sap.github.io/ui5-webcomponents-react/v2/?path=/story/inputs-input--default&args=showClearIcon:!true
The 'Clear' button in the input field is not accessible via keyboard navigation, and its type button is not announced by screen readers.
Affected Component
Input
Expected Behaviour
Keyboard is the prerequisite for support of assistive technologies to enable users with disabilities to read and operate software applications, hence all the UIs must be accessible with keyboard.
With screen reader enabled, UI elements type for all the UIs should be communicated to the user.
Isolated Example
No response
Steps to Reproduce
No response
Log Output, Stack Trace or Screenshots
No response
Priority
None
UI5 Web Components Version
2.7.0
Browser
Chrome
Operating System
No response
Additional Context
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: