Accessibility Statement

Our commitment to making Paraclyst usable by everyone

Last reviewed: April 2026

Paraclyst is committed to ensuring that our platform is accessible to everyone, including people with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, which defines how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, and neurological conditions.

This statement covers the Paraclyst web application at paraclyst.com and the authenticated platform. It was last reviewed in April 2026.

Conformance status

Paraclyst is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. We are actively working to resolve all known gaps, detailed below.

What we have done and what is still in progress

The table below covers the most significant accessibility criteria and the current status of each.

Keyboard navigation

Implemented

All interactive elements are reachable and operable via keyboard alone. Focus indicators are visible at all times.

Colour contrast

Implemented

All body text and UI labels meet the WCAG 2.1 AA minimum contrast ratio of 4.5:1. Large text meets 3:1.

Semantic HTML

Implemented

Pages use correct landmark regions (main, header, nav, footer), heading hierarchy (h1–h3), and list markup.

Screen reader support

Implemented

All form fields have associated labels. Icon-only buttons carry aria-label attributes. Dynamic content updates are announced via aria-live regions.

Descriptive link text

Implemented

Links describe their destination. No bare 'click here' or 'read more' text is used in isolation.

Alt text for images

Implemented

All meaningful images carry descriptive alt attributes. Decorative images use empty alt text so screen readers skip them.

Resizable text

Implemented

The interface remains functional and readable when browser text size is increased up to 200% without horizontal scrolling.

No content that flashes

Implemented

The platform contains no content that flashes more than three times per second, which could trigger photosensitive seizures.

Full ARIA authoring practices for complex widgets

In progress

Data tables, date pickers, and modal dialogs are being audited against the latest ARIA Authoring Practices Guide. Updates are shipping progressively.

Mobile screen reader optimisation

In progress

We are testing and refining the experience with VoiceOver (iOS) and TalkBack (Android) across all core workflows.

WCAG 2.2 AA upgrade

In progress

WCAG 2.2 introduced new success criteria around focus appearance, dragging movements, and accessible authentication. We are working through these now.

Technical implementation details

Testing approach

We test with automated tools (axe-core) integrated into our development pipeline, supplemented by manual keyboard-only testing and screen reader testing with NVDA on Windows and VoiceOver on macOS.

Assistive technologies tested

NVDA 2024 + Chrome, JAWS 2024 + Chrome, VoiceOver + Safari (macOS 14), VoiceOver + Safari (iOS 17), TalkBack + Chrome (Android 14).

Browser compatibility

Paraclyst is tested and supported on the latest two major versions of Chrome, Firefox, Safari, and Edge. The platform requires JavaScript to be enabled.

Third-party content

Some areas of the platform embed third-party components (such as payment forms via Paddle). We cannot guarantee the accessibility of third-party content, but we select providers that publish their own accessibility conformance reports.

Known limitations

Despite our best efforts, some content may not yet be fully accessible. The following known limitations are being actively worked on:

  • Complex data tables — some tables in the analytics and reports sections do not yet expose full row and column header relationships to screen readers. A fix is in active development.
  • PDF exports — exported PDF documents are not currently tagged for accessibility. We are evaluating accessible PDF generation libraries.
  • Rich text editor — the lab notebook editor has limited screen reader support for toolbar controls. We are working with the component vendor on a fix.

If you encounter a barrier not listed here, please tell us — we take every report seriously.

Standards and guidelines we follow

Procurement and institutional use

If you are procuring Paraclyst on behalf of a university, research institution, or government body and require a formal Voluntary Product Accessibility Template (VPAT) or detailed conformance report, please contact us. We will provide the most current documentation available.

Request a VPAT

Reporting an accessibility problem

If you experience a barrier that prevents you from accessing any part of Paraclyst, or if you have a suggestion for improvement, we want to hear from you. We aim to respond to accessibility reports within 5 business days and to resolve confirmed issues within 30 days.

Contact us by email

support@paraclyst.com

Or use our contact form

paraclyst.com/contact

When reporting, please tell us: the page or feature affected, the assistive technology or browser you are using, and a description of what you expected to happen versus what actually happened. This helps us reproduce and fix the issue faster.

Formal complaints and enforcement

If you are not satisfied with our response, you have the right to escalate a complaint to the relevant authority in your jurisdiction:

← Back to Home