Accessibility

What I aim for

This site, and every booking system I build, targets WCAG 2.2 Level AA. That is the standard US courts and regulators point at, and it is the one worth building to regardless.

What that means in practice

• Everything works by keyboard, in a sensible order, with the focus always visible.
• Text meets contrast minimums, and is not the only way anything is communicated — no state shown by colour alone.
• Real headings, real landmarks, real labels on every form field, so a screen reader gets a structure rather than a wall.
• Tap targets sized for a thumb, not a mouse pointer.
• Animation respects prefers-reduced-motion; if your system asks for less movement, the site stops moving.
• Light and dark both meet the same contrast bar, rather than one being an afterthought.
• Text resizes and reflows to 200% without losing content or function.

Where it falls short

Honestly: I test with a keyboard, with VoiceOver, with automated checks, and at reduced motion — but I am one person and I have not had this audited by a professional accessibility firm, so I will not claim conformance as a finished fact. Parts of the booking flow I hand off to third parties — Cal.com for scheduling, Stripe for payment — are built to their own standards, not mine.

If something does not work for you

Write to hello@21x.studio and tell me what you were trying to do and what got in the way. It comes straight to me. I will reply within two working days, and fix what I can fix quickly rather than adding it to a roadmap.

If you need something on this site in another form — the terms read out, a document sent differently — ask, and I will get it to you.

For clients

Your booking system is built to the same standard, and accessibility is not an upgrade or a line item. If a client of yours cannot book because of something I built, that is a defect and I fix it as one.