Legal & compliance

Accessibility Statement

Last updated June 30, 2026

neolife is infrastructure that clinical teams rely on every day. It has to work for every one of them — including people who navigate by keyboard, use a screen reader, or need motion turned down. This statement explains where we stand, what we have done, what we are still working on, and how to reach us if something gets in your way.

Our commitment

We build neolife so that clinical and operations staff can send a compounded-prescription order to their pharmacy and track it through fulfillment without fighting the tool. That promise only holds if the tool works for everyone. We treat accessibility as part of the product, not a thing we bolt on at the end.

This statement covers the neolife marketing site at neolife.health and the authenticated application clinics use to capture orders, route them for provider approval, and follow tracking back. Where a third party we depend on falls short — a payment screen, an embedded document viewer, a carrier tracking widget — we say so plainly below and tell you how to get help in the meantime.

The standard we hold ourselves to

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. These are the guidelines published by the World Wide Web Consortium (W3C) and the same baseline referenced by US Section 508 and the European Standard EN 301 549. AA is the level most organizations and regulators treat as the working bar for software like ours.

"Aim to conform" is honest language. Most of our surfaces meet AA today. A few do not yet — those are listed under known limitations. We test against the four WCAG principles: content should be perceivable, operable, understandable, and robust.

What we have done

These are the concrete measures already in place across neolife:

  • Semantic HTML. Pages are built from real headings, lists, landmarks, buttons, and form elements rather than generic containers styled to look like them. This gives assistive technology a structure it can announce and navigate.
  • Full keyboard navigation. Every interactive control — links, buttons, menus, the order-capture forms, the approval action — can be reached and operated without a mouse. Tab order follows the visual order of the page, and we do not trap focus inside components you cannot leave.
  • Visible focus states. The element you are on always shows a clear focus indicator, so keyboard users never lose their place.
  • Color contrast. Body text, headings, and meaningful interface text meet the WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text and interface components). We do not use color alone to carry meaning — status and state are also conveyed with text or icons.
  • Respect for reduced motion. We honor the operating-system prefers-reduced-motion setting. If you have asked your device to reduce motion, our scroll reveals, counters, and transitions are minimized or removed.
  • Text alternatives. Images that carry meaning have descriptive alternative text; images that are purely decorative are hidden from assistive technology so they do not add noise. Icons that act as controls carry accessible labels.
  • Labels and instructions. Form fields have programmatically associated labels, and errors are announced in text — not signaled by color or position alone.
  • Resizable text and responsive layout. Content reflows and stays usable when text is enlarged or the viewport is small, without horizontal scrolling or clipped content.

Assistive technology and browsers

We design and test neolife to work with current versions of the major browsers — Chrome, Safari, Firefox, and Edge — on desktop and mobile. We test core flows with widely used screen readers, including VoiceOver on macOS and iOS and NVDA on Windows.

Accessibility depends on the combination of your browser, operating system, and assistive technology. If you hit a problem on a specific pairing, please tell us which ones you were using when you report it — it helps us reproduce and fix the issue faster.

Known limitations and ongoing work

We would rather be candid than claim perfection. These are areas we know fall short of our target, along with what we are doing about them:

  • Embedded third-party content. Some screens render content we do not fully control — carrier tracking widgets, document and PDF previews, and certain payment fields. These may not meet AA in every respect. We are working with these providers and, where needed, building accessible alternatives. In the meantime, contact us for an alternate way to get the same information.
  • Complex data tables and dense order views. A few order and history views pack a lot of data into a small space. They are usable with assistive technology, but the experience is not yet as smooth as we want. Improving table semantics and on-screen summaries is on our roadmap.
  • Legacy documents. Older attachments and exported records may not be fully tagged for screen readers. We can provide an accessible version of any document on request.

Accessibility work is continuous, not a one-time project. We fold accessibility checks into design review and into our release process, and we prioritize reported barriers alongside other product work.

Report a barrier or request a format

If something on neolife is hard or impossible to use, we want to hear about it — and if you need information in a different format, we will provide it. Email [email protected].

To help us help you quickly, please include what you can of the following:

  • The page or screen where the problem happened (a URL or a short description).
  • What you were trying to do and what went wrong.
  • The browser, operating system, and any assistive technology you were using.
  • The format you would prefer, if you are requesting an accessible version of something.

You do not need to use any special language or cite a guideline. "I could not get past this step with my screen reader" is exactly the kind of report we want.

How quickly we respond

We aim to acknowledge every accessibility report within two business days and to give you a substantive response — a fix, a timeline, or an accessible alternative — within ten business days. Some fixes take longer to ship; when that is the case, we will tell you our plan and offer a workaround so you are not blocked while we work.

How often we review this

We review this statement and reassess neolife against WCAG 2.1 AA at least once a year, and again after any significant change to the product or its design system. The "last updated" date at the top reflects the most recent review. As newer versions of WCAG mature, we will track them and update our target accordingly.

Scope and enforcement

This statement applies to the neolife marketing site and the neolife application operated by neolife. It does not extend to external sites we link to, or to software your clinic or pharmacy runs independently of neolife.

If you have raised an accessibility issue with us and are not satisfied with our response, you may have rights under the laws that apply to you, such as the Americans with Disabilities Act in the United States or the relevant accessibility legislation in your jurisdiction. We would much rather resolve it directly first — please give us the chance to put it right.

Contact

For anything related to accessibility — barriers, format requests, or questions about this statement — email [email protected].

This statement is provided for transparency and may be updated from time to time as the product changes and as we make further progress toward full WCAG 2.1 AA conformance.