Accessibility

The standard we work to

We target the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as our benchmark. We do not claim to meet it in full, because parts of this site have not been tested the way a conformance claim requires. The known gaps are listed further down, in detail, rather than summarised away.

What is built in

What the markup and the stylesheet actually do:

• Skip to content. Pressing Tab on a fresh page offers a "skip to content" link first, so you can jump past the navigation straight to the page itself.
• Standard page structure. Headings are properly nested, with one main heading per page, and lists and specification tables are built as real lists and tables rather than as text made to look like them. Controls are real buttons and real links. Product cards can also be clicked anywhere as a mouse shortcut; the keyboard route to the same thing is the "Full specifications" control inside the card.
• Keyboard focus is always visible. A two-pixel outline with an offset, and a lighter ring on the dark sections so it stays visible on both grounds. Nothing removes the focus indicator.
• The request drawer is keyboard-operable. Focus moves into it when it opens and returns to whatever you were on when it closes, Escape closes it, and Tab cycles within it.
• Specification sheets open in a native dialog, so the focus trap, Escape handling and the inert background behind it come from the browser rather than from our own code.
• Specifications work without JavaScript. Underneath the dialog they are a native expand-and-collapse element, so all 237 specification rows are reachable, keyboard-operable, and present in the page even with scripting turned off.
• Every image has alternative text, and the product images carry width and height so the layout does not jump as they load.
• The form is properly labelled. Every field has a real label tied to it, required fields are marked in text and not by colour alone, error messages are linked to their field and the field is marked invalid, the error summary is marked as an alert, and focus moves to the confirmation after sending.
• Colour contrast. Text and background pairs were measured rather than eyeballed. Body text runs from 5.57:1 upward against a 4.5:1 requirement, and the focus ring measures 4.09:1 on dark grounds against a 3:1 requirement. Where a pair was found short — a link hover colour and the form's placeholder text — it was corrected rather than disclosed.
• Reduced motion is respected. If your device asks for less motion, transitions and animations are effectively removed.
• Zoom is not blocked. Nothing on this site prevents pinch-zoom or scaling.
• Controls are large enough to hit. Every button meets the 24-by-24-pixel minimum that WCAG 2.2 asks for, which is stricter than the 2.1 level we target. The two close buttons are 40 by 40.

How the site is built

It is static HTML with one stylesheet and one script — no framework, no component library, and nothing that rewrites the page after it loads. Accessibility here comes mostly from using the right element in the first place, which is more durable than adding attributes afterwards.

Checking so far has been code review and measurement: contrast computed for every text and background pair, keyboard paths traced through the drawer and the dialog, and the markup checked for labels, landmarks and heading order. That is real, and it is not the same as testing with assistive technology.

Known limitations

Stated plainly, because a list of features without a list of gaps is not useful to anyone deciding whether they can use this site:

• No formal screen-reader testing. The site has not been tested end to end with VoiceOver, NVDA or JAWS. The markup is built to work with them; that is not the same as having confirmed it does.
• Not tested at 400% browser zoom. The layout reflows to a 320-pixel-wide viewport without horizontal scrolling, which is the measurement that matters most, and it survives increased text and letter spacing without clipping. Behaviour at 400% zoom on every page has not been checked.
• The request list and the form need JavaScript. Everything else on the site, including all the specifications, works without it. If scripting is off or fails, the form tells you so and gives you the phone number instead.
• The form uses Cloudflare Turnstile to keep spam out. It is a third-party control and its accessibility is Cloudflare's. If it stops you completing the form, call us and we will take the details over the phone.
• Typefaces are served by Google Fonts, a third party whose delivery we do not control. If they fail to load, the site falls back to your system font and remains readable.
• No independent audit. Nothing here has been reviewed by a third-party accessibility specialist.
• These are the next items on the list, not a settled state. Screen-reader testing and an independent review are what this page is measured against. When either happens, this page changes and the review date at the top moves with it.

Tell us about a problem

If something here is in your way, tell us. We will get you the information another way straight away, and look at fixing what got in your way. This is the fastest route to someone who can act on it.

Call (305) 767-4621. If a voice call is not a route you can use, dial 711 to reach us through the free telecommunications relay service, which handles the call in text on your side and speech on ours. You can also send a request through the quote form and describe the problem.

We are a small operation, so we are not going to promise you a turnaround we might not meet. What we will do is give you the information another way while we look at fixing the thing that got in your way.

You never have to use this site to buy from us. Everything on it can be done by phone.

Review

We review this statement when the site changes. The published and last-reviewed dates are at the top of this page.

More

See also the Privacy Policy and the Terms & Conditions.