Skip to content Skip to sidebar Skip to footer

How to Choose an NDIS Web Designer: 10 Questions to Ask

The right NDIS web designer builds a site that participants, families and support coordinators can actually use. It’s accessible, accurate, easy to find on Google and built to turn visits into enquiries. When the job is done, you own all of it.

Most providers worry about one of two outcomes. Paying for a site that looks professional and produces nothing. Or getting locked in with a designer who controls everything.

These 10 questions test any designer against that standard, including us. Use them to compare quotes side by side. To see how the standard plays out in a real build, start with our NDIS website design page.

How to Choose an NDIS Web Designer: 10 Questions to Ask

A general web designer builds for one kind of visitor. An NDIS provider site has to work for several at once.

Participants want to know what support looks like and whether you can help. Families and carers want to know who your support workers are and whether they can trust you. Support coordinators and plan managers want registration details, service areas and a fast way to refer.

That changes how the site is built. Accessibility can’t be an afterthought when visitors may use screen readers, magnification or keyboard navigation. Accuracy matters because overstating registration groups or services can mislead participants and breach the NDIS Code of Conduct.

Local search matters too, since most enquiries start with a search for a service in a specific area. Enquiry handling has to account for personal and sometimes health information.

You don’t need a designer who builds nothing but NDIS sites. You do need one who understands these audiences and rules, and can show you how they’ve handled them before.

10 Questions to Ask an NDIS Web Designer

Ask every designer the same questions, in the same order. Note their answers in the scorecard further down.

1. Have you built websites for registered NDIS providers? Can I see them?

Why it matters: Experience shows up in the details. Referral forms, registration information and coordinator-friendly service pages are easy to get wrong the first time. Live sites are the only proof that counts.

A good answer: “Yes. Here are live sites we’ve built for providers, what each one needed, and how we handled it.” Expect working links you can click through, not just screenshots. A strong designer explains the decisions behind each site, not just how it looks.

Red flag: Only mockups, or general business sites with “we can adapt this for NDIS.” A designer new to the sector isn’t automatically wrong for you. Weigh it against how well they answer the other nine questions.

You can see how we approach this in our NDIS website portfolio. For a wider look at what separates strong provider sites from weak ones, see these NDIS website examples.

2. How do you build for accessibility, and how do you test it?

Why it matters: If a visitor can’t read your pages, move through the menu or complete your form, you’ve lost the enquiry. The Web Content Accessibility Guidelines (WCAG) are the standard accessible websites that are commonly built and tested against. The Disability Discrimination Act is the relevant Australian law, and the Australian Human Rights Commission has published guidance on accessible websites.

A good answer: They name the WCAG version and level they build to, such as WCAG 2.2 Level AA. They describe testing that combines automated tools with manual checks: keyboard-only navigation, screen reader testing, colour contrast, image descriptions and form labels. They also explain what your team needs to keep doing when adding new content.

Red flag: “Yes, it’s accessible” with no detail. Another warning sign is a plug-in widget presented as the whole solution. Ask how they’d prove the site meets the level they claim.

3. How do you make sure the site is accurate and compliant for an NDIS provider?

Why it matters: Coordinators check your site before they refer. Wrong registration groups, outdated services or claims you can’t back up can mislead participants and fall short of the NDIS Code of Conduct. Allied health providers also have to follow AHPRA advertising rules, including limits on testimonials.

A good answer: They check your registration details and groups against your records before anything goes live. You approve every claim about services, capacity and outcomes. They know the AHPRA testimonial rules if your team includes registered health practitioners. They get written consent before using any participant’s photo or story.

Red flag: “We’ll write something that sounds good.” Copy that promises outcomes, or describes services you aren’t registered for, creates risk for you, not the designer.

For the detail on what this covers, see our guide to NDIS website compliance. None of this is legal advice, so check your own obligations with the NDIS Quality and Safeguards Commission.

4. Who will own the website, its files, content and accounts?

Why it matters: If a designer controls your site or the accounts behind it, leaving them later can be slow, expensive or impossible. Your website is part of how coordinators and families find you. You need control of it.

A good answer: “You own the site, the files, the content, the images and every account, including analytics and your Google Business Profile. We work through the access you grant us, and you can remove it any time.” A strong designer is happy to put this in writing.

Red flag: The designer holds all the logins and won’t hand them over. Watch for a site built on a closed platform you can’t move elsewhere. Vague answers like “don’t worry, we look after all that” are worth pressing on.

5. How will support coordinators and families find what they need quickly?

Why it matters: Coordinators often manage many participants at once. They want registration groups, service areas, availability and a referral pathway within seconds. Families need something different: who you are, how support works and whether they can trust you.

A good answer: The designer talks about structure, not just looks. Expect clear service pages, service area information, a way to show current availability, a short referral form and contact details on every page. They should explain how coordinators and families each get a clear path through the site.

Red flag: The conversation is all colours, fonts and imagery. A site can look polished and still make a coordinator hunt for basic referral information.

Our guide on how support coordinators choose NDIS providers covers what referrers look for. For the full list of pages, see what an NDIS provider website should include.

6. Is the site built to rank on Google for my services and service areas?

Why it matters: A site nobody finds produces nothing. Most searches for NDIS support name a service and a location. Your site needs pages that match those searches.

A good answer: They plan separate pages for your main services and key areas. They handle the technical basics: fast loading, mobile layout, clear headings and clean page structure. They connect the site to your Google Business Profile and are honest that rankings take time to build.

Red flag: Any guarantee of first-page or number-one rankings. Nobody controls Google’s results. Be equally wary of “SEO included” with no explanation of what that means.

Building a site that ranks is the starting point. Ongoing work is covered in our guide to SEO for NDIS providers.

7. How do enquiry forms work, and how is participant information kept secure?

Why it matters: Enquiry and referral forms can collect personal and health information. You need to know where it goes, who can see it and how long it’s kept. Many NDIS providers have obligations under Australian privacy law regardless of their size, so check yours with the Office of the Australian Information Commissioner.

A good answer: The site uses a secure connection (HTTPS). Forms ask only for what you need to respond. Submissions go to an inbox or system you control, with spam protection and a privacy policy link beside the form. They can explain whether form data is also stored on the website and for how long.

Red flag: “It just emails you” with no answer on storage or access. Forms that ask for diagnosis details upfront collect more sensitive information than an initial enquiry needs.

8. Who writes the content, and who checks it?

Why it matters: The words on your site decide whether a coordinator refers or a family calls. Designers who drop in placeholder text leave you writing everything at the last minute.

A good answer: They’re clear about who writes each page and who reviews it. The writer understands NDIS terms and uses respectful, person-centred language. You approve every page before launch, and they get consent for any participant photo or story.

Red flag: “Just send us your content” with no help or guidance. Copy lifted from other providers’ sites is another one. It hurts your search rankings and tells coordinators nothing about you.

9. What’s included in the price, and what will it cost after launch?

Why it matters: Quotes vary for good and bad reasons. You can only compare them fairly when you know what each one includes.

A good answer: An itemised scope. It should list the number of pages, content writing, accessibility testing, search setup, forms, training and post-launch support. Ongoing costs should be listed upfront: software licences, updates, maintenance and support. A good designer explains which factors drive the price, so you can see where the money goes.

Red flag: A low headline price with everything else charged as extras. Watch for a vague monthly fee with no defined scope. Long lock-in contracts with heavy exit costs deserve a second look.

10. What happens after launch, and how will we know the site is working?

Why it matters: Launch is the start, not the finish. Software needs updates, your availability changes, and you need to know whether enquiries are coming in.

A good answer: Enquiry tracking is set up from day one, covering form submissions, referral forms and calls from the site. You get a simple report showing enquiries by source, not just visitor numbers. Support terms are clear, and your team is trained to update availability and news.

Red flag: “Once it’s live, you’re on your own.” Equally weak is a monthly report showing traffic and nothing about enquiries or referrals.

Red Flags When You Hire an NDIS Website Designer

Any one of these is worth a follow-up question. Two or three together is a reason to keep looking.

  • No NDIS work to show. Without live provider sites, you can’t judge how they handle referrals, registration information or accessibility.
  • A vague answer on accessibility. If they can’t name a standard or a testing method, accessibility probably isn’t being tested.
  • The designer keeps control of your site or accounts. You should own every account and file, with access you can grant and remove.
  • A template with your logo swapped in, sold as custom. Templates can work well when that’s what you’re paying for. Read our comparison of NDIS website template vs custom to know what you’re buying.
  • No plan for tracking enquiries. Without tracking, nobody can tell whether the site is working.
  • Guaranteed rankings. No one can guarantee a position on Google. Treat any promise like this as a warning.
  • Copy that overstates services or registration. It may read well, but it creates compliance risk and damages trust with coordinators.

A Simple Scorecard to Compare NDIS Web Designers

Use this table in your calls. Note each designer’s answer in their column, then compare them row by row.

Question

What a strong answer includes

1. NDIS experience

Live provider sites and the decisions behind them

2. Accessibility

Named WCAG version and level, manual and automated testing

3. Accuracy and compliance

Registration checks, your approval of claims, consent process

4. Ownership

You own the site, files, content and every account

5. Coordinator and family paths

Service pages, service areas, availability, short referral form

6. Google rankings

Service and area pages, technical basics, no guarantees

7. Forms and privacy

Secure connection, minimal fields, data goes to a system you control

8. Content

Clear writer and reviewer, NDIS language, your sign-off

9. Price

Itemised scope, ongoing costs listed upfront

10. After launch

Enquiry tracking, clear support terms, team training

 

FAQ

1. What should I look for in an NDIS web designer?

Look for live NDIS provider sites you can test, a clear accessibility standard and testing method, and full ownership of your site and accounts. They should check registration details for accuracy, build pages for your services and areas, secure your enquiry forms, and track enquiries after launch. Use the 10 questions in this guide to compare designers on the same terms.

2. Does my NDIS website need to be accessible?

Yes, in practice. Many visitors to provider sites have disability, and an inaccessible site loses enquiries. The Disability Discrimination Act makes disability discrimination unlawful, and the Australian Human Rights Commission has published guidance on accessible websites. WCAG is the standard sites are commonly built and tested against. Ask your designer which version and level they build to and how they test it.

3. Should I hire a freelancer or an agency for my NDIS website?

Either can work. A freelancer may cost less and give you direct contact, but check their capacity for testing, content and ongoing support. An agency usually covers more skills under one roof, but check who actually does the work. In both cases, ask the same 10 questions and judge the answers, not the business size.

4. Do I need a local NDIS web designer in my city?

No. Most website work happens through video calls, shared documents and email, so experience matters more than location. BuzzPilot is based in Perth and works with providers there through NDIS website design in Perth. We also work with Melbourne providers remotely from Perth through NDIS website design in Melbourne. What matters is that your designer understands your local search market.

5. Can NDIS funding be used to pay for a provider website?

No. NDIS participant funding pays for supports for participants. It can’t be used to pay for a provider’s website, advertising or other business costs. Your website is a business expense your organisation funds directly. Speak to your accountant about how it’s treated for tax purposes.

6. How long does it take to build an NDIS provider website?

It depends on scope. The number of pages, who writes the content, how quickly your team reviews drafts, and any integrations with booking or client management systems all affect the timeline. Ask each designer for a written timeline based on your actual scope, including the review stages that depend on you.

Talk to a NDIS Web Designer Who Builds for Enquiries

BuzzPilot is based in Perth and builds websites for NDIS providers across Australia, working remotely outside WA.

See how we approach NDIS website design in Perth or read the Hope Disability Services case study. For the full scope of what we build, see our NDIS website design services.
Start with a free audit. It's also a chance to ask us every question on this list. Call 0470 249 058

Leave a comment