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
Remove the class of .hidden from the input and move the input outside of the label element so that the input and its label are siblings. The SVG icon can remain inside of the label element but should also have aria-hidden="true" added.
Notes
This is an issue identified by Accessibility issues for screenreader users #5187
The text was updated successfully, but these errors were encountered:
With this when you remove the .hidden class the input element will become visible and overlap with the svg.
Some further updates to hide the input but keep the UI accessible:
Hide the input visually and reduce the size of the element so that is not a visible element but programmatically accessible. Something like this which hides it visually but keeps it located within the label's box and interactive.
This goal is to make the input element useable for screen readers and other Assistive Technology with the correct name and role while hiding it visually but also providing focus to keyboard users.
With these updates it should provide keyboard focus and screen reader access with the correct names and roles: https://share.zight.com/xQukj6mo
The "Import" button here is a bit different than the "Clear all". The Import uses the <label> and <input> elements but the <input> element is not part of the "Clear all" so the fixes will be a little different. I made a new issue for the "Clear all" to suggest a fix, #5441.
These buttons ("Clear all", "Import") cannot be tabbed to using a keyboard.
WCAG Criteria
2.1.1 Keyboard - A
Testing Method
Manual - Chrome/MacOS
Screenshot
Code Snippet
Action
Remove the class of
.hidden
from the input and move the input outside of the label element so that the input and its label are siblings. The SVG icon can remain inside of the label element but should also havearia-hidden="true"
added.Notes
This is an issue identified by Accessibility issues for screenreader users #5187
The text was updated successfully, but these errors were encountered: