Quick Answer: WCAG 2.2 AA is the mandatory baseline for ACT and Commonwealth government web properties, procurement suppliers, and NDIS service providers. Critical technical requirements include 4.5:1 colour contrast, full keyboard Tab navigability, descriptive form error recovery, and at least 24×24px interactive tap targets.

Accessibility Is Not Optional

WCAG Principle Core Standard Practical Check on Your Site
Perceivable Contrast >= 4.5:1, image alt text No faint light-grey text; meaningful alt tags on every photo
Operable Keyboard-only Tab flow, Target Size >= 24×24px Visible focus rings; zero trapped dropdowns or tiny footer icons
Understandable Plain English, explicit error guidance Forms tell users what to fix rather than turning boxes red
Robust Semantic HTML & screen-reader ARIA Clean H1→H2→H3 hierarchy and labelled inputs

If your Canberra business has a website — and in 2026, every business does — then web accessibility affects you. The Web Content Accessibility Guidelines, known as WCAG, are the internationally recognised standards that define how websites should be built so they can be used by people with disabilities. The current version is WCAG 2.2, and the compliance level most commonly required is AA.

For some Canberra businesses, this is a legal requirement. For others, it is a competitive advantage. For all businesses, it is the right thing to do.

Who Needs WCAG 2.2 AA Compliance in Canberra?

Government departments and agencies: All ACT Government and Commonwealth Government websites must meet WCAG 2.2 AA. This is not negotiable.

Businesses tendering for government contracts: If you are a private business that supplies services to government, your digital presence is increasingly scrutinised as part of the procurement process. A non-compliant website can disqualify you from consideration.

NDIS providers: As registered providers serving participants with disabilities, NDIS businesses have both a moral and practical obligation to ensure their websites are accessible. A visually impaired participant trying to find your services page and failing is not just a usability problem — it is a trust-destroying experience.

Everyone else: While there is no specific Australian federal law mandating WCAG compliance for all private websites (unlike the ADA in the United States), the Disability Discrimination Act 1992 has been used in complaints against organisations with inaccessible websites. The legal landscape is moving in one direction, and it is towards mandatory compliance.

The Core Principles of WCAG

WCAG is built on four principles, remembered by the acronym POUR:

Perceivable: Users must be able to perceive the content. This means providing text alternatives for images (alt text), captions for videos, and ensuring sufficient colour contrast between text and background. That light grey text on a white background that your designer thought looked elegant? It fails WCAG because people with low vision cannot read it.

Operable: Users must be able to navigate and interact with the site. This means every function must be accessible via keyboard alone — no mouse required. It means no content that flashes more than three times per second (seizure risk). And it means providing enough time for users to read and interact with content without arbitrary timeouts.

Understandable: Content and navigation must be logical and predictable. Forms need clear labels. Error messages need to explain what went wrong and how to fix it. Navigation must be consistent across pages. If your contact form just highlights a field in red without explaining what is wrong, that fails WCAG.

Robust: Content must work reliably across different browsers, devices, and assistive technologies like screen readers. This means using proper semantic HTML — heading hierarchies that make logical sense, form elements with explicit labels, and ARIA attributes where native HTML is insufficient.

What Changed in WCAG 2.2

Version 2.2, released in October 2023, added nine new success criteria. The most impactful for Canberra businesses are:

Dragging Movements (2.5.7): If your website has any drag-and-drop functionality (reordering items, moving elements on a dashboard), there must be an alternative method that does not require dragging. Not everyone has the fine motor control to drag precisely.

Target Size Minimum (2.5.8): Interactive elements like buttons and links must be at least 24 by 24 CSS pixels. Those tiny social media icons in your footer that are 16 pixels wide? They fail this criterion.

Consistent Help (3.2.6): If your site provides help mechanisms (chat widgets, phone numbers, FAQ links), they must appear in the same relative location on every page. Moving your contact information around the site depending on the page layout is now a compliance failure.

Accessible Authentication (3.3.8): Login processes must not rely on cognitive function tests. If your client portal requires users to solve a CAPTCHA, remember a complex password without password manager support, or transcribe a code from an SMS, you may be failing this criterion.

Practical Steps for Your Canberra Business

You do not need to rebuild your entire website to achieve compliance. Here is a practical starting point:

Run an automated audit. Tools like Google Lighthouse, axe DevTools, and WAVE will catch roughly forty to sixty percent of accessibility issues automatically. They will flag missing alt text, insufficient colour contrast, missing form labels, and heading hierarchy problems.

Test with a keyboard. Unplug your mouse and try to navigate your entire website using only Tab, Shift+Tab, Enter, and Arrow keys. Can you reach every link, button, and form field? Can you see where you are on the page (is there a visible focus indicator)? If not, you have operability failures.

Test with a screen reader. VoiceOver is built into every Mac. NVDA is free for Windows. Turn one on and try to complete a task on your website — find a service, read a blog post, submit a contact form. This will reveal whether your HTML structure makes semantic sense or whether it is a confusing mess when read aloud.

Fix the high-impact items first. Colour contrast, alt text, form labels, and keyboard navigation cover the vast majority of real-world accessibility barriers. Start there before worrying about edge cases.

The Business Case for Accessibility

Beyond compliance and ethics, accessibility improves your website for everyone. Proper heading hierarchies help Google understand your content structure, improving SEO. Sufficient colour contrast makes text easier to read for all users, including on mobile devices in bright sunlight. Keyboard navigation benefits power users who prefer keyboard shortcuts. Clear form labels reduce abandonment rates for everyone.

Building accessible websites is simply building good websites.

At Maximum Ideas, every site we build is tested against WCAG 2.2 AA criteria before launch. It is not an add-on or an afterthought — it is part of our standard process across our NDIS website engineering builds and government supplier engagements. Run our free WCAG & site health audit or book a consultation to remediate accessibility issues on your domain.

Maximum Ideas is a registered business name of Indesign Media Group Pty Ltd (ABN 99 609 102 374).