Perceivio Book a free 30-minute audit call

Website accessibility statement

We built this site to meet WCAG 2.2 AA. This page says what we did, what is still open, and how to tell us about a barrier. Below it sits the template we used.

Last reviewed: 2 October 2026. All 41 pages were checked at 1440 and 320 pixels in both themes, the new pages also at 900 pixels with text spacing applied, and the checker was checked with its results on screen rather than empty.

What we did

Semantic landmarks, one H1 per page, skip link, visible focus, labelled form fields, 46px targets, text pairs measured at 4.5:1 or better, one-shot animation with header and local pause controls, full content with reduced motion, layouts checked at 320px and 400% zoom. This includes the checker, the news page, the blog and the posts added in the on-page SEO pass. See ACCESSIBILITY-CHECK.md in the build notes for the full results.

What is still open

This is a new site. A full assistive-technology pass across NVDA, JAWS, VoiceOver and TalkBack lands with our stage 5 checks, and this statement updates with its results. Third-party fonts load from Google Fonts with system fallbacks.

Report a barrier

Email hello@perceivio.in with the page and what blocked you. We reply within two working days.

Write your own statement

Seven headings, in this order. Fill them in honestly and the page does its job.

  1. What this covers

    Name the website, app or service the statement applies to, and the organisation behind it.

  2. The standard and the level

    Say what you tested against and when. WCAG (Web Content Accessibility Guidelines) 2.2 Level AA is the usual floor. A conformance claim without a version and a date is not a claim.

  3. What you have done

    Concrete work rather than intention: the manual passes, the assistive technology, and the checks sitting inside your release process.

  4. What is still open

    The barriers you already know about, named plainly. Every honest statement has this section. Leaving it out is the quickest way to make the rest of the page read as marketing.

  5. How a reader reports a barrier

    An email address or a form, and a reply time you will actually keep.

  6. How you assess the work

    Who tested, with what, and on what schedule. An outside audit, a review in house, or both. Say which.

  7. When it was last reviewed

    A date. A statement written two years ago and left alone tells a reader something you did not intend to say.

Reading an example critically

When you borrow an accessibility statement template, or copy the wording of an accessibility statement example, read it for the parts that cannot be borrowed. Another organisation's known gaps, contact route and review date belong to them, and putting your name on those is worse than a shorter statement of your own. Copy the structure, then fill in your own facts.

This page is our own statement, and our own example of the shape. The structure is free to copy. The results are ours, from the checks written up in our build notes, and the open items are real work still to do.

More on bringing a site into line, in order · Check one page's markup, free