Accessibility statement

We sell a plugin that finds accessibility problems. It would be difficult to explain an inaccessible site of our own, so this one is tested the way we would want a client's site tested — and this page says what that actually covers, including where it stops.

What we aim for

WCAG 2.2 Level AA. That is the target for every page on wowstudio.dev, and we believe the site currently meets it. We say "believe" rather than "certify" for the same reason our plugin refuses to: automated testing settles part of WCAG and a person has to settle the rest.

How it is tested

• Every deploy is gated. axe-core runs over every built page in light and dark themes, at desktop and mobile widths, before anything is uploaded. A build with a violation does not ship.
• Colour is checked at the source. Every text pairing in the design system is verified at 4.5:1 or better, and the border of every real control at 3:1 or better, against the actual token values rather than by eye.
• Keyboard paths are walked by hand — the navigation, the project brief and the plugin page's expanding questions — because automation cannot judge whether an order makes sense.

What we have built in deliberately

• A skip link to the main content, as the first thing a keyboard reaches.
• A visible focus ring on everything focusable. It is never removed.
• Underlined links in body copy, so colour is not the only signal.
• Real landmarks and one h1 per page, with headings in order.
• Text that reflows to 320px and stays usable at 200% zoom.
• Motion limited to a single fade, which stops entirely under prefers-reduced-motion.
• A dark theme that follows your system setting, with a manual switch.
• Forms that work without JavaScript, with labels on every field.

Known limitations

We would rather list these than let you find them.

• Screenshots of the plugin's admin. These are dense interfaces, and the alt text describes what each screen shows rather than reproducing every number in it. If a screenshot carries something you need, ask and we will put it in the page text.
• Testing with disabled users. We have not yet done a formal round of it on this site. Automated checks and a keyboard pass are not a substitute, and we are not going to pretend otherwise.
• Third-party content. Pages we link to are outside our control.

Tell us if something is wrong

If any part of this site is difficult or impossible for you to use, email contact@wowstudio.dev. Say which page and what happened, and tell us how you would like the answer sent. We aim to reply within one working day and to fix genuine barriers rather than explain them.

This statement was prepared by reviewing the site against WCAG 2.2 and by reading the output of the checks described above. It is reviewed whenever the site changes substantially.