Input being required should not result in aria-invalid="true" #18140
Assignees
Labels
Accessibility
This issue is related to accessibility (a11y)
area: material/input
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
jelbourn
added
Accessibility
|
Can not reproduce it on the current version 9.2.1. The
Tested on Mac, browsers Chrome, Brave and Firefox |
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jan 15, 2021
Only sets `aria-invalid` on a `MatInput` if it is invalid and it has a value, otherwise it'll likely overlap with `aria-required` and cause more noise for users. Furthermore, it may be confusing if the user lands on an input that they haven't interacted with, but it's already invalid. Fixes angular#18140.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jan 15, 2021
Only sets `aria-invalid` on a `MatInput` if it is invalid and it has a value, otherwise it'll likely overlap with `aria-required` and cause more noise for users. Furthermore, it may be confusing if the user lands on an input that they haven't interacted with, but it's already invalid. Fixes angular#18140.
mmalerba
pushed a commit
that referenced
this issue
Feb 10, 2021
#21609) Only sets `aria-invalid` on a `MatInput` if it is invalid and it has a value, otherwise it'll likely overlap with `aria-required` and cause more noise for users. Furthermore, it may be confusing if the user lands on an input that they haven't interacted with, but it's already invalid. Fixes #18140.
mmalerba
pushed a commit
that referenced
this issue
Feb 10, 2021
#21609) Only sets `aria-invalid` on a `MatInput` if it is invalid and it has a value, otherwise it'll likely overlap with `aria-required` and cause more noise for users. Furthermore, it may be confusing if the user lands on an input that they haven't interacted with, but it's already invalid. Fixes #18140. (cherry picked from commit d0c53ac)
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
Input being required should not result in aria-invalid="true".
What is the expected behavior?
An input field that is required should be marked as required in the HTML (which it is), but should not be marked as aria-invalid until the user enters an invalid value.
What is the current behavior?
An input field that is required is marked as both required and aria-invalid before any content is entered by the user.
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
Expected: The input element should have aria-invalid="false" or no aria-invalid attribute.
Actual: The input element has aria-invalid="true".
What is the use-case or motivation for changing an existing behavior?
It is confusing to users with a screen reader why it would be invalid before they have even entered any content.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Latest. It is on your example page.
Is there anything else we should know?
Thank you for your attention on this issue.
The text was updated successfully, but these errors were encountered: