1. Our commitment
Development teams include people with a wide range of abilities, and the decisions Bayes Pharma.ai supports are too important to be gated by an inaccessible interface. We aim to design, build, and maintain BayesPharma Innovator, Bayes Pharma Generics.ai, and Bayes Pharma Clinical.ai in line with recognized accessibility standards, and to keep improving as we add new workspaces.
2. Conformance target
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). This statement describes our current conformance status as a good-faith self-assessment; it is not a certification by an independent auditor.
3. Measures we've taken
- Keyboard access: primary navigation, the workspace search palette (accessible via a keyboard shortcut), mega-menu dropdowns, the interactive product-preview tabs, and modal dialogs are operable without a mouse, with visible focus indicators.
- Skip navigation: a "skip to main content" link is provided at the top of each page for keyboard and screen-reader users.
- Semantic structure: pages use landmark elements (navigation, main, footer), heading hierarchy, and ARIA attributes (such as
aria-expanded,aria-controls, androle="tablist"/role="tabpanel") on interactive components like the product tour and mega-menus. - Color & contrast: our design system targets readable contrast ratios for body text and interactive states in both light and dark themes, and status/priority information is paired with text or icons rather than color alone in most workspace views.
- Reduced motion: pages honor the operating-system
prefers-reduced-motionsetting, disabling scroll-reveal animation, hover transforms, and decorative motion for users who request it. - Responsive & zoom-friendly layout: layouts reflow for small screens and support browser zoom without loss of content or functionality.
- Descriptive labeling: interactive controls include accessible names (for example,
aria-labelon icon-only buttons) and form fields are associated with visible labels.
4. Known limitations
Some data-dense workspaces (for example, complex modeling dashboards, charts, and large evidence tables) are still being reviewed for full screen-reader and keyboard-navigation parity with their visual presentation. Some third-party embedded content or file exports (such as generated PDF or PowerPoint reports) may not yet fully meet the same accessibility standard as the core web application. We are actively working through these areas and prioritize fixes based on user-reported impact.
5. Feedback & contact
If you encounter an accessibility barrier using any Bayes Pharma.ai product, please let us know the page, the workspace, and the assistive technology or browser you were using — this helps us reproduce and fix the issue quickly.
6. Technical specifications
Accessibility of Bayes Pharma.ai products relies on the following technologies working together in your browser:
| Technology | Role |
|---|---|
| HTML | Semantic structure and landmarks |
| CSS | Visual presentation, including light/dark themes and reduced-motion support |
| JavaScript | Interactive components such as navigation, search, and the product tour |
| WAI-ARIA | Additional semantics for custom interactive components |
These technologies are relied upon for conformance with the accessibility standards referenced above. Accessibility of content outside our control (such as third-party embedded services) is not covered by this statement.