Skip to content
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

Request form: Org name error focus #2909

Open
1 task
AnnaGingle opened this issue Oct 7, 2024 · 0 comments
Open
1 task

Request form: Org name error focus #2909

AnnaGingle opened this issue Oct 7, 2024 · 0 comments

Comments

@AnnaGingle
Copy link

Issue description

URL: Organization name and mailing address | Request a .gov | .gov Registrar (cloud.gov)
Test ID: 4.F Focus order meaning
Issue: When leaving required form fields blank and continuing to the next page, the page gets refreshed and the focus shifts the beginning of the main content (Previous page). However, when using a screen reader, the first thing that is announced to assistive technology users is the URL and when you press the TAB key, the focus starts at the first interactive element in the main content area. Users may be confused when the focus suddenly shifts without warning as they may not understand why it moved or what action to take next. The field in error is identified and a message is shown visually but no announcement is made to screen readers, hindering them to effectively complete tasks and interact with the website. To fix the issue, the focus should move to the error message at the top of the page or if that is not possible, there must be an audible announcement and focus can either go to the first field in error or remain on the button that triggered the error.

Acceptance criteria

  • When a user attempts to proceed to the next step of the form and there is an error on this page, the focus goes to the first field in error.

Additional context

No response

Links to other issues

No response

@AnnaGingle AnnaGingle changed the title Request form: Org Request form: Org name error focus Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🍦 Backlog
Development

No branches or pull requests

1 participant