NDIS Website Requirements: What Every NDIS Provider Has to Get Right
Most advice about NDIS websites is written to make you nervous. Comply or fail your audit. Get accessible or get sued. It sells web design, but it is not an honest picture of what a website does for an NDIS provider, and it leaves the genuinely important things unsaid.
Here is the more useful version, based on what actually decides whether a support coordinator refers someone to you, and on what people with disabilities need from your site once they arrive.
The legal position on website accessibility, stated accurately
The Disability Discrimination Act 1992 covers the provision of information and services through the web. That is not a grey area. The Australian Human Rights Commission has published advisory notes on web access under the DDA for years, and they apply to any organisation running a website in Australia, private businesses included.
Two things are worth being precise about, because a lot of marketing copy overstates them.
First, the Commission’s advisory notes do not carry direct legal force. The DDA itself does. The notes explain how the Act applies and recommend a minimum of Level AA conformance with the Web Content Accessibility Guidelines, which is also the benchmark the Australian Government works to for its own digital services.
Second, nobody audits your website against these accessibility standards and issues a fine. The risk is a disability discrimination complaint. The Commission’s own position is the practical one worth remembering: a complaint is much less likely to succeed where reasonable steps were taken to address accessibility during the design stage. Accessibility is risk reduction, not a certificate you hang on the wall.
For anyone in the disability sector there is a second reason that matters more than the legal one. Your audience is disproportionately made up of people using assistive technology. An inaccessible website is not a compliance problem for them. It is a closed door.
What WCAG 2.1 Level AA means for an accessible website
WCAG 2.1 Level AA is the working benchmark. Stripped of the jargon, meeting it means a handful of concrete things:
- Colour contrast that passes. Light grey text on white fails. So does white text on a mid-tone brand colour, which is where most provider sites come unstuck.
- Everything reachable by keyboard. If you cannot tab to your own phone number, your referral form or your menu, neither can someone who does not use a mouse.
- Real headings, in order. Screen readers navigate by heading structure. Text that is merely bold and large is invisible as structure.
- Alt text that describes the image. Not the filename, and not a keyword.
- Forms that announce themselves. Every field labelled, every error message readable by assistive technology, so a referral can be completed rather than abandoned halfway.
- Captions on video. If you publish participant stories or service explainers, they need captions.
- Usable on mobile devices. Most first visits arrive on smartphones, and a layout that only works on a desktop fails the majority of your visitors before accessibility even enters into it.
Two things that are not on the checklist but matter just as much. Write in simple language, because plain, readable copy serves participants, families and carers better than the sector’s usual vocabulary. And be sceptical of overlay widgets and bolt-on accessibility tools that promise instant compliance; they do not deliver it, and they frequently make usability worse for the assistive technology users they claim to help. Inclusive design is something you build, not something you install.
None of this is exotic. It needs to be built into the website design from the start, which is considerably cheaper than retrofitting it later.
The NDIS logo rule almost every NDIS provider gets wrong
This one catches people constantly, so it is worth stating plainly.
The NDIS logo itself is a registered trade mark. You cannot put it on your website simply because you deliver supports and services under the National Disability Insurance Scheme. Using it requires written consent from the NDIA.
What providers registered with the NDIS can use is the separate participant-facing badge the NDIA makes available for that purpose, with the registered provider tagline, downloaded from the NDIA and used according to its conditions. Unregistered providers cannot use that either, whatever their registration group.
The NDIA updates these guidelines from time to time, so the sensible habit is to check the current rules before any badge goes on a page, rather than copying whatever a competitor is displaying. Plenty of provider sites are showing marks they are not entitled to.
What support coordinators look for on an NDIS provider website
Accessibility and compliance get a website to the starting line. They do not win referrals. What wins referrals is answering four questions fast, because a coordinator comparing different providers is doing it quickly and usually on a phone.
- What NDIS supports do you actually deliver? Not “person-centred supports tailored to your goals”. The actual list of services you offer, whether that is support coordination, community access, SIL or therapeutic supports.
- Where do you cover? Suburb by suburb, or at minimum by region. Claiming all of Sydney reads as claiming nothing.
- Do you have capacity right now? The single most common gap on provider websites, and the single easiest to fix. A dated line saying whether you are open to referrals saves everyone a phone call.
- How do I refer someone without ringing you? An enquiry or referral form that works, that a coordinator can complete on behalf of NDIS participants, and that lets them attach a plan or a report.
Most provider sites bury all four somewhere below a stock photo and a paragraph about compassion. The ones that answer them plainly convert far better, and the fix usually costs less than a redesign.
What an NDIS website can and cannot do for your audit
Being straight about this: a website does not pass or fail an audit for you. Audits against the NDIS Practice Standards look at your systems, your records and your practice, and the NDIS Quality and Safeguards Commission is assessing how your organisation actually operates.
Where a website genuinely helps is in presenting clearly, and in one place, the things the practice standards require you to have. Complaints and feedback pathways. Your privacy position. How someone raises a concern, and what happens next. On most disability services sites that material is buried in a PDF nobody opens. Bringing it onto real, readable pages is good practice, and it happens to be exactly what a family checking you out is looking for.
What a website will not do is compensate for gaps in the underlying systems. Anyone selling you a site on the promise that it makes you compliant is selling you something they cannot deliver.
Where to start if your current site is not there yet
In this order, because doing it backwards wastes money:
- Run your homepage and one service page through a free accessibility checker, test the colour contrast, and try navigating both with the keyboard alone. Twenty minutes usually finds the worst of it.
- Add or fix the capacity line and the referral form. This is the change that most often shows up in enquiries from potential clients.
- Make your service list and coverage area specific. This also happens to be the groundwork for any SEO you do later, because specific pages are the ones that rank.
- Then consider the redesign, if you still need one.
An accessible, user-friendly website that answers a coordinator’s questions will out-perform a beautiful one that does neither. Your online presence is usually the first thing a coordinator checks and the last thing most providers fix. For an NDIS provider, that is the whole game.
Julian Mikhael is the founder of MindSite, a Sydney web design studio that has been building and maintaining Australian websites since 2016, including accessible websites for NDIS providers.
