Web design for NDIS providers
Your website is read by participants and their families, and by the support coordinators and plan managers deciding who to shortlist. It has to be accessible in practice, plain to read, and clear about what you deliver, where you deliver it, and how someone gets started.
NDIS Code of Conduct
The Code binds registered and unregistered providers alike, so the wording, claims and imagery on the site have to be honest and respectful.
Complaints Management and Resolution Rules
Information on how to complain, to you and to the NDIS Commission, has to be public and accessible, which puts it on the site.
NDIS logo guidelines
The heart logo and 'Registered Provider' tagline rest on NDIA permission and registration status, which shapes the badges the site carries.
What NDIS providers need from a website
-
Accessibility that stands up to real use
Your readers include people using screen readers, keyboard-only navigation, screen magnification and switch access, and a template with an accessibility widget bolted on top does not hold up to any of them. WCAG 2.2 Level AA is the benchmark most Australian organisations work to, and anti-discrimination law here applies to services offered online.
-
Plain language and Easy Read
The NDIS Practice Standards expect information about your supports and how to access them to be given in the language, mode of communication and terms a participant is most likely to understand. That is a different job from the sector language used in tenders and audits, and it usually means Easy Read versions sitting alongside the main pages rather than replacing them.
-
Two readers, one set of pages
A participant or family member wants to know whether you can help, what it is like, and who to talk to. A support coordinator wants supports, service areas, capacity and accepted plan-management types inside a minute, and the site has to serve both without burying either.
What we build for NDIS providers
Accessible custom WordPress theme
A theme hand-coded to WCAG 2.2 Level AA, with visible focus states, sensible heading order, colour contrast, labelled form fields and no meaning carried by colour alone, rather than a page builder with an overlay on top.
Service pages by support type
A page for each support you deliver, written in the participant's terms, covering who it is for, which areas you cover and what happens after someone gets in touch.
Referral and enquiry forms
Custom forms for participants, families and support coordinators that capture supports needed, plan-management type, location and preferred contact method, hosted in Australia and routed to the right inbox.
Easy Read document library
A tidy, searchable place for Easy Read versions, service agreements, policies and your feedback and complaints information, so nobody has to ask for them.
Careers and recruitment pages
Support worker roles, position descriptions, screening requirements and application forms on your own site, so recruitment is not left entirely to job boards.
Ongoing care after launch
Updates, backups, monitoring, security patching and small content changes, so service areas, supports and policy documents stay current between audits.
Common questions
Does our website have to meet WCAG?
The NDIS Practice Standards do not name a technical web standard, but they do expect information to be given in a way each participant can understand, and Australian anti-discrimination law applies to services offered online. WCAG 2.2 Level AA is the benchmark most Australian organisations and government bodies work to, so that is what we build to. Automated checkers only catch part of it, so testing with people who actually use assistive technology is worth the time.
Can we say we are a registered NDIS provider?
Only if you are registered with the NDIS Quality and Safeguards Commission, as that wording is restricted, and the NDIS logo cannot be used without written consent from the NDIA. The ACCC has also put NDIS providers on notice about misleading advertising, so we keep the claims on your site to plain statements you can evidence. If you are not registered, the site can still say clearly that you work with self-managed and plan-managed participants.
How do support coordinators use our site?
Mostly to shortlist quickly: what supports you deliver, which areas you cover, whether you have capacity, and whether you accept the participant's plan-management type. We put that where it can be scanned rather than buried in an about page, and pair it with a referral form that collects what your intake team needs in one sitting. That saves the back-and-forth phone calls that usually follow a vague enquiry.