← Blog/Industry··10 min read

NDIS Provider Websites: Trust, Clarity, Compliance

An NDIS provider website serves two audiences. What participants need, what support coordinators check in ninety seconds, and why accessibility decides it.

G
Written by
Graham Sissons · Founder, Pryce Digital

A support coordinator with a participant's plan open and four referrals to place gives your website about ninety seconds. They are not reading your values statement. They want four things: which supports you deliver, which postcodes you cover, whether you're registered, and whether you have capacity before Christmas. Most NDIS provider websites answer none of those in the first screen, and two of them nowhere at all.

Our position is that an NDIS provider site should be built as a referral document first and a marketing site second. Plenty of providers will push back on that, because the sector's design convention runs the other way — soft photography, a paragraph about being person-centred, a values grid, a contact form at the bottom. That site reads fine and refers nobody, because the person doing the referring gave up on the third scroll.

The complication is the second audience. Participants and families arrive with different questions and far less tolerance for jargon. A site that speaks only to coordinators reads cold to a parent researching supports at eleven at night; a site that speaks only to families gets skipped by the professional who controls the referral. Both have to be served by the same site, and the way you do that is structure, not tone.

The two audiences, and only one of them is shopping

Support coordinators are repeat buyers. They place referrals every week, keep a mental list of providers who answer the phone, and are ruthless about time because their own hours are funded and finite. What they want from your website is a fast, unambiguous yes or no. Anything that makes them work for it costs you a place on the shortlist, and they will not tell you why.

Participants and families are once-in-a-plan buyers. They are usually anxious, often new to the scheme, and reading on a phone after a long day. They want to know what happens next, whether you'll actually turn up, and whether they can talk to a person first. Boilerplate reads as evasion to that audience, because they've already been through two intake processes that went nowhere.

The structural answer is two signposted paths from the homepage — one for participants and families, one for referrers — leading to genuinely different pages, not the same content under different headings. The coordinator path can be dense and stripped of warmth. The participant path can be slow, plain and reassuring. Neither compromises for the other, which is the point of splitting them.

Registered or not, say it in the first screen

This is the most common failure on NDIS provider sites, and it costs unregistered providers enquiries and registered providers credibility.

Registration status is not a marketing detail. It's a hard filter. Participants whose plans are agency-managed can only use registered providers, so if you're unregistered and don't say so, you'll collect enquiries you cannot convert and waste the time of people who have little to spare. If you are registered, you're carrying the cost of audits and the NDIS Quality and Safeguards Commission's practice standards, and burying that on an About page throws away a credential competitors can't copy overnight.

Say it plainly, near the top, in the words the sector uses. Registered providers should state the registration groups they hold, because "registered" alone doesn't tell a coordinator whether you can deliver the specific support in the plan. Unregistered providers should state it just as plainly and qualify it immediately: which management types you work with, and what you do instead of registration to evidence quality — worker screening, insurance, supervision, training records.

The instinct is to soften this. Don't. The provider who says "we are not registered, so we work with self-managed and plan-managed participants" reads as competent and honest. The provider who leaves it out reads as hiding something, and the coordinator assumes the worse of the two possibilities. Registration requirements in the scheme have been under review for some time, so keep the claim in one editable place rather than baked into an image or a hard-coded footer.

Accessibility is the credibility test, not the compliance chore

Every Australian business has an obligation here — the plain-English version of what the Disability Discrimination Act means for websites applies to everyone. For a disability services provider it stops being a legal question and becomes a product demonstration.

Think about what a failure communicates. A participant using a screen reader hits your enquiry form and can't tell which field is which, because the labels are placeholder text that vanishes on focus. A person with low vision zooms to 200% and your navigation collapses into an unusable pile. In any other industry that's a bug. In this one, the visitor has just learned something concrete about how well you understand the people you're paid to support, and no amount of inclusive language further down the page undoes it.

The standard to build to is WCAG 2.2 Level AA, maintained by the W3C's Web Accessibility Initiative — our plain-English WCAG AA checklist covers the practical side. Conformance is unglamorous work: proper heading order, visible focus states, contrast that survives your brand colours, forms with persistent labels and errors announced in text, captions on video, and keyboard access to everything a mouse can reach.

What it is not is an overlay widget. The accessibility toolbars sold on monthly subscription do not deliver conformance and are actively disliked by many screen reader users — we've covered why they aren't a fix. An NDIS provider running one instead of an accessible build is making a statement about its priorities to exactly the audience most likely to recognise it.

Test with people, not only with tools

Automated scanners catch a useful fraction of issues and miss most of the ones that matter — whether the reading order makes sense, whether error messages are comprehensible, whether a form can be completed under real conditions. If you deliver supports to people who use assistive technology, you already have access to testers most agencies go looking for. Paying participants properly for that time is good practice and the fastest route to a site that works.

Plain language is part of the service

The scheme runs on acronyms and provider websites absorb them without noticing. A homepage opening with capacity building, core supports, SIL, SDA and plan management in the first hundred words is written for people who already work in the sector.

Write for a reader who has had a plan for three weeks. Say what the support is in ordinary words, then name the funding category in brackets for the coordinator. "Help at home with cooking, cleaning and getting to appointments" first; "core supports, assistance with daily life" second. Both audiences served, neither patronised.

Easy Read is worth doing properly if your participant base includes people with intellectual disability. It's an established format, not just shorter sentences — one idea at a time, supporting images, generous spacing — and an Easy Read version of your service information and service agreement says more about your practice than any values statement. Publish it as an accessible page as well as a download; a PDF on a phone is its own accessibility problem.

The capacity question nobody answers

Here is what coordinators complain about constantly and almost no provider site answers: whether you are taking referrals right now.

A coordinator ringing six providers to find one with a vacancy is burning funded hours on your behalf. A site that says "accepting referrals for support work in the western suburbs, roughly three weeks for weekday supports, updated 18 August" earns a call ahead of every competitor with a contact form. It costs a fortnightly edit and it is the highest-value content on an NDIS provider site.

The same goes for coverage. "Melbourne and surrounds" is not a service area — it's a way of avoiding a commitment. List the actual suburbs or local government areas, and say so if travel time changes what you can offer. If you run distinct teams in distinct regions, give each one a page with its own contact, coverage and capacity detail.

Trust signals that survive scrutiny

Not every proof point carries the same weight here. Ranked by what a referrer or a family responds to:

STATUS
Registration and the groups you hold
In the first screen, in sector language, with the management types you work with. The fastest filter either audience applies, and the one most sites make people hunt for.
WORKERS
Screening, training and supervision
Screening clearances, first aid, the supervision structure behind the team. Say what you require of every worker rather than calling them passionate. Families are deciding who comes into their home.
PEOPLE
Named staff with real photographs
The intake coordinator, the team leads, the person who answers the phone. Stock photography of a wheelchair at a sunset does the opposite of its job, and everyone in this sector spots it instantly.
PROCESS
What happens after the enquiry
Who calls back, how fast, what the intake meeting covers, when supports start. Anxiety about the unknown kills more enquiries than price does.
RECOURSE
Feedback and complaints, in the open
Your complaints process, and the participant's right to go to the NDIS Commission instead. Publishing it reads as confidence. Hiding it reads as the reverse.

One caution on testimonials. For disability support services they're fine with informed, revocable consent, and they're persuasive. But if you also deliver allied health under registered professions — physiotherapy, occupational therapy, psychology — the national advertising rules administered by AHPRA prohibit testimonials about those services, and the prohibition follows the service, not the business structure. Speech pathology sits outside the national registration scheme, which is exactly the sort of distinction that makes a blanket "collect reviews" policy dangerous for a mixed team.

FAQ

Do NDIS providers have to say whether they are registered?

No rule forces a website to display it, but leaving it out works against you either way. Participants with agency-managed plans can only use registered providers, so an unregistered provider who stays quiet collects enquiries that can't convert, and a registered provider who stays quiet wastes their strongest credential. State it near the top with the plan management types you work with, and check current requirements against the NDIS Quality and Safeguards Commission rather than assuming.

Does an NDIS provider website legally have to be accessible?

The Disability Discrimination Act 1992 applies to goods and services provided online, and websites are covered. The benchmark used across Australian government and industry is WCAG 2.2 Level AA. For a disability services provider the legal position is almost beside the point — an inaccessible site demonstrates the opposite of what you're selling, to the audience most likely to notice.

Can NDIS providers use participant testimonials on their website?

For disability support services, yes, with informed consent that can be withdrawn and real care around identifying details. The exception matters: where you deliver a health service under a profession registered with AHPRA, such as physiotherapy, occupational therapy or psychology, testimonials about that service are prohibited by the national advertising rules. If you deliver both, separate the pages and keep the regulated services clean.

How much does an NDIS provider website cost in Australia?

A template site on a builder platform is cheap to stand up, and for a sole-trader support worker that may be enough. A custom build starts at $8,000 AUD with us, and that buys an accessible front end tested beyond automated scanners, the two-audience structure, editable capacity and coverage information, and forms that work under assistive technology. The cheap version usually fails the accessibility test, which here is the expensive kind of saving.

Where to start this week

You don't need a rebuild to fix the biggest gaps. Put your registration status and the management types you accept in the first screen. Add a dated capacity line and edit it fortnightly. Replace "Melbourne and surrounds" with a real list of suburbs or LGAs. Write the "what happens after you enquire" section almost every provider site is missing.

Then test the enquiry form with a keyboard only — tab key alone, top of the page to the submit button. If you can't complete it, neither can a portion of your participants, and that's the fix to fund before anything cosmetic. Our free instant site audit gives you the technical baseline in a couple of minutes, though it won't judge whether your reading order makes sense to a screen reader; that part needs people.

If the two-audience structure is the problem rather than the copy, that's a build question, and the kind of thing our small business website development work is shaped around. Book twenty minutes and bring your referral sources — where they come from now, and where they stall. Usually the site isn't underperforming because it looks dated. It's underperforming because it never answered the four questions in the first ninety seconds.

END OF POST

Want this for your business?

Get a free instant audit of your current site, or book a 20-minute call to talk through what you're building. No sales pitch.

Free auditBook a call
Or email studio@prycedigital.com
Keep reading
Wedding Venue Websites: Winning the ShortlistIndustryVet Clinic Website Design: The 11pm TestIndustryThe State of Adelaide Small Business Websites 2026Industry
Explore our services
Custom Web Design Melbourne — hand-coded sites built from scratchWebsite Development for Small Business — the full breakdownWeb Design Melbourne — why local matters
← Back to blog indexFree audit