Accessibility statement

What we build in

Accessibility is treated as part of the job rather than an afterthought, the same way torque is part of a hitch install. We work to these habits on every page, and we fix them when a review finds a gap.

• Text that scales without breaking the layout
• Color choices checked for readable contrast
• Images described with meaningful alt text
• Forms that can be filled with a keyboard

Where we may fall short

A hardware-heavy site carries tables of load ratings, fitment charts and part imagery, and those are the hardest things to make fully accessible. If a table does not read cleanly in your screen reader, or a caption is missing on a photo, that is a gap we want to know about rather than one we would rather not hear.

Telling us about a problem

If a page blocks you, send a short note through the contact form describing the trouble and the device or browser you used. You do not need the technical vocabulary; a plain description is enough. We will treat an access problem with the same seriousness as a safety one, because a reader who cannot use a page has been let down by it.

How we improve over time

We re-check pages as we add to the site, and each new guide or hub is built to the same habits as the last. When a reader reports a barrier, we note it and fix it in the next round of work rather than leave it standing. Accessibility is a maintenance job, not a one-time badge, and it gets the same attention as the hardware we fit.

A note on this statement

This statement is written in plain language on purpose, because a policy a reader cannot parse is its own kind of barrier. It describes our intent and our practice rather than a certification we claim. If you want to know how a specific page performs, ask and we will tell you what we know rather than what sounds best, and if a fix is needed we would rather hear about it than assume the page is fine.