Good design should let you in.

Our approach

We use established WCAG principles to guide structure, contrast, interaction and reading. Our current checks include automated WCAG 2.0/2.1 A and AA rules and targeted keyboard testing. We do not claim that every page, assistive technology or third-party service is fully conformant, or display a certification badge that has not been earned.

Navigation and reading

Links, buttons, filters and forms are intended to be keyboard usable. The mobile menu returns focus to its trigger when closed with Escape. Dialogs have named controls and return paths. Long policy pages have a contents list and section anchors; core reading remains available without JavaScript.

Motion, sound and display choices

The site respects reduced-motion preferences and offers a visible motion control. The homepage has a still fallback when a renderer is unavailable. The sound demo is silent until you press Play, plays one loop and can be stopped; changing tabs stops it. No microphone access or recording is requested.

Forms and practical controls

Form steps announce their headings through focus, and validation identifies a field needing attention. Information is retained on a failed delivery so it can be corrected or downloaded. Currency and language are independent choices. A test receipt is clearly distinguished from a confirmed live enquiry.

Known limitations and testing scope

The current evidence comes primarily from desktop and mobile-sized Chromium automation and targeted keyboard/visual review. It is not a physical iPhone/Safari test or a comprehensive screen-reader study. Some interactive demos require JavaScript; their explanatory content remains available. The original cultural graphics and motion may not convey identical detail to every visitor.

Tell us where the experience breaks

A useful report describes the page, what you tried to do, what happened instead, and any browser or assistive-technology detail you are comfortable sharing. Do not include passwords or sensitive personal records. The verified contact route will be displayed when approved; the local test form is not a monitored support inbox.

We will use reports to prioritize repairs and discuss a practical alternative where possible. No universal response deadline or completed certification is promised by this preview statement. Before public release, the statement and feedback route need operator approval.