Alpha Level
Dashboard Contact us
Legal · Accessibility statement

Accessibility at Alpha Level.

We design and build for everyone — not just the able-bodied majority. This statement explains the standards we hold our work to, where we’re still falling short, and how to tell us when something doesn’t work for you.

Last reviewed: 7 May 2026  ·  Conformance target: WCAG 2.2 Level AA

Our commitment

Alpha Level is committed to making its website — and the websites we build for clients — usable by people with the widest possible range of abilities. Accessibility is not a checklist we run at the end of a project; it’s a constraint we design and develop against from day one.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, which is the standard referenced by EU directive 2016/2102 and the harmonised standard EN 301 549. For US clients we additionally align to Section 508.

What this means in practice

  • Keyboard. Every interactive element on this site can be reached and operated with a keyboard alone. Focus is always visible.
  • Screen readers. Pages use semantic HTML (proper headings, lists, landmarks) and ARIA only where native semantics aren’t enough. We test against NVDA, JAWS and VoiceOver.
  • Colour and contrast. Body text meets a minimum 4.5:1 contrast ratio against its background; large text and UI components meet 3:1. We support both light and dark modes.
  • Motion. All animations respect the prefers-reduced-motion setting. If you’ve asked your OS to reduce motion, our site won’t override that.
  • Zoom and reflow. Content reflows up to 400% zoom without horizontal scrolling on standard viewport widths.
  • Forms. Every form input has a programmatic label, an accessible error message and a clear focus state. We don’t hide labels in placeholders.
  • Images. Every meaningful image has descriptive alt text. Decorative images are marked as such, so screen readers skip them.
  • Language. The page language is declared so screen readers pronounce content correctly.

How we test

Accessibility checks happen at three points in our process:

  1. During design. Mockups are reviewed for colour contrast, hit-target sizes, and focus order before a single line of code is written.
  2. During development. Every pull request runs through automated checks (axe-core, Lighthouse) on each commit. Failing builds don’t merge.
  3. Before release. Manual QA on real assistive tech — keyboard-only navigation, screen-reader walkthroughs (NVDA on Windows, VoiceOver on macOS / iOS), and high-contrast mode — on a representative set of templates.

We re-audit this site at least every six months and after any significant redesign.

Known limitations

Honesty over branding: a few areas don’t yet meet our own bar. We’re actively working on them.

  • Embedded third-party content. Some YouTube / Vimeo embeds and external chat widgets don’t fully respect our reduced-motion or contrast settings. We’re replacing them with self-hosted alternatives where feasible.
  • Older blog posts. Articles published before 2024 may have images without alt text or insufficient heading hierarchy. We’re working through the archive.
  • Complex data visualisations. A handful of dashboards include charts that don’t yet expose a text-equivalent for screen readers. A tabular alternative is on the roadmap.

Tell us when we get it wrong

If you hit a wall, we want to hear about it — even (especially) on things we don’t know are broken. Please include:

  • The page URL where you encountered the issue
  • The assistive technology / browser / OS you were using
  • What you were trying to do and what happened instead

Email us at accessibility@alphalevel.net. We aim to respond within 5 working days and to fix verified issues within 30 days, or to give you a clear timeline if the fix takes longer.

You can also reach us through the contact form — mention “accessibility” in your message and it’ll be routed to the right person.

Enforcement and escalation

If you’re not satisfied with our response, you can escalate to the relevant national enforcement body:

Statement preparation

This statement was last reviewed on 7 May 2026 by Alpha Level’s engineering team using a combination of self-evaluation, automated testing (axe-core 4.10, Lighthouse 12) and assistive-tech walkthroughs. The next scheduled review is six months from this date.

This statement is published under the model recommended by Annex of Commission Implementing Decision (EU) 2018/1523.

Found something broken?

Tell us. The faster we hear about it, the faster we fix it.

Email accessibility@ → Use the contact form