Accessibility statement

We want everyone to be able to use this website. It is built to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, and we test it against them. This page says what we check, what we know is not yet right, and how to tell us if something stops you doing what you came to do.

How accessible this site is

We aim to meet WCAG 2.2 level AA throughout. We have not yet had the site independently audited, so we do not claim full conformance — we describe below what we have actually checked.

How we check

• Automated checks with axe-core run against every public page, and against the booking flow, on every change we make. A change that introduces a failure does not ship.
• Colour contrast of our text and interface colours is measured against the WCAG thresholds, not judged by eye.
• The booking flow, the main menu and the process diagram are tested using the keyboard alone, without a mouse.
• Lighthouse accessibility, performance, SEO and best-practice scores are checked on every change.

Automated tools find only part of the problems real people meet, which is why we also test by hand and why we want to hear from you.

What works

• You can use every page with a keyboard, and the keyboard focus is always visible.
• A “Skip to main content” link is the first thing a keyboard or screen-reader user reaches on every page.
• In the booking calendar, available times are announced to screen readers as you move between days, and the countdown on a held slot is announced as it changes.
• The step-by-step process diagram is also a plain numbered list on smaller screens, and a labelled group of buttons on larger ones.
• If your device is set to reduce motion, animation is switched off and the automatic slideshow starts paused. You can pause or resume the slideshow at any time.
• The site works at 200% zoom and on a phone screen without sideways scrolling.

What we know is not yet right

• We have not had an independent accessibility audit.
• The booking calendar is built on a third-party component. We have tested it with the keyboard, but we have not yet tested it with every screen reader, and we do not control every detail of how it behaves.
• The spam-protection step on our forms runs automatically in the background, with nothing for you to solve. If it ever fails, the form tells you so and you can email us instead.

If you find something that is not on this list, please tell us — see below.

Tell us about a problem

If you cannot use part of this site, or you need information in a different format, email contact@ligosolutions.tech. Tell us the page, what you were trying to do, and what got in the way. If it is easier, you can also book a call from the booking page. We will reply as soon as we can and, where we can fix the problem, we will.

If you are not happy with our reply

If you raise a problem and are not satisfied with how we deal with it, you can contact the Equality Advisory and Support Service (EASS), which gives free advice and support on equality and discrimination issues in Great Britain.

Technical information

LiGo Solutions Limited aims for this website to meet WCAG 2.2 level AA. It relies on HTML, CSS, JavaScript and WAI-ARIA to work, and is designed to work with current versions of the major desktop and mobile browsers and with screen readers. We have not tested every combination.