Evidence

Most component libraries describe themselves as accessible and tested. This section is the attempt to publish the underlying measurements instead, including the ones that came out badly and those that have not been taken at all.

Everything here is generated from artifacts in the repository. Nothing on these pages is typed by hand, no state is rounded up, and no absence is hidden: a requirement nothing has measured renders as unrun, in the same table and with the same weight as a requirement that passed.

The catalogue, in one table

1662 evidence cells across 144 public components and 23 kinds of evidence.

State	Cells
pass	585
present	597
stale	22
excepted	17
unrun	441

Of those, 441 are unrun — nothing has measured them — and 22 are stale. Which cells, on which components, is on the capability matrix and on each component page.

The assistive-technology matrix is counted separately, and its number is 0 of 534: 89 components times 6 declared AT/browser pairings, of which 0 have been executed. See the AT matrix.

How to read a state

State	What it means
pass	A lane ran against this component and passed.
present	An artifact exists and is bound to this component. It exists; it is not a result.
stale	The artifact exists but predates the component's last change, so it describes older behaviour.
excepted	The requirement was waived, with a recorded reason that travels with the row.
unrun	Nothing has measured it. Not a pass, not a failure, not an oversight — an absence.

There is no state meaning "failed". That is a real limitation of the matrix schema rather than a claim that nothing fails, and where a measured failure exists it is published as its own record rather than squeezed into a cell that cannot hold it.

What this evidence is admissible for

It is locally qualified: produced by local runs on a developer machine, against a working tree carrying uncommitted work. That makes it useful for judging the library and useless as a compliance record.

It is not continuous-integration evidence — no gate in a pipeline produced any of it. It is not release evidence — nothing here is bound to a published version. It is not production evidence. Those are the distinctions the library refuses to blur, and they are printed on every page rather than confined to this page.

The pages

Page	What it holds
Capability matrix	Every evidence cell for every public component, by kind and by component.
Assistive technology	Every AT/browser pairing every component owes, and what has been run.
Accessibility conformance	The WCAG position, including the open gap.
Browser support	The engine lane, and what it does not cover.
Styling posture	Restyleable by contract, not unstyled.

Provenance

Every number on this page is read from a generated artifact at build time. The artifacts, and the SHA-256 of the exact bytes these pages were rendered from:

Artifact	sha256	Present
packages/core/docs/capability-matrix.json	e0b9aa1e5e03e020…	yes
packages/core/docs/quality-matrix.json	15fe628024cef1b5…	yes
e2e/at-matrix/index.json	d35ef2dfa049e253…	yes

Capability matrix sourceCommit 7f340779 · quality matrix 527dbd15.

Standing

Locally qualified. Not continuous-integration evidence, not release evidence, not production evidence. See what this evidence is admissible for.