Accessibility

Built to be used by everyone.

Including what still does not work well. An accessibility statement that overclaims is worse than none.

Effective 23 August 2026

The Full Statement

Where we are, honestly.

Open Justice exists so that people without a lawyer can still handle their legal matter. That only means something if the platform works for people using a screen reader, a keyboard, magnification, or voice control. This statement sets out where we are, honestly, including what still does not work well.

§ 1

Our commitment

Our current working target is WCAG 2.1 Level AA. We treat an accessibility defect as a defect, not a nice-to-have: it goes in the same bug tracker with the same severity scale as anything else.

WCAG 2.2 is the newer version of that standard, and Australian guidance on digital accessibility has moved with it. We are naming 2.1 AA because it is what we can honestly say we work to today, not because it is the highest bar available. Closing the gap to 2.2 AA is planned work, and the 2.2 success criteria we have not yet assessed against are part of why the conformance claim below is a partial one.

If something here blocks you, you do not have to work around it quietly. Tell us and we will fix it, and in the meantime we will help you get what you needed another way.

§ 2

How we measure, and what we score

We run automated Lighthouse accessibility audits across the public site and review the results before release. Our most recent full run covered 11 pages and scored 96 on mobile and 97 on desktop.

We want to be straight about what that number is worth. Automated tools catch roughly a third of real accessibility problems. A perfect automated score does not mean a page is usable with a screen reader, and we do not claim it does. Automated testing is our floor, not our ceiling.

Our current conformance claim is therefore partial: most of the site meets WCAG 2.1 AA, with the known exceptions listed below.

§ 3

What we have built in

  • Reduced motion is respected. The site uses a lot of scroll-driven animation. If your system is set to reduce motion, the ambient background animations stop entirely rather than merely slowing down.
  • Keyboard navigation works through the main journeys, and interactive elements show a visible focus ring.
  • Images carry alternative text, and images that are purely decorative are marked so a screen reader skips them instead of announcing a filename.
  • Decorative interface mock-ups are hidden from assistive technology. The illustrated product screenshots on the home page and the Ask a Lawyer page contain realistic-looking buttons that do nothing; they are hidden from screen readers and excluded from tab order so they cannot waste your time.
  • Icon-only buttons are labelled, so a control that shows only a symbol still announces what it does.
  • Page language is declared as Australian English, so screen readers use the right pronunciation.
  • Every page has a unique, descriptive title, which is how you tell tabs and history entries apart.
§ 4

What we know is not good enough yet

This list is deliberately specific. If you hit something not on it, that is a bug and we would like to hear about it.

  • We have not completed a full manual screen reader audit. Our testing to date is largely automated plus keyboard checks. A full NVDA and VoiceOver pass across sign-up, the AI Lawyer chat and booking is planned, and until it is done we cannot claim those flows are verified.
  • Colour contrast on frosted and glass surfaces. Several sections use translucent panels over moving backgrounds. Contrast can vary with what is behind them, and while we have checked the main cases, this is the area most likely to fall short.
  • The AI Lawyer response streams in as it is generated. We have not yet confirmed that screen readers announce the arriving text in a way that is useful rather than overwhelming.
  • Generated PDF documents. Documents produced by the drafter are not yet tagged for accessibility, so they may not read well in a screen reader. If you need an accessible version of a document you have generated, contact us and we will provide one.
  • Third-party components. Scheduling, video consultations and payment are provided by external services, and their accessibility is not fully within our control. We will still help you complete any of these another way.
§ 5

If something does not work for you

Email support@openjustice.au and tell us what you were trying to do, what happened, and what you were using — for example "NVDA on Firefox" or "keyboard only". You do not need to diagnose it or use technical language; describing what went wrong is enough.

We aim to respond within 5 business days. If the fix will take longer than that, we will tell you how we can help you complete what you were doing in the meantime, because a legal deadline does not wait for our release schedule.

If you are up against a court or tribunal deadline and an accessibility barrier is in your way, say so in your first message and we will prioritise it.

§ 6

If we do not resolve it

If you are not satisfied with how we have responded, you can make a complaint to the Australian Human Rights Commission at humanrights.gov.au. That right exists independently of us, and using it does not affect your access to Open Justice in any way.

This statement is reviewed whenever we make a significant change to navigation, forms or the AI Lawyer, and at least once every twelve months.

Something in your way?

Tell us what you were trying to do and what you were using. You do not need to diagnose it — describing what went wrong is enough. If you are up against a court deadline, say so and we will prioritise it.

support@openjustice.au