Every control on this parts catalog works without a mouse

Our aim is to meet Web Content Accessibility Guidelines 2.1 at level AA across the catalog, the configurator, and every form. In practice that means every link, button, tag and form field carries a visible label rather than relying on an icon alone, focus is always visible with the amber outline you can see if you tab through this page right now, and headings run in a single logical order down each page so a screen reader's heading list matches what a sighted visitor would read.

The horizontal rail of category photographs on the homepage responds to the arrow keys and to Tab as well as to drag and scroll, and it collapses to a plain vertical stack of the same six photographs automatically if your system is set to reduce motion. The configurator's sliders, checkboxes and steppers all carry their own text label, not just a placeholder, and the live summary panel updates are announced through the page rather than only shown visually.

Long fitting-spec tables on a category page, such as the blade-size table on the clipper blades page, scroll horizontally inside their own frame on a narrow phone rather than resizing the whole page; that frame is keyboard-focusable and scrolls with the arrow keys once focused, but we know a table that scrolls at all is not as good as one that never needs to.

The support chat widget is a live, moving region. We keep new messages announced politely rather than interrupting whatever you are doing, but a very fast back-and-forth conversation can still be a lot for a screen reader to read out in order. If that happens, closing the widget and using the inquiry form on the contact page gets you the same answer without the pace.

Before a page is published we tab through it end to end, check it with a screen reader, and zoom the browser to 200% to confirm nothing overlaps or gets clipped. We do not claim to have covered every combination of browser and assistive technology in existence, and a device or setting we have not tested against can still surface a problem we have not seen.

We do not claim any third-party accessibility certification for this site, because none has been issued to us, and this statement should not be read as one.

If a page, the configurator, the horizontal rail, or either form gets in your way, tell us the page, what you were trying to do, and the browser or assistive technology you were using. We read every report ourselves; this is a six-person shop, not a queue behind a support desk.