Conformance status

We aim for WCAG 2.1 Level AA. This website is partially conformant: most of the standard is met, and the specific gaps we know about are described under where it falls short.

"Partially conformant" is the honest description. We have not commissioned an independent audit, and we have not yet tested the site with people who use assistive technology daily. Until we have done both, we will not claim more than we can show.

What works, and how we know

These are measured results on the live pages, not intentions.

Keyboard. Every control on every page can be reached and operated with a keyboard alone. The menus open on focus, close on Escape and report their open state to assistive technology. "Skip to content" is the first thing the keyboard reaches and "Pause motion" is the second, both before any content that moves.
A visible focus indicator. Every focusable element draws a 2px outline with a 3px offset, in a colour that clears the 3:1 minimum for non-text contrast against the surfaces it appears on.
Contrast. Text meets the 4.5:1 minimum throughout. The floating navigation was the tightest case, because it passes over dark and light sections: measured 6.07:1 at its worst point, and it changes its own colours to stay legible over whatever is behind it.
Reduced motion. If your system asks for reduced motion, this site stops moving. That covers the animations and, just as importantly, every panel that updates itself on a timer.
An accessibility panel, on every page. The button in the bottom corner opens four settings that each change the page rather than just naming a change: pause motion, larger text, higher contrast and underline links. Your choices are remembered for your next visit, and one button resets all of them. It is our own code. We deliberately did not install one of the third-party accessibility overlays, because they do not fix what is underneath and the people they claim to help have said so publicly.
What those settings actually do, measured. Pause motion: around 980 page updates in four seconds while running, five while paused. Larger text: everything grows by 18%, with no sideways scrolling introduced, on a phone as well as a desktop. Higher contrast: body text goes from 5.74:1 to 13.16:1, which is past the strictest level the standard defines.
A pause control that a keyboard finds first. Besides the panel, "Pause motion" sits with the skip link, which makes it the second thing the keyboard reaches on every page, before anything that moves.
Reflow. The pages work down to a 320px viewport with no horizontal scrolling, which is the width the standard asks for.
Structure. One first-level heading per page, no skipped heading levels, real landmarks for the header, navigation, main content and footer, a declared page language, alternative text on every image, no duplicated element identifiers, and a name on every control.
The booking dialog is a real modal: focus moves into it when it opens, the page behind it stops scrolling, and it can be closed with Escape, with the backdrop, or with a named close button.
Tables are tables. Comparison data is marked up as a real table with real header cells, so a screen reader can announce the row and column you are in.

Where it falls short today

Three things we know are not right yet. This list is shorter than it was on 19 September, because two of the items on it have since been fixed rather than reworded.

The comparison table still scrolls sideways on a phone. It carries five columns of data that lose their meaning if stacked, so it stays a table and becomes a horizontally scrollable region on a narrow screen. We have made that as easy as we can: the row label stays pinned to the left edge while the values scroll past it, there is a shadow at whichever edge still has more to show, and the table was narrowed so there is about a third less to scroll than there was. It is still scrolling, and scrolling is more work than not scrolling.
No independent audit. Everything on this page is our own measurement. It has not been checked by an accessibility specialist from outside the company.
No testing with assistive-technology users. We have tested with a keyboard and with automated tools. That is not the same as watching somebody use the site with a screen reader, and we know it.

Parts we do not control

Booking a demo opens a calendar supplied by a third party inside a frame on our page. Its accessibility is set by that supplier, not by us. If it gets in your way, write to us and we will book the time with you directly by email instead, which is always an option.

How we test

Every page is checked on the published URL, never only on a local copy. The checks are: an automated audit on every page, which currently reports a perfect accessibility score on all of them; keyboard-only walkthroughs of the navigation, the menus and the dialog; contrast measured in the browser against the surface each piece of text actually sits on, including the translucent ones; reflow at 320px; a run with reduced motion forced on, to confirm the page really does stand still; and a count of how often the page changes by itself, with the pause control on and off, so that "it stops" is a number rather than an impression. Each setting in the panel is measured the same way, which is where the numbers above come from.

Automated tools are useful and limited. They catch a minority of the barriers that matter, which is why the list above separates what a machine verified from what a human still needs to check.

Tell us if something is in your way

If any part of this site is hard or impossible to use, we want to hear it, and a short note is enough. Tell us the page, what you were trying to do, and what got in the way. If you use a screen reader or another assistive technology, saying which one helps us reproduce the problem.

Write to hello@getscayla.com. We aim to reply within five working days, and to tell you either what we fixed or when we will.

If you need something on this site in another form in order to use it, ask, and we will send it to you directly.

Keeping this page true

This statement was last reviewed on 20 September 2026. We review it whenever the site changes in a way that affects any of the claims above, and at least twice a year. If you find a statement on this page that is not true of the site, that is itself a bug worth reporting.

Accessibility statement