The portal targets WCAG 2.2 AA through semantic landmarks, visible focus, keyboard-operable controls, responsive reflow, text equivalents for diagrams, reduced-motion support, and appearance modes. This is a target and test record, not a certification.
Implemented behavior
- One primary heading in controlled templates and a logical heading hierarchy in seeded content.
- A skip link, semantic header/navigation/main/footer landmarks, and accessible breadcrumbs.
- Keyboard-operable mobile navigation and search dialog with Escape handling and focus restoration.
- Form labels, descriptions, native validation, status regions, and non-color status text.
- Code copy feedback, horizontally contained code blocks and tables, and no page-wide horizontal overflow at 390 pixels.
- System, Light, and Dark appearance choices with forced-colors and reduced-motion support.
- Text equivalents immediately following architecture and decision diagrams.
Known limitations
- Automated checks cannot prove every screen-reader or cognitive-accessibility outcome.
- Third-party WordPress plugins and manually edited content can introduce regressions outside the controlled release.
- Connected production checks remain necessary after hosting, caching, and security-header configuration.
Report an issue
Use the contact form, select Accessibility issue, and include the route, browser, assistive technology, expected behavior, and observed behavior without sending sensitive data.
Operational boundary
What this page covers: Tested accessibility behavior, limitations, and reporting path.
Available now: The theme and tools include explicit accessible interaction patterns and automated test coverage.
Host responsibility: Operators and editors must preserve semantic content, test production, and remediate reports.
Not claimed: Formal WCAG certification or complete coverage of every assistive-technology combination.
Canonical sources: WCAG 2.2 · Contact
Last reviewed UTC: