There is a version of accessibility that is entirely about compliance.
It begins with WCAG — the Web Content Accessibility Guidelines — and works through a checklist. Sufficient colour contrast. Alternative text on images. Keyboard navigability. Screen reader compatibility. Captions on video content. These are important standards. Meeting them is necessary. But meeting them is also, in the most important sense, only a starting point.
The compliance model of accessibility asks: does this system meet the technical requirements for accessibility? The genuine inclusion model asks a different and more demanding question: can every citizen who needs to access this service actually access it?
The answer to the second question, in most public-sector environments, is no.
The Limits of Technical Compliance
Consider what WCAG compliance actually addresses. It addresses the technical accessibility of a digital interface — ensuring that a person using a screen reader can navigate the page, that a person with colour vision deficiency can read the content, that a person with motor impairments can interact with the interface using a keyboard.
These are genuine and important accessibility requirements. Failing to meet them excludes real people from real services. Meeting them is not optional for public-sector organisations with legal and ethical obligations to serve their entire communities.
But WCAG says nothing about language. A website can be fully WCAG 2.1 AAA compliant and entirely inaccessible to a citizen who does not read English.
WCAG says nothing about digital literacy. A website can be perfectly keyboard-navigable and practically inaccessible to an elderly resident who has never used a web browser and does not know how to find the page they need.
WCAG says nothing about time of access. A service that is accessible during business hours — accessible in the technical sense, with staff available to assist — may be effectively inaccessible to a shift worker who can only engage with public services at 10pm.
These are accessibility failures. They affect millions of Australians. And they are not addressed by WCAG compliance.
The Three Dimensions of Genuine Accessibility
Genuine accessibility in public services operates across at least three dimensions that technical compliance frameworks do not fully address.
Language. The ability to access public information in one's own language is a fundamental equity requirement — not a convenience feature. For the approximately one in five Australians who speak a language other than English at home, the effective accessibility of English-only services is dramatically lower than their nominal availability. This is an accessibility failure with real consequences: reduced access to healthcare information, reduced ability to navigate government services, reduced capacity to access benefits and entitlements that are formally available to them.
Digital literacy and interface complexity. Public-sector digital services have improved significantly. They are generally better designed, better organised, and better supported than they were a decade ago. They remain, however, designed for citizens with moderate to high digital literacy and sufficient familiarity with government service structures to know where to look. For citizens who lack this familiarity — elderly residents, recent arrivals, those with limited formal education — the navigational complexity of even a well-designed government website represents a genuine access barrier.
Availability. Services that require human interaction for their accessibility — services where the only path to accessing a complex inquiry is speaking with a staff member — are services that are only accessible during staffed hours. For a significant proportion of the population, those hours do not align with the times when they are able to engage. This is particularly acute for working adults, carers, and residents in rural or regional areas with limited local service access.
Conversational Infrastructure as Genuine Accessibility
Multilingual conversational infrastructure addresses all three of these dimensions simultaneously.
It removes the language barrier by responding in the citizen's own language — not through a translated static page, but through a conversational interface that interprets natural-language questions and provides accurate responses.
It reduces the digital literacy barrier by providing a natural-language interface that does not require knowledge of website structure, department names, or service navigation pathways. The citizen describes what they need; the infrastructure interprets and responds.
It removes the availability barrier by operating continuously — providing access to approved public information at any hour, any day, without restriction to staffed service hours.
None of this replaces the need for human services. Complex matters, sensitive situations, and decisions that require judgement will always require human engagement. But the informational and navigational layer of public service access — the layer that accounts for the majority of citizen-institution interactions — can be made genuinely accessible to every citizen, in every language, at any time.
The Infrastructure Commitment
The argument for conversational infrastructure as an accessibility investment is not primarily a technology argument. It is a public service commitment.
It is a commitment that every citizen — regardless of language background, digital literacy, time of access, or geographic location — deserves equitable access to the public information and services that exist to serve them.
WCAG compliance is the floor. Genuine inclusion is the ceiling. The distance between them is significant — and bridging it requires infrastructure investment, not just interface improvement.
For public-sector organisations that take their accessibility obligations seriously, that investment is not optional. It is the infrastructure of genuine public service.