Accessibility Statement

No conformance claim

This site does not claim WCAG conformance at any level. No formal audit has been carried out against WCAG 2.1 or 2.2, and no screen reader testing has been done. A conformance claim means an audit happened; saying it without one is the same kind of unearned badge as a fabricated certification, and this site does not print those either.

What follows is the list of things that were measured, and how.

Measured, in a browser, on the built site

The checks below run against the deployed output in a real browser engine, not against the source. The harness is in scripts/verify.mjs, and every check in it has been proved to fail when the mechanism it guards is deliberately broken.

• Text contrast on composited pixels. Sampled from rendered screenshots rather than declared colours, and cross-checked against the authored colour pair. Body text is required to clear 4.5:1 and large text 3:1, in both themes and in all four colour schemes. A scheme that could not pass in both is not offered.
• No horizontal overflow at 320, 375, 414, 768, 1024, 1280, 1440 and 1920 pixels, across 21 pages, measured as scrollWidth — the site does not set overflow on the body, which would hide overflow from that measurement rather than fix it.
• The largest text size survives 320px. The text-size control in the kit panel is set to its largest step and the overflow check is run again.
• Reduced motion genuinely stops motion. The drifting light in the hero is sampled twice, 600 milliseconds apart, and must be bit-identical. Every scroll-driven animation must report no timeline. Nothing may be left invisible.
• The kit panel is focus-trapped, closes on Escape, and returns focus to the control that opened it.
• Every page has exactly one h1, a title, and a meta description.

Built in, but not independently verified

• Keyboard access. Every interactive element is a real button, link, input or <details> rather than a div with a click handler, so keyboard operation comes from the element itself. Focus indicators are never removed.
• Skip link. First focusable element on every page.
• Forms. Every field has a visible label, not a placeholder standing in for one. Errors appear beside the field, are announced, and focus moves to the first problem on submit.
• Images. Meaningful images carry descriptive alt text; decorative ones are marked so screen readers skip them.
• Touch targets are at least 44 by 44 pixels.
• Without JavaScript, all content remains readable, including every FAQ answer and the whole emergency guidance section. The accordions are built on <details> and work with no script at all.
• Zoom to 200% is supported and pinch-zoom is never disabled.

The controls in the kit panel

The panel on the left edge of every page carries five accessibility controls, each wired to a real mechanism rather than a badge: three text sizes, a high-contrast mode, reduce motion, underline every link, and a plainer typeface. Reduce motion starts switched on if your device already asks for it.

Known limitations, named rather than hidden

• No screen reader testing has been done. The markup is semantic and labelled, but that is not the same as somebody having driven it with NVDA or VoiceOver.
• The before-and-after comparison is operable by keyboard through its range control, but the comparison itself conveys information that is hard to express non-visually. Both photographs carry full alt text describing the condition of the tree.
• The trunk gauge and the season dial both present their answer as text as well as as a drawing, but the drawings themselves are not described in detail to a screen reader beyond their titles.
• This is a demonstration site. There is no organisation behind it to receive a complaint or act on one.

If something does not work

On a real site this is where you would find a monitored address and a response commitment. This one is a demonstration, so the contact details are illustrative: crew@tree2.thesamplesite.com and (512) 555-0142, a number inside the range reserved for fiction.