Accessibility statement

Last reviewed 2026-10-17. kwiKBio Inc. is a subsidiary of HydroJoule LLC. The Service is in beta.

1. Our goal

We want everyone to be able to use kwiKBio, including people who use a screen reader, a keyboard only, magnification, voice control or reduced motion. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.

2. Current status

We believe kwiKBio partially conforms to WCAG 2.2 AA: most of the site meets it, and the exceptions are listed in section 4. We have not yet had an independent audit or a full manual review with assistive technology, so this is our own assessment.

3. How we test

• Every proposed change to the site runs an automated check (axe-core, WCAG 2.2 AA rules) on every page, on a desktop screen and on a phone screen. The check also covers states you reach by interacting: a research result, a selected node, the research demo, the open site menu and the first-visit dialog. Our practice is to merge and release only changes that pass it.
• The same run checks the site header, menu and footer at widths from 360 px to desktop for sideways scrolling, and checks the menu by keyboard: Enter opens it, Escape closes it and returns focus to the menu button.
• Automated checks cannot find every problem. A manual review with screen readers has not been done yet; it is planned.

4. Known limitations

• 3-D flight view (Flight): the 3-D scene is drawn on a canvas and has no text equivalent yet. Its controls (subject and depth) are labelled. Until a text alternative is added, the Cards view of a PRISM-9 search lists a topic's nodes and links as text.
• PRISM-9 graph: nodes can be reached and opened with the keyboard, and animation stops when your system asks for reduced motion. Dense graphs are easier to follow in the Cards view, which lists the same nodes and links as text.
• Signed-in pages (your account): these are not yet in the automated check, because it runs without an account.
• Other sites: vendor pages in the CRO Market and our ecosystem sites are run by others and are outside this statement.

5. Report a barrier

If something on kwiKBio is hard or impossible for you to use, tell us at legal@kwikbio.com with the page address and what happened. We aim to reply within 5 business days, and we will offer the information in another way while we fix it where we can.

6. Technical details

kwiKBio relies on HTML, CSS, JavaScript and WAI-ARIA, and works in current versions of Chrome, Edge, Firefox and Safari on desktop and mobile.