Statable WCAG Checker Privacy Policy
Last updated: August 7, 2026
This privacy policy explains how the Statable WCAG Checker browser extension ("the extension") handles information. Statable WCAG Checker is an accessibility auditing tool published by Key Arg B.V. for Chrome. All processing described below happens locally in your browser: the extension makes no network requests of its own, and the information it reads never leaves your device.
This is a separate extension from the Statable Debugger and the Statable GDPR Checker, each of which has its own policy. The three read different things: the Debugger inspects Statable's own script, the GDPR Checker observes what a page loads from third parties, and this extension examines the page's own markup for accessibility problems. If you use more than one, each policy applies to its own extension.
1. Who We Are
Statable WCAG Checker is developed and published by Key Arg B.V., a company registered in the Netherlands, and Key Arg B.V. is responsible for it. Because the extension transmits nothing, we never receive, store or decide what happens to anything it reads: that processing takes place on your device, under your control, and ends there. Key Arg B.V. is a data controller only for personal data you send us directly — an email to the address below, for instance — and for the statable.com website and analytics service. This policy is governed by the laws of the Netherlands. You can contact us at support@statable.com. Full company contact details are available in our main Privacy Policy.
2. Single Purpose
Statable WCAG Checker has one purpose: it examines the page you are looking at for accessibility problems defined by the Web Content Accessibility Guidelines, and lists what it found. Automated checks cover only part of those guidelines, so a clean result means no automatically detectable issues were found — not that the page is accessible or WCAG compliant. The extension reports findings; it does not certify compliance, and nothing it shows is legal advice.
3. Scope Of This Policy
This policy covers the browser extension only. Our website and analytics service are covered by our main Privacy Policy. Using the extension requires no Statable account, and the extension is not connected to any account you may hold with us.
4. When The Extension Is Active
The extension does nothing until you open its side panel. There are no content scripts that run on every page: nothing is injected into any page while the panel is closed. Opening the panel is what starts a scan, and closing it stops the extension from touching pages again. While the panel is open it scans the page in the active tab of that window, and re-scans when you navigate or switch tabs, because a report that silently belonged to a different page would be worse than no report at all.
5. Information The Extension Reads
While the panel is open, the extension reads the http and https page in the active tab. That reading is the check: there is no way to report that an image lacks a text alternative without looking at the image. Everything it reads is processed locally on your device and shown only in the panel.
For each page it scans, the extension reads:
- the page's rendered markup — its elements, their attributes, their text and their computed styles, including colours, sizes and positions. Colours and sizes are what a contrast or target-size check is; attributes and text are what an alternative-text or form-label check is;
- the same information inside frames embedded in the page, where the browser allows it. A cookie banner, video player or payment form is usually a frame, and a report that ignored them would declare a visibly broken page clean;
- the address of the page being scanned, and the id and load state of the tab it is in, so a report is labelled with the page it actually describes and is discarded when you navigate away;
- a short excerpt of the markup of each element that failed a check — up to 300 characters — and the selector that locates it, so the panel can show you which element is meant.
The extension reads no request or response headers, no cookies, no storage, no form values and no keystrokes. It does not observe what you click, type or scroll.
6. What The Extension Changes On The Page
Two features in the panel change the page you are looking at, and both act only when you press them:
- Highlight on page draws an outline around the elements that failed a check and scrolls the first one into view. It sets an inline outline on those elements and nothing else;
- Preview fix on page changes the text colour of elements that failed the contrast check to the nearest colour that would pass, so you can see the fix before making it. It sets an inline colour on those elements and nothing else.
Both changes are visual, local to your browser, and reversible: the original inline value is saved before the change and restored when you switch the feature off, when the panel moves to another tab, and when the panel closes. Nothing is saved to the site, submitted to it, or visible to anyone but you, and reloading the page removes every trace regardless. The extension makes no other modification to any page.
7. How That Information Is Used
Everything in section 5 is used for one thing: producing the report you see in the panel. Computed colours decide whether a contrast check passes; attributes and text decide whether an element has an accessible name; positions and sizes decide whether a target is large enough. The markup excerpt and selector exist so the panel can point at the element in question. None of it is used for any other purpose, and none of it is combined with anything else.
8. Information We Do Not Collect
The extension makes no network requests of its own. It has no server to send anything to, contains no analytics, no telemetry and no error reporting, and does not use the Statable analytics service or any other. We do not know that you installed it, which pages you scanned, or what it found. It requires no account, no sign-in and no configuration, and it does not read or write cookies, local storage or browser history.
9. Sharing And Disclosure
Nothing is shared, because nothing is received. There are no third parties, no processors, no advertising partners and no data sales. No information the extension reads is ever sold, rented, transferred or disclosed to anyone, and none of it is used to train any model.
10. Store Disclosures
Because the extension reads the markup of the pages you scan and the address of the page it is scanning, our Chrome Web Store privacy disclosure declares "Website content" and "Web history". It does not declare "User activity": the extension records no clicks, keystrokes, mouse movement, scrolling or network monitoring. Chrome requires these categories to be disclosed even when the data never leaves the device, which is the case here: everything described above is read, used to build the report, and discarded inside your browser.
11. Data Retention
Reports live in the extension's memory only. A report is replaced when the page is scanned again, discarded when you navigate to another page or close the tab, and lost entirely when the browser shuts the extension down. Nothing is written to disk, and there is nothing to delete or export because nothing is stored. The extension requests no storage permission at all.
12. Data Security
The strongest security property of this extension is that it transmits nothing: information that never leaves your device cannot be intercepted, breached or subpoenaed from us. What it reads exists only in your browser's memory for as long as the report is on screen.
13. Private Browsing
The extension is not granted access to incognito windows unless you grant it explicitly in Chrome's extension settings. If you do, behaviour there is identical to a normal window and, as everywhere else, nothing is stored or transmitted.
14. Third-Party Code
The accessibility checks are performed by axe-core, an open-source engine by Deque Systems, licensed under the Mozilla Public License 2.0. A copy of that engine is included in the extension package and runs locally in your browser; it makes no network requests and reports nothing to Deque or to us. The licence text ships alongside it in the extension, and the source is available at the link above.
15. Remote Code
The extension executes no remote code. Every line it runs, including the accessibility engine, is contained in the package you install from the Chrome Web Store and is reviewed by the store before publication. Nothing is fetched, evaluated or updated at runtime.
16. Changes To This Policy
If this policy changes, the updated version is published on this page with a new date at the top. Material changes to what the extension reads will be described in the extension's release notes as well.
17. Contact Us
Questions about this policy or about what the extension does can go to support@statable.com.