Legal
Accessibility statement
How accessible GarnerDocs is, what we know needs work, and how to tell us about a problem.
Last updated
We want everyone to be able to use GarnerDocs, whether they work at a firm or are a client sending documents from their phone. This statement explains how we test GarnerDocs, what works, what we know doesn't yet, and how to tell us about a problem.
What this statement covers
It covers three parts of GarnerDocs:
- This website, including the help center and these legal pages.
- The GarnerDocs app that firms and their teams sign in to.
- The client upload page, the private link a firm sends its clients. Clients don't need an account, and many open the link on a phone, so we test it at phone, tablet and desktop widths like the rest of GarnerDocs.
How we test
We test against the Web Content Accessibility Guidelines (WCAG) 2.1, levels A and AA.
- Automated checks on every page. We run axe, an automated accessibility checker, on every page of the website, the app and the client upload page, at phone and desktop widths. The same run checks at four widths, from 390 pixels (a phone) to 1440 pixels, that no page scrolls sideways.
- Keyboard testing. We check that these tasks can be done with a keyboard alone:
- creating a request, step by step, with focus moving to each new step and to the first field that needs fixing
- reviewing and approving uploads
- uploading files on the client upload page
- the command palette (⌘K or Ctrl+K), with the arrow keys and Esc
- dialogs and slide-over panels, which keep focus inside while open, close with Esc and return focus to where you were
- dropdown menus, which close with Esc
Last tested: 19 October 2026.
What works
- Skip links. Pages start with a link that skips past the navigation to the main content. On the client upload page it goes straight to your documents.
- Visible focus. Links, buttons and form fields show a clear ring when you reach them with the keyboard.
- Progress you can hear. Upload progress and request progress bars are marked up as progress bars, so screen readers announce what they measure and how far along they are.
- Labelled controls. Buttons that show only an icon have a text label for screen readers, and wide tables that scroll sideways can be reached and scrolled with the keyboard.
- Phones and zoom. Pages reflow to fit narrow screens without scrolling sideways, including the client upload page.
- Reduced motion. If your device is set to reduce motion, GarnerDocs stops its animations, transitions and smooth scrolling.
- Readable brand colours. A firm can choose a brand colour for its client upload page and emails. GarnerDocs won't accept a custom colour that's too light for white text to be read on it (WCAG's 4.5:1 contrast ratio).
Known issues
Some secondary text doesn't meet WCAG 2.1 AA's contrast requirement. This is light grey text on white, such as timestamps, helper text under form fields and the section labels in the app's sidebar, in the app, on the client upload page and on this website. Its contrast is about 2.6:1, below the 4.5:1 that AA asks for. Our automated checks report it on every run.
We're deciding how to fix it across GarnerDocs. Until then, if you find any text hard to read, your browser's zoom or your device's high-contrast and text-size settings may help, and you can tell us where it's a problem.
Our testing so far is automated checks and keyboard testing. We haven't had an independent accessibility audit, and we haven't yet tested every task with people who use screen readers or other assistive technology.
Reporting a problem
If something in GarnerDocs is hard or impossible to use, please tell us. Let us know the page or the link you were using, what you were trying to do, and the device, browser and any assistive technology you use. Please don't send us any documents.
Contact us at [email protected].
If you're a client and need your documents to reach the firm another way, contact the firm that sent you the link. They can tell you what else they accept.
Changes to this statement
We'll update this statement and the "Last tested" date when we test again or fix an issue listed here.