Skip to main content
← Back to writing
Web design

WCAG accessibility requirements for Australian not-for-profits

12 June 2026·11 min read·Ben Adams
WCAG accessibility requirements for Australian not-for-profits
WCAG Accessibility Requirements for Australian Not-for-Profits | Marzipan
Marzipan · Sydney

WCAG accessibility requirements for Australian not-for-profits

Australian charities have legal obligations around website accessibility. This guide explains what those obligations are, what WCAG 2.1 AA requires in plain English, and what to do if your site does not currently meet the standard.

Last updated June 2025 · 10 min read · Ben Adams, Marzipan

What WCAG 2.1 AA actually means

WCAG — the Web Content Accessibility Guidelines — is an internationally recognised technical standard developed by the W3C. Version 2.1, Level AA is the current accepted benchmark for Australian websites.

It is built around four core principles. Content must be:

P

Perceivable

Information must be presentable to users in ways they can perceive — including people who cannot see, hear, or distinguish colours.

O

Operable

All functionality must be operable without requiring a mouse — keyboard navigation, voice control, and switch access must all work.

U

Understandable

Content and navigation must be understandable — clear language, predictable behaviour, and helpful error messages.

R

Robust

Content must be robust enough to be reliably interpreted by assistive technologies, including screen readers and voice software.

In practical terms, meeting WCAG 2.1 AA means your website can be used by people who rely on screen readers, keyboard navigation only, high-contrast display settings, captions for video content, and other assistive technologies.


The most common accessibility failures on nonprofit websites

These are the issues found most frequently when auditing community organisation and charity websites in Australia.

Images without alternative text

Every meaningful image on a website needs descriptive alt text so that screen reader users can understand what it conveys. Decorative images should have empty alt attributes so screen readers skip them. This is one of the most pervasive failures — and one of the easiest to fix.

Insufficient colour contrast

WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Many websites use light grey text on white backgrounds, or coloured text on coloured backgrounds, that falls well short of this threshold. People with low vision or colour blindness are disproportionately affected.

Forms without accessible labels

Contact forms, referral forms, and donation forms frequently have fields with placeholder text but no properly associated labels. Screen readers cannot convey what a field is for if the label is missing or incorrectly associated.

Keyboard traps and missing focus indicators

Many website components — modal dialogues, dropdown menus, interactive maps — trap keyboard users or fail to show a visible focus indicator. A keyboard user who cannot see where focus is cannot navigate the site.

Videos without captions

Any pre-recorded video with speech or meaningful audio requires captions. Auto-generated captions from YouTube do not reliably meet the accuracy standard required.

Incorrect heading structure

Screen reader users navigate pages by heading. A page that skips from H1 to H4, or uses headings for visual styling rather than semantic structure, is very difficult to navigate.

  • Missing or unhelpful alt text on images
  • Text contrast below 4.5:1 ratio
  • Form fields without properly associated labels
  • No visible keyboard focus indicator
  • Video content without captions or transcripts
  • Broken heading hierarchy (H1, H2, H3 out of sequence)
  • Links that say “click here” or “read more” without context
  • PDFs that are not tagged for screen reader access

How to test your website’s accessibility

A meaningful accessibility assessment requires both automated tools and manual testing. Automated tools alone catch approximately 30–40% of WCAG failures — the rest require human review.

Automated tools (free)

  • WAVE (wave.webaim.org) — browser-based tool that highlights errors and warnings directly on the page
  • Axe — browser extension for Chrome and Firefox, widely used by developers
  • Google Lighthouse — built into Chrome DevTools, includes an accessibility score
  • Colour Contrast Analyser — desktop tool from TPGi for checking contrast ratios

Manual checks you can do now

  • Tab through your entire website using only a keyboard — can you reach everything?
  • Turn off your monitor and try to navigate using a screen reader (NVDA for Windows is free; VoiceOver is built into Mac and iPhone)
  • Zoom your browser to 200% — does the layout break or does text overflow?
  • Check that every form field has a visible, accurate label
  • Review your heading structure — does it flow logically from H1 through H2 and H3?
  • Try our free Accessibility Audit tool Check Your Website’s Accessibility
Professional assessment

Marzipan’s Digital Capacity Diagnosis includes an accessibility assessment as one of its six core areas. It covers automated testing, manual review of common failure points, and a plain-English summary of issues with a prioritised remediation plan. Learn more.


What remediation involves

The approach to fixing accessibility issues depends on their nature and severity. Some can be resolved quickly by whoever manages your website content; others require developer involvement.

Content-level fixes (no developer needed)

  • Adding alt text to existing images
  • Correcting heading structure in page content
  • Replacing non-descriptive link text (“click here”) with meaningful descriptions
  • Adding transcripts to audio content

Template and theme-level fixes (developer required)

  • Correcting colour contrast in CSS
  • Adding visible focus indicators to interactive elements
  • Fixing form label associations
  • Resolving keyboard trap issues in navigation components
  • Adding ARIA roles and landmarks to improve screen reader navigation

For organisations with older websites, remediation is sometimes more cost-effective as part of a broader rebuild. For newer sites, targeted fixes are usually sufficient. A proper assessment is the most useful first step — without one, it is difficult to prioritise.


Accessibility as ongoing practice

Accessibility is not a project that ends. A website that passes an audit today can develop regressions within months — when a new plugin is installed, a template is updated, or a content editor adds images without alt text.

Organisations that treat accessibility as a one-time remediation exercise consistently find themselves with recurring issues. The most effective approach is to embed accessibility into ongoing website governance: regular automated scans, periodic manual reviews, and training for anyone who adds content to the site.

For not-for-profits without an in-house digital team, this is one of the areas where digital stewardship adds the most consistent value — handling ongoing monitoring and catching regressions before they become complaints.

Not sure where your site stands?

A Digital Capacity Diagnosis includes a plain-English accessibility assessment — what the issues are, how serious they are, and what to do about them. $1,500 + GST.

Book a Diagnosis →

Frequently asked questions

Do Australian charities have to make their website accessible?
Yes. The Disability Discrimination Act 1992 requires Australian organisations to make their services — including digital services — reasonably accessible to people with disability. The accepted standard is WCAG 2.1 Level AA. Organisations serving vulnerable populations have a particularly strong duty of care.
What is WCAG 2.1 AA?
WCAG 2.1 AA is the internationally accepted technical standard for website accessibility. It is built around four principles: content must be perceivable, operable, understandable, and robust. In practical terms, it means your website can be used by people who rely on screen readers, keyboard navigation, high-contrast displays, captions, and other assistive technologies.
What happens if a not-for-profit website fails WCAG standards?
Anyone in Australia can lodge a formal disability discrimination complaint with the Australian Human Rights Commission at no cost. If upheld, the organisation may be required to remediate the website, pay compensation, and cover costs. For organisations serving vulnerable populations, an accessibility failure also directly prevents the people you exist to help from accessing your services.
How do I check if my charity website is accessible?
A combination of automated and manual testing is required. Free tools such as WAVE and Axe identify many common issues, but cannot catch everything. A proper audit combines automated testing with manual review. Marzipan’s Digital Capacity Diagnosis includes an accessibility assessment as one of its six core areas.
← Back to Web design for charities
B
Ben Adams Ben is the founder of Marzipan, a Sydney-based digital practice specialising in digital stewardship for community legal centres, not-for-profits, and regulated organisations.
© 2025 Marzipan · Digital Stewardship for High-Trust Organisations · Sydney · ABN 61 181 193 114 Always Was, Always Will Be
Charity Web DesignNonProfitsWCAG accessibility
Begin

Need more than a document?Start with a Diagnosis.

The Digital Capacity Diagnosis gives your organisation a full digital risk assessment with a clear, prioritised action plan.