Access and experience
Keyboard use, semantics, focus, contrast, reflow, content clarity, task completion, and agreed assistive-technology checks.
Acceptance must be earned
Built is not the same as verified.
Verification tests the approved requirements before operational acceptance—then records what passed, what failed, what remains limited, and who owns the next move.
Verification basisApproved requirements
Primary outputAcceptance record
Operational resultStewardship baseline
The verification surface
Test the claims that made the investment worth approving.
The exact test plan follows the approved scope. The categories below keep quality from collapsing into a single automated score.
Discovery and knowledge
Crawl paths, metadata, internal relationships, source clarity, direct answers, structured information, and indexability.
Performance and measurement
Responsive behavior, material performance targets, instrumentation, event definitions, error handling, and evidence integrity.
When a requirement does not pass
A failed check becomes a decision—not a hidden footnote.
Verification protects trust by making the disposition visible.
Correct
Resolve the defect and retest before acceptance.
Defer
Record the reason, consequence, owner, and required review point.
Accept a limit
Document the known limitation and the authority responsible for accepting it.
Verification creates the baseline stewardship must protect.
The acceptance record captures tested requirements, evidence, unresolved exceptions, responsible owners, measurement definitions, and the conditions that should trigger review.
That baseline prevents future changes from being judged against memory, preference, or a dashboard without context.