[Decision Reviews]: Design Spike - Accessibility Experience of More than One Error on Page

[davidakennedy]

Value Statement

As a Veteran

I want to understand errors more efficiently when more than one occurs on a page

So that I can confidently and quickly fix them

---

Background Context

In past accessibility audits, I've noticed that when multiple errors occur on a page, they may not be all immediately understandable by the Veteran. This is because:

• How we announce inline errors via role="alert". If more than two exist on a page, a screen reader announces the last one in the DOM.
• We don't have a pattern or component to cover this since we strive to have one thing per page, which limits fields. However, there may be cases where more than one error can be triggered at the same time.

Tasks

• Perform a design exploration for Decision Review forms to come up with options to better surface multiple errors to people who use screen readers.

Dependencies

• Related: [Decision Reviews & BMT]: Discovery - Accessibility Experience of More than One Error on Page #102281.

Acceptance Criteria

• Exploration work is added or linked to from this ticket. Likely a design file or prototype.

Out of scope

N/A

Open questions

N/A

Designs and Build Notes

N/A

Outcome, Success Measure, KPI(S), and Tracking Link

N/A

Enablement team (if needed)

N/A

Definition of Ready

• Clear value description
• Testable acceptance criteria
• Accessibility added to acceptance criteria
• Approved designs attached
• Sample data provided where appropriate
• Estimated to fit within the sprint
• Dependencies and blockers linked

Definition of Done

• Meets acceptance criteria
• Passed E2E testing (90% coverage)
• Passed unit testing (90% coverage)
• Passed integration testing (if applicable)
• Code reviewed (internal)
• Submitted to staging
• Team approved production verification process
• Reviewed and approved by product and/or design

[eileen-coforma]

Started on Friday, a continuation of work done last sprint to audit multiple errors on a single page. Desk research started to see if other teams have tackled this issue.

[eileen-coforma]

FIGMA file started for the work. Review with Eileen, and iterate.

[davidakennedy]

I met with Eileen and Robin yesterday to walk through the error exploration Figma file. Some takeaways:

• I'm going to check into research around the Review and Submit page, since multiple errors do happen there.
• I'm going to spruce up the design and specs to finalize them and make a ticket for the backlog.
• I'll talk to the design system team about whether this is a good candidate for a experimental design recommendation.

[davidakennedy]

An update on this work:

• I didn't find any specific research related to errors around the Review and Submit page.
• I've finished a v1 of the design specs in the Figma file.
• I'm chatting with accessibility specialists about how best to handle this as a ticket in the design system.
• I created a bug for the Supplemental Claim and Higher Level Review forms.

[davidakennedy]

This ticket is mostly complete: I'm waiting on some feedback from the Design System team about how best to file a ticket for this there since it's both a bug and an enhancement.

[davidakennedy]

This ticket is now complete. I heard back from the design system team, and for now, we decided only to file an experimental design request. We already have a ticket open with the design system to fix validation issues in the date components, so no need to file more bug requests. cc: @comaurice