WCAG compliance for law firm websites: why it matters and how to get there

Accessibility is one of those topics that gets nodded at and rarely acted on, usually because it sounds like a technical checklist rather than something that affects real enquiries. For a law firm specifically, it’s worth taking seriously for two separate reasons: a meaningful share of the people who need a lawyer are older, dealing with an injury, or otherwise more likely to be using assistive technology than the average website visitor, and there’s a genuine, if still-developing, legal dimension to getting it wrong in Australia. This sits alongside the broader website design best practices guide as part of the same site.

What WCAG compliance actually means, in plain terms

WCAG stands for the Web Content Accessibility Guidelines, an international standard published by the W3C that sets out how to make websites usable by people with a range of disabilities, vision, hearing, motor and cognitive. The guidelines are organised into three conformance levels, A, AA and AAA, each stricter than the last. In practice, almost nobody targets AAA for a full commercial website; AA is the level treated as the practical, expected benchmark by governments, courts and accessibility professionals internationally, including in Australia. In practical terms, WCAG compliance for a WCAG website usually comes down to a shorter, more manageable list of fixes than the standard’s length suggests.

WCAG 2.1 AA has been the working benchmark for some years. WCAG 2.2, the newer version, adds a handful of criteria around things like consistent placement of help links, larger clickable targets, and clearer keyboard focus indicators, aimed particularly at people with low vision, motor difficulties and cognitive disabilities. The Australian Human Rights Commission updated its own guidance in 2025 to point toward WCAG 2.2 AA as current best practice, so it’s worth treating that as the level to aim for on anything built or rebuilt from here on.

Underneath the version numbers, WCAG criteria all sit under four simple principles, sometimes shortened to POUR: content should be Perceivable (people can actually see or hear it), Operable (people can navigate and interact with it, including without a mouse), Understandable (language and layout make sense), and Robust (it works reliably across browsers and assistive technology). Most of what follows in this article maps back to one of those four ideas.

Why this matters more for a law firm than for most businesses

Every business benefits from an accessible website, but the argument is stronger for a law firm specifically. Client bases for many practice areas skew toward exactly the groups most likely to rely on accessible design: older clients making a will or dealing with an estate, people managing a vision or hearing impairment after an accident that’s the very reason they’re contacting a personal injury lawyer, and people in a vulnerable or stressful circumstance more broadly, going through a family law matter or facing a criminal charge, where cognitive load is already high before a confusing website adds to it.

There’s also a compliance dimension worth understanding, even in outline. In Australia, the Disability Discrimination Act 1992 (Cth) makes it unlawful to discriminate against someone with a disability in the provision of goods and services, and the Australian Human Rights Commission has taken the position for some years that this extends to websites, on the basis that an inaccessible site can functionally exclude people with disability from a service in the same way an inaccessible physical office would. The Commission’s guidance points businesses toward WCAG as the practical standard for meeting that obligation, and complaints that can’t be resolved through the Commission’s conciliation process can, in principle, escalate further. None of this means every law firm website is at meaningful legal risk today, but it’s a real and active area of regulatory guidance, not a hypothetical one, and it’s a reasonable thing to ask your own lawyer about rather than relying on a marketing agency’s summary of it. It’s a separate question from the legal advertising rules that govern what a firm’s marketing can actually say, but the two are worth reviewing together.

Practical starting points that get most sites most of the way there

You don’t need to become an accessibility specialist to make meaningful progress. Most of the value comes from a relatively short list of fixes, most of which a competent developer or designer can implement without a full rebuild.

Quick WCAG compliance self-check

None of this requires technical expertise to check for yourself in a few minutes. Tick off what’s already true for your site; anything left unchecked is a reasonable starting point.

• Every meaningful image has descriptive alt text, or is marked as decorative.
• Body text has enough colour contrast against its background to read comfortably.
• The whole site can be navigated using the keyboard alone, with a visible focus indicator.
• Text can be resized in the browser without the layout breaking.
• Any video content, testimonials or firm introductions, has captions.
• Every form field has a real, visible label, not just placeholder text that disappears.
• Headings follow a logical order rather than skipping around the page.
• Links and buttons describe what they actually do, not just "click here."
• Nothing on the site relies on colour alone to convey important information.
• The site behaves reliably across common browsers and assistive technology.

The law-firm-specific gaps a generic checklist misses

Standard accessibility advice covers contrast and alt text. A few issues turn up on legal sites specifically and are almost always missed:

• PDFs. Law firms publish more of them than almost any other kind of business, fact sheets, client guides, costs disclosures, forms to fill in. A scanned or untagged PDF is completely opaque to a screen reader. Where the content matters, publish it as a web page and offer the PDF as a secondary option rather than the only one.
• Complex tables. Fee schedules and process timelines need proper header cells so a screen reader can announce which column a value belongs to. A table built visually with styled divs is unreadable.
• Plain language as an accessibility issue, not just a marketing one. WCAG’s "understandable" principle covers comprehension, and dense legal prose is a genuine barrier for people with cognitive disabilities, low literacy or English as a second language, which describes a meaningful share of legal clients.
• Time-limited forms and session timeouts. A form that expires while someone is slowly completing it with assistive technology is an accessibility failure, and an enquiry lost.
• Chat widgets and booking embeds. Third-party tools are the most common source of keyboard traps on otherwise decent sites. Test them specifically; being someone else’s code does not make it someone else’s problem.
• Video and audio content, a firm introduction or a testimonial, needs captions, and a transcript is better still since it is also indexable.

A word on accessibility overlay widgets

Products that promise instant compliance by adding a floating accessibility button to your site are widely marketed to small businesses, including law firms. They do not do what they claim. An overlay sits on top of the existing code without fixing it, and disability advocates and screen reader users have criticised them consistently, in some cases they actively interfere with the assistive technology a person is already running.

The practical risk for a firm is a false sense of security: the widget is installed, the box feels ticked, and the actual barriers remain in place. If accessibility matters enough to buy a product for, it matters enough to fix properly in the code, which is usually a smaller job than the overlay’s subscription cost over a couple of years.

This is really an extension of good website design, not a separate project

Most of what makes a site accessible overlaps heavily with what makes it good in general. Clear heading structure, fast load times, sensible contrast and legible text all help every visitor, not just those using assistive technology, and much of it overlaps with what search engines reward too. Treating accessibility as a bolt-on audit at the end of a build tends to produce a worse result, and often a more expensive one, than building it in from the structure and design stage. If you’re planning a new site or a redesign, this is worth raising with whoever’s building it before the first wireframe, not after launch, and our website design service builds it in from the start.

Where to start if you haven’t looked at this before

A reasonable first step is a genuine, honest look at your own site: try navigating it using only the keyboard’s Tab key, check your body text contrast with a free online contrast checker, and confirm your images have alt text in the page code. That alone usually surfaces the most obvious gaps. From there, a proper WCAG 2.2 AA review, ideally by someone who does this professionally, will catch the less obvious issues around form structure, ARIA labelling and dynamic content that a manual click-through won’t reveal. If you’d like a second opinion on where your own site sits, a free growth plan is a reasonable place to raise it.