Read this as a boundary, not a launch claim.
Current web tools are browser-only. Any release, commercial, server, account or external-service capability remains deliberately disabled until its evidence and owner decisions exist.
Automated evidence
Every production build checks all generated pages for one H1, sequential headings, named navigation landmarks, labelled form controls, named links and buttons, image alternatives, natural focus order, internal fragments and public-index metadata. Lighthouse is recorded separately because automated checks cover only part of accessibility.
Keyboard and display modes
No journey requires dragging, pointer-only input or WebGL. Interactive controls use visible focus; anchored sections reserve scroll space; reduced-motion and forced-colour preferences receive explicit CSS handling.
Files and results
File controls have text labels. Result panels are focusable selectable text; a separate short status region announces success, review or error without reading a potentially large result aloud. Colour is not the only status signal.
Evidence boundary
Passing automated checks is not a WCAG conformance claim. Formal WCAG 2.2 AA review, representative assistive-technology testing and broader non-Chromium browser evidence remain publication gates.