Software a whole firm can use — including the person who cannot see the screen.
Accessibility is not a compliance exercise for a practice system. Receptionists, paralegals, court clerks and clients all use the same software, on different devices, with different needs. This page states what we have done, what we have not, and how to tell us when we get it wrong.
The standard we work to
We aim for WCAG 2.2 level AA on the public website and on the product’s core workflows: sign-in, matters, deadlines, time, billing, documents and the client portal.
We have not yet commissioned an external audit. Until we have, this page describes our own testing rather than claiming a certification we do not hold — and we would rather say that than imply one.
What this statement is not
- Not a certification. No audit body has assessed us yet.
- Not a claim about third-party services you connect — their accessibility is theirs.
- Not finished. Screen-reader workflows inside the product need more attention, and that is on the list below.
Built in, not bolted on
Semantic structure
Real landmarks, headings in order, lists where lists belong, a skip-to-content link on every page, and labelled form fields rather than placeholder text standing in for a label.
Keyboard complete
Every interactive element is reachable and operable by keyboard, with visible focus rings, escape routes from menus, and tab-like components that respond to arrow keys.
Contrast in both themes
Text and interface contrast are checked in light and dark mode, including the dark theme’s buttons — where an early version failed the ratio and was changed rather than excused.
Motion respected
Animations, marquees and reveals are all suppressed when the visitor’s system asks for reduced motion. Nothing moves that a person has asked not to move.
Readable at any size
Layouts reflow from 320px upwards without horizontal scrolling, and text scales with the browser’s own zoom and font-size settings rather than fixed pixel traps.
Errors that explain themselves
Form validation messages are associated with the field they concern, stated in words, and announced rather than only turning a border red.
Accessible components
Tabs, accordions, toggles and menus expose their state (selected, expanded, pressed) to assistive technology, not just visually.
Content written plainly
Short sentences, expanded acronyms on first use, and no reliance on colour alone to convey meaning — statuses carry a word as well as a colour.
No motion-only content
Nothing essential is delivered through animation: every transition has a static equivalent, and every auto-playing element can be stopped or ignored.
What we have not fixed yet
Listed here because a firm may be relying on these, and because a gap that is written down is a gap that gets closed.
| Gap | Detail | Status |
|---|---|---|
| No external audit | Our testing is internal. An independent WCAG 2.2 AA audit is planned before general release, and we will publish the result whichever way it goes. | Planned |
| Screen-reader depth in the product | The marketing site is in good shape; complex product screens — the matter workflow and the ledger — need a dedicated pass with real screen-reader users, not just automated checks. | In progress |
| Generated documents | PDFs generated from templates are not yet tagged for accessibility. If your firm issues documents to clients who use assistive technology, tell us — it changes the priority. | Known |
| Data tables in reports | Wide comparison tables scroll horizontally on small screens rather than reflowing into stacked cards. Usable, but not ideal. | Known |
| Third-party embeds | Signature and payment screens are provided by other companies. We choose providers carefully and raise issues with them, but we cannot guarantee their conformance. | Out of our control |
Five checks before a page ships
- Keyboard-only pass. Tab through the page and operate everything without a mouse, including the theme toggle and mobile menu.
- Contrast measurement in both themes, with the actual computed colours rather than eyeballed.
- Reflow checks at nine viewport widths from 390px to 1440px, looking for horizontal scrolling and overlapping content.
- Zoom to 200% and system font-size increases, to confirm nothing is clipped or unreachable.
- Reduced-motion pass with the operating-system preference switched on.
Tell us what we have missed
If something on this site or in the product is difficult or impossible to use with your setup, we want the specifics — what you were doing, what happened, and what would have helped. We will tell you honestly whether we can fix it, and when.
Email: access@openlpm.com
Response: acknowledgement within two business days, with a plan or an explanation.
If you are a firm with a specific accessibility requirement — a staff member using a screen reader, a client needing larger text in the portal — raise it before you buy, and we will tell you what works today rather than after signature.