mtcA6
commented
2 weeks ago Notes on pointing: feels like a 3, making sure the focus goes to the right place, seems like a small change in one spot but there's a little bit of investigation to locate, and working w/the specific screen reader called out might be a challenge if it doesn't work w/mac
ACParker89
Label: 15247
https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-2
Issue Title: 508 Defect 2, screen readers, when errors occur, focus isn't placed consistently on the error message. Point of Contact: Angela Fowler VFS Point of Contact: _First name only: Angela
User Story or Problem Statement:
As a screen reader user, when encountering an error message which JAWS indicates has a Close button, my first inclination would be to close out the message. With focus placed on the message I can find the close button easily. When focus isn't managed, it defaults to the top of the page, and it takes several seconds of searching to locate the close button.
Details
On Profile 2.0, when a screen reader user attempts to change their address, phone number or email, they may be presented with an error message effectively stating we are unable to make the requested change. This message comes with a close button. The majority of the time, focus is placed at the top of the page, causing the user to search through several buttons before they come to "close."
Acceptance Criteria
In the event of an error, focus is consistently placed on the error message.
Environment
Consistent across all environments.
Steps to Recreate