Skip to content

Accessibility as a gate #36

Description

@iderex

Depends on the rendered timing budget issue.

The markup checks catch missing alt text and skipped headings. The rest of
accessibility is about the rendered page: contrast, focus order, the visible
focus indicator, and roles that are announced.

An automated audit over every produced page, run in the same headless browser as
the timing gate, refusing any serious or critical finding. Anything below that
threshold is reported and not refused, and the report is kept with the run.

Contrast is checked against every colour vision preset the design system offers,
not only the default, because a preset that fails contrast is a preset that was
never usable and nothing else would notice.

Two limits stated rather than implied. An automated audit finds a minority of
real accessibility problems, so a green run means the mechanical failures are
absent and not that the page is usable. And nothing here judges a keyboard
journey through the site; that is in the integration harness with its own
honest name.

Done when

The audit runs over every produced page in the headless browser, a deliberately
low-contrast token reds it, every colour vision preset is covered by the
contrast leg, and the run states the two limits above in its output.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions