Back to Home

Accessibility Statement

We want Sortio to be usable by everyone. This statement explains our commitment, our progress, and where we know we still fall short.

Date of statement: 16 May 2026

Conformance target

We aim for the Sortio marketing site (getsortio.com) and the desktop application to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. The marketing site is the focus of the current pass; the desktop app accessibility work is on a parallel track.

Measures we have taken

  • Set lang="en" on the HTML root to support assistive technologies.
  • Audited all marketing pages for missing alt text and added descriptive alternatives.
  • Added prefers-reduced-motion guards around hero animations, parallax effects, and floating elements.
  • Reviewed color contrast for body text, links, and CTAs against Apple-style dark backgrounds.
  • Associated all form inputs (consent banner, opt-out form, contact form) with labels via either htmlFor or aria-label.
  • Ensured all interactive elements are keyboard reachable and show a visible focus ring.

A detailed log of each fix is available in our repository at docs/ACCESSIBILITY_PASS.md (link available on request).

Known limitations

We are tracking the following issues; expect fixes in upcoming releases:

  • The animated 3D hero on the homepage may not fully respect prefers-reduced-motion in older browsers (specifically, browsers without the matchMedia support we rely on for the early return). Users on those browsers will see a CSS fallback background that still includes light pulse and float animations.
  • Some persona landing pages contain auto-playing background videos. They are muted and have a poster image, but they may not pause automatically for users who request reduced motion outside of our framework.
  • A small number of decorative gradient orbs are not yet hidden from assistive technologies; they have no functional content but are exposed in the DOM.
  • The session-replay tool (Microsoft Clarity), when enabled by user consent, may capture pointer interactions outside our control.

Tooling used

  • axe DevTools (Chrome extension) for spot checks.
  • Lighthouse accessibility audit.
  • Manual keyboard navigation and screen-reader (VoiceOver) review of the highest-traffic pages.
  • Static code review of section components for landmark structure, heading hierarchy, and image alt coverage.

Reporting an issue

If you encounter an accessibility barrier, email marcus@getsortio.com with the page URL, a short description, and your assistive technology (if relevant). We aim to respond within 5 business days and to fix WCAG 2.1 AA failures within 30 days where feasible. If the fix takes longer, we will propose a workaround in the meantime.

Formal complaints

If we cannot resolve your concern, US users may contact the United States Access Board (access-board.gov) and EU users may contact their national equality body. UK users may contact the Equality and Human Rights Commission (equalityhumanrights.com).

Your cookie choices

We use strictly necessary cookies to run the site. We also use optional analytics, marketing, and preference cookies if you agree. You can change your mind anytime via the "Cookie Settings" link in the footer. See our Cookie Policy and Privacy Policy.