Inclusive design in digital government platforms means building public services so people with diverse capabilities, contexts, and literacy levels can complete important tasks with dignity, confidence, and low effort. In practice, that requires human-centred research, accessible interaction patterns, plain language, and continuous measurement, especially for people with cognitive disabilities who are often excluded by complexity, time pressure, and fragmented service journeys.
What does inclusive design mean in digital government?
Inclusive design in this article means the deliberate design of government websites, portals, forms, and assisted digital journeys for the widest practical range of users, including people with disability, low digital confidence, low literacy, limited English proficiency, older age, or constrained devices and connectivity. It is broader than technical accessibility alone. WCAG 2.2 defines testable accessibility requirements for digital content,^1 but inclusive design also covers service logic, language, trust, recovery from error, channel choice, and the social context in which a person uses a service.
Digital government teams should treat inclusive design as a service quality discipline, not a compliance add-on. The Australian Government’s Digital Inclusion Standard states that digital government experiences should be inclusive and accessible for all people and business,^2 while the Digital Service Standard requires services to meet user needs with consistency, accessibility, and transparency.^3 In Australia, this work also sits within anti-discrimination obligations for digital goods and services.^4
Why does inclusive design matter now?
Government platforms mediate access to essential rights, payments, licences, healthcare, and justice. When those platforms are hard to understand or navigate, exclusion becomes operational, not abstract. In Australia, 5.5 million people had disability in 2022,^5 which means inaccessible or overly complex digital services can affect a large share of the population, their carers, and frontline staff who must compensate for poor design.
Digital exclusion also creates cost and risk. A difficult form increases abandonment, contact centre demand, rework, and complaints. A fragmented identity or eligibility process increases distrust and service avoidance. Recent research on e-government services shows that accessibility, self-service capability, user support, personalisation, and privacy protection shape citizens’ service experience and perceived value.^9 For public agencies, inclusive design therefore improves both social equity and delivery performance.
How does inclusive design work for people with cognitive disabilities?
Cognitive accessibility focuses on how people process information, sustain attention, understand sequences, remember instructions, and recover from mistakes. W3C guidance notes that cognitive and learning disabilities affect how people process information and interact with digital systems.^10 Designing for cognitive disabilities therefore means reducing avoidable mental effort, not reducing the seriousness of the task.
Teams should simplify task flows, chunk content, keep layouts stable, label controls clearly, and give users enough time and support to complete forms. Plain language matters because users cannot act on information they do not understand. In a randomized study, plain language versions improved adults’ understanding, accessibility, usability, satisfaction, and preference compared with standard versions.^11 For government, that translates into shorter instructions, meaningful headings, predictable buttons, visible progress, error prevention, and recovery paths that explain what happened and what to do next.
Which principles matter most?
Human-centred design provides the operating model. ISO 9241-210 requires design to be based on an explicit understanding of users, tasks, and environments, and it emphasises iteration and multidisciplinary teams.^6 ISO/IEC 30071-1 extends that discipline into accessible ICT development and procurement processes.^7 Together, these standards point to a practical sequence: understand users, co-design with them, prototype early, test with assistive and mainstream users, then improve continuously.
The highest-value principles are consistency, clarity, tolerance for error, and equivalent access across channels. Consistency reduces memory load. Clarity reduces interpretation effort. Error tolerance protects users from irreversible mistakes. Equivalent access ensures that people who cannot complete a task online still have a supported pathway. These principles are especially important in high-stakes government contexts such as payments, identity, health, and compliance.
How is inclusive design different from accessibility compliance?
Accessibility compliance verifies whether a product meets defined technical requirements. Inclusive design asks whether a person can actually complete a real task in a real context. Compliance remains necessary because WCAG 2.2 and procurement standards such as AS EN 301 549:2024 set a defensible baseline for digital accessibility and testing.^1 ^8 But compliance alone does not guarantee a usable service.
A compliant form can still fail if the language is dense, the service logic is confusing, or the recovery path pushes users into a dead end. Inclusive design adds contextual research, journey mapping, trauma-aware content, service blueprinting, and usability testing with people who are often underrepresented. For digital government leaders, the practical distinction is simple: compliance checks the interface, while inclusive design checks whether the service works for the person.
Where should agencies apply it first?
Agencies should start with high-volume, high-consequence journeys such as onboarding, identity proofing, eligibility assessment, address changes, bookings, complaints, and status tracking. These journeys generate the most failure demand when design is poor. They are also where inclusive improvements deliver visible returns in completion, confidence, and channel shift.
A strong starting point is mixed-method research that combines behavioural evidence with direct user observation. Customer Science’s CX Research & Design approach is relevant here because it links service research, journey diagnosis, and design decisions across public-sector channels. In digital government, that kind of work is most effective when it includes participants with cognitive disability, carers, interpreters, and frontline staff who see where journeys break in practice.
What risks do agencies face if they get this wrong?
Exclusion risk is the most visible outcome, but it is not the only one. Poor inclusive design increases legal and policy exposure, especially where essential services become effectively unavailable to some users.^4 It also drives hidden operating costs through repeat contacts, assisted completions, manual overrides, appeals, and staff workarounds.
Trust risk is equally important. Citizens interpret confusing digital experiences as signals about fairness, competence, and respect. Research on participatory technology design with people with disabilities shows that inclusive involvement improves relevance and ethics while reducing the chance that teams institutionalise biased assumptions into products and processes.^12 In government, failure to include affected users early often produces solutions that are technically finished but socially brittle.
How should agencies measure success?
Measurement should track both conformance and lived experience. Agencies need accessibility audits, but they also need task success, time on task, abandonment, avoidable contact, error frequency, assisted digital demand, and confidence scores for priority cohorts. Progress should be reviewed at the journey level, not only at the page level, because many failures emerge between steps rather than inside a single screen.
Customer Science’s Customer Science Insights is relevant to this measurement problem because inclusive design improves when behavioural, operational, and experience signals are analysed together. The most useful dashboards separate baseline performance from subgroup performance, so leaders can see whether apparent gains for the average user hide persistent barriers for people with cognitive disability, older users, or low-confidence users.
What should leaders do next?
Leaders should make inclusive design a governance requirement across policy, procurement, design, content, and operations. That means naming inclusive outcomes in service KPIs, requiring accessibility and usability evidence before release, and funding ongoing iteration rather than one-off remediation. It also means treating assisted digital and contact centre insights as part of design evidence, not just service operations data.
The next practical step is to select one critical journey, define the excluded user groups most affected by it, map the highest-friction moments, and redesign those moments with direct user participation. This creates a visible proof point and a reusable operating pattern. Over time, inclusive design becomes part of how digital government platforms are planned, tested, procured, and improved.
What evidence supports this approach?
The evidence base is now strong enough for executive action. International standards provide process and procurement discipline.^6 ^7 ^8 Australian policy sets clear expectations for inclusive and accessible digital government experiences.^2 ^3 Australian human rights guidance links those expectations to equal access obligations.^4 Academic studies show that service design characteristics shape e-government experience,^9 plain language improves comprehension and usability,^11 and participatory design with people with disabilities strengthens outcomes and governance quality.^12
For senior leaders, the conclusion is straightforward. Inclusive design is not a niche usability preference. It is a measurable public service capability that improves access, trust, operational efficiency, and policy delivery when built into the full service lifecycle.
FAQ
What is the core difference between inclusive design and accessibility?
Accessibility sets the technical baseline for access.^1 Inclusive design goes further by ensuring people can complete real government tasks across the whole journey, including content, process logic, support, and recovery from error.
Why should digital government teams prioritise cognitive disabilities?
People with cognitive disabilities are often excluded by complexity, dense language, time pressure, and inconsistent flows.^10 Designing for cognitive accessibility usually improves clarity and completion for many other users as well.
Does WCAG 2.2 solve the problem on its own?
No. WCAG 2.2 is essential,^1 but agencies still need human-centred research, plain language, journey testing, and assisted digital pathways to make services work in practice.
What should be measured first?
Start with task completion, abandonment, error rates, repeat contact, and assisted digital demand for priority journeys, then compare outcomes across user groups rather than relying on averages alone.
Where can teams start improving public-sector digital services?
A practical place to begin is a high-volume journey such as onboarding, eligibility, or complaints handling, supported by service redesign capability such as Customer Science’s Digital Service work.
How does inclusive design affect contact centres and service operations?
Better digital design reduces avoidable calls, escalations, rework, and staff intervention. It also improves the quality of assisted service because the underlying journey becomes clearer and more consistent.
Sources
- W3C. Web Content Accessibility Guidelines (WCAG) 2.2. 2023. https://www.w3.org/TR/WCAG22/
- Australian Government Digital Transformation Agency. Digital Inclusion Standard. 2024. https://www.digital.gov.au/policy/digital-experience/digital-inclusion-standard
- Australian Government Digital Transformation Agency. Digital Service Standard. 2024. https://www.digital.gov.au/policy/digital-experience/digital-service-standard
- Australian Human Rights Commission. Guidelines on equal access to digital goods and services. 2024. https://humanrights.gov.au/resource-hub/resources-for-organisations-businesses/disability-resources-employers/guidelines-equal-access-digital-goods-and-services
- Australian Bureau of Statistics. Disability, Ageing and Carers, Australia: Summary of Findings, 2022. 2024. https://www.abs.gov.au/statistics/health/disability/disability-ageing-and-carers-australia-summary-findings/latest-release
- ISO. ISO 9241-210:2019 Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems. 2019. https://www.iso.org/standard/77520.html
- ISO. ISO/IEC 30071-1:2019 Information technology — Development of user interface accessibility — Part 1: Code of practice for creating accessible ICT products and services. 2019. https://www.iso.org/standard/70913.html
- Standards Australia. AS EN 301 549:2024 Accessibility requirements for ICT products and services. 2024. https://store.standards.org.au/product/as-en-301-549-2024
- Chan FKY, Techatassanasoontorn AA, Venkatesh V, Thong JYL. Design characteristics and service experience with e-government services: A public value perspective. International Journal of Information Management. 2025;80:102834. https://doi.org/10.1016/j.ijinfomgt.2024.102834
- W3C Web Accessibility Initiative. Cognitive Accessibility at W3C. 2024. https://www.w3.org/WAI/cognitive/
- Sayfi S, Charide R, Elliott MJ, et al. A multimethods randomized trial found that plain language versions improved adults’ understanding of health recommendations. Journal of Clinical Epidemiology. 2024;165:1-12. https://doi.org/10.1016/j.jclinepi.2023.11.009
- Küchler S, Heitplatz V, et al. Guidelines for Participatory Technology Design with People with Disabilities. Interacting with Computers. 2025;iwaf012. https://doi.org/10.1093/iwc/iwaf012