Accessibility Statement

What this statement does and does not claim

This site has not been audited against WCAG by anyone, so it claims no conformance level. Saying "WCAG 2.2 AA compliant" without an audit behind it is a claim, and this is a demonstration site that is not entitled to make it.

What it can tell you is what was actually measured. An automated browser harness runs on every build (scripts/verify.mjs in the repository) and checks the items in the first list below. The items in the second list have not been checked by anybody.

Verified on every build

• Contrast. Text is sampled from the rendered pixels — over the particle field, over gradients, with everything composited — and must clear 4.5:1. It is checked in all four colour schemes, in light and dark, and in both the calm and storm states. The authored colour tokens are asserted separately, so a broken pair cannot pass by being clamped at runtime.
• Keyboard access. Every interactive element can be reached and operated by keyboard, in an order that matches the visual layout. Focus indicators are clearly visible and never removed.
• Skip link. A skip-to-content link is the first thing a keyboard user reaches on every page.
• Headings. Each page has one h1 and a heading structure that descends in order, so screen reader users can navigate by heading.
• Images. Meaningful images carry descriptive alt text. Decorative images are marked so screen readers skip them.
• Forms. Every field has a visible label rather than a placeholder standing in for one. Errors appear next to the field they relate to, are announced to screen readers, and focus moves to the first problem on submit.
• Reduced motion. The particle field freezes to a single static frame, every scroll-driven animation stops, all 3D transforms are removed and revealed content appears immediately — verified by reading the canvas pixels and the computed animation state, not merely by declaring a media query. The site also carries its own reduce-motion switch, which defaults to your system setting.
• Touch targets. Every control is at least 44 pixels tall, measured at a 320px viewport.
• No horizontal scrolling. Measured at 320, 375, 414, 768, 1024, 1280, 1440 and 1920 pixels across six page templates.
• Dark mode. The site follows your system preference and offers a manual toggle, with contrast verified independently in both themes.
• Zoom. Text can be enlarged to 200% without loss of content or function, and pinch-zoom is never disabled.
• Without JavaScript. All content, including every FAQ answer, remains readable if JavaScript does not run.

Not verified

Naming these matters more than the list above does.

• No screen reader testing. Nobody has run this site through VoiceOver, NVDA or JAWS. Landmarks, labels and aria attributes are written carefully, but written carefully is not the same as tested.
• No testing with disabled users. None at all.
• No formal audit. Automated checks catch a minority of accessibility problems. They cannot judge whether alt text is useful, whether a heading structure makes sense to somebody navigating by heading, or whether the storm-mode reordering is comprehensible when you cannot see the page change.
• The before-and-after slider. It is operable by keyboard through its range control, but the comparison itself carries information that is difficult to express non-visually. Both images carry alt text describing the condition of the tree; that is a mitigation, not a solution.

Tell us if something does not work

If any part of this site prevents you from doing what you came to do, we want to know. Email crew@tree1.thesamplesite.com or call (512) 555-0142 — both are demonstration contacts on a demonstration site. Tell us the page and what happened.

On a real version of this site, the right commitments to make here would be a response time you can actually meet and a way to complete the whole enquiry by phone. We are not putting numbers on either, because there is nobody at the other end to honour them.