Pristine Care — NDIS Provider Website (Next.js)

The Brief

Pristine Care is a registered NDIS (National Disability Insurance Scheme) provider based in Melbourne, delivering Positive Behaviour Support, Community Nursing, Supported Independent Living (SIL), and related disability services across Victoria, New South Wales, and the ACT. They needed a website that could do three things at once: load fast, rank for competitive NDIS-related search terms, and genuinely meet the accessibility needs of the people actually visiting it — many of whom are NDIS participants, families, or support coordinators, some with cognitive, visual, or motor impairments.

A Dynamic Next.js Build

I built the site on Next.js using dynamic routing for both the services section and the blog — pages like /services/positive-behaviour-support, /services/community-nursing-care, and individual blog posts are all served through dynamic [slug] routes pulling from a structured content source. This means the site behaves like a real application rather than a fixed set of HTML files: content, services, and blog posts can be added or updated without touching the codebase, and the routing layer resolves and renders each page dynamically. It gave the client a site that's easy to extend — new service categories or blog content just slot into the existing route structure.

Accessibility Was a Core Requirement, Not an Afterthought

Websites built for NDIS participants carry a real accessibility responsibility — this isn't a nice-to-have. I built a custom, client-side accessibility toolbar (no third-party plugin) giving visitors direct control over:

• Text scaling
• Grayscale / high-contrast display mode
• Underlined links for readability
• Dyslexia-friendly font switching

This sits alongside semantic HTML structure and NDIS registration badges in the header and footer, so both users and Google can immediately verify the provider's registered status.

Engineering Details

• Swiper.js lifecycle handling in React: Swiper instances don't clean up automatically across Next.js client-side route transitions — left unmanaged, this causes duplicate sliders and dead event listeners. I wrote a lifecycle wrapper that destroys the active Swiper instance on unmount and reinitializes it cleanly on the next page, so the service and testimonial carousels stay smooth across navigation.
• Viewport-aware stat counters: Built with the native IntersectionObserver API rather than a counter library, so the homepage stats only animate once they're actually visible — lighter bundle, no wasted animation cycles offscreen.
• Mobile content ordering: Used Bootstrap's flex ordering utilities so that on mobile, the actual page content (what a parent, participant, or support coordinator searching for services actually needs to read) renders before secondary navigation elements — better for usability and aligned with how Google's mobile-first indexing evaluates page content.

Results

• Fast, SEO-optimized service pages built around real NDIS search intent (Positive Behaviour Support, SIL, Community Nursing, Respite Care)
• Custom accessibility toolbar meeting practical WCAG-aligned usability standards
• Structured, dynamic routing that lets the client add services and blog content without developer involvement
• Enquiry and referral forms built with proper client-side validation to reduce dropped leads

I write more about the performance side of projects like this on my blog — including a full breakdown of how I approach Core Web Vitals and real-world Vercel Speed Insights scores.

Who This Project Is a Good Fit Example For

If you're an NDIS provider, disability support organisation, allied health practice, or healthcare business looking for a Next.js developer who understands both accessibility requirements and SEO, this project is a solid reference point. I also work on related builds — see my healthcare and clinic website development services and technical SEO services for the kind of work that goes into projects like this one.

Want to see more builds like this? Check out all my projects, or get in touch if you're planning something similar.