Accessibility statement

Our commitment

DocFlow is a tool people use for a full working day. We treat accessibility as part of whether it works at all, not as a layer applied afterwards, and we keep improving it as the product changes.

Conformance

This application aims to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Those guidelines describe how to make content usable by people with a wide range of disabilities.

What we do

• Every screen can be operated from the keyboard alone, and every focusable control shows where focus is.
• A skip link on every page moves straight to the main content, past the navigation.
• Status is never carried by colour alone. Each state has an icon and a word as well, which is also what makes the interface readable in a printout.
• Form fields have real labels, hints are announced with the field they describe, and an error is announced when it appears rather than sitting silently on the page.
• Light and dark palettes are chosen independently and both are checked for contrast, rather than one being an inversion of the other.
• Animation respects the operating system's reduced-motion setting.
• Sign-in, password reset and the public pages work without JavaScript.

Known limitations

Two surfaces are not yet at the standard the rest of the product holds, and we would rather say so than let you find out:

• The document viewer renders a page image with extraction boxes drawn over it. The extracted values are all available as text beside it, but the overlay itself is visual and cannot be explored with a screen reader.
• Charts in reporting convey their shape visually. Every chart has the underlying figures in a table beneath it.

Telling us about a barrier

If something here stops you working, we want to hear about it — including the things not listed above. Email accessibility@docflow.example and describe what you were trying to do. We aim to reply within five working days.