[a11y]: Agencies View - accessibility findings

[lsr-explore]

Why is this issue important?

This ticket contains multiple accessibility issues in arpa_reporter. As support for Arpa reporter is winding down we collected issues in one page.

Note: These were identified during a developer accessibility review to double check the accessibility of the elements on the page. To fully insure the site is accessible to users, more comprehensive testing by an accessibility subject matter expert should be performed.

Testing approach
All testing was done against staging and local dev.

1. Run axe DevTools chrome extension against the page. This checks contrast
2. Run through the page with the keyboard - I used Microsoft's Accessibility Insights Chrome Extension to track keyboard focus
3. Zoom the page to 200x and 400x to check reflow
4. Run through the page using a screen reader - mac voice over
5. Validate the HTML by pasting parts of the html into W3C Markup Validation Service

Testing gaps

1. Windows screen readers - JAWS / NVDA
2. Mobile web devices - the arpa reporter was not designed to be responsive
3. Real user workflow steps.

---

Agencies View

axe DevTools report is clean

Create new agency

Edit agency

---

issue 1 - Edit buttons should have more specific aria-label that includes the name of the agency being edited.

Current State

See issues above

Expected State

No a11y issues

Implementation Plan

TBD

Relevant Code Snippets