Accessibility

Built To Be Used By Everyone

An event should not be harder to book because of how somebody reads a screen or works a keyboard. Here is the standard we build to, what we have tested, and how to tell us when we have got something wrong.

Last updated: 2 August 2026. This statement applies to business.tickethaul.com and legal.tickethaul.com.

Our Commitment

We want every organiser to be able to use this website, however they browse it. That means the site should work with a keyboard alone, with a screen reader, at high zoom, with colours or spacing overridden, and without animation for anyone who finds movement uncomfortable.

Accessibility is not a feature we bolt on at the end. It is checked as the site is built, and it is checked again before anything is published.

The Standard We Work To

We build to the Web Content Accessibility Guidelines (WCAG) version 2.2, level AA. That is the standard referenced by public sector rules in the United Kingdom and the European Union, and the one usually applied to commercial websites in the United States.

We do not use an accessibility overlay, toolbar or widget. Overlays sit on top of a site and try to patch problems in the browser. They are unreliable, they interfere with the assistive technology people already use and have set up the way they like it, and they leave the underlying problems in place. We would rather fix the site.

What We Have Built In

  • Keyboard access throughout. Every link, button, menu and form control can be reached and operated with a keyboard alone, including the Solutions menu, which opens on focus rather than only on hover.
  • A visible focus indicator. Whatever you are currently on is marked with a high contrast outline, in yellow on dark surfaces and black on yellow ones, so it never disappears into the background.
  • Skip to main content. The first thing a keyboard reaches on every page is a link that jumps past the navigation, so you are not tabbing through the whole menu on each page.
  • Proper page structure. One main heading per page, headings in order without skipped levels, and header, main and footer marked up as landmarks so a screen reader can jump between them.
  • Colour contrast. Text meets the 4.5:1 ratio, and large text the 3:1 ratio, against whatever sits behind it.
  • Text descriptions for images. Every image carries a description, and images that are purely decorative are marked so a screen reader skips them.
  • Labelled form fields. Every field on the demo form has a visible label attached to it, and errors are described in words rather than by colour alone.
  • Target sizes. Buttons, links and checkboxes are at least 24 by 24 pixels, so they can be hit without fine motor control.
  • Reflow and zoom. Pages work down to 320 pixels wide, which is the same as zooming to 400 per cent, without scrolling sideways.
  • Text spacing. Line height, letter spacing, word spacing and paragraph spacing can all be increased without any content being cut off or overlapping.
  • Reduced motion. If your device is set to reduce motion, the scroll animations and counters do not run.
  • Self-hosted fonts. Typefaces are served from our own domain, so pages render without waiting on a third party.

How We Have Tested It

Every page on both sites has been checked against the criteria above, using automated testing built for this site alongside manual keyboard testing. We checked heading order, landmarks, colour contrast, image descriptions, form labels, target sizes, reflow at 320 pixels and behaviour under the WCAG text spacing overrides.

We have not yet commissioned an independent accessibility audit, and we have not yet completed testing with every major screen reader. Automated testing catches a good deal but not everything, so we are not claiming full conformance on the strength of it. Where we say something works, it is because we tested it.

Known Limitations

Being straight about this is more useful than a claim of perfection.

  • Screen reader testing is not complete. We have tested structure and labelling but not every page with NVDA, JAWS and VoiceOver end to end.
  • No independent audit yet. Our testing is our own. An external audit is planned.
  • Product screenshots. The interface images across the site are illustrations of the product. They carry text descriptions, but the detail inside them is not readable by a screen reader.
  • Linked sites. Where we link out to another organisation, we do not control their accessibility.

Tell Us About A Problem

If something on this site does not work for you, we want to know. It is more useful to us than almost any other feedback, because it tells us about a barrier we could not see.

Email legal@tickethaul.com. It helps if you can tell us the page, what you were trying to do, and what happened instead. Please also say what you browse with, for example a screen reader, keyboard only, or high zoom, if you are comfortable doing so.

We aim to reply within five working days. If we cannot fix something quickly, we will tell you what we are doing about it and give you another way to get the same result. If you need information from this site in a different format, ask us and we will provide it.

If You Are Not Satisfied

Please tell us first and give us the chance to put it right. If you are still unhappy, and you are in the United Kingdom, you can contact the Equality Advisory and Support Service, which handles complaints under the Equality Act 2010. If you are in the European Union, the enforcement route is set by your own member state. If you are in the United States, accessibility of commercial websites is dealt with under the Americans with Disabilities Act.

Our Details

Zo Republic Limited, trading as Tickethaul
167-169 Great Portland Street, London, W1W 5PF
Company number 16035320
legal@tickethaul.com