A clear NDIS provider website states your services, areas and registration status accurately, works for everyone, and makes enquiring simple.
Key takeaways
- Put your services, service areas and registration status where people can find them quickly, and keep them accurate.
- Build to the Web Content Accessibility Guidelines (WCAG) so the site works with assistive technology, captions and larger text.
- Offer several ways to enquire, and make sure enquiries that arrive after hours are recorded and answered.
- Write in plain language and leave every decision with the participant.
Who is actually reading your website?
More than one kind of reader arrives at your site, often with different questions. A participant may want to know whether your team would be a good fit for them. A parent, partner or carer may be looking on someone’s behalf, with their permission.
Support coordinators are often comparing several providers for a participant at once. They need facts quickly: what you do, where you do it, whether you have capacity and how a referral works.
Plan managers and allied health professionals may also look you up before mentioning you to someone. Writing for all of these readers is simpler than it sounds: lead with facts, keep the language plain and make the next step obvious.
What should you say about your services and areas?
Vague lines such as “we support you with everything” make people work harder to find out whether you can help. Specific, honest detail lets them rule you in or out quickly, which respects their time.
A useful services page covers:
- The supports you provide, described in everyday words, with the formal NDIS support name alongside where that helps coordinators match it to a plan.
- The suburbs, towns or regions you cover, and whether supports happen at home, in the community, at a centre or online.
- Who the service tends to suit, and when another provider may be a better fit.
- Your current availability, including whether you have a waitlist.
- What happens after someone makes contact, from the first conversation to a service agreement.
- Your registration status, stated accurately.
Keep this page current. An out-of-date availability note causes real frustration for someone who has already been waiting for support.
How should you describe your registration status?
Families and coordinators often need to know whether you are a registered provider. Depending on how a participant’s plan is managed, it can affect whether they can use your services.
Say plainly whether you are registered and for which supports. If you are not registered, say that too, and avoid vague phrases that could be read as a registration claim. Registered providers can be looked up on the Commission’s website, so any mismatch is easy to spot.
The rules around registration have been changing, so check the NDIS Quality and Safeguards Commission’s current guidance before you write this section. Review it again whenever your status or the guidance changes.
How accessible does the site need to be?
Your readers include people with disability who use a wide range of assistive technology, so accessibility is core to the job rather than a finishing touch. It should shape NDIS provider website design from the first sketch.
The Web Content Accessibility Guidelines at level AA are a sensible target. In practice that means:
- text that is comfortable to read, with strong colour contrast
- pages that work with a keyboard alone and with screen readers
- meaningful alt text on images that carry information
- captions on videos, and transcripts where they help
- clear headings, descriptive link text, and forms with visible labels and helpful error messages
- no auto-playing media and no time limits that rush people
Consider Easy Read versions of key pages, and information in other languages or Auslan if your community uses them. Automated checkers catch some issues, but testing with people who use assistive technology gives a much truer picture.
How should people be able to get in touch?
People prefer different channels, and some channels are harder for some people to use. Offer a phone number that can be tapped on a mobile, an email address and a short enquiry form, and say whether you take calls through the National Relay Service.
Keep the form brief. Ask only what you need for a first conversation, let people choose how and when they would like to be contacted, and make it easy for a coordinator or family member to enquire on someone’s behalf with their consent. Explain how you will use their information and link to your privacy policy.
Not everyone can get in touch during business hours. Make sure after-hours enquiries are recorded, send an automatic acknowledgement that says honestly when someone will reply, and follow up promptly. This kind of routine work is what business automation is for.
If you do not provide crisis support, say so clearly and point people to emergency services.
Why plain language matters as much as design
Plain language is part of accessibility, and it builds trust. On an NDIS provider website, use short sentences and everyday words, and explain any NDIS terms you need to use.
Avoid language that defines people by a diagnosis or treats them as passive recipients of care. Follow the preferences of the people you support, whether they use person-first or identity-first language.
Keep the tone warm and factual, and let people decide in their own time. Urgency tactics and promises about outcomes have no place here, and misleading claims can breach your obligations. Our guide to becoming findable and trusted covers the wider picture.
What does each reader need to find, and how do you show it?
Participants, families, support coordinators and plan managers each arrive with a different question, so each needs a clear, plain-language answer they can find quickly.
| Reader | What they need to know | How to show it |
|---|---|---|
| Participants | What you offer and where | Plain-language service and area pages |
| Families and carers | Whether you are a good fit and easy to reach | Several contact options, including after hours enquiry capture |
| Support coordinators | Your registration status and availability | Accurate registration details and a simple referral path |
| Plan managers | How you invoice and your business details | Your ABN and invoicing approach, stated plainly |
Where Launch Your Dream fits
Launch Your Dream (LYD) is an AI-integrated business suite built for one industry at a time, by Sharktech Global. For small NDIS providers it brings the website, enquiry handling, follow-up and local search presence together in one system, on the VCPility platform. You decide what you say about your services, and we build and look after the systems behind it.
To see how the pieces fit together, explore LYD Assist, our live demo. If it looks relevant to your organisation, book a discovery call and we can talk about your services, your areas and how enquiries reach you today.
Common questions
- Should an unregistered provider say so on its website?
- Yes. State your registration status plainly and accurately, because depending on how a participant's plan is managed it can affect whether they can use your services. Check the NDIS Quality and Safeguards Commission's current guidance and update the page if your status changes.
- What accessibility standard should a disability support website aim for?
- The Web Content Accessibility Guidelines (WCAG) at level AA are a widely used target. Automated checkers help, but testing with people who use assistive technology gives a truer picture of what works.
- How can a small provider handle enquiries that arrive after hours?
- Make sure every form, email and missed call is recorded, send an honest acknowledgement that says when someone will be in touch, and follow up promptly. If you do not offer crisis support, say so and point people to emergency services.