What an NDIS Provider Website Needs: A Plain-English Guide

Before a participant, a family member or a support coordinator calls you, they usually look at your website. If they can't quickly tell what you do, where you work and how to refer someone, they move on to the next provider.

This guide is for owners of NDIS businesses, registered or not. It covers what to put on your website, the NDIS rules on names and logos, how to make the site work for people with disability, and how to keep referral details private. You don't need any technical knowledge to follow it.

The short version

• Say what supports you offer, in everyday words.
• List the suburbs and areas you cover.
• Say whether you are a registered NDIS provider and which plan types you accept.
• Make it easy to call, email or send a referral.
• Build the site so people with disability can use it. The standard to aim for is WCAG 2.2 level AA.
• Keep NDIS out of your business name and web address, and don't use the NDIS logo.
• Treat referral details as private health information.

Who reads your website

Most NDIS provider websites have three kinds of reader.

Participants want to know if you can help them, whether you work in their area and whether you have staff available. Some use a screen reader, a keyboard instead of a mouse, or larger text.

Family members and carers often do the research for someone else, usually on a phone. They want to know who will come into the home, how you choose your workers and what happens if a worker is sick.

Support coordinators and plan managers often compare several providers for one person. They look for your service areas, how long people wait to start, how to send a referral and whether you are registered.

A good website answers all three on the first page they land on, without making them call to find out.

What to put on the website

Your supports, in everyday words

The NDIS uses formal names for its support categories, such as Assistance with Daily Life. People don't usually search that way. They search for things like support worker, community access, respite or help at home.

Use the everyday words for your headings, then mention the NDIS category name underneath. That way participants find you on Google, and coordinators can see how your service fits a plan.

Where you work

List the suburbs and regions you cover, such as Logan, Ipswich or the Redlands. Use the same areas in your Google Business Profile, which is what shows up in Google Maps and local searches.

Registration and plan types

Say clearly whether you are registered with the NDIS Quality and Safeguards Commission. It matters to the people reading:

• Participants whose plans are managed by the NDIA can only use registered providers.
• Self-managed and plan-managed participants can usually use registered or unregistered providers.
• Some supports need a registered provider whatever the plan type. Since 1 July 2026, providers of supported independent living and NDIS digital platforms have needed to be registered, with a short transition for those already operating. The Government has funded mandatory registration for all high-risk supports from 1 July 2027.

Source: the NDIS Commission's page on mandatory registration.

If you are registered, coordinators can check you on the NDIS Commission's provider register, which they can search by business name or ABN. Put your legal business name and ABN in the footer of your site so they can match you quickly.

How to get in touch or make a referral

Put your phone number at the top of every page, so people on a phone can tap it to call. Add an email address, and a referral form for coordinators and families.

A good referral form is short. It usually asks for:

• the name and contact details of the person filling it in
• the participant's first name and suburb
• the supports they want and roughly how many hours
• how their plan is managed
• the best time to call

Ask for anything more, such as NDIS numbers or detailed support needs, after you've spoken. Then say on the page what happens next, for example "We'll call you within one business day", and stick to it.

How you charge

Families and plan managers want to know what a service will cost. Say how you charge, such as by the hour, and whether your rates stay within the NDIS price limits. If you charge for travel or late cancellations, say how.

Your team

Families want to see who might come into their home, so use real photos of your team rather than stock photos. Two cautions:

• Get written consent before you use a photo or story of a participant, and make it easy for them to change their mind later.
• If your team includes Ahpra-registered practitioners, such as occupational therapists, physiotherapists or psychologists, Ahpra's advertising rules ban testimonials about clinical care, and your website counts as advertising. Comments about things like customer service are fine.

The NDIS rules on names, logos and claims

The NDIA owns the NDIS name and logo as trade marks, and its logo guidelines set rules for providers. In short:

• Don't put NDIS in your business name, trading name or web address. The NDIA treats this as a misleading claim of a connection to the scheme.
• Don't use the main NDIS logo on your website.
• Only registered providers can call themselves a registered provider, or use the 'I heart NDIS' and 'We heart NDIS' logos with the 'Registered Provider' tagline.
• Don't say your service is NDIS approved or 100% NDIS funded. The NDIA doesn't approve providers or products.

You can still use NDIS to describe what you do, such as "support work for NDIS participants in Logan". That helps people find you on Google and is allowed, as long as it doesn't suggest you are part of the NDIS.

If your current web address includes NDIS, it can be changed. Moving to a new address doesn't mean starting again on Google, as long as each old page redirects to the matching new one.

Making the site accessible

Many of the people reading an NDIS provider's website have a disability. If they can't use your site, you lose them, and you risk a discrimination complaint.

The Disability Discrimination Act covers websites. In 2000, a blind man, Bruce Maguire, won a complaint against the organisers of the Sydney Olympics because their website couldn't be read with a screen reader. The Australian Human Rights Commission has long pointed to the Web Content Accessibility Guidelines, known as WCAG, as the benchmark. The current version is WCAG 2.2, and level AA is the usual target.

In everyday terms, an accessible website means:

• Text has strong contrast with its background.
• Text can be made twice as large without the page breaking.
• Every link, button and form works with a keyboard alone.
• Pages work with screen readers, the software blind and low-vision people use to hear a page read aloud. That needs headings in order, a short description on each image, and links that make sense on their own, such as "Make a referral" rather than "Click here".
• Videos have captions.
• Forms have clear labels, and error messages say what to fix.
• Nothing moves, flashes or times out without a way to stop it.
• Words are plain, and Easy Read versions of key information are easy to find if you have them.

One warning. Some web companies sell accessibility toolbars or plugins that add buttons for bigger text or different colours. These don't fix the problems in the site underneath. A screen reader user still gets stuck on the same broken form.

Check your own site in a few minutes

You can spot the biggest problems yourself:

1. Put your mouse away and use only the Tab and Enter keys. Can you reach your phone number and send the referral form?
2. Zoom your browser to 200%. Is all the text still there, with nothing cut off or overlapping?
3. Turn on the screen reader on your phone. It's called VoiceOver on an iPhone and TalkBack on Android. Now try to find your phone number.
4. Run your home page through WAVE, a free checker from WebAIM. It flags common problems such as missing image descriptions and low contrast.

If any of these fail, people with disability are hitting the same wall.

Keep referral details private

Referral forms collect sensitive details. Under the Privacy Act, information about a person's health or disability is health information, a kind of sensitive information with extra protections.

Some small businesses are exempt from the Privacy Act, but not businesses that provide a health service and hold health information. The OAIC's guidance includes care for people with disability in that group. So if your forms collect disability or health details, plan on the Privacy Act applying to you.

In practice:

• Only ask for what you need on the first form. You can collect the rest once you've spoken.
• Think about where form details end up. A basic website form emails them to an inbox, where they can sit for years and be forwarded by mistake. For forms that collect NDIS numbers or support needs, it's safer to save them in a secure system, ideally hosted in Australia, that only the right staff can open.
• Publish a privacy policy that says what you collect, why, and who can see it. If the Privacy Act applies to you, you need one anyway, and your website is the place for it.
• If you are registered, you are also audited against the NDIS Practice Standards, which cover how participant information is managed.

What an NDIS provider website costs

Prices vary a lot between designers. For typical Brisbane prices, see our website cost guide.

Our prices are fixed:

• Launch: a one-page website for $799, plus $30 a month for hosting and care, with no lock-in.
• Growth: up to 5 pages from $2,500.
• Referral forms that store details securely, or send them into software such as ShiftCare, Brevity or Lumary where it allows, get a fixed quote once we know what you need.

Every NDIS website we build is made to WCAG 2.2 level AA and tested with a keyboard and a screen reader before it goes live. See websites for NDIS providers for what's included.

Next step

If you'd like a second opinion on your current website, or you're starting a new one, book a free 30-minute chat. Tell us what supports you offer and who usually refers people to you, and we'll tell you what your website needs.