Clear structure
Headings, landmarks, labelled controls and a skip link help people understand and navigate a page.
Readable content and usable controls
Accessibility.
People should be able to find information and use the controls. This page explains our approach, the checks recorded and the testing still required.
The approach
Information people can use.
Accessibility starts with the audience and continues through design, content and testing. This website does not claim verified WCAG conformance.
Readable layouts
Short explanations, suitable text sizes, contrast checks and responsive layouts support reading on different screens.
Keyboard and motion choices
Visible focus supports keyboard navigation. Motion controls and reduced-motion preferences offer a quieter experience.
Checks with a defined scope
Links, layouts and interactions are checked against the task. Findings are recorded alongside testing limitations.
Recorded checks
What has been reviewed.
Latest recorded review: 11 October 2026. The current HODRA preview was reviewed in local Chromium. All 26 HTML pages passed structural checks, and the company pages and case studies were checked at 320, 390, 862 and 1440-pixel widths. Keyboard menus, brand-letter controls, demo previews and focus return were exercised. Enquiry validation, reviewed email links, edited-draft safeguards and copy/downloads were checked without sending a live form or opening a mail app. All six fictional demonstrations were exercised, including the locally loaded 3D car, service cards, quiz, filters and planners. Defined text-contrast pairs were checked. This is a bounded browser review, not full accessibility conformance or a production-speed measurement. Phone widths were emulated; physical devices, Safari, Firefox, real screen readers and a full WCAG assessment remain outstanding. The capability PDF is untagged; an equivalent HTML statement is available.
The capability PDF is not tagged for accessible PDF reading. Equivalent service and demonstration information is available in the HTML capability statement.
Recorded checks cover only their stated edition and scope. Later changes need their own review; a previous review does not establish their conformance.
Browser checks and screen-size emulation do not replace testing with people, assistive technology and physical devices.
If something is difficult to use.
Record the page, task, device and browser, and explain what prevented you continuing. Avoid including sensitive information. Use the contact form or contact email inbox to report an accessibility issue.