Skip to main content
sentrytex
Start free

Accessibility statement

Last updated: April 2026

Last updated: 24 May 2026

Last reviewed: 24 May 2026

Sentrytex is committed to making our service usable by everyone, including people with disabilities. This statement explains our target conformance level, the methods we use to test, the limitations we currently know about, and how to give us feedback.

Conformance target

Sentrytex aims to conform to:

  • WCAG 2.2 Level AA — the W3C Web Content Accessibility Guidelines, current version, Level AA success criteria.
  • EN 301 549 — the European harmonised standard for accessible ICT products and services, referenced by the EU Accessibility Act (EAA).

We treat WCAG 2.2 Level AA as the floor, not the ceiling. Where it's reasonable to meet AAA criteria, we do.

How we test

  • Automated scans in CI. Every build runs axe-core against our pages and components. Pull requests that introduce new accessibility violations are blocked from merging.
  • Manual keyboard testing. Each new page and interactive component is exercised with keyboard only — tab order, focus visibility, escape-key handling, skip-to-main link.
  • Screen-reader spot-checks. We test critical flows (signup, alert detail, settings, billing) with VoiceOver on macOS and iOS, and periodically with NVDA on Windows.
  • Colour contrast verification. Our design tokens are checked against a 4.5:1 minimum contrast ratio for normal text and 3:1 for large text and non-text UI components.

We do not currently use a paid third-party accessibility auditor. We plan to commission an external WCAG 2.2 audit in the next 12 months.

Accessibility features

  • Skip-to-main-content link as the first focusable element on every page.
  • Semantic HTML landmarks (<header>, <nav>, <main>, <footer>).
  • ARIA labels and roles where semantic HTML alone isn't enough.
  • Visible focus indicators on every interactive element.
  • Keyboard operation of all functionality, including the dashboard, settings, and alert flows.
  • Colour contrast of at least 4.5:1 for body text and 3:1 for large text and UI components.
  • Respect for the prefers-reduced-motion user preference — animations are reduced or removed when the OS signals reduced-motion.
  • Text resize support up to 200% without loss of content or functionality.
  • No content that flashes more than three times per second.
  • Form fields with associated labels, error messages tied to the field via aria-describedby, and autocomplete hints where appropriate.

Known limitations as of 2026-05-24

We track known limitations as GitHub issues tagged a11y in our private repository. The current notable items:

  • Light-mode amber accent — decorative scope only.Sentrytex's brand amber (#FFB84D / oklch(0.75 0.15 65)) is the same value in both themes so the brand reads identically across them. In the light theme it is used decoratively on:
    • Citation superscripts on the landing page
    • The “Most popular” badge background on the pricing page
    • TL;DR card borders on legal pages
    • Inline link accents in body copy
    These uses fall below the WCAG 2.2 AA 4.5:1 contrast threshold on the cream canvas:
    • Amber text on canvas measures approximately 3.3:1 (fails AA for normal text, passes AA Large for ≥18pt or ≥14pt bold)
    • Amber surface fills on canvas measure approximately 1.9:1 (fails AA non-text contrast 3:1)
    Amber is never used for primary content, headings, body text, form labels, error states, status indicators, or any load-bearing information. Every amber-coloured element conveys its meaning through an additional non-colour channel — text, icon, position, or list semantics. Users who need higher contrast can switch to the dark theme via the toggle in the top navigation, where amber renders at approximately 9:1 against the ink canvas. A high-contrast theme variant is on the roadmap for the first half of 2026.
  • The Klaro consent dialog is an open-source library we self-host. We've reviewed its default markup for keyboard operability and contrast, and we override its CSS custom properties to match our palette, but upstream Klaro updates can shift the structure between releases.
  • The Stripe-hosted billing portal uses Stripe's own accessibility implementation. Sentrytex links out to it; we don't control its markup.
  • Some marketing-page micro-interactions (CountUp, scroll-reveal stagger) are softened — not eliminated entirely — under prefers-reduced-motion. We're tightening this to a full skip in a follow-up.

When an issue is resolved, this statement is updated.

Feedback

If you encounter an accessibility barrier on Sentrytex, please tell us. We treat accessibility reports with the same priority as security reports.

  • Email: [email protected]
  • What to include:the page or feature, the assistive technology and browser you were using, and a description of what didn't work.

We aim to acknowledge feedback within 2 business days and to publish a fix or a workaround within 30 days for issues we can reproduce.

Routing note: [email protected] is being provisioned. Until 24 June 2026, please send accessibility reports to [email protected] with “Accessibility” in the subject line.

Enforcement procedure (EU)

If you are in the European Union and you are not satisfied with our response to your accessibility feedback, you may contact your national Market Surveillance Authority under the EU Accessibility Act (Directive (EU) 2019/882). A current list of national authorities is published by the European Commission.

Related

Statement preparation

This statement was prepared on 18 May 2026 by the Sentrytex team. It will be reviewed at least annually and after any significant change to the service.