Last updated
Our target
We are building this site to WCAG 2.2 Level AA, and treating it as a design requirement rather than a late audit. Accessibility decisions are made in the components themselves: native controls before ARIA, focus states that are more visible than hover states, and no information carried by colour alone.
What that means in practice
- Every interactive control works by keyboard, and focus is visible and restored correctly after menus and dialogs close.
- Text meets a 4.5:1 contrast ratio, and interface boundaries meet 3:1. Contrast is asserted by an automated test that fails the build rather than being checked by eye.
- Nothing essential depends on animation. If you have asked your system to reduce motion, movement is removed and no content is hidden as a result.
- The site works without JavaScript. The navigation, the forms, the disclosures and the size selector all function; JavaScript only makes them smoother.
- Data tables use real table semantics with captions, header cells and units, and scrollable tables can be scrolled with the keyboard.
- Images have alt text written for the image, and captions written for the context. They are separate on purpose.
- Forms have persistent labels, programmatic error messages, an error summary that links to each field, and a minimum 16px input text so mobile browsers do not zoom.
What we have tested
Automated accessibility checks run against every page at five viewport widths, including a 320 CSS-pixel reflow, as part of the build. A build that introduces a violation does not pass.
Known limitations
Listed here rather than left for you to discover.
- Screen-reader testing is not complete. Automated tools are a floor, not a ceiling. Manual passes with VoiceOver on Safari and iOS, and TalkBack on Android, have not all been completed. Until they are, we do not claim full conformance.
- Third-party documents. Certificates and laboratory reports issued to us as scanned PDFs are not accessible documents. This is why we publish the information as HTML records instead, and treat any PDF as a supporting download rather than the primary version.
Tell us about a problem
If something here does not work for you, please email contact@kudukoliwaters.com with the page address and what happened. You do not need to know why it is broken or use any particular terminology.
We aim to acknowledge within two business days and to tell you either how we have fixed it or when we will. If something blocks you from contacting us about supply, tell us what you needed and we will deal with the enquiry directly at the same time.