Skip to content

JAWS - Autocomplete should announce invalid input when blurring #3380

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DaveBest99 opened this issue Mar 2, 2017 · 3 comments
Closed

JAWS - Autocomplete should announce invalid input when blurring #3380

DaveBest99 opened this issue Mar 2, 2017 · 3 comments
Labels
Accessibility This issue is related to accessibility (a11y) needs: verification A member of the team needs to verify whether this issue is fixed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@DaveBest99
Copy link

Bug, feature request, or proposal:

Bug: AutoComplete has no error detection.

What is the expected behavior?

Moving focus out of an empty auto complete field where a value is required should either invoke an error or if a default value was initially assigned, reset the value to the default value. Also, moving focus out of an auto complete field that does not contain a valid entry should either invoke an error or if a default value was initially assigned, reset the value to the default value.

What is the current behavior?

Currently there is no error detection and anything can be typed into the Edit box.

What is the use-case or motivation for changing an existing behavior?

Help users (particularly elderly, screen reader and cognitive users) with accurate input.

Is there anything else we should know?

The user can press Enter key to select a blank Edit box or an invalid entry "Ontario", with no notification. An aria-alert could be used to notify the user that the selected list entry is not valid.

@kara kara added the Accessibility This issue is related to accessibility (a11y) label Mar 2, 2017
@kara
Copy link
Contributor

kara commented Mar 3, 2017

Related: #3416

@kara kara changed the title A11y keyboard control AutoComplete error detection A11y - Autocomplete should announce invalid input when blurring Mar 4, 2017
@kara kara added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Mar 4, 2017
@kara kara self-assigned this Mar 4, 2017
@kara kara changed the title A11y - Autocomplete should announce invalid input when blurring JAWS - Autocomplete should announce invalid input when blurring Mar 10, 2017
@LilSebastian5000
Copy link

LilSebastian5000 commented May 18, 2017

@kara I'm curious if there's an update on this? We disable/enable submit buttons in our application based on the status of required fields, so this is a bit of an issue and inconsistency from other material form controls. Thanks!

@jelbourn jelbourn added the needs: verification A member of the team needs to verify whether this issue is fixed label Sep 19, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility This issue is related to accessibility (a11y) needs: verification A member of the team needs to verify whether this issue is fixed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

4 participants