Accessibility statement

Last updated 2026-10-10.

Our commitment

People reach this site under financial stress, often on a phone, sometimes in a hurry. It has to work. We target WCAG 2.2 Level AA and treat an accessibility failure as a bug, not a feature request.

What we have done

• Contrast — text meets at least 4.5:1 against its background in both light and dark mode, and we verify this in the build rather than by eye.
• Keyboard — every control is reachable and operable by keyboard, focus is always visible and never removed, and a skip link gets you straight to the content.
• Structure — one h1 per page, headings in order, landmarks, and real <table>, <label> and <fieldset> elements rather than styled divs.
• Forms — visible labels, not placeholder-only; hints and errors associated with their field; errors announced to screen readers.
• Touch — interactive targets are at least 44 by 44 pixels with real spacing between them.
• Motion — we use very little, and prefers-reduced-motion removes what there is.
• Zoom and reflow — the page works to 400% zoom and down to 320 pixels wide without horizontal scrolling. Zoom is never disabled.
• No colour-only meaning — status is always carried by text as well as colour.
• Progressive enhancement — every guide and county page is server-rendered HTML and readable with JavaScript switched off. The calculators need JavaScript; the information they are based on is written out on the same page.

Where we know we fall short

We would rather name these than claim perfection:

• Generated PDFs are not fully tagged for screen readers yet. The on-screen version of every document is accessible, and we are working on the PDF output.
• Official court forms we link to are published by the Judicial Council and we do not control their accessibility.
• Our testing is automated plus manual keyboard and screen reader passes. It is not yet a formal third-party audit.

Tell us

If something on this site does not work for you, email support@filemysmallclaims.com with the page and what happened. We treat these as priority bugs. If you cannot complete something because of an accessibility barrier, tell us what you were trying to do and we will help you do it another way while we fix the cause.