Accessibility
The portal targets WCAG 2.2 AA and publishes known limitations instead of claiming perfect conformance.
Accessibility interactive detail
What the interface is designed to support
- Keyboard access and visible focus for every public workflow.
- Text and non-text contrast evaluated with automated and manual checks.
- Reduced-motion, increased-contrast and forced-color preferences.
- Semantic landmarks, headings, tables, forms and status announcements.
- Responsive reflow from 320 pixels without page-level horizontal scrolling.
- The self-hosted Capitaine cursor theme keeps native fallbacks, is disabled for coarse pointers and forced-color mode, and is never the sole carrier of meaning.
How it is checked
The release gate combines axe-core route scans, keyboard-path tests, target-size checks, reduced-motion checks, responsive matrices and a manual review of contrast and reading order. Automated results do not replace testing with assistive technology.
Current boundaries
The portal has not yet completed independent testing with a broad group of screen-reader, switch-control and voice-control users. The interactive renderer slices are bounded demonstrations and are not proof of native host integration.
Report a barrier
Describe the route, task and assistive technology involved. Security-sensitive reports should continue to use the private security channel.
Until a dedicated accessibility channel is published, use the private security contact with the subject “Accessibility”.