Legal

Accessibility

Last updated: September 13, 2026

We target WCAG 2.1 Level AA across this site. That’s a goal we actively test for, not a certification — if something here doesn’t work for you, we want to hear about it (see Contact below) rather than have you assume it’s intentional.

How we test this, not just claim it

An automated axe-core scan runs against every real public page on this site as part of our test suite (Playwright, see e2e/accessibility.spec.ts) — not a curated subset, since legal and compliance pages are exactly the ones cheapest to silently regress.
A Lighthouse accessibility score threshold is a required gate in our CI pipeline (see /status for the dated, real results), across every core page.
Both checks block merging broken accessibility, they don’t just report on it after the fact.

What’s actually in place

Every interactive element is reachable and operable by keyboard alone, with a visible focus indicator.
Text and interactive-element color contrast is checked against WCAG AA’s 4.5:1 minimum — our own dark theme’s primary/link colors were split into two separate tokens specifically because one color couldn’t clear the contrast bar in both a solid button and as text on our dark background at once.
Every meaningful image carries real alt text; purely decorative icons are marked aria-hidden so a screen reader doesn’t announce noise.
Semantic HTML and landmark regions (header/nav/main/footer, real heading levels) throughout, not generic <div> soup.
Motion respects your system’s prefers-reduced-motion setting — entrance and scroll animations are skipped entirely rather than just shortened when it’s set.
Nothing on this site auto-plays audio or video.
The cookie-consent banner and its preference controls are fully keyboard-operable, matching everything else on the site.

Known limitations

We aren’t aware of any open accessibility barrier on this site as of the date above — our automated scans currently report zero violations across every real page. That’s a snapshot of our own testing, not a guarantee against every possible assistive-technology combination; if you find something we missed, the fastest way to get it fixed is to tell us directly.

Contact

Found a real barrier, or something that doesn’t work with your assistive technology? Contact hello@ramsio.tech — a real person reads it, and we’ll acknowledge within 72 hours, the same commitment we make for every other support request on this site.