Accessibility

Accessibility statement

How accessible cheap car tow is, the standard we work to, the alternative channels available, and how to report a barrier.

Editorial summary

Accessibility statement

Last reviewed
17 May 2026
Reviewer
cheap car tow editorial team
Reading time
~6 minutes

cheap car tow is a booking and price-publication service. The recovery itself is performed by an independent PAS 43 compliant operator dispatched at the published rate. See terms for the operator-panel arrangement.

Accessibility

Accessibility statement

section

Standard we work to

WCAG 2.1 at AA conformance. The Web Content Accessibility Guidelines are the international standard for web accessibility, and AA is the level the UK public sector aims for under the Public Sector Bodies Accessibility Regulations 2018. We apply the same standard to this private-sector site.

Testing happens at five breakpoints (sm, md, lg, xl, 2xl) and against three assistive technology pathways (screen reader, keyboard navigation, reduced motion).

insight

What we have done

Semantic HTML for every page: real headings, lists, tables, forms. ARIA only where the default semantics fall short.

Colour contrast verified against the WebAIM contrast checker. Text passes AA at 4.5:1 for body and 3:1 for large text; non-text contrast for interactive elements passes 3:1.

Keyboard navigation: every interactive element receives focus in a logical order and has a visible focus indicator.

Screen reader compatibility: tested with NVDA on Firefox and JAWS on Chrome.

Reduced motion: animations respect the prefers-reduced-motion media query.

by the numbers

Where we know we are not yet conformant

The booking form is a placeholder and the live form, when deployed, will be tested for accessibility separately. The placeholder fields carry labels and a logical tab order but the live form is what counts.

Some stock imagery is placeholder SVG; production photography will need the same alt text discipline.

Where we identify a barrier we list it in the public register below with a planned fix date.

the moment

How to report a barrier

Email hello@cheapcartow.co.uk with the page URL, your assistive technology setup, and a description of the barrier. The accessibility team replies inside three business days and includes a workaround where possible.

Where a barrier prevents you from booking a recovery, call the dispatch line; the dispatcher takes the booking by phone.

in the press

Alternative channels

If the website is not working for you, the dispatch phone line is staffed 24/7. The dispatcher can also book on the customer's behalf from notes provided by a third-party advocate.

The vulnerable customer policy describes the wider set of adjustments available; see the vulnerable customer policy.

Key takeaway · 06

Testing routine

Pre-release testing: every new page is checked against the WCAG 2.1 AA criteria before deployment. Tooling: axe-core, Lighthouse accessibility audit, WAVE.

Annual review: an independent accessibility review every 12 months. Findings feed the public register and the page update roadmap.

section

Public register of known issues

Issue: live booking form not yet deployed. Workaround: phone booking, dispatch line 24/7. Planned fix: before launch.

Issue: some stock imagery is placeholder SVG. Workaround: alt text on every placeholder. Planned fix: production photography in stages.

Issue: the magazine card visual variants rely on colour contrast for emphasis; tested at AA but a higher-contrast theme is being scoped for AAA conformance. Workaround: standard system contrast modes work. Planned fix: high-contrast theme in scope.

insight

Screen reader test results

Screen reader testing is run against two software combinations on Windows: NVDA on Firefox and JAWS on Chrome. Both are the dominant Windows screen readers in the WebAIM screen reader user survey. macOS VoiceOver on Safari is also tested. The latest pass results:

  • Page structure: headings nest correctly (one H1 per page, H2 for sections, H3 for sub-headings). The screen reader rotor lists headings cleanly. PASS.
  • Landmark navigation: header, main, footer and aside landmarks are announced. Breadcrumbs are an explicit nav with aria-label="Breadcrumb". PASS.
  • Link text: every link has descriptive text; no "click here" or bare URLs in body copy. PASS.
  • Alt text: every img has alt text; decorative images use empty alt or aria-hidden. PASS on the placeholder SVG set; will be re-verified when production photography lands.
  • Form labels: the placeholder booking form has explicit labels associated with each input. The live booking form will be re-tested separately.
  • Magazine card variants: the decorative drop cap, the quote ornament and the stat tile all carry aria-hidden so screen readers skip them and read the heading + body cleanly. PASS.

Issues found during testing are logged in the public register below with a planned fix date.

by the numbers

Keyboard navigation audit

Every interactive element on the site is reachable via keyboard. The tab order is left-to-right, top-to-bottom, matching the visual reading order. Focus indicators are visible on every interactive element (links, buttons, form fields, FAQ disclosure widgets) thanks to the :focus-visible outline rules in globals.css.

Specific keyboard interactions tested:

  • Header nav: Tab advances through the logo, the primary nav links, and the Book recovery button. On mobile the hamburger toggle is reachable; pressing Enter or Space opens the drawer; Tab continues into the drawer links.
  • FAQ accordion: each FAQ item is a details/summary pair. Tab focuses the summary; Enter or Space expands and collapses. The disclosure indicator (+/-) is decorative and aria-hidden.
  • Magazine TOC anchors: each section has an id (section-N) so future in-page TOC links can jump cleanly; scroll-mt-24 keeps the sticky header from covering the heading on landing.
  • Skip link: a skip-to-main-content link is on the roadmap; it is not yet shipped. Listed in the public register below.

The audit is repeated on every layout change and on the annual review cycle.

the moment

Reduced-motion and high-contrast mode support

The site respects the prefers-reduced-motion: reduce media query for the small number of motion effects in the design (the mobile-nav hamburger icon morph, the FAQ accordion open/close, the magazine card hover state where added). When reduced motion is requested the animations are skipped and the state change is instant.

High-contrast mode is not yet shipped as a dedicated theme. The default colour palette passes WCAG 2.1 AA contrast at 4.5:1 for body text and 3:1 for large text against the published background palette. Forced-colors mode (the Windows high-contrast setting) is respected by the browser default; bespoke high-contrast styles using prefers-contrast: more and forced-colors: active media queries are on the roadmap.

For users who require a different contrast or text size, browser-level overrides work: every browser exposes a minimum-font-size setting and most have a high-contrast extension or theme. The site does not block these settings.

in the press

Statutory basis

The Equality Act 2010 makes it unlawful to discriminate against people with disabilities in the provision of goods and services. The Public Sector Bodies Accessibility Regulations 2018 set the WCAG 2.1 AA standard for public-sector websites; we apply the same standard voluntarily.

If you are dissatisfied with our response to a barrier complaint, you can escalate to the Equality Advisory and Support Service.

Key takeaway · 12

Review and change history

First published 2026-05-17. The accessibility statement is reviewed every 12 months or sooner if the cited primary source changes. Material changes (new lawful basis, new escalation route, new scope) are added below with a date and a one-line reason. Editorial corrections (typo, broken link) are not logged here; the live page is the source of truth.

If anything in this accessibility statement reads as inaccurate, out of date, or unclear, email the editorial team at hello@cheapcartow.co.uk with the page URL and a description of the issue. The editorial team replies inside three business days; a material correction is published with a dated note in this section. External escalation routes (ICO, Trading Standards, Financial Ombudsman Service) apply where the relevant complaint is in scope for the regulator.

Primary sources cited on this page

Common questions

Frequently asked questions

What standard do you work to?

WCAG 2.1 AA. We test against the spec at five breakpoints and verify contrast against the WebAIM tools.

Can I use the site with a screen reader?

Yes. Semantic HTML structure underlies every page; ARIA is added where the default semantics fall short. Decorative elements carry aria-hidden.

Is the site keyboard navigable?

Yes. All interactive elements have a visible focus indicator and a logical tab order.

What if I find a barrier?

Email hello@cheapcartow.co.uk with the page URL and a description. The accessibility team replies inside three business days.

Is the booking phone line accessible?

Yes; the dispatcher can take a booking from a relay service or a third-party advocate. The vulnerable customer policy describes the adjustments.

Do you support text-only browsing?

Yes. Images carry alt text; the page is readable without JavaScript on all marketing pages (the booking form requires JS).

Need a recovery?

Published price, PAS 43 compliant operator, 24/7 dispatch.

Book recovery on the TowManVan app