Accessibility

01What we aim for

OpsBrio is built to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA — the standard the US Department of Justice and the courts use for the web. The aim covers all of it: the office’s portal, the drivers’ app, the job application pages a company publishes, and this website, in the light and the dark theme, on a phone and on a computer.

Today OpsBrio partially conforms: most of it meets the standard, and section 4 lists the parts that do not yet.

02Built in, not laid on top

We do not use an accessibility “overlay” or plugin. Those add a second layer over a website and promise to fix it automatically; the organisations of the people they claim to serve have asked companies not to use them, because they get in the way of the screen readers and settings people already rely on.

OpsBrio is built to work with the tools already on your phone or computer — VoiceOver and TalkBack, zoom and larger text, high-contrast and reduced-motion settings, and the keyboard — so the fixes are in the product itself.

03How we check it

• Every screen, automatically, against WCAG 2.2 A and AA, in both themes, at a phone’s width and a desk’s.
• Every colour a word is written in is held at a contrast of at least 4.5 to 1 against every background it sits on, by a test that runs on every change we make.
• With the keyboard alone: every control can be reached, you can always see where you are, and nothing traps you.
• As a screen reader hears it: every control says what it is, every page has its heading and its main content marked, and the headings run in order.
• Zoomed and spaced: the pages reflow at 320 pixels wide and at 200% zoom, and nothing is cut off when the spacing between letters, words and lines is increased.
• With motion turned down: nothing keeps moving when your device asks for reduced motion.

The last full check was on 15 October 2026.

04Where it still falls short

• The dispatch board and the weekly schedule are dense grids built for a desk. Every control on them works from a keyboard, but a screen reader reads them row by row, not yet as a table it can move through by column.
• The van walk-round asks the driver for photographs of the van, which needs the phone’s camera and sight of the van.
• The check that a person, not a program, is signing in is Cloudflare’s, and so are its words and controls. It usually passes without asking anything.
• Amazon’s own websites and apps, which OpsBrio reads from and links to, are Amazon’s.

05What it works with

The current versions of Chrome, Safari and Edge on a computer; Safari and Chrome on an iPhone; Chrome on an Android phone; and the OpsBrio apps for iPhone and Android. OpsBrio is a website first, so it works with the screen reader, magnifier and keyboard your device already has.

06Tell us

If anything in OpsBrio is hard to use with your setup, tell us — email support@opsbrio.com or call (609) 676-4965. Say what you were trying to do and on which screen. We answer within two business days, and we fix what we can in the order it gets in people’s way.

If you work for a company that uses OpsBrio, you can also ask your office for help with the task in the meantime.