Skip to content
Beta Free audit

Accessibility

Accessibility statement.

The audit tool that audits other sites for accessibility must audit clean against its own pillar. Here is exactly what we commit to, how we test it, and the limitations we are honest about.

The standard we hold ourselves to

WCAG 2.2 Level AA throughout the freewebsiteaudit.ai estate. This is the same standard the audit tool measures other sites against. We test continuously in CI with axe-core (the same engine our Lens agent uses), and we re-test manually with a screen reader at every release.

We do not claim AAA conformance. AAA is appropriate for special-purpose contexts (e.g. government services for users with severe cognitive impairments); AA is the right standard for a public marketing and product surface, and the level we believe is honestly achievable and sustainable.

What is in scope

This statement covers:

  • freewebsiteaudit.ai, every marketing page, the audit application, the live agent dashboard, and the results page
  • docs.freewebsiteaudit.ai, the methodology subsite
  • PDF audit reports, generated with tagged structure, reading order, heading semantics, and image alt text
  • Email templates, transactional and marketing, with plain-text alternatives and sufficient contrast

Explicitly out of scope:

  • admin.freewebsiteaudit.ai, internal admin tool; accessibility maintained for our own work but not held to public standard
  • status.freewebsiteaudit.ai, third-party status page (Uptime Kuma); best-effort

How we test it

Continuous (every commit)

  • axe-core runs via Playwright against every public route, asserting zero WCAG 2.0 AA, 2.1 AA, and 2.2 AA violations
  • A separate test asserts the keyboard focus indicator is visible on the primary CTA
  • Single-h1-per-page and skip-to-content-link checks enforced in CI
  • Type checking, linting, and a11y lint rules enforced before any commit lands

Per release

  • Manual keyboard navigation test of critical flows (audit submission, dashboard, results, payment)
  • Screen reader spot check (VoiceOver on macOS, NVDA on Windows)
  • Manual contrast review of any new visual elements
  • Reduced motion mode (prefers-reduced-motion: reduce) spot check

Annual

  • Comprehensive manual audit with a focus on the live agent dashboard (the most dynamic surface)
  • Third-party accessibility review (planned for year two)

Known limitations

We are honest about where we are not yet meeting the standard. Currently known issues:

  • None blocking core functionality. The marketing pages, the homepage, and the documentation subsite all currently pass axe-core at WCAG 2.2 AA.
  • Live agent dashboard not yet built. When it ships, frequent SSE updates will need ARIA live regions (polite by default, assertive for critical updates). The implementation plan documents this explicitly.
  • PDF accessibility not yet shipped. Tagged PDFs are part of the v1 release plan but not yet built. The current PDF generation path is a temporary scaffold.

This list is updated each release. If an issue affects you and is not listed, please report it (next section).

Report an issue

Found an accessibility issue? Use the accessibility report form. We confirm receipt within one working day and triage as follows:

  • Critical (blocks core functionality for users with disabilities): fixed within 7 days
  • Significant (major friction): fixed within 30 days
  • Cosmetic: fixed in the next regular release cycle

You receive a confirmation when the issue is fixed.

Detailed commitments

Perceivable

  • Text contrast at least 4.5:1 for normal text and 3:1 for large text and meaningful graphical elements
  • Alternative text on all informative images; decorative images marked with empty alt
  • Captions on any video content; transcripts on any audio
  • Text resizes to 200% without loss of content or function
  • Information is not conveyed by colour alone (icon + colour + text on the agent dashboard, for example)

Operable

  • Every interactive element is reachable and operable via keyboard
  • Visible focus indicator on every interactive element (we use a terracotta-toned ring)
  • No keyboard traps
  • Skip-to-content link as the first focusable element on every page
  • Target size minimum 24 × 24 CSS pixels (we use 40+ for primary CTAs)
  • Focused elements never obscured by sticky headers (we set scroll-padding-top on every focusable target)

Understandable

  • Page language declared as en-GB
  • Consistent navigation and identification across pages
  • Form labels associated programmatically with inputs; errors identified and described
  • No cognitive function tests required for authentication (we will use passwordless magic links)

Robust

  • Valid HTML, semantic-first; ARIA only where needed
  • Compatible with current and recent assistive technologies (VoiceOver, NVDA, JAWS)
  • Reduced motion respected throughout

Last tested

Continuous CI testing on every commit. Most recent manual review: 15 May 2026. Next scheduled review: 15 November 2026 (or sooner, if a material change is shipped).

Questions? Use the contact form and a human replies within one working day.

Wingenious Ltd · Registered in England and Wales · Wrexham, North Wales.

Run my free audit