Accessibility statement

WebAccez exists to help teams find and fix accessibility problems on their websites. That only means something if our own product holds itself to the same bar. This page says, plainly, what we aim for, what we actually do to get there, and where our approach has limits.

Our commitment

We want every part of WebAccez (signing up, reading a report, changing a setting, exporting a PDF) to work for people who use a keyboard, a screen reader, magnification, high contrast, or reduced motion. Accessibility is not a feature we added; it is the subject of the product, and we treat regressions in our own app with the same severity as regressions in the scanner we sell.

The standard we target

We target WCAG 2.2 level AA , the same conformance level our scanner checks customers’ sites against. We deliberately do not describe ourselves as “fully compliant” or “100% accessible”: no honest team can promise that, and we built this product partly because such claims are so often wrong. What we can say is that we target WCAG 2.2 AA, verify continuously with automated checks, and fix what those checks and our users find.

What we do to get there

Automated self-scans on every change. Every page of our app is run through axe-core, the same engine our product uses, against WCAG 2.2 A and AA rules, including dialogs and panels that only exist after a click. A single violation fails the check.
Computed contrast. Every text-and-background pairing in our palette is verified by calculation, not by eye: at least 4.5:1 for text everywhere, and AAA-level contrast in the high-contrast mode.
Keyboard-reachable UI. Interactive controls are reachable and operable with a keyboard. Dialogs move focus in, close on Escape, and return focus to where you were.
Respect for motion settings. Animations honour your system’s reduced-motion preference, and the app has its own switch to turn motion off regardless of system settings.
Display settings you control. Inside the app you can set the text size, contrast level, motion, and link underlines. These are stored only in your browser, and every type size in the app is defined in relative units so text scaling actually works.
Colour never carries meaning alone. Severity, status, and trends are always labelled in text, not just tinted.

Known limitations

Automated testing, ours included, cannot catch every barrier. It cannot judge whether alternative text is genuinely descriptive, whether a flow makes sense when heard rather than seen, or whether wording is clear. We have not yet commissioned an independent manual audit of WebAccez by assistive-technology users, and until we do, there will be problems our checks miss. If you hit one, we genuinely want to hear about it. Reports from real use are worth more to us than any scan.

Tell us what we missed

If any part of WebAccez is difficult or impossible for you to use, please write to accessibility@webaccez.com. Please note this mailbox is still being set up, so if your message bounces in the meantime, reply to any email we have sent you and it will reach the same people. Tell us what you were trying to do, what happened, and what browser or assistive technology you were using; we aim to respond within a few business days.

What this statement is not

WebAccez does not certify legal compliance, not our own and not our customers’. Accessibility law depends on jurisdiction and circumstances that no automated tool can assess, and a statement like this one describes an ongoing practice, not a certificate. The same honesty applies to the reports we sell: they show what automated WCAG 2.2 checks can find, never a promise that a site is compliant.

This statement was prepared on 30 August 2026 and reflects the product as of that date. We revise it as our practices change.