Accessibility statement

How accessible this site is.

We sell accessibility work, so it would be poor form not to publish where our own site stands. This page covers what we have done, what we know is still wrong, how we checked, and how to tell us when we have missed something.

  • WCAG 2.2 level AA
  • Last reviewed 3 August 2026
  • Self-assessed

Scope & status

What this statement covers, and how far we think we've got.

Scope

This statement applies to itch.studio and everything under it: the studio and services pages, the product pages for our apps, their support pages including the translated ones, and our privacy and terms pages.

It does not cover our iOS and macOS apps themselves, which have their own accessibility behaviour, nor the embedded YouTube player used for promo films, which is Google's software and outside our control. It also does not cover the third-party booking page our "Book a call" links point to.

Conformance status

We believe this site is conformant with WCAG 2.2 level AA. We know of no success criterion it currently fails. Where we are less than certain, or where something sits outside our control, it is written down under known issues rather than left for you to discover.

This is our own assessment, not a certified third-party audit, and nothing here is a legal declaration of conformity. If you need a formal conformance report for procurement, email us and we will arrange one properly.

What we've done

The specific things, rather than a claim that we care.

01

Keyboard and Focus

Every page opens with a skip link to the main content. Interactive elements take a visible focus ring in ink at roughly 16:1 against the background, offset clear of the control. The project dialogs are real <dialog> elements, so focus is trapped while they are open and returns to whatever opened them on close.

02

Structure and Landmarks

One h1 per page and no skipped heading levels anywhere on the site. Header, main, navigation and footer landmarks throughout, with the primary navigation labelled. The translated support pages carry their own lang so screen readers pronounce them in the right language rather than reading German with an English voice.

03

Contrast and Text

Body text sits at 6:1 or better and headings at 16:1. The studio's orange is only 2.5:1 against our background, so text that uses it now takes a darker tone of the same hue at 4.5:1, and the bright orange is kept for rules and badges where nothing depends on reading it. Text scales with browser and OS text size settings.

04

Motion and Media

Promo films are muted, carry pause and sound controls we built rather than relying on the embedded player, have captions covering every sound in them, and each has a written description beside it for anyone who cannot see the screen or would rather read. Nothing autoplays for visitors who have asked their system to reduce motion: the scrolling capability bands stop, entrance animations are removed, and films load with ordinary controls instead. The bands also pause on hover or keyboard focus.

Known issues

What we are less than certain about.

This list is the honest part of an accessibility statement and the part most sites leave out. We know of nothing here that fails the standard outright, but these are the edges of what we can vouch for. If you hit something not listed, we would genuinely like to know.

Things we do not control

The promo films play in YouTube's embedded player. We control the frame, the muting, the autoplay behaviour and the pause and sound controls beneath it, and we have published captions describing the audio and a written description of each film. What we cannot change is the player's own internals, so if you open it out to YouTube you are in Google's interface rather than ours.

The same applies to the third-party booking page behind our "Book a call" links. If either gets in your way, email us and we will find another way to get you what you need.

Testing coverage

Our checks so far have been structural and programmatic: contrast ratios computed across the palette, heading order and alternative text verified across every page, language attributes checked, keyboard focus behaviour reviewed, and reduced-motion paths exercised.

What we have not yet done is a full screen-reader pass with VoiceOver on every page, or tested this site with Switch Control and Voice Control the way we would for a client app. That is the honest limit of the claim above: it is well-founded rather than proven, and if a screen reader makes a mess of something here we would rather hear it from you than not.

Report a problem

If something here does not work for you, tell us and we will fix it.

Email hello@itch.studio with the page and what went wrong, in whatever detail suits you. What you were using helps, if you know it, but do not let not knowing stop you writing. We aim to reply within two working days and to tell you either when it is fixed or why it will take longer.

If you need something on this site in another format, ask and we will send it to you.

Preparation

This statement was prepared on 3 August 2026 and describes the site as it stood on that date. It was written by Itch Studio Ltd based on our own review of the site. We revisit it whenever we make a substantial change, and at least once a year.

Who we are

Itch Studio Ltd, Suite RA01, 195-197 Wood Street, London, E17 3NU, United Kingdom. Registered in England and Wales, company number 14729010.