Commitment
This site is a reading and enquiry tool. If a buyer cannot read a guide, operate the quote form with a keyboard, or understand an error message, the site has failed at its main job. We treat accessibility as part of editorial and engineering quality, not as a separate feature.
The site is designed and built to be used with a keyboard, a screen reader, browser zoom, and reduced-motion settings. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA for the pages we control.
Conformance target
Our working target is WCAG 2.2 Level AA. This statement describes the current build; it is not a certification, and it does not claim that every page has passed a formal third-party audit.
The site is checked with a combination of automated tooling, manual keyboard testing, zoom and reflow checks, and review of color contrast and form behaviour. Checks are repeated when a page template or shared component changes.
What we have done
- Semantic landmarks, a skip link, and a single visible
h1on each page. - Visible focus styles for links, buttons, form fields, and the table wrapper.
- Text and interface colors checked against WCAG AA contrast targets.
- No information conveyed by color alone; labels and text accompany status and error states.
- Form fields with programmatic labels, field-level errors, and an error summary that receives focus.
- Reduced-motion support: reveal animations are skipped when the visitor prefers reduced motion.
- Responsive layout that reflows at 320 CSS pixels without horizontal scrolling for normal reading content.
- Alternative text or
aria-hiddentreatment for decorative graphics and woven swatches; catalogue reference photos carry descriptive alternative text and a visible Ref. photo label. - Data tables with captions and header scope, wrapped in a focusable scroll region.
- No autoplaying media, no flashing content, and no time limit on reading a page.
Keyboard and navigation
The site can be navigated with Tab and Shift + Tab. The first focusable element is a “Skip to content” link. Menus, accordions, and form controls use native elements where possible, so they follow the browser’s expected keyboard behaviour.
The mobile menu button exposes an expanded state, and the quote form’s step controls are ordinary buttons. If a control cannot be reached or operated with a keyboard, that is a defect; please report it using the route below.
Content and forms
Headings follow a logical order. Link text describes the destination rather than saying “click here”. Tables are used for data, not layout. Images that carry meaning have alternative text; decorative swatches are hidden from assistive technology.
The quote form marks required fields, links errors to the affected field, and keeps a visible summary of what happens next. If JavaScript is unavailable, the form presents all fields and submits to the server endpoint; the interactive step flow is an enhancement, not a requirement.
The 12-point supplier checklist uses native checkboxes and stores progress in local browser storage. It can be printed or saved as a PDF. A reset control clears the stored ticks.
Known limitations
- Automated checks cannot detect every barrier; some issues may remain until a person encounters them.
- Third-party content, such as WhatsApp or an external analytics dashboard, is outside our direct control.
- PDF files supplied by a third party may not be tagged or readable in a screen reader. Where we create a document, we aim to provide an accessible HTML alternative.
- Translations are not currently offered. The site is written in English.
Feedback
If something blocks you, tell us the page, what you were trying to do, and the browser or assistive technology you used. Use the contact form and put “Accessibility” in the message. We will acknowledge the report and tell you what we can fix.
If you need a guide or policy in another format, ask through the same route. We will provide a reasonable alternative where we can.
Third-party content
WhatsApp, Cloudflare Turnstile, and analytics providers have their own interfaces and accessibility characteristics. Where a third-party control is essential to a task, we aim to provide an alternative route. For the enquiry form, the form itself is the primary route; WhatsApp is an option, not a requirement.