Accessibility

§9.1 Target

• Every public page of a stack app targets WCAG 2.2 Level AA (the stack's accessibility design).
• W3C says content conforming to 2.2 also conforms to 2.1 and 2.0, so the target meets the WCAG 2.1 AA floor named in the ADA Title II web rule (the stack's accessibility design).

§9.2 Components

• WayneUI is the stack's component library; pages built from its components start from markup and tokens already checked by WayneUI's own runnable accessibility gate (the stack's accessibility design).
• An app MUST NOT fork or restyle a WayneUI component in a way that removes focus indicators, labels or contrast (the stack's accessibility design). PROCTOR check: wayneui-forked-views catches forked views.

§9.3 Checks

• An automated accessibility check SHOULD run in CI on the app's key pages. GitLab's accessibility testing uses Pa11y and is available on every self-managed tier (the stack's accessibility design).
• An automated tool catches regressions; it is not proof of conformance, and it never replaces a manual keyboard and screen reader pass before launch (the stack's accessibility design).
• Preflight has no accessibility component yet (not built yet).

§9.4 Not decided here

• Whether and when the ADA Title II web rule applies to a given WSU unit. The rule applies WCAG 2.1 AA to public entities on dates that depend on the entity's size; the answer is for WSU's counsel and accessibility office, and this chapter does not decide it.
• Which pages need a manual audit.