The Digital Inclusion Standard is not an accessibility job. Content owns part of every criterion.

The Digital Inclusion Standard has applied to every existing public-facing Australian Government service since 1 January 2026. New public-facing and new staff-facing services came into scope a year earlier, on 1 January 2025.

Most agencies file it as an accessibility job and route it to developers. That is where it stalls.

The Standard is not an accessibility job. It is 5 decisions about a service, and a content team owns part of every one of them.

## What the Standard asks

It sets the requirements for inclusive and accessible digital government experiences. It builds on Criterion 3 of the Digital Service Standard, Leave no one behind, and it has 5 criteria:

1. Embrace diversity

2. Motivate digital use

3. Protect users

4. Make it accessible

5. Provide flexibility and choice

Each criterion comes with its purpose, your responsibilities, when to apply it, and a set of suggested activities. The suggested activities are not requirements. That distinction matters more than it sounds, and it catches people out on Criterion 5.

## Which services it covers

The Standard is mandatory. It covers informational and transactional digital services in 4 categories:

- services subject to the Investment Oversight Framework

- new or replacement public-facing services

- new staff-facing services

- all existing public-facing services

Read the last one twice. It is the category agencies get wrong. The compliance guide says all existing public-facing services must comply with the Digital Service Standard and the Digital Inclusion Standard. No investment condition attached.

The Investment Oversight Framework condition applies to new or replacement services. A legacy website with no current investment proposal is still in scope.

The Standard does not apply to state or territory services. Agencies outside the mandatory scope are welcome to adopt it, but nothing obliges them to.

## What content owns in each criterion

None of the 5 is only a content job. Claiming otherwise gets content teams ignored. Here is where the line falls.

### 1. Embrace diversity

Co-design dominates this criterion. It also names 8 cohorts with specific requirements. They run from people who are blind or have low vision to people affected by family and domestic violence.

Content owns the reading level, the languages the core task appears in, and the support content for people who cannot finish online. Content does not own the co-design program.

### 2. Motivate digital use

Three things: communicate the benefits of the digital channel, understand what motivates your audience, and make the service easy to use.

Content owns the benefit statement and the jargon. If your page leads with a form number, nobody has written that statement.

### 3. Protect users

It leads with establishing and maintaining a safe digital environment. That is security, moderation and incident response as much as it is words. It then asks agencies to counter scams and misinformation, and to provide transparency and feedback loops.

Content owns the scam-awareness wording, the privacy content, and whether a person can find how to report a problem.

### 4. Make it accessible

This criterion names 3 instruments to comply with:

- the Disability Discrimination Act 1992

- the latest version of the Web Content Accessibility Guidelines

- the Australian Government Style Manual

A standard naming the Style Manual by title makes it a compliance instrument, not a house preference.

Content owns headings, link text and alt text. It owns captions, transcripts and reading level. It does not own assistive technology testing or the procurement conditions, which sit in the same criterion.

### 5. Provide flexibility and choice

This is the one people get wrong. It has 2 stated responsibilities. Flexibility in how users engage, and what the Standard calls seamless experiences across service delivery channels. Adaptable interfaces, themes and font controls sit in the suggested activities. Not the requirements.

So the test is not whether your layout reflows. A person starts online, rings the contact centre, then walks into a shopfront. Do they get the same answer?

That is a content problem with an owner-shaped hole in it.

## What you have to show

Agencies show compliance through the Digital Transformation Agency (DTA). It runs through the data collection activities that support the Investment Oversight Framework. No separate return exists.

The compliance guide says any future reporting will cover services above 50,000 end-to-end transactions a year. The policy page puts it as transactions or page visits. Neither document describes a penalty.

Exemptions exist for genuine barriers. The guide names 2. Legacy technology that cannot reasonably be overcome, and substantial financial burden in modifying the service. That list is illustrative rather than closed.

An exemption can cover one or more criteria, or a whole standard. It cannot cover the whole policy. Apply in writing to the DTA.

Where to start

If you want to work through the criteria one service at a time, use the content checklist. It turns each criterion into a plain question, what good looks like, and a decision to record.

If you have inherited an estate you cannot take down, read the guide to retrofitting existing services. It starts from evidence you already hold and sequences the work by harm.

What good looks like

  • Somebody in your agency can say which of your services are in scope, and why.

  • Nobody on your team believes Criterion 5 is about responsive layouts.

  • You have routed the design, engineering and procurement gaps to those teams, in writing.

  • Your content evidence is in a format a policy area can attach to a compliance return.

  • Anything you cannot fix this year has an exemption case with a plan behind it.

Your agency already holds most of the evidence, in audience research, content reviews and accessibility audits. It is in the wrong format, not missing.

So here is the question for your next service meeting. If somebody asked today how one of your services meets the Standard, who in your agency would answer, and what would they hand over?

Photo by Steve A Johnson on Unsplash.

Previous
Previous

Digital Inclusion Standard content checklist

Next
Next

AI procurement for government content