How to prepare for 2026 Australian Government accessibility requirements
A practical, plain-language readiness guide for agencies and the suppliers who serve them: the standards that apply, what to check first, and how to turn a point-in-time audit into sustained conformance.
Overview
What do Australian government services need to meet in 2026?
Australian government digital services are expected to meet WCAG 2.2 Level AA. The federal Digital Service Standard references WCAG conformance, the Disability Discrimination Act 1992 makes inaccessible services a discrimination risk, and most agency procurement now specifies WCAG 2.2 AA. Preparing for 2026 means treating WCAG 2.2 AA as the baseline across websites, applications, native apps and documents, and being able to evidence it.
The standards that apply
There is no single 2026 switch that turns accessibility on. Instead, several established obligations converge, and the practical expectation for Australian government in 2026 is consistent conformance to WCAG 2.2 AA:
- WCAG 2.2 Level AA: the current version of the Web Content Accessibility Guidelines, a W3C Recommendation since 2023. It is the de facto target across Australian government.
- Digital Service Standard: the federal standard for government services references accessible, inclusive services and WCAG conformance.
- Disability Discrimination Act 1992 (DDA): makes it unlawful to provide services in a way that discriminates against people with disability. The Australian Human Rights Commission points to WCAG as the practical benchmark.
- EN 301 549: the European procurement standard, increasingly referenced in Australian tenders for software and ICT.
- PDF/UA: the document-accessibility standard for published files such as PDFs and forms.
A 2026 readiness sequence
Order matters. Auditing everything at once produces a backlog no one can action. This sequence concentrates effort where exposure is highest first.
-
1. Baseline your highest-risk services
Run an independent WCAG 2.2 AA audit of your highest-traffic and highest-risk services first, transactional services, login flows and anything tied to a legal entitlement. This gives you a defensible current-state position.
-
2. Prioritise by impact, not by criterion number
Rank findings by user impact and legal exposure, not by WCAG reference order. A blocked checkout or an inaccessible benefits form matters more than a minor contrast issue on a footer.
-
3. Fix the document estate, not just the website
Most agencies overlook the thousands of published PDFs and forms behind the site. Set a documented approach to accessible document production and batch-remediate the existing estate.
-
4. Update procurement to require conformance
Require WCAG 2.2 AA and a VPAT or Accessibility Conformance Report from suppliers, and learn to evaluate those claims with appropriate scrutiny rather than accepting a tick-box.
-
5. Embed it so it survives the next release
A point-in-time audit drifts. Assign a named accessibility owner, add testing to your release process, and consider an organisational uplift programme scoped against the W3C Accessibility Maturity Model.
If you are a government supplier
Agencies increasingly pass accessibility obligations down through procurement. If you bid for government work in 2026, expect to demonstrate WCAG 2.2 AA conformance of your product and your delivery process, supported by independent evidence. Our WCAG 2.2 compliance checklist for government suppliers walks through exactly what to prepare, and how we work covers engagement and procurement detail.
For the agency-side view, see our government accessibility consulting overview, and our research on the current state of the sector in the Australian Government Accessibility Index.
Common questions about 2026 government accessibility requirements
Plain answers to the questions agencies and suppliers ask most often.
What is the difference between WCAG 2.1 and WCAG 2.2 for government?
WCAG 2.2 adds nine new success criteria to WCAG 2.1, covering focus appearance, dragging movements, target size, consistent help and accessible authentication. It became a W3C Recommendation in 2023 and is the current version. Agencies built to WCAG 2.1 AA should re-test against the new 2.2 criteria, as several apply directly to common government patterns like multi-step forms and login flows. See our WCAG 2.2 Quick Reference.
What should a government agency do first to prepare?
Start with an independent WCAG 2.2 AA audit of your highest-traffic and highest-risk services to establish a baseline, then prioritise remediation by user impact and legal exposure. In parallel, update procurement templates to require WCAG 2.2 AA and Accessibility Conformance Reports, and assign a named owner. A point-in-time audit without governance will drift.
Does accessibility apply to documents and PDFs, not just websites?
Yes. Published documents such as PDFs, Word files and forms must be accessible too, typically to WCAG 2.2 AA and PDF/UA. Document estates are a common gap because agencies focus on the website and overlook the thousands of published files behind it. A 2026 readiness plan should include accessible document production and remediation of the existing estate.
How long does it take to get ready?
A focused WCAG 2.2 audit of a priority service typically takes 3 to 6 weeks; a full compliance uplift programme runs 3 to 9 months end to end. The realistic answer depends on the size of your digital and document estate. The sooner you baseline, the sooner you can sequence the work against your deadline. See how we work for indicative timeframes.
Get ahead of your 2026 deadline
Tell us your service, your estate and the date you are working towards. We will come back with a realistic baseline and a prioritised path to WCAG 2.2 AA.
Book a Discovery Call Get in Touch