NDIS Website Design
& Care Plans

Website accessibility for Australian organisations is assessed under the Disability Discrimination Act 1992, which does not name a version. WCAG is the benchmark applied in practice, and the Australian Human Rights Commission’s current guidance points to WCAG 2.2 Level AA as the minimum. The NDIS Practice Standards separately require providers to make information accessible to participants. In plain terms: if your participants cannot use your website, that is a problem well before it is a legal one. We build to WCAG 2.2 AA as standard. For a formal conformance statement or legal advice on your specific obligations you need a specialist, and we will say so rather than guess.

2.2, and it is worth knowing why that matters. WCAG 2.2 became the W3C Recommendation in October 2023, and the Australian Human Rights Commission now points to 2.2 Level AA as the minimum. The versions are backwards compatible, so a site that meets 2.2 also meets 2.1 and 2.0. If your procurement documents still specify 2.1, you are covered either way. Plenty of agencies still quote 2.1 because their process has not caught up.

A set of testable criteria covering whether people with disability can perceive, operate and understand your website. Level AA is the practical benchmark: sufficient colour contrast, full keyboard operation, correct heading structure, form labels screen readers can announce, captions on video, and no content that depends on a single sense to understand. Version 2.2 added criteria that matter a great deal for NDIS audiences: minimum target sizes for people with limited motor control, no task that requires dragging, logins that do not depend on memory or puzzles, help in the same place on every page, and never asking for the same information twice.

No. Overlay tools sit on top of an inaccessible site and have been widely criticised by accessibility advocates and disability organisations. They also do not fix the underlying problem. We fix the site.

Encryption in transit and at rest, data minimisation (we challenge every field), automatic retention rules so submissions do not sit in WordPress forever, and role-based access with an access register. Your site is hosted in Australia. Our team works across Sydney and Kathmandu, access is role-based and covered by written agreements, and we will walk your risk team through exactly who can see what.

A custom NDIS website design is scoped and quoted after a short discovery. Ongoing care starts at $2,500/month for the Care Plan. Month-to-month is always available with 30 days notice, and a 12-month commitment lowers your hourly rate. Most providers are better served by a plan than a project, because accessibility decays and a one-off build has nobody watching it.

Yes. That is a design requirement, not a nice-to-have. We build with the WordPress block editor and locked templates so your team can add services, update capacity or publish news without breaking the layout or the accessibility. Includes a recorded training session.

Yes. Technical SEO is part of every build, and search visibility is part of the Scale Plan. Most NDIS provider websites are structured around the organisation rather than around what a support coordinator searches for. Fixing that structure is usually the single biggest organic gain available.

A template gets you online cheaply and it will almost certainly fail accessibility, because commercial themes are built for looks and breadth rather than semantic markup. If budget is genuinely tight, a template plus a proper accessibility remediation pass is a reasonable path. Just know you are paying twice.

Yes. Aged care, community services, allied health and mental health providers face the same combination of accessibility obligations, sensitive data and non-technical content teams. Same approach applies.

Yes. Enquiry and referral data can flow into the platforms your team already works in rather than sitting in a WordPress inbox nobody owns. We agree the field mapping with you before we build anything, and we configure tracking at the same time so you can see which services and which locations are actually generating contact. Where an off the shelf connector does not exist, our developers build it.

Usually yes, and it is normally the better option. We audit against WCAG 2.2 AA, give you a prioritised remediation list by severity, and work through it. A rebuild is the highest-risk thing you can do to a working website, and most agencies propose one in the first meeting. We only recommend it when the underlying build genuinely cannot get there.