Accessibility statement
Last updated: 13 November 2026
In short. Kerbwise checks other people's websites for accessibility issues, so our own website, account area and extension should hold up to the same checks. We aim to meet WCAG 2.2 level AA. We test with automated checks and keyboard checks, and we know of some limitations, listed below. If something doesn't work for you, email hello@kerbwise.dev and we'll help.
1. What this statement covers
- The website kerbwise.dev, including the EAA scope check, the articles, the legal pages and shared prospect reports.
- The demo shop at kerbwise.dev/demo. This fictional shop, Maison Ostrelle, contains accessibility issues on purpose, so you can try Kerbwise on them. Those issues are not covered by this statement. The same pages without the issues are at kerbwise.dev/demo/fixed, and they are covered.
- The account area at app.kerbwise.dev: sign-in, your account and the hand-off to the extension.
- The side panel of the Kerbwise Chrome extension, and the reports it opens for printing.
It does not cover the websites you check with Kerbwise. We don't control those.
2. The standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. For web content, the European standard EN 301 549 (V4.1.1) follows WCAG 2.2, so it is the same target.
We believe Kerbwise partly meets WCAG 2.2 AA: the known limitations are in section 5. We have not had an external audit.
3. What we did to make it accessible
- Every page has one main heading, landmarks and a skip link on the website, labelled form fields, and real links and buttons.
- Every link, button and field is designed to show a clearly visible focus ring when you use the keyboard.
- Severity (critical, serious, moderate, minor) is always shown as a shape, a word and a colour, never by colour alone.
- Animations are turned off when your system asks for reduced motion.
- The side panel follows your system's light or dark setting, and every text and background colour pair is checked for a contrast of at least 4.5:1 in both. The account area also has a light and a dark theme.
- The side panel is designed to work at widths from 320 to 560 pixels, and the account area from 320 pixels.
4. How we test
This statement is a self-assessment by Zorzen Studios, the company that makes Kerbwise, not an audit by an independent party. We test:
- With automated checks. We run axe-core, the open-source engine Kerbwise itself uses, on our pages. On 13 November 2026 it found no issues on the home page, the privacy policy, the terms of service and this page, at 1280, 390 and 320 pixels wide. The account area showed no issues on every page on 12 November 2026, at 320 and 1280 pixels wide, in the light and the dark theme. The extension's automated test suite runs axe-core on its side-panel screens and checks the contrast of every text and background colour pair in both themes.
- With the keyboard. On 13 November 2026 we pressed Tab through the home page, the privacy policy, the terms of service and this page, in a browser driven by a script, and checked that each stop showed a focus indicator and that the first stop is the "Skip to content" link. In the account area, confirmation dialogs take the focus, close with Escape and return the focus to where you were.
- At different sizes. On 13 November 2026 we checked the same four pages at 1280, 390 and 320 pixels wide for sideways scrolling. None of them scrolls sideways. On narrow screens, the code example in "How it works" scrolls sideways inside its own box, so the code stays readable; you can reach that box with Tab and scroll it with the arrow keys.
Automated checks find many issues, but not all. A manual review is still needed, and that applies to our own pages too.
5. Known limitations
- We have not yet tested with a screen reader in a structured way. Our pages are built to work with one, but a full pass with VoiceOver and NVDA is still to do. Until then, some things may sound wrong or be hard to use. Please tell us if they are.
- The picture of Kerbwise at work on the home page has pale text on purpose. It shows Kerbwise checking our demo shop, and the shop's prices in it are pale to show a contrast issue Kerbwise finds. The picture has a text description; the pale prices themselves are hard to read. They are drawn as part of the picture, so automated checks don't report them, but they are still pale.
- The demo shop's issues are deliberate. The pages under kerbwise.dev/demo have missing image descriptions, unnamed buttons, low contrast, a keyboard trap, unclear form errors and more, on purpose. Use kerbwise.dev/demo/fixed for the same content without them.
- The sign-in check is made by a third party. The sign-in form at app.kerbwise.dev can show a Cloudflare Turnstile check that protects it from automated sign-ups. It runs in a frame we don't control. If you can't complete it, email hello@kerbwise.dev and we'll help you get signed in.
- PDF reports are printed by your browser. The extension shows reports as a web page that you save as a PDF with your browser's print function. How well the saved PDF is structured for assistive technology (headings, reading order, tags) depends on the browser. We have not tested the saved PDFs with a screen reader. If you need a report in another format, ask us.
- The outlines Kerbwise draws on a page are visual. When you check a page, Kerbwise can outline problem elements and number the keyboard focus order on that page. The same findings are listed as text in the side panel.
- The websites you check are not ours. Kerbwise works on top of other people's pages. Their accessibility, and anything they change, is outside our control.
6. Feedback and contact
If you find something on kerbwise.dev, app.kerbwise.dev or in the extension that is hard or impossible to use, or you need information in another format, tell us:
- Email: hello@kerbwise.dev
- Post: Zorzen Studios, Salland 1, 1948 RE Beverwijk, the Netherlands (Dutch Chamber of Commerce (KvK) number 98717847)
Please say which page or screen it is and what went wrong. We aim to reply within 5 working days. We'll tell you what we'll fix and when, or help you another way in the meantime.
7. If you're not satisfied with our reply
Contact us first, so we can try to put it right. If you're still not satisfied, you can raise it with the Authority for Consumers and Markets (ACM), which supervises the Dutch accessibility rules for e-commerce services. This is general information, not legal advice.
8. About this statement
This statement was prepared on 13 November 2026 by Zorzen Studios, using our own testing described in section 4. We review it when we change the website, the account area or the extension in a way that could affect accessibility, and at least once a year.