Neurodiversity is not niche. Accessibility can no longer be an afterthought
In a world increasingly reliant on technology, accessibility should not be an afterthought - it must be a foundational principle.
For many individuals, the concept of accessibility in mainstream software programs is limited to superficial "fixes" such as a basic screen reader function or changing font sizes, heralding their "commitment" to "accessibility".
However, the concept of "accessibility" runs much deeper than that, reflecting more than just an inconvenience; it represents a barrier to participation in education, employment, and daily life, for many people living with disability, neurodiversity, or even just the struggles that come with the eternal plod of time.
Despite being better than most, even Microsoft Office, often championed as the "gold standard" fails to meet more than the basics of the diverse needs of its users.
It is time for software developers to embed accessibility for individuals into their design processes, ensuring that we do not have to self-advocate for basic access.
Let's talk neurodiversity.
Neurodiversity encompasses a range of conditions, including autism, ADHD, dyslexia, and dyspraxia.
“For many neurodiverse individuals, continuously advocating for their needs can be an exhausting and demoralising process.”
In Australia, approximately 15-20 per cent of the population is estimated to be neurodivergent.
These figures highlight a significant portion of the population whose needs are often overlooked in software design.
Moreover, the neurodiverse market is a growing niche. As awareness increases and diagnostic tools improve, more individuals are being diagnosed later in life.
This trend underscores the urgent need for inclusive design not just at an early education level, but at the professional level too. Businesses that fail to address this market are not only perpetuating inequity but also missing out on a substantial commercial opportunity.
For many neurodiverse individuals, continuously advocating for their needs can be an exhausting and demoralising process.
They often feel like "whispers in the mainstream crowd" with their voices drowned out by the noise of larger, more dominant user groups.
This is particularly true in the realm of software development, where accessibility features are frequently added as an afterthought rather than integrated from the outset.
Inclusive design is not just a moral obligation; it is a business imperative.
Research shows that diverse teams, including neurodiverse individuals, are more innovative and productive.
Companies that prioritise accessibility can tap into this potential, creating products that are not only more equitable but also more competitive.
For software developers, this means rethinking the design process. Accessibility should be a default consideration, not an optional feature. This involves:
Simplified workflows: Streamlining complex tasks to make them more intuitive would increase efficiency and productivity across the board (not just for people with accessibility needs), reduce cognitive and visual overload, enhance user experience and assist with task initiation, planning and organisation.
Customisable interfaces: Allowing users to adjust layouts, colours, and fonts to reduce sensory overload, while also reducing the change impact following updates for users for those who have customised their layouts to suit their needs.
Deeper customisable display options: Deeper customisable display options such as high-contrast themes and adjustable font sizes could aid people with vision impairments and reduce overwhelm and cognitive overload that often comes with complex interfaces,
Integrated accessibility tools: Including features like native text-to-speech, speech-to-text, and focus modes that don't require subscriptions or internet connections, and are available in standalone products.
User design engagement and testing with neurodiverse individuals: Ensuring that products are designed with diverse users in mind, thus meeting the needs of all users, not just the mainstream.
The responsibility for change lies with software companies, not users. By employing a diverse workforce and user-group design teams, companies can gain valuable insights into the challenges and opportunities of inclusive design.
Programs like the Aurora Neuroinclusion Program in Australia demonstrate the benefits of this approach, providing structured support for neurodiverse employees and fostering innovation.
It is time for software developers to take proactive steps, embedding accessibility into their design processes and creating tools that empower all users. By doing so, they can not only address a pressing social issue but also unlock the potential of a growing and underutilised market.
The future of technology should be inclusive by design. Let us build it together.
Zoë is a regular op-ed columnist for Australian Community Media, with her column syndicated across their papers. This blog post first appeared in The Canberra Times on 19 March 2025.
