Built to WCAG 2.2 AA, and checked on every change.
Accessibility is a target the product is tested against automatically, not a page we wrote once and left. The same checks run against staff screens, the client portal and this public site.
What that looks like in the product
Keyboard and focus
Visible focus on every control, a skip link past the navigation on every screen, and a dialog that traps focus while open and returns it on close.
Labels that mean something
Every input has a real label, every icon-only button has a name, and a progress indicator always says what it is a progress bar of.
Colour that reads, in both themes
Contrast is checked as a property of the colour tokens themselves — light and dark, and against a firm’s own chosen accent colour, not only the default.
A phone screen is not an afterthought
Every screen reflows at 320 pixels wide with no sideways scroll of the page itself; a table that must scroll does so in its own reachable region, by keyboard too.
How it is checked
An automated accessibility audit runs against real, signed-in screens as part of the same suite that has to pass before any change ships — the same discipline as the tests that check a balance adds up correctly.
Found something that doesn’t work with the tools you use: [email protected].