Website Accessibility Guidelines: WCAG 2.2 Explained

What WCAG 2.2 actually is

The Web Content Accessibility Guidelines (WCAG) are an internationally recognised set of website accessibility standards published by the World Wide Web Consortium (W3C). They define how to make digital content usable by people with a wide range of disabilities. That covers blindness and low vision, deafness, limited mobility, cognitive differences, and conditions like tremors that make a mouse hard to control.

WCAG 2.2 is the current version, which the W3C recommended in October 2023. It builds on WCAG 2.1 and adds nine new success criteria aimed at real problems: forms that forget what you typed, controls that vanish behind sticky headers, drag-and-drop interactions with no alternative, and logins that ask you to memorise and re-type a code. Australian small business owners hit these every week. They are not edge cases.

The website accessibility guidelines sit on four principles. Content must be Perceivable, Operable, Understandable and Robust (often shortened to POUR). Every requirement, called a success criterion, falls under one of those four headings, which makes the framework easier to reason about than it first looks.

The A, AA and AAA conformance levels

WCAG 2.2 defines three conformance levels. The difference between them matters when you decide what to aim for and what to budget.

• •Level A is the minimum. It clears the most fundamental barriers, the ones that stop some people from using your site at all. Level A on its own falls short for a public business website.
• •Level AA is the practical target, and the level most laws and procurement rules reference worldwide. WCAG 2.2 AA covers colour contrast, text resizing, keyboard navigation, clear focus indicators, and consistent navigation. Aim here.
• •Level AAA is the strictest. It includes sign-language interpretation for video and very high contrast ratios. The W3C says AAA is not a realistic requirement for entire websites, so most organisations apply it to selected content rather than the whole site.

When people talk about "website accessibility standards" in a commercial or legal context, they mean WCAG 2.2 AA. That is the benchmark we build every business website to at Peer 2 Peer IT.

Website accessibility standards in Australia

For website accessibility standards Australia follows WCAG directly. The federal Digital Service Standard requires government websites to meet WCAG 2.0 Level AA at a minimum, and agencies are moving to the newer version. That mandate covers government, yet it sets the benchmark the private sector gets measured against.

For private businesses, the legal backbone is the Disability Discrimination Act 1992 (DDA). The DDA makes it unlawful to discriminate against a person on the basis of disability in the provision of goods, services and facilities, and the Australian Human Rights Commission has confirmed this reaches websites. The Commission points businesses to WCAG as the recognised way to meet those obligations.

Around one in five Australians lives with disability. A website that excludes them turns away a fifth of your potential market at the door.

There is a well-known Australian precedent. Before the 2000 Sydney Olympics, a tribunal found the organising committee had unlawfully discriminated against a blind user whose screen reader could not access the official ticketing site. That case still shapes how courts apply the DDA to digital services, and it shows that "we didn't realise" won't hold up as a defence.

Why it matters beyond compliance

Legal risk is real, but most businesses we work with come to value the commercial upside more. An accessible website is a better website, and the gains show up in numbers you can track.

Reach and revenue

When you design to the website accessibility guidelines, more people can finish the action that earns you money: booking, enquiring, buying. Think of older customers, people on slow regional connections, and anyone reading their phone in bright Sydney sun where low-contrast text disappears. Strong website accessibility design widens your audience.

SEO and AI search

Accessibility and search performance overlap. Descriptive alt text, a proper heading structure, clear link text, and semantic HTML help both screen readers and search engines read your content. The same markup that lets assistive technology parse your page lets Google and AI search engines index and cite it. If you invest in AI search engine optimisation, accessibility shares the same foundation.

Reputation and trust

An accessible site shows you take your customers seriously. If you tender for government or enterprise contracts, WCAG 2.2 AA conformance now appears as a hard requirement in procurement documents. Being able to demonstrate it can decide whether you make the shortlist or get cut on a checkbox.

A practical WCAG 2.2 AA checklist

You don't need to memorise all 87 success criteria to make progress. Here is a practical WCAG 2.2 AA checklist covering the issues we find most on Sydney business websites. Fix these and you clear most of the barriers.

• •Colour contrast: normal text needs a contrast ratio of at least 4.5:1 against its background. Pale grey text on white is the failure we see most.
• •Keyboard navigation: you should be able to operate every menu, form and button without a mouse, in a logical order, with a visible focus indicator showing where you are.
• •Image alt text: meaningful images need descriptive alternative text; mark decorative images so screen readers skip them.
• •Form labels and errors: give every field a programmatic label, and write error messages that say what went wrong and how to fix it.
• •Heading structure: use real headings (H1, H2, H3) in order, not bold text dressed up to look like headings.
• •Focus not obscured (new in 2.2): when an element takes keyboard focus, a sticky header or cookie banner must not cover it.
• •Accessible authentication (new in 2.2): don't make users solve puzzles or memorise codes to log in; let them use password managers and copy-paste.
• •Resizable text: content must stay usable at 200% zoom, with no horizontal scrolling or overlapping elements.

How to get your site compliant

Reaching WCAG 2.2 AA is a process, not a switch you flip. Here is the approach we use with clients.

Start with an audit. Automated tools like Lighthouse, axe DevTools or WAVE catch roughly 30 to 40 percent of issues quickly and for free. The rest, keyboard traps, illogical screen-reader order, unclear link text, need a person who knows what to look for to test by hand. A proper audit combines both and hands you a prioritised list instead of a wall of warnings.

Fix in priority order. Start with the criteria that block people from core tasks (checkout, contact forms, navigation), then work outward to content and media. Bake accessibility into your design system so new pages inherit it instead of reintroducing the same problems. That costs far less than retrofitting later, which is why we treat it as a default in our website development work rather than an add-on.

Test and maintain. Accessibility is not a one-off project. A new blog post, product page or campaign landing page can each introduce regressions, so build checks into your publishing process and revisit the site on a schedule. If you would rather hand this off, ongoing accessibility monitoring sits well alongside managed IT support, keeping standards from slipping as your content grows.

This article reflects best practices as of the publication date. Technology and security recommendations change, so check current guidance with the original sources or our team before you act.