The conformance reports and accessibility claims vendors publish, dated and in one place.
For every platform the entities in the Record deploy, one product record: whether an accessibility conformance report is published, what it says criterion by criterion, what the vendor claims elsewhere, and which public entities use the product. The register documents publication. It does not test any product and does not state whether any product is accessible or conforms to any standard.
What the flags do
A procurement officer reading a bid response has three questions the vendor's document does not answer at a glance: how old is this, who wrote it, and does the fine print match the headline. The flags answer those mechanically, in the vendor's own words, with dates. Level-remark tension, for example, shows a row marked Supports beside a remark that says most elements; claim divergence shows a marketing statement of full accessibility beside the report's own Partially Supports rows. The register draws no conclusion from either; the two quotations sit side by side and the reader decides.
The register cuts both ways by design. A vendor that publishes a current, third-party report is recorded as such, and an entity that links it is recorded as such. The publisher's own products, where a public entity deploys them, are recorded on the same terms and marked as the publisher's.
Eight field groups, in the vendor's own words
The unit of record is a product; the vendor is its parent. A product enters the frame only when an entity profile identifies it as a platform the entity deploys, when it is on the SLAT Index roster, or, from a later wave, when it appears on a state master contract. Products are never added because a vendor asks.
Identity
Vendor, product and edition, category, the product identifier, and the vendor's own product page, with the capture date.
Availability
Whether a conformance report is published openly, available only on request, gated behind a login, published only on a third party's site, or not found, with the pages checked.
The report
Title, template and version, report date, product version tested, standards reported against, author as stated and attestation type, evaluation methods quoted, contact stated.
Claims, one row per criterion
Every criterion's claimed level (Supports, Partially Supports, Does Not Support, Not Applicable) and its remark, parsed from the report's own tables, never summarized.
Accessibility publications
The accessibility statement, the contact route, any roadmap or known-issues page, quoted verbatim with URL and capture date.
Marketing claims
Every general accessibility claim on the vendor's public pages, quoted verbatim with URL and capture date, beside the report's own rows.
Public-entity use
Every entity in the Record whose profile identifies the product, with that entity's own code for whether it links or publishes the vendor's report.
Custody
The captured report as the vendor published it, held for custody and never republished, with its hash, so that every parsed row can be checked against the source.
Seven flags are computed from the field groups, each with its inputs shown: report age against a twenty-four month threshold; version currency; standard drift; attestation; remarks completeness; level-remark tension; and claim divergence. A flag is a pair of quotations with a date, never a verdict.
The product record rulesProducts and vendors
Search by product name; filter by category, standard, attestation, currency, and flag. Default order is alphabetical; sort order is not a ranking.
As of 13 September 2026
Product and vendor records render here. No product is in frame until the first entity profiles identify the platforms their entities deploy; the vendor and product register seeds fourteen products from the pilot's expected platforms.
Notice, correction, and comment on identical terms
Before a product record is released the vendor receives the draft through its own published accessibility contact, with a ten business day window to identify any published report or page the audit missed. A code changes only on a published artifact on the vendor's own presence; a report supplied by attachment and not published is recorded as supplied on request, because the register documents what a procurement officer can find.
After release the standing correction and comment routes apply. No vendor can pay for a row, a code, a flag, or its removal, and no badge, seal, or certificate is ever issued.
Read the product record rules
The framework and the specification for the fourth section are published with the rest of the method.
The methodCorrections and comments →