Accessibility statement

We want everyone to be able to use this website, and we build and test it to WCAG 2.2 Level AA.

Last updated 8 October 2026

Hatcha (“we”, “us”) is a software development company. Building accessible websites is part of our craft, so we hold our own site to the same standard. This statement explains our goals, what we do to meet them, and what to do if you run into a barrier.

Our commitment

We want people with a wide range of abilities, using a wide range of assistive technologies, to be able to read, navigate and use this website. That includes people who use screen readers, keyboards only, voice control, magnification or high-contrast settings. Accessibility is part of how we design, build and review every page, not an afterthought.

Conformance target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. These guidelines are published by the World Wide Web Consortium (W3C) and are widely used as the benchmark for accessible web content. We work towards this target continuously, and we can’t promise that every page is perfect at every moment.

What we do

We take these measures to make the site accessible:

  • Semantic HTML. We use proper headings, landmarks, lists, buttons, links and form labels so assistive technology can understand the structure of each page.
  • Keyboard navigation. All interactive elements can be reached and used with a keyboard, in a logical order, without getting trapped.
  • Visible focus states. When you move through the page with a keyboard, a clear indicator shows where you are.
  • Colour contrast. We choose text and interface colours to meet the WCAG contrast requirements, and we don’t rely on colour alone to convey meaning.
  • Reduced motion. We respect the reduced-motion setting on your device and limit or remove animation when you ask for it.
  • Text alternatives. Meaningful images have descriptive alt text, and purely decorative images are hidden from assistive technology.
  • Testing. We use automated tools such as axe and Lighthouse, and we also check pages by hand with keyboard-only navigation and screen reader testing, because automated tools catch only part of the picture.

No accessibility overlays

We don’t use accessibility overlay widgets or plugins that claim to fix a site automatically. They often interfere with the assistive technology people already use. We fix issues in the code itself instead.

Known limitations

One part of the experience is provided by a third party, and we don’t fully control its accessibility:

  • Google Calendar booking page. The “Choose a time” buttons on our contact pages take you to an appointment page operated by Google.

If it doesn’t work for you, you don’t need to use it. Email us at hello@hatcha.com and we will arrange a call or continue the conversation by email instead.

We may also have missed an issue on a page of our own. If you find one, please tell us.

Feedback and help

If you have trouble using any part of this site, or you’d like content in a different format, please email us at hello@hatcha.com. Tell us the page address, what you were trying to do, and what got in the way. If you use assistive technology, it helps to know which kind and which browser, though it isn’t required.

We aim to respond within one working day. We take every report seriously and will work with you to find a solution or an alternative way to get what you need.

See our privacy policy and terms and conditions, or visit our contact page.