Accessibility / goals and gaps
Accessibility statement
Resistance work should be usable by as many people as possible. This statement describes targets and known limits. It does not claim a completed WCAG AA certification or exhaustive assistive-technology test matrix.
Last updated
Overclaimed Supported stamps removed.
WCAG 2.1 AA
Not presented as a completed certification.
Feedback channel
Dedicated intake is not live yet.
Commitment
We aim toward WCAG 2.1 Level AA as a design and engineering target. Hub routes prioritize native mobile section selectors over horizontal scroll tabs. Focus styles and semantic structure are intentional; gaps should be treated as defects, not features.
Accessibility targets
| Area | Status | Note |
|---|---|---|
| Keyboard access | Target | Interactive controls should be reachable and operable from the keyboard with visible focus. |
| Semantics / names | Target | Prefer semantic HTML and accessible names; hub section pickers use native selects on small screens. |
| Contrast | Target | Aim for WCAG 2.1 AA contrast. Not every screen has a published audit artifact. |
| Motion | Partial | Respect prefers-reduced-motion where animations are authored; some decorative motion may remain. |
| Zoom / reflow | Target | Layouts should remain usable when zoomed; report breakage if you find it. |
Known issues
- Some decorative or atmospheric motion may still be distracting if reduced-motion is incomplete on a given surface.
- Third-party publisher pages opened from Resistance Wire are outside this site’s control.
- PDF or external documents linked from guides may not meet the same bar as HTML routes.
- Policy/support pages are being aligned to a shared reading surface; residual inconsistency may remain during transition.
Keyboard basics
- Tab / Shift+Tab — move between interactive elements
- Enter / Space — activate buttons and controls
- Esc — dismiss menus/dialogs where implemented
Feedback
Accessibility feedback intake is coming soon. Until a channel is listed as available on /secure-contact, assume there is no live project inbox for bug reports. When you can report elsewhere, include the page URL, what broke, and your browser / assistive technology if relevant.