Skip to content
NinjaMunk

Concept project · WordPress · Accessibility

Kindred Clinic

A self-initiated concept testing whether a clinic booking journey can be genuinely accessible without becoming a second-class alternative flow. Kindred Clinic is an invented company; nothing here is client work and no results are claimed.

Kindred Clinic

Type
Concept project
Industry
Private healthcare and multi-practitioner clinics
Disciplines
WordPress · Accessibility
Year
2025

Overview

A self-initiated concept testing whether a clinic booking journey can be genuinely accessible without becoming a second-class alternative flow. Kindred Clinic is an invented company; nothing here is client work and no results are claimed.

Business challenge

Clinic sites push booking to the phone because online journeys break for anyone with an atypical need — a screen reader, a shaky connection, low confidence with forms — and reception absorbs the cost.

Business goal

Move routine appointment booking off the phone without losing patients who need assistive technology or plain-language guidance.

Research

  • Reviewed clinic booking flows against WCAG 2.2 AA and found date pickers the most common failure.
  • Collected the questions reception answers most: which practitioner, how long, what to bring.
  • Tested plain-language treatment explanations against clinical descriptions for comprehension.

Wireframes

  • Booking sketched as one linear flow with no branching alternative path.
  • Date and time selection prototyped as a native-first control before any custom widget.
  • Error and recovery states drawn for every step, not just the final submission.

Design decisions

Calm, high-contrast interface with large tap targets and no time-pressured interactions, so the design carries reassurance rather than urgency.

  • No countdown timers or held-slot urgency — reassurance outperforms pressure in healthcare.
  • Large tap targets and generous spacing tuned for older and less confident users.
  • Plain-language explainers written alongside clinical terms rather than replacing them.

UX strategy

One booking flow for everyone, verified with keyboard and screen reader at each step, with clear recovery from every error state and no dead ends.

Features

  • Practitioner and treatment matching
  • Accessible date and time selection
  • Plain-language treatment explainers
  • Editor-controlled clinic hours and closures

Technology stack

  • WordPress
  • Custom blocks
  • PHP
  • Playwright

SEO considerations

Treatment pages mapped to symptom-led searches, MedicalBusiness and FAQ schema, location pages with consistent name, address and phone data.

  • Treatment pages written for symptom-led searches rather than clinical taxonomy.
  • MedicalBusiness and FAQ schema with consistent name, address and phone data across locations.
  • Internal links from explainers into the matching booking step with descriptive anchors.

Performance strategy

  • No client-side date library; the picker is progressive enhancement over a native input.
  • Custom WordPress blocks with a strict per-template script and style budget.
  • Images generated in modern formats at build with explicit dimensions to prevent layout shift.

Responsive strategy

  • One-question-per-screen booking on mobile, with progress stated in text as well as visually.
  • Practitioner cards reflow to a single column with the next available slot surfaced first.
  • Content set at a comfortable reading measure with no horizontal scrolling at any width.

Accessibility notes

  • Every step operable by keyboard alone, verified manually against NVDA and VoiceOver.
  • Errors announced in a live region, described in plain language and linked to the field.
  • Motion respects prefers-reduced-motion; nothing essential is conveyed by animation alone.

Expected business outcome

A larger share of appointments booked online, and a booking journey that holds up to an accessibility audit rather than needing a workaround.

Expected, not measured: this is a concept project with no client data behind it.

Next step

Tell us what the
site has to do

Send the goal, the deadline and a budget range. You will get a considered reply within one working day — including an honest answer if we are the wrong studio for it.