Accessibility statement
We aim to meet WCAG 2.1 Level AA across every page and component.
What weβve built in
- Full keyboard navigation; visible focus rings throughout.
- Semantic landmarks (
<main>,<nav>,<aside>) on every page so screen readers can skim structure. - Skip-to-main-content link surfaces on first Tab.
- Adjustable site-wide text size in /settings (M / L / XL / 2XL).
prefers-reduced-motionrespected: hero animations, splash screen, and chrome transitions step down or disable.- Light + dark themes with WCAG AA contrast on body text and interactive elements.
- Form fields are explicitly labelled; errors are announced via
aria-live. - Print stylesheet for case briefs and revision notes β clean hard-copy for highlighting and annotation.
- No autoplaying audio. Voice clips (Pro feature) require explicit user activation.
Known gaps
- Some long-form case briefs include images of court hierarchy diagrams without long-text descriptions; weβre backfilling.
- The flashcard swipe interaction has a keyboard alternative (left/right arrows) but the gesture indicators are visual-only.
Tell us if you hit a wall
If anything on caselaw is hard to use with assistive technology, email [email protected]. We aim to triage within 48 hours and fix critical blockers within 7 days.
Last reviewed: 25 April 2026.