Accessibility Statement

Our standard

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the same baseline used by US government procurement (Section 508), the Americans with Disabilities Act effective-communication standard, and the European EN 301 549 standard. Healthcare is a regulated industry; our customers expect us to take this seriously.

What we have implemented

Our most recent code-side accessibility audit (2026-05-23) verified the following patterns across the public marketing pages, the demo tool, and the customer dashboard:

• Skip-to-content link

  Every page exposes a keyboard-activated link that jumps focus past the navigation directly into the main content.

• Single <main> landmark per page

  Screen readers can navigate by landmark instead of hearing the header on every page.

• Logical heading hierarchy

  One h1 per page, descending h2 and h3 without level skips.

• Color contrast of 4.5:1 or better

  All body text on the dark interface (background #0a0a0a) was verified against the WCAG 1.4.3 minimum.

• Visible keyboard focus indicators

  Every interactive element shows a visible focus ring. We do not remove the default focus outline without a replacement.

• Form labels and error messages

  Every form input has an associated label, and validation errors are announced via aria-describedby. Honeypot fields used to deter bots are hidden from assistive technology.

• Icon-only buttons carry text labels

  The notification bell, help button, account menu trigger, and similar icon-only controls have aria-label so screen readers announce their purpose.

• aria-current on active navigation

  Screen readers announce which page you are currently on as you move through the primary nav.

• prefers-reduced-motion honored

  If your operating system requests reduced motion, our animations and transitions collapse to near-instant. Vestibular safety is a hard requirement.

• Schema.org SpeakableSpecification

  Blog posts and key landing pages expose a speakable block so voice assistants can identify the most readable summary of each page.

What is still in progress

We are honest about the gaps. The items below are areas where we have not yet completed verification or where work is ongoing.

• Third-party VPAT / ACR conformance audit

  A Voluntary Product Accessibility Template (VPAT) and Accessibility Conformance Report (ACR) are paid audits performed by independent firms. We expect to commission one within the first six months of public availability and will update this page when it is filed.

• Manual screen-reader testing

  Our current audit is code-side. We test against patterns and components; we have not yet completed end-to-end testing with NVDA, JAWS, and VoiceOver against the full customer journey.

• High-magnification and small-viewport testing

  We test mobile responsive design at standard breakpoints. We have not yet exhaustively verified behavior at 400% browser zoom or in the WCAG 1.4.10 reflow case at 320 CSS pixels.

• Windows High Contrast Mode

  Operability under Windows High Contrast Mode has not been verified.

• Captioning and transcripts

  We do not currently publish videos with spoken audio. If we add them, we will provide captions and transcripts.

The Stripe-hosted payment iframe is a third-party component. We selected Stripe in part because their checkout has its own published accessibility commitment, but the iframe's behavior is not within our direct control.

How to report an accessibility issue

If you encounter an accessibility barrier on RegenCompliance, please tell us. Include:

• The page URL where you ran into the problem
• A description of what happened (or did not happen)
• The assistive technology and browser you were using, if you can share it

Email legal@regencompliance.ai with the subject line "Accessibility". We aim to acknowledge within two business days and to either resolve the issue or provide a workaround within thirty days.

Alternative formats and accommodation

If our public website, application, or documentation is not accessible to you in its current form, we will provide the same information in an alternative format (plain-text email, audio, a phone walkthrough) at no charge. Email legal@regencompliance.ai with the subject line "Accommodation" and describe what would work for you.

Formal complaints

If you believe RegenCompliance is not meeting its accessibility obligations and our response above has not resolved the matter, you may file a complaint with the US Department of Justice ADA complaint portal. For European Union users, the relevant national enforcement body listed in your country's transposition of the European Accessibility Act. We would prefer to fix the issue directly; the escalation path is your right.

Updates

This statement is reviewed each time we make a material change to the site's accessibility posture. The "Last reviewed" date at the top of the page reflects the most recent code-side audit. For general product questions unrelated to accessibility, use our contact form.