Accessibility Statement

Last updated: June 23, 2026

RecallStream is committed to making our website and application accessible to as many people as possible. We aim to meet WCAG 2.2 Level AA and follow the European Accessibility Act (EAA), Section 508, and EN 301 549 where applicable. This statement explains our current conformance status, the features we have implemented, known gaps, and how to contact us if you encounter an issue.

Partially conformant — WCAG 2.2 AA

RecallStream is partially conformant with WCAG 2.2 Level AA. This means that some parts of the content do not yet fully conform to the accessibility standard. We are actively working to identify and address remaining gaps, prioritising the most-used parts of the application first.

The main landing pages and legal documents are designed to meet WCAG 2.2 AA requirements. Some areas of the application — particularly complex data tables and the webhook event log — may have partial gaps that we are in the process of resolving.

Keyboard navigation: all interactive elements — buttons, links, form inputs, and navigation — are fully reachable and operable using a keyboard alone. The tab order follows a logical reading sequence on every page.
Visible focus indicators: keyboard focus is always visible, displayed as an amber outline ring that meets or exceeds the WCAG 2.2 AA minimum contrast and size requirements.
Skip link: every page includes a "Skip to main content" link as the first focusable element, allowing keyboard and screen reader users to bypass the navigation.
Semantic HTML5: pages use appropriate landmark roles (<header>, <main>, <nav>, <footer>, <aside>) and heading hierarchy (h1→h2→h3) to convey structure to assistive technologies.
ARIA landmarks and labels: navigation regions, search inputs, and dynamic UI regions are labelled with ARIA attributes to provide context to screen reader users.
Colour contrast: text colours meet the WCAG 2.2 AA 4.5:1 contrast ratio for normal text and 3:1 for large text and UI components, against all background layers used in the Sentinel design system.
Text resize: all text resizes correctly up to 200% zoom without loss of content or functionality, and without horizontal scrolling on a desktop viewport.
Alt text: all meaningful images carry descriptive alt text. Decorative images (such as the stream animation background) use alt="" to be ignored by screen readers.
Reduced motion: all CSS animations and transitions respect the prefers-reduced-motion: reduce media query. When this preference is set, animated data streams become static graphics, skeleton shimmer animations stop, and scroll-reveal transitions are instant.
Form labels and errors: all form inputs have associated <label> elements. Error messages are associated with their input via aria-describedby and are announced by screen readers.

We are aware of the following gaps and are working to address them:

Complex data tables: the recall events table and webhook delivery log use dynamic data loading patterns that may not be fully announced by some screen readers. We are refining ARIA live region usage in these components.
Date picker inputs: some filter date-range inputs rely on the native browser date picker, whose accessibility varies across browser and OS combinations. We are evaluating keyboard-accessible fallback options.
Third-party components: certain third-party components used in the billing and payment flow (the Paddle checkout) are outside our direct control. Paddle publishes their own accessibility documentation and we will raise any issues with them directly.

If you encounter an accessibility problem that is not listed here, please let us know — we treat accessibility issues as bugs and aim to fix them promptly.

We welcome feedback on the accessibility of RecallStream. If you encounter a barrier that prevents you from accessing any part of our website or application, please contact us:

Email: support@recallstream.com (subject: "Accessibility feedback")
Response target: 5 business days

Please describe the page or feature affected, the assistive technology you are using, and what you were trying to do when you encountered the problem. If we are unable to fix an issue within a reasonable time, we will provide an accessible alternative method of accessing the same information or functionality.

Automated checks: automated accessibility checks are part of our development workflow, and we run manual keyboard and screen-reader passes on major features.
User feedback loop: accessibility reports are tracked as high-priority bugs and reviewed at each sprint cycle.
Design system alignment: the Sentinel design system (used across all RecallStream interfaces) encodes accessible defaults — focus styles, contrast ratios, and reduced-motion handling — so new components inherit them automatically.