Accessibility statement
Updated
We build tools that help others make their websites accessible, so our own site has to be accessible too. This statement applies to perceivly.com, including the free checker and its results.
Our target
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We don’t use an overlay widget: accessibility is built into the code.
How we test
- Every change is tested automatically before it is released: every page is checked with axe-core against WCAG 2.0, 2.1 and 2.2 (A and AA), in both light and dark mode.
- Automated keyboard tests check that every page starts with a working skip link, that every interactive element shows a visible focus outline, and that keyboard focus never gets trapped.
- Every color pair in our design system is checked to have a contrast ratio of at least 4.5:1.
- Forms announce errors and results to screen readers, and move focus to where it helps.
Automated tests find only part of accessibility issues, so we also review pages by hand with a keyboard and a screen reader. We publish the result of that review here once it is complete.
What we know isn’t perfect yet
- Screenshots of failing elements in check results describe the element’s position in the page, not its visual content. The HTML of the element is always shown next to the screenshot as a text alternative.
- If a site we check refuses automated browsers, Cloudflare’s bot check may ask you to complete a challenge. Cloudflare provides accessible versions of its challenges, but we don’t control them.
Feedback
If something on our site doesn’t work for you, please tell us at [email protected]. Describe the page and what went wrong, and we’ll reply within five working days.