Accessibility Statement

This statement applies to everything Statable publishes and runs:

• the public website at statable.com, including the legal pages;
• the analytics dashboard you sign in to;
• the documentation at statable.com/docs and the blog at statable.com/blog;
• the panels of our browser extensions (WCAG Checker, GDPR Checker and Debugger) as they appear inside Chrome, Edge and Firefox.

It does not cover third-party pages we link to, or the websites our customers measure with Statable.

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. They define three levels of conformance: Level A, Level AA and Level AAA.

statable.com is partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. The public pages, the documentation and the blog pass our automated checks; the gaps we know about are listed under Limitations below, and the analytics dashboard behind the login has not yet been through a full manual audit.

Statable takes the following measures to keep the site accessible:

• Every public page is run through an automated WCAG check (axe-core 4.13, WCAG 2.0, 2.1 and 2.2 level A and AA rules) before it ships, and again after each release.
• Colour contrast for text and controls is set to at least 4.5:1 in both colour schemes; interface colours live in one token file so a fix applies everywhere at once.
• Pages use semantic HTML: one heading per page as the title, landmarks for header, navigation, main and footer, real buttons and links, labelled form fields, and visible keyboard focus.
• Images that carry information have text alternatives; decorative images are marked so screen readers skip them.
• Accessibility is part of our frontend guidelines, so it is reviewed with every change rather than audited once a year.

If you find something on statable.com, in the dashboard, in the documentation or in one of our extensions that you cannot use, please tell us. We answer within five working days and try to fix what you report in the next release.

• Email: support@statable.com
• Postal address: Key Arg B.V., Herckenrathstraat 1, 2681 DG Monster, the Netherlands

It helps if you include the page address, what you were trying to do, and the browser and assistive technology you were using.

statable.com is designed to work with the current and previous major versions of Chrome, Edge, Firefox and Safari, on desktop and mobile, together with the screen readers built into those platforms (VoiceOver, Narrator, TalkBack) and NVDA on Windows.

The site depends on JavaScript for the dashboard and the interactive parts of the public pages. The documentation and the blog read without it.

Accessibility of statable.com relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML
• WAI-ARIA
• CSS
• JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Despite our best efforts, some parts of statable.com may not yet be fully accessible. Known limitations:

• Dashboard charts. The traffic charts in the analytics dashboard convey their data visually. The headline numbers are in the metrics row above each chart, and the source, page and country breakdowns are plain tables, but a chart itself is not yet readable by a screen reader. We are working on a data table view.
• Payment pages. Checkout and invoices are provided by Stripe. Stripe publishes its own accessibility commitments, but we do not control its interface.
• Manual audit of the dashboard. Automated checks cover only part of WCAG. The public pages have been reviewed by hand for keyboard use and reading order; the dashboard behind the login has not yet had the same review.

If any of these stops you from doing something, write to support@statable.com and we will get you the information another way.

Statable assessed the accessibility of statable.com by:

• Self-evaluation: automated checks (axe-core, WCAG A and AA rules) on the home page, pricing, about, the extension pages, sign-in, the legal pages, the documentation and the blog, plus keyboard and screen-reader walkthroughs of the public pages by the team.

The last full pass over the public pages was on September 04, 2026. The automated check is the same one our WCAG Checker extension runs; it is described in the documentation.

This statement was created on September 04, 2026 using the structure of the W3C Accessibility Statement Generator. It is reviewed whenever the site changes in a way that affects accessibility, and at least once a year.