Semantic and keyboard access
Pages use landmarks, ordered headings, skip links, visible focus, native controls, labeled forms, keyboard-operable tabs and disclosures, and status announcements.
ACCESSIBILITY
Policy participation must work without a mouse, a large screen, or perfect vision.
Pre-production target · conformance not yet claimed
WorkingPolicy targets WCAG 2.2 AA and tests its public and workspace routes across keyboard, screen-reader semantics, zoom, reflow, contrast, reduced motion, and required viewport sizes.
Readable institutional typography
Ordinary content does not rely on tiny interface text. Inputs remain at least 16px, touch targets meet practical minimums, and metadata remains readable.
Reflow and alternatives
Routes are tested at 200% zoom, 400% reflow, and 320 through 1600px widths. Tables and charts require responsive or equivalent textual alternatives.
State without color alone
Evidence, risk, version, review, funding, and outcome states use text and structure in addition to the approved palette.
Evidence before a claim
Automated axe checks and manual keyboard, zoom, contrast, and browser evidence are required before any conformance statement.
INSPECTABLE RECORD
What the system shows.
Labels describe the state of the record. They do not confer legal authority, certification, or government endorsement.
RecordStateMeaning
Current targetWCAG 2.2 AA
An engineering target, not a current certification or legal conclusion.
Automated checksRoute-level axe tests
Automation supplements and never replaces manual evaluation.
Feedback channelActivation pending
The production accessibility contact requires operator-approved legal/contact details.
Accessibility issues belong in the product record.
The contact route states the current development channels and the operator action still required before public launch.