Accessibility Statement

Last updated August 14, 2026

People look for a lawyer at the worst moments of their lives, often on a phone, sometimes with a disability that the stress makes harder to work around. A directory that is hard to use fails exactly the people it is supposed to serve. We aim to meet WCAG 2.2 Level AA.

We are not claiming to have reached it. This page says what is true, including the parts that are not finished.

What is in place

  • Every page is real HTML rendered on the server, with real headings and real links. The site works without JavaScript for reading and navigating.
  • One h1 per page, headings in order, and landmarks (banner, navigation, main, contentinfo) so a screen reader can skip around.
  • Everything interactive is reachable by keyboard and shows a visible focus ring. There are no keyboard traps, no autoplaying media, and no CAPTCHAs anywhere on the site.
  • Body text is set at a readable size with generous line height and is not locked against zooming. Layouts reflow down to a 320px viewport.
  • Colours are re-measured whenever the palette moves, and the ones that fail are fixed at the token rather than patched on the component. Against the page background, secondary text sits at 5.80:1, the tertiary tone that carries fine print at 4.55:1, links at 6.12:1, and the border of a field, a secondary button or an unchecked checkbox at 3.03:1.

What we know falls short

  • The heading scale is uneven. Two heading levels currently share a size and differ only in weight, which is weaker visual structure than it should be. Semantic order is still correct, so assistive technology reads the hierarchy properly.
  • We have not tested with real assistive tech. No screen-reader pass, no testing with disabled users. Everything above comes from code review and measurement, which catches less than a person does.

Reporting a barrier

If any part of this site keeps you from finding or contacting an attorney, tell us at [email protected]. Say what page it was and what happened — you do not need to know the name of the standard, and “the text is too small to read on my phone” is a perfectly good bug report.

We read every message and will tell you what we can do and when. If something we have shipped is the barrier, fixing it comes before new features.