Legal

Accessibility statement.

Version 1.0 · Last updated: 2 August 2026
Also available: Complaints · Terms of Service · Privacy Policy

1. Our position, stated plainly

Obiter is partially conformant with the Web Content Accessibility Guidelines version 2.2, level AA. Partially conformant means some parts of the service do not fully conform.

We are not claiming more than that, and we want to be clear why. Our assessment is our own: we have checked the code, computed our colour contrasts, and walked the site with a keyboard. We have not had an independent audit, and we have not tested with screen readers such as VoiceOver, NVDA or JAWS. Until we have done those things, a claim of full conformance would not be supported by anything.

2. What we fixed in August 2026

  • Our muted grey text failed the minimum contrast requirement at 2.59:1, where 4.5:1 is needed. It was used for section labels, billing notes and captions throughout the site. It is now 4.65:1.
  • The green and red used for form success and error messages also failed as text. Those messages now use darker variants that pass. The green ticks and red crosses in our illustrations are unchanged — as graphics they only need 3:1, and they already met it.
  • The pre-contract information on our pricing page is deliberately set in a stronger colour than a footnote would normally use. Information you are legally entitled to should not be the hardest thing on the page to read.

3. What already works

  • A “Skip to content” link on every page, which actually lands somewhere — we checked the target exists rather than assuming it.
  • Headings, lists and tables use real semantic markup, with column headers properly associated.
  • Every image carries alternative text; decorative graphics are hidden from screen readers rather than described pointlessly.
  • The page language is declared as British English.
  • Every page has its own distinct title.
  • If your system asks for reduced motion, our animations honour it.
  • Nothing requires a mouse: navigation, links and forms are built from standard elements that work from the keyboard.
  • The app's text colours pass comfortably in both light and dark mode.

4. What we know is not right yet

This list is deliberately specific. A vague statement helps nobody decide whether Obiter will work for them.

  • No screen reader testing. Our markup is structurally sound, but sound markup and a good spoken experience are not the same thing.
  • No independent audit. Everything above was assessed by the people who wrote the code.
  • Focus indicators. We rely on browser defaults in most places rather than styling focus ourselves. That usually works. We have not verified it everywhere.
  • Small tap targets. WCAG 2.2 asks for a minimum target size. Some of our denser controls — the FAQ chevrons, the carousel dots, the comparison table toggles — may fall short. We have not measured them.
  • Zoom and narrow screens. We have not tested the site at 320 pixels wide, or with text enlarged to 200%. Our home page uses full-height scrolling sections, which is exactly the pattern most likely to break under both.
  • The setup wizard. Our newest and most complex screen has not been audited. It has drag-and-drop file upload; there is a normal file-picker button next to it, so it should not require dragging, but we have not confirmed that properly.
  • The mobile apps. Not yet audited with VoiceOver or TalkBack.

5. If you hit a barrier

Email support@obiter.sitewith “Accessibility” in the subject. Tell us what you were trying to do, what got in the way, and what you use — browser, screen reader, magnifier, whatever is relevant.

We will acknowledge within 3 working days and tell you what we can do and when. If something is going to take a while to fix, we will look for a way to get you what you needed in the meantime rather than making you wait for the fix.

If you need information from this site in a different format — larger print, plain text, or read aloud — ask and we will provide it.

If you are not satisfied with our response, our complaints procedure applies.

6. The legal bit

The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 do not apply to Obiter, because we are not a public sector body.

The Equality Act 2010 does. As a service provider we have a duty to make reasonable adjustments for disabled people, and that duty is anticipatory: it means thinking ahead rather than waiting for someone to be turned away. Publishing the gaps in section 4, instead of a comfortable claim of conformance, is part of how we take it seriously while they remain open.

7. How this statement was prepared

Prepared on 2 August 2026 following a self-assessment of obiter.site and app.obiter.site against WCAG 2.2 level AA. The assessment covered code inspection, computed colour contrast ratios, and keyboard traversal. It did not cover assistive technology testing or independent review.

We will review this statement by 2 February 2027, or sooner if we complete any of the work in section 4.