Editorial policy

One question, answered first

Each page answers one implementation question in its opening paragraph, then shows a complete original example and walks through the cases that usually break. Every page ends with what it does not cover and its sources.

Original work only

Explanations, examples and test pages are written new for this site. We do not reuse prose, code, images or data from earlier sites at this domain; owning a domain is not a licence to old content. We quote primary documentation briefly and with attribution.

Documented, observed or unknown

We keep three kinds of statement apart. A vendor’s documentation establishes what the vendor documents. A behaviour we report comes from a test page we publish, with the exact steps, browser version, operating system and date. Anything we did not run stays “not tested”. Expected behaviour is never reported as observed, and simulated input (for example emulated touch or a simulated reduced-motion setting) is labelled as such.

A keyboard pass, an automated scanner result or a documentation reference is not an accessibility certification. We make no compliance claims.

AI assistance and responsibility

Pages are drafted with AI assistance. The publisher is responsible for every page: claims are checked against their sources and test pages before publication, and errors are corrected in public as described in corrections.

Review

Independent technical review by a named frontend engineer is being added. A reviewed page shows the reviewer’s name, credential and review date. Reviewers must be independent of any sponsor on the page.