A legal citation of a standard is a citation of a dated version

What it is

The contract says “meets WCAG 2.0.” The report cover says “executed against 2.2, all pass.” Success criteria that exist only in the later edition were never asked for; criteria the instrument still names, which 2.2 rewrote or moved, may never have been tested. When law and procurement cite a standard, they cite a dated edition, not “whatever draft the committee is holding this month.” If the editions differ, the conformance talk is not about the same document.

“We followed the latest” sounds diligent. In a citation relationship it can be an answer to a question nobody asked.

Why it happens

Law and contracts freeze an external standard with a dated reference: which document, which year, sometimes which clause. A harmonised standard (an edition of EN 301 549) then re-cites an edition of WCAG or of the ISO 9241 family. New criteria in a later standard are not owed by the old instrument; criteria the old edition had, which a new protocol dropped or rewrote, may simply not be tested. Meeting “a newer copy” is therefore neither sufficient nor necessary — unless the instrument uses an undated, moving target, which accessibility legislation rarely does.

The second layer is lag in the citation chain. The harmonised standard a statute names is often one or two minor editions behind current WCAG. A team that tests only the latest, on grounds of technical correctness, hands acceptance a report that does not match: extra tests are not credited; missing tests are the breach. Checking the version means checking the link the instrument named, not “what everyone uses now” on social media.

Studying it

Lay the instrument, the harmonised standard, and the test protocol in three columns: a cited-edition comparison. Copy the standard number and year from the statute or contract, copy the next hop it cites, copy the method version actually used. Mark criteria that exist only in the instrument and only in the test.

Independent variables: standard+year in the instrument, standard+year in the protocol, presence of a harmonised hop in between. Dependent variables: size of the two-sided set difference, whether the difference contains blocking items on critical tasks.

This is documentary work. Do not turn edition drift into a litigation story, and do not assume a newer edition is always stricter — sometimes it is a renumbering, or a move from AAA to AA.

Where it stops holding

If the instrument explicitly says “and subsequent editions,” or points at a continuously updated technical spec, following the moving target is lawful; most public procurement does not write that. Voluntary certification and internal quality goals may chase a newer edition; that report cannot be handed over to satisfy the older citation. Translations, corrigenda, and national adoptions (same ISO number, different year or adoption note) count as editions — the number without the year is not enough. Process standards have editions too: a claim against a given year of ISO 9241-210 needs evidence collected under that year’s clauses, not activity names borrowed from another year.

Applying it

• Copy the standard number+year from the statute or contract onto the first line of the test plan. Do not type “latest WCAG” by hand.
• If the team also tested a newer edition, split “the set the instrument asked for” and “the extra set” into two tables; submit only the first at acceptance.
• When a harmonised standard re-cites, open the citation page and confirm which WCAG / ISO year it points at; do not trust only the cover year of the harmonised document.
• How to check: the report cover, the test-case titles, and the instrument’s citation are the same string. Pick two success criteria that exist on only one side and see whether they were silently treated as covered. Each mismatch is an unaligned edition, not a test that was not thorough enough.

Related

• Same group: J1.03.1 Ergonomics standards often bind the process, not only the finished interface · J1.03.3 Meeting a standard is not evidence that people can complete the task
• Nearby: J1.04 Legal requirements · J1.02 Conformance levels · J1.10 Scope of conformance claims
• Search terms: dated reference · EN 301 549 · standard version