Accessibility Statement

We aim to conform to WCAG 2.2 Level AA of the Web Content Accessibility Guidelines, published by the W3C. These guidelines explain how to make web content more accessible for people with a wide range of disabilities — visual, auditory, physical, speech, cognitive, language, learning, and neurological.

We also follow Section 508 of the U.S. Rehabilitation Act and the relevant requirements of the Americans with Disabilities Act (ADA) Title III as applied to commercial websites and healthcare Providers.

• Native semantic HTML, ARIA landmarks, and a skip-to-content link on every page.
• Visible keyboard focus indicators that meet 3:1 contrast.
• Full support for prefers-reduced-motion: autoplaying video, parallax, and non-essential animation are disabled when the operating system requests it.
• Color contrast tested against WCAG AA thresholds for body text, eyebrows, and interactive elements.
• No third-party accessibility overlay. Overlays are not a substitute for native conformance and are increasingly cited as evidence in ADA litigation rather than as a defense.
• A standing internal accessibility dashboard reviewed by our digital team, with every remediation logged and timestamped.

The list below is the live remediation tracker maintained by our internal accessibility working group. Each item links to a WCAG 2.2 success criterion, the scope of the issue, and the planned fix.

• In progress1.4.3 Contrast (Minimum) · AA · Perceivable

  Body copy at text-charcoal/80 on cream may fail 4.5:1

  Site uses charcoal at 70–80% opacity on a cream background. Spot-checked combinations measure ~4.0:1 to ~4.6:1 — borderline against the WCAG 4.5:1 normal-text minimum.

  Scope: All marketing pages — paragraph copy

  Planned fix: Raise default body opacity from /70 → /80 across marketing pages, or darken --charcoal token. Also raise text-cream/80 to /85 minimum.

• In progress1.4.3 Contrast (Minimum) · AA · Perceivable

  Gold link/eyebrow on cream below 4.5:1 at small sizes

  The gold token (#C8A96E or similar) reads ~3.1:1 on cream. Acceptable for >24px display text, borderline-failing for 11–14px eyebrows.

  Scope: Eyebrow labels, gold accent text under 18px

  Planned fix: Darken --gold for small-text usage, restrict gold to ≥18px, or introduce --gold-text token.

• Resolved1.1.1 Non-text Content · A · Perceivable

  Hero/lounge images use alt='' or descriptive alt

  Recently added images set descriptive alt. Decorative images correctly use aria-hidden.

  Scope: Hero, IV Lounge, services pages

  Planned fix: No action. Maintain pattern.

• Open1.2.2 Captions (Prerecorded) · A · Media

  Hero background video has no captions track

  The hero video autoplays without a captions track. Even decorative ambient video should mark itself as such.

  Scope: Home hero — /hero-clinic-opt.mp4

  Planned fix: Mark video aria-hidden=true, confirm silent. If narration added, add captions track. Honor prefers-reduced-motion.

• Open2.3.3 Animation from Interactions · AAA · Perceivable

  fade-up animations and autoplay video ignore prefers-reduced-motion

  Site uses .fade-up entrance animations and a 105% scale on the hero video. No prefers-reduced-motion override exists.

  Scope: Hero animations, fade-up utility, scaling hover effects

  Planned fix: Add global @media (prefers-reduced-motion: reduce) block disabling fade-up, scale, transitions, and pausing autoplay video.

• In progress2.4.7 Focus Visible · AA · Operable

  Custom CTAButton may not show a visible focus ring

  Many gold/cream buttons rely on hover state but the component does not appear to add a high-contrast focus-visible outline.

  Scope: CTAButton across the site

  Planned fix: Add focus-visible:outline focus-visible:outline-2 focus-visible:outline-gold to CTAButton variants.

• Open2.4.1 Bypass Blocks · A · Operable

  No skip-to-content link in __root or TopNav

  Keyboard / screen-reader users have to tab through the entire TopNav on every page navigation.

  Scope: Site-wide layout shell

  Planned fix: Add early skip-to-content link in __root. Add id="main" to each page main.

• In progress1.3.1 Info and Relationships · A · Understandable

  Multiple H1s or skipped levels on long pages

  Long catalog pages can fall into using h2 for every section without a clear hierarchy.

  Scope: /precision-iv-therapy, /services, /hormone-therapy

  Planned fix: Audit each page for exactly one h1, semantic h2/h3/h4 levels. Run pa11y or Lighthouse a11y.

• Resolved3.1.1 Language of Page · A · Understandable

  <html lang> attribute confirmed

  Root sets lang=en.

  Scope: __root.tsx

  Planned fix: No action.

• Resolved3.3.2 Labels or Instructions · A · Forms

  Login form inputs have visible labels

  Login form uses associated label elements.

  Scope: /login

  Planned fix: Maintain pattern.

• In progress3.3.1 / 3.3.3 Error Identification · A / AA · Forms

  Form error states should be announced to assistive tech

  Errors today render as visual text only. Screen readers may not announce on submit failure.

  Scope: /login, future contact/booking forms

  Planned fix: Wrap error region in role=alert aria-live=polite. Set aria-invalid. Use aria-describedby.

• Resolved4.1.2 Name, Role, Value · A · Operable

  FAQ accordion (Radix) ships with correct ARIA

  Radix Accordion provides aria-expanded, aria-controls, role=region.

  Scope: /precision-iv-therapy FAQ + other Radix Accordion uses

  Planned fix: Maintain — keep using shadcn Accordion.

• In progress2.1.2 No Keyboard Trap · A · Operable

  Mobile menu drawer lacks focus trap and Esc-to-close

  When the mobile drawer opens, focus is not moved into it, Esc does not close it.

  Scope: TopNav mobile drawer

  Planned fix: Replace custom drawer with shadcn Sheet, or add focus trap + Esc handler + aria-hidden on rest.

• In progress2.5.8 Target Size (Minimum) · AA (WCAG 2.2) · Operable

  Some inline gold links and microbar items may be under 24px target

  Inline text-only links can fall under the 24x24 minimum.

  Scope: Footer links, gold inline buttons

  Planned fix: Add min-h-[24px] inline-flex items-center, or convert to small pill buttons.

• In progress4.1.2 Name, Role, Value · A · Robust

  Decorative arrows (→) used as link affordance need aria-hidden

  Many CTAs render → inline. Screen readers will announce right arrow.

  Scope: Service cards, CTA arrows

  Planned fix: Sweep components, wrap decorative arrows in span aria-hidden=true.

• In progress1.4.1 Use of Color · A · Perceivable

  Status indicators rely on color alone in compliance dashboard

  Red/yellow/green dots convey state. Color-blind users cannot distinguish without a label.

  Scope: Internal admin dashboards

  Planned fix: Pair every dot with a text label or icon shape.

• Open4.1 Compatible · A · Robust

  Sunset the third-party accessibility overlay

  Third-party accessibility overlays do not bring a non-compliant site into ADA compliance and are routinely cited in ADA lawsuits.

  Scope: Site-wide

  Planned fix: Remove overlay script. Use native semantic HTML, focus-visible, contrast, reduced-motion, and accessibility-statement page.

• Resolved2.4.2 Page Titled · A · Understandable

  Each route sets a unique <title>

  Routes set their own head() titles.

  Scope: All routes via TanStack head()

  Planned fix: Maintain. Audit any new routes.

Despite our best efforts, some content may not yet be fully accessible. We are actively working on:

• Captions and transcripts for older video content.
• Alternative text on a small number of legacy marketing images.
• PDF documents authored before 2025 that have not yet been re-tagged for screen-reader navigation.

If you encounter any other accessibility barrier, please tell us — see Contact & accommodations below.

Our website is evaluated through a combination of automated testing (axe-core), manual keyboard and screen-reader testing (NVDA on Windows, VoiceOver on macOS and iOS), and quarterly reviews by our internal accessibility working group.

Last audited: June 13, 2026

We welcome your feedback. If you experience any difficulty accessing any part of this website, or if you need content in an alternative format or other accommodation to access our services, please contact us:

• Email: accessibility@next-health.com
• Phone: (310) 295-2075
• Mail: Next Health, Attn: Accessibility Coordinator, 8920 Sunset Blvd, West Hollywood, CA 90069

We aim to respond to accessibility inquiries within 5 business days. When you contact us, please describe the page URL, the assistive technology you are using (if any), and the nature of the barrier so we can help you faster.

If you are not satisfied with our response, you may file a complaint with the U.S. Department of Justice, Civil Rights Division, under the Americans with Disabilities Act:
ada.gov/file-a-complaint