Accessibility statement
This build is designed around semantic HTML, visible keyboard focus, a skip link, descriptive headings, alt text, labelled search controls, responsive layouts, reduced-motion respect and strong text/background contrast. The target is WCAG 2.2 AA-style good practice, although a formal claim of complete conformance should be made only after testing the deployed site with automated tools, keyboard navigation, zoom/reflow and representative assistive technologies.
How we apply this
The site avoids essential information that is available only through colour and does not require drag interactions, complex animation or a pointer-specific gesture. Images have explicit dimensions to reduce layout shift. Navigation remains usable on smaller screens, and catalogue filters are optional: every item also has a crawlable normal link and can be reached without JavaScript.
What must be verified
Accessibility is an ongoing operational responsibility. New packaging images should receive meaningful alt text, new forms should have programmatic labels and clear error messages, and any third-party widget should be evaluated before it is added. If a user reports an accessibility barrier, the operator should provide a monitored contact route and record the fix. The verified contact route is one of the business particulars still required before public launch.

