Accessibility

We want everyone to be able to use the FleetFixer platforms (Maintenance, Learn, and Race), whatever their ability and however they access the web. We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA across our public website and our applications.

We also aim to make reasonable adjustments for people with disabilities, in line with our duties under the Equality Act 2010. Accessibility is something we keep working on as we build new features, so this statement describes where we are now and where we are heading.

In our day-to-day design and development work we aim to provide:

• Keyboard navigation, so the main features can be used without a mouse or touchscreen.
• Semantic structure, with headings, landmarks, and lists that assistive technology can interpret.
• Clear labels on form fields, buttons, and other controls.
• Alternative text for images that carry meaning.
• Resizable text that stays readable when you zoom or increase the font size.
• Sufficient colour contrast between text and its background.

Accessibility is an ongoing effort, and some parts of our platforms are still being improved. Areas that may not yet fully meet our target standard can include richer interactive components, data tables, charts, and media such as video.

Where you meet a barrier, please tell us using the details below. We treat that feedback as a priority for fixing, and we can often provide the same information or service in another way while we work on a longer-term fix.

If you find something hard to use, or you need information in a different format, email us at accessibility@fleetfixer.io. It helps if you tell us:

• The web address (URL) of the page, or where in the app the problem is.
• What you were trying to do.
• The browser, device, or assistive technology you were using, if you know it.

We aim to respond within 30 days. If you are not satisfied with how we have handled your request, please let us know so we can try to put it right.

Some parts of our platforms rely on components, fonts, or services provided by other organisations, and embedded content from those vendors may behave differently from the rest of our site. We do not always control how that content is built.

Where we have a choice, we aim to select vendors that have their own accessibility commitments. If a third-party component is causing a barrier for you, please still get in touch, because we can usually find an alternative way to help and raise the issue with the supplier.