Accessibility Improvements: Screen Readers and Keyboard Navigation

What's New

Harvey has improved how the web app works with screen readers and keyboard-only navigation. The updates apply across Assistant, Vault, workflows, Library, History, Settings, the left navigation, and the sign-in page.

Screen Reader Improvements:

• Buttons, fields, menus, filters, and the left navigation announce their name, role, and state
• Status updates are announced, such as result counts, cleared selections, and when a response starts and finishes
• Pages and dialogs use headings at the correct levels

Keyboard Improvements:

• Menus, row actions, and filters work with Tab, Enter, and Space
• Disabled buttons remain reachable by keyboard and announce why they're unavailable
• Dialogs move focus inside when they open, keep it there while open, and return it to the control that opened them when they close

Why It Matters

These accessibility updates address barriers identified in Harvey's previous third-party accessibility audit and reported by customers who use screen readers every day.

How To Use

These accessibility improvements are available to all users automatically; no setup is needed.

Next Phase: Accessibility Audit of Critical User Journeys

Harvey is commissioning a new third-party accessibility audit that tests critical user journeys, the end-to-end flows people rely on in Harvey, across Assistant, Vault, Review Tables, Agents, Spaces, and first-time setup. Each journey is tested using only a keyboard and with the NVDA and JAWS screen readers, against WCAG 2.2 Level A and AA. The results will inform Harvey's next Accessibility Conformance Report (VPAT). The audit runs in a dedicated Harvey workspace, not in customer workspaces.

FAQs

Q: Where can I find Harvey's accessibility conformance documentation?

Harvey's most recent Accessibility Conformance Report (VPAT) is available under NDA in the Harvey Trust Center.

Q: How do I report an accessibility issue?

Submit a ticket or contact your Customer Success Manager.