Last reviewed: [REVIEW DATE].
Our commitment
Mechanics use this site on a phone, outdoors, in gloves, often in a hurry. Accessibility is not a separate concern from that — it is the same concern. We build this site so that it can be operated by keyboard alone, read by a screen reader, used at high zoom, and seen in sunlight.
Conformance target
We build to WCAG 2.2 Level AA and we claim conformance to WCAG 2.1 Level AA.
[CONFIRM] §7.13 item 11 — whether to claim 2.2 AA as the conformance level rather than build to it. 2.2 is a superset of 2.1, and its added criteria (focus appearance, dragging alternatives, target size, redundant entry, accessible authentication) are cheap when designed in and expensive to retrofit, which is why we build to them.
Conformance status
[FULLY / PARTIALLY] conformant. [STATE HONESTLY. A partially conformant site that says so is in a far better position than one that overclaims — an overclaim is itself evidence.]
Known limitations
[LIST EACH KNOWN FAILURE, THE PAGES IT AFFECTS, THE WORKAROUND, AND THE DATE IT WILL BE FIXED. An empty list here is not credible; if the list is genuinely empty, say when the assessment that emptied it was done.]
- Caution badges and alerts (amber on pale amber) measure 2.45:1 against a 4.5:1 requirement. Affects lead-time, backorder and warning labels across the site. The text always repeats information available elsewhere on the page, so no information is lost, but the labels are hard to read. The fix is a one-word change to the shared badge component and a text-weight amber token that is already defined. Fix planned [DATE].
- [ADD ANY FURTHER KNOWN FAILURE HERE, WITH THE PAGES IT AFFECTS, THE WORKAROUND, AND A DATE.]
How we test
- Automated checks on every build: JSX accessibility linting, a repository-wide accessibility scan, and a contrast assertion over the color pairs the site actually uses. Automated testing catches roughly a third of accessibility problems, and we treat that number honestly rather than as coverage.
- A manual keyboard pass with the mouse unplugged, covering: find a kit through the parts finder, read the kit contents, add to cart, check out as a guest, create an account, open a support ticket with an attachment, change cookie preferences, and submit a privacy request. Any step that cannot be completed by keyboard blocks the release.
- A screen reader pass with [VoiceOver / NVDA] over the parts finder, the diagram and kit contents table, and the checkout.
- Re-tested whenever the finder, the diagram viewer or the checkout changes.
Specific things we have done
- The parts finder works as ordinary links and real form controls, and every step has a real URL you can bookmark, share, or reach without JavaScript.
- Every exploded-diagram hotspot has a matching row in the kit contents table, and that table is always rendered — it is never hidden behind a "view as table" toggle. A diagram is never the only route to a part number.
- Dimension and specification tables use real table headers with scope, and captions.
- Every interactive element has a visible focus indicator and a target at least 44 by 44 pixels.
- Form errors are announced, linked to their field, listed in a summary at the top of the form, and never signalled by color alone.
- The cookie banner is a proper dialog: focus moves into it and back out, Escape closes it and is treated as "reject non-essential", and it never traps a keyboard user.
If something does not work for you
Tell us and we will fix it, and we will help you complete what you were doing in the meantime.
- Email: [ACCESSIBILITY EMAIL]
- Phone: [ACCESSIBILITY PHONE]
- Post: [MAILING ADDRESS], marked "Accessibility"
- Named contact: [ACCESSIBILITY CONTACT NAME, TITLE]
We respond within [N, typically 2] business days. We will tell you what we found, what we are going to do, and when.
Ordering another way
If any part of this site prevents you from completing an order, call [SUPPORT PHONE] or email [SUPPORT EMAIL] and we will take the order, identify the kit from your measurements, and arrange payment and delivery. This route is available for any reason, costs the same, and you do not have to explain why you are using it.
Formal approval
This statement was prepared on [DATE] following [SELF-EVALUATION / THIRD-PARTY AUDIT BY [AUDITOR]]. The evidence — the dated automated reports and the signed manual keyboard and screen-reader passes — is held by [ACCESSIBILITY CONTACT NAME].