Healthcare Website Design: Accessibility That Converts
A healthcare website costs $2,000 to $5,400 for a standard six- to ten-page practice site in 2026, with WCAG accessibility work adding about $900 and online booking about $1,800. The sector-specific truth is different from every other vertical: accessibility is not a differentiator here, it is the baseline. A patient population skews older and more impaired than the general web audience, Ontario's AODA and US accessibility law both point at WCAG 2.2 AA, and a booking flow that excludes a keyboard user is a booking flow that fails both the legal test and the business one.
What follows is how Havenoro scopes healthcare sites: what they cost, which accessibility rules actually bite, and how to design enquiry flows around patient intent instead of marketing convenience.
What a healthcare website costs
Budget $1,964 to $3,287 for a six-page practice site (typical $2,626, three weeks), $3,140 to $5,415 for a ten- to twelve-page multi-provider site, plus feature work at $150 per hour: WCAG accessibility $900, online booking $1,800, patient portal $2,400, advanced intake forms $900. Multi-location groups add pages, not complexity.
These are Havenoro's published estimator figures — the same model behind our cost estimator, using the $400 to $700 per-page band with WordPress. Healthcare projects skew toward the upper half of the page range and the feature-heavy end, because provider directories, service pages per specialty, and booking flows are the product, not the brochure layer.
Accessibility is the conversion feature
The usual accessibility pitch is legal risk avoidance. That is real — AODA in Ontario requires WCAG for organizational websites, and US accessibility litigation has been prolific for a decade — but the stronger argument is commercial. Patients are disproportionately older, stressed, and on whatever device is in their hand. Every accessibility failure is a lost appointment:
- Contrast below 4.5:1 on a service list is unreadable to a meaningful share of your patient base. WCAG 2.2 AA sets the ratio; brand guidelines that pick pretty-but-pale greys do not override it.
- Unlabelled form fields break screen readers and frustrate everyone. A booking form with three unlabelled inputs is a form half your audience cannot finish.
- Keyboard traps and missing focus states strand users who cannot use a mouse. Visible focus styling is cheap to implement and non-negotiable for clinical audiences.
- Touch targets under 24 pixels (the WCAG 2.2 addition) fail precisely the patients with tremor, arthritis, or poor vision — the patients most likely to need care soonest.
- Performance failures compound everything above. A site that takes six seconds to load on a phone in a parking lot is inaccessible de facto; see our Core Web Vitals guide.
For healthcare, accessibility is not a premium line item to upsell. It is the difference between a site that serves the population you exist to treat and one that only serves the healthy and the young.
Privacy and HIPAA-aware design without the mythology
Two conversations get conflated constantly. HIPAA is a US regulation governing protected health information at covered entities and their business associates. AODA and similar frameworks govern accessibility of public-facing services. They are different problems with different fixes.
On the HIPAA side, the honest guidance: a brochure site with a plain contact form that does not solicit clinical information is low-risk territory. The moment you add patient intake, records access, or a portal, you need HIPAA-aware infrastructure — encrypted transmission and storage, signed business associate agreements with every vendor in the chain, access controls, and audit logging. "We use WordPress with a plugin" is not a compliance strategy for PHI. Design accordingly: keep clinical data out of marketing-site forms, route it through systems built for it, and say plainly on the form what will happen to what the patient types.
On the privacy side generally — Canadian PIPEDA, US state privacy laws — every healthcare site needs a real privacy policy describing data handling and retention, cookie consent where required, and analytics configured to avoid collecting health-adjacent signals carelessly. None of this is expensive; all of it is non-optional.
Patient enquiry flows that convert
Patient intent arrives in three modes, and the site should route each differently:
- "I need care now." Give them a phone number and click-to-call at the top of every screen, plus booking if triage allows. Every friction minute here is a patient calling a competitor instead.
- "I'm researching options." Service pages written in plain language — condition, treatment, what to expect, what it costs if you can say — with structured data so search and AI assistants can cite them accurately.
- "I need to verify this practice is legitimate." Provider credentials, licences, location photos, insurance accepted, and real reviews. This is the quiet majority, and the trust signals from the financial services discipline apply almost directly.
The highest-converting pattern we have built for clinics is a short intake form — name, contact method, service needed, preferred time — that creates a booking request without soliciting clinical detail. Four fields. Every additional field measurably reduces completion; clinical questions belong in the intake process after contact, on infrastructure designed for them.
Original data: healthcare scopes at Havenoro
| Scope | Pages | Cost range | Typical | Timeline |
|---|---|---|---|---|
| Single-provider practice | 6 | $1,964–$3,287 | $2,626 | 3 weeks |
| Multi-provider clinic + booking | 10 + 12h booking | $4,940–$7,215 | $6,077 | 4–5 weeks |
| Practice + WCAG + intake forms | 10 + 12h features | $4,940–$7,215 | $6,077 | 4 weeks |
| Health tech / member platform | 8 + portal | $4,952–$6,732 | $5,842 | 6–8 weeks |
Derived from Havenoro's per-page model, WordPress (1.10), client-supplied content. Feature hours at $150/hour: WCAG 6h, booking 12h, multi-step forms 6h, memberships/portal 16h. HIPAA-aware infrastructure scoping is quoted separately for PHI-handling builds.
Notice the typical figures cluster around $5,000 to $6,000 rather than the brochure-site floor: healthcare practices that treat the website as a patient-acquisition surface buy the booking flow and the accessibility work, because both pay back in appointments. The practice that buys the $2,626 brochure and never adds booking is optimizing for the wrong patient journey.
Common mistakes
- Soliciting clinical details in a marketing form. "Describe your symptoms" on a WordPress contact form creates PHI exposure with no infrastructure to justify it. Keep forms logistical; move clinical intake to purpose-built systems.
- Treating accessibility as a post-launch audit. Retrofitting contrast, labels, and focus states after launch costs multiples of building them into the design system. Six hours of feature-scope work during the build is the cheap version; the audit-and-fix version is not.
- Hiding the phone number. Booking flows are wonderful; a significant share of patients — especially older ones — will call. Phone-first visibility is both a conversion feature and an accessibility requirement in practice.
- Skipping structured data on service pages. When patients ask an AI assistant which clinics treat a condition nearby, the answers are assembled from pages with clear service definitions, locations, and provider information. Image-only service pages cannot be cited.
Frequently asked questions
How much does a healthcare website cost?
A professional healthcare or clinic website costs $2,000 to $5,400 in 2026 for a six to ten-page site. Accessibility (WCAG) work adds about six hours ($900), online booking adds twelve hours ($1,800), and patient portals or memberships add sixteen hours ($2,400) at $150 per hour.
What accessibility standard should a healthcare website meet?
WCAG 2.2 Level AA is the practical target in Canada and the US. It covers contrast ratios of at least 4.5:1 for text, keyboard navigability, visible focus states, labelled form fields, 24-pixel minimum touch targets, and no keyboard traps. Ontario's AODA and US ADA litigation both point to this standard.
Does HIPAA apply to my medical practice website?
HIPAA applies to covered entities and their business associates in the US — anything handling protected health information. A brochure site with a plain contact form is low-risk; patient intake, records, and portal functionality require HIPAA-aware infrastructure, signed BAAs with vendors, and encryption in transit and at rest.
Should a clinic offer online booking on the website?
Yes, for appointment types that need no clinical triage. Booking converts the patients who would otherwise call during busy hours or abandon the search. Keep phone booking visible for high-acuity journeys, and never make booking the only path — accessibility includes alternatives.
What pages does a medical practice website need?
Home, Services (one page per treatment or specialty), About with provider credentials, Location with embedded map and transit details, New Patient information, FAQs, and Contact or Book. Ten to fifteen pages is typical. Every provider should have a page with licences, specialties, and accepting-status.
How do patients find healthcare providers online in 2026?
Local search, insurance directory listings, and increasingly AI assistants answering questions like 'accepting new patients near me.' Practices with structured data, consistent name-address-phone, real provider bios, and citable service pages appear in all three channels. Practices without them appear in none.
How long does a healthcare website project take?
Three weeks for a six-page practice site, four to five weeks with booking integration, and six weeks or more for multi-provider groups with credentialing content. The most common delay is content — provider bios and service descriptions that only clinicians can approve.
Related reading
- Core Web Vitals Fail: Causes and Fixes — performance as a patient-access requirement.
- Financial Services Website Design — the trust-signal discipline healthcare shares with regulated finance.
- UI UX Web Design Services — accessible design systems built into the work, not bolted on.
- Website Cost Estimator — price your practice's scope in about a minute.
Building or modernizing a practice site? Let's talk — we build healthcare sites with accessibility and patient flow designed in from the first wireframe.