Accessibility · What we aim for

Accessibility

Last reviewed: 29 September 2026

This page sets out what we aim for, what we know is not yet right, and how to ask us for an adjustment if something does not work for you. It is a statement of aims, not a certificate. We have not commissioned an independent accessibility audit, and this page does not claim one.

1. What we aim for

We work towards the Web Content Accessibility Guidelines 2.2, in plain words: content people can perceive, controls people can operate, wording people can understand, and a site that works with the tools people use to reach it.

We work towards the Web Content Accessibility Guidelines 2.2 at level AA. We have not yet had an independent audit, and we do not claim a conformance level. This is an aim we are building toward, not a badge we have earned.

In plain words, that means four things. Perceivable: text and images should be readable, including with a screen reader, and colour should not be the only way information is shown. Operable: everything you can do with a mouse, you should also be able to do with a keyboard, and moving parts should respect a request to reduce motion. Understandable: pages should read in plain English, labels should say what they mean, and forms should tell you clearly when something is wrong. Robust: the site should work with the browsers and assistive tools people actually use, not just the ones we test on ourselves.

Both of our codebases already carry real accessibility work: labelled form fields, keyboard focus styles, a "skip to content" link, motion that can be turned down on most of the site, and a page language set for screen readers. That work is not complete and it has not been independently checked. It is progress toward the aim above, not a finished claim.

2. What we know is not yet right

One thing we already know is not right is named below, with two more that were named here and have since been fixed. We have not audited every page beyond them and we expect other gaps. Tell us what you hit and we will look at it.

On the booking page, the searching animation did not respect a device's reduced motion setting. A fix shipped to the platform on 29 September 2026. We have not yet been able to read it on a live booking page, so we do not call it fixed here. If you have asked your device to reduce motion and that animation still plays for you, please tell us and we will chase it.

Two other problems were named on this page and have since been fixed. The opening animation now respects a request to reduce motion, and the card details field on the booking form is now linked to its label, so a screen reader reads out the deposit amount with it. We have left this note here rather than delete the record quietly.

Beyond that one, we have not run a page-by-page accessibility audit across the website or the platform, so we cannot give you a complete list of what is wrong. We have not tried to hide behind that: it is the honest position, and it is why this page asks for an aim rather than claims a standard. If something does not work for you, whether that is a form field, a colour that is hard to read, a page that fights your screen reader, or anything else, please tell us. A real problem you report gets looked at. A gap nobody has told us about is a gap we cannot fix.

3. Ask for an adjustment

If part of the site or a booking page does not work for you, tell us how you would like to use it and we will find a way: by email, by a phone call we arrange, or another way that works for you.

If part of the site, or a business's booking page, does not work for you, tell us how you would like to use it and we will find a way. We will take your details by email, or by a phone call we arrange, or another way that works for you: tell us which. Where it is a booking or a request for one of our business customers, we pass it to that business for you, because only the business can place a booking in its own diary.

If you do not yet have an account with us, or with the business whose page you are on, email hello@optitechautomation.co.uk. We aim to reply within two working days. That is an aim we hold ourselves to, not a promise enforced by any system, because a first email from someone we do not yet know has no case record behind it.

If you are a business owner or a worker with an account, use Talk to Cristian inside the app (Support in your menu). If you booked a job as a customer, email us. The in-app door writes down what you tell us the moment you send it, gives you a case reference straight away, and if you raise it as something not working, you get a real answer within 2 Business Days. It goes to one named person, Cristian Moise-Putanu, and our customer service process is built around making sure it is answered.

4. For businesses using our booking pages

If you are a subscribing business, your customers are covered by the Equality Act 2010 too, and a booking page we build for you is part of how you meet that duty.

If you are a business using OptiTech Automation to take bookings, the Equality Act 2010 requires businesses that provide services to make reasonable adjustments for disabled customers, and your booking page is one of the places that duty shows up. We build the page. We aim for the aims in section 1 above, and we fix what our customers and yours tell us is not working.

We cannot promise on your behalf that every adjustment a customer might need is covered, because some of that depends on how you run your business, not just on the page. If one of your customers asks you for an adjustment your booking page cannot make, the route in section 3 above is open to them as well, and we would rather know about it than have it go unanswered. This is general information about the law, not legal advice.

5. What this page is not

It is not an audit result, not a conformance certificate, and not a promise about every page. It is true on the date at the top.

This page describes an aim and the route to ask for help, not the result of an independent audit. We hold no accessibility accreditation and we do not claim one.

Accessibility work continues after this date. This page is true on the date at the top and we re-read it whenever something on it changes, including if we ever do commission an independent audit.

hello@optitechautomation.co.uk