Skip to main content
BioPath
WCAG 2.1 Level AA target

Accessibility Statement

BioPath Hub is built to conform with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Our goal is a platform usable by every life-sciences professional, including users of screen readers, keyboard-only navigation, and assistive technology.

Conformance summary

The platform is partially conformant with WCAG 2.1 AA. Most pages meet all Level A and AA success criteria; we continuously audit and fix new findings as they arise.

  • Semantic HTML and ARIA via Radix UI primitives (Dialog, Menu, Tabs, Combobox, etc.)
  • Keyboard-first design: every action reachable with Tab / Enter / Space / Esc.
  • Color tokens chosen to meet 4.5:1 contrast for body text and 3:1 for large text and UI components.
  • Screen-reader friendly: meaningful labels, live regions for toasts, and skip-to-content link.
  • Responsive reflow down to 320 px without horizontal scrolling.
  • Forms include programmatic labels, error messages with role="alert", and red borders on invalid fields.
Standards we check against
  • 1.1.1
    Non-text content

    All meaningful images carry alt text; decorative images use alt="".

  • 1.3.1
    Info & relationships

    Semantic landmarks (header, main, nav, footer), heading levels, lists.

  • 1.4.3
    Contrast (minimum)

    Foreground/background pairs use design-token colors that meet 4.5:1 (3:1 large text).

  • 1.4.10
    Reflow

    Layouts reflow at 320px; no horizontal scrolling below 1280px CSS px.

  • 1.4.11
    Non-text contrast

    Focus indicators and form borders meet 3:1.

  • 2.1.1
    Keyboard

    All interactive controls reachable via Tab; modal traps focus and returns it on close.

  • 2.1.2
    No keyboard trap

    Esc closes dialogs and popovers everywhere.

  • 2.4.1
    Bypass blocks

    Skip-to-content link at the top of every page.

  • 2.4.3
    Focus order

    DOM order matches visual order; no positive tabindex values.

  • 2.4.4
    Link purpose

    Links describe their destination; icon-only links carry aria-label.

  • 2.4.6
    Headings & labels

    One H1 per page; form labels are programmatic.

  • 2.4.7
    Focus visible

    Every focusable element shows a visible focus ring (ring-2 ring-primary).

  • 2.5.5
    Target size

    Primary tap targets ≥ 44×44 px on mobile (Button default; icon buttons get min-h-11).

  • 3.1.1
    Language of page

    <html lang> set per request locale.

  • 3.2.2
    On input

    Form submission only on explicit Submit; no auto-navigation on field changes.

  • 3.3.1
    Error identification

    Inline validation messages with role=alert and red border.

  • 3.3.3
    Error suggestion

    Mentor application and forms suggest specific corrections.

  • 4.1.2
    Name, role, value

    shadcn/Radix primitives expose correct ARIA roles for dialogs, menus, comboboxes, tabs.

  • 4.1.3
    Status messages

    Toasts use polite live regions; loaders use aria-live.

Known limitations

• Third-party embeds (some video providers, payment SDKs) may not match our accessibility standard; we use them sparingly and provide text alternatives.

• A small number of legacy chart visualizations rely on color alone; we are adding patterns and labels.

• PDF exports inherit accessibility properties from their source documents; user-uploaded PDFs may not be tagged.

How we test

• Automated CI scans with axe-core and Lighthouse on every build.

• Manual keyboard-only and screen-reader (NVDA, VoiceOver) passes before each release.

• Quarterly third-party audit (in progress for institutional B2B procurement readiness).

Report an issue

Found a barrier? Email accessibility@biopathhub.com with the page URL, the assistive technology you use, and what failed. We respond within 5 business days.

Last reviewed: July 2026. References: WCAG 2.1