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 input mask alphanumeric example does provide clear examples for screen reader users to follow.
While the instructions and example information are adjacent to the input mask field, it is not clear to a screen reader user (nor anyone) that there are non-conforming letters or number combinations.
Although our input mask help text gives an example, it doesn't clearly provide a warning when users enter the wrong kind of characters nor does it explicitly state "only numbers and letters in this combination".
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
The input mask alphanumeric example does provide clear examples for screen reader users to follow.
While the instructions and example information are adjacent to the input mask field, it is not clear to a screen reader user (nor anyone) that there are non-conforming letters or number combinations.
Although our input mask help text gives an example, it doesn't clearly provide a warning when users enter the wrong kind of characters nor does it explicitly state "only numbers and letters in this combination".
Related WCAG success criteria:
3.3.2 Labels or Instructions
3.3.6 Error prevention (all)
1.3.1 Info and relationships
When input mask is used to collect personal data, 1.3.5 Identify Input Purpose also applies.
Steps to reproduce the bug
Expected Behavior
When using a screen reader I would expect to hear the instructions state "Only type letter, number, letter. All other combinations are invalid"
Additionally, if I type in an incorrect/invalid character I hear a "ping" or noise indicating my character wasn't accepted.
Related code
No response
Screenshots
No response
System setup
Dell Windows Laptop
Windows 10
Chrome
NVDA
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: