<!-- cspell:ignore testplan -->

Accessibility Coverage Matrix

Inputs

• scope: Required. Repository or target scope to assess.
• frameworks: Optional. Comma-separated framework set to evaluate. Defaults to wcag-22,aria-apg,coga,section-508,en-301-549.
• mode: Optional. Matrix execution mode. Allowed values are build, refresh, report, or probe. Defaults to build.
• baseUrl: Optional. Base URL for runtime probing. If omitted, derive it from the target configuration or ask the user.
• serve: Optional. Serve mode for the harness. Allowed values are auto or external. Defaults to auto.

Core model

Treat the matrix as a criterion x surface x method grid.

• Criterion: framework-specific success criteria or control identifiers.
• Surface: discrete UI surfaces such as a page, component, widget, global chrome, or content type.
• Method: evidence method such as static-source, axe-auto, runtime-automation, manual-keyboard, cognitive-walkthrough, screen-reader, or other method names recorded by the engine.
• Cell lifecycle: not-started -> blocked, partial, fail, pass, or not-applicable based on newly ingested evidence and method adequacy.
• Method-adequacy semantics: a cell is counted as covered only when the winning evidence method is one of the criterion's adequateMethods in the reviewed criteria catalog. A pass from an inadequate method does not count as covered. The probe-criteria-map records which criteria a probe reports on. It never authorizes coverage on its own.

Required steps