Accessibility approach
Unmanned Innovation is designed so technical material remains usable across screen sizes, input methods, and common assistive technologies. Accessibility is treated as part of the page system and editorial workflow, not as a separate overlay.
The target is WCAG 2.2 Level AA. Automated checks and browser review can identify many problems, but they do not establish complete conformance or replace testing by people who use assistive technology.
Current accessibility features
- Semantic landmarks, logical heading structure, and a skip link to the main content
- Keyboard-operable navigation and visible focus treatment
- Responsive layouts intended to avoid horizontal page overflow
- High-contrast text and controls, with reduced-motion preferences respected
- Descriptive alternative text for meaningful images and empty alternative text for decorative images
- Labeled tables, captions, breadcrumbs, and source links with meaningful text
- Server-rendered content with minimal client-side behavior
Editorial accessibility
Editors should use plain technical language, define specialized terms when first useful, preserve heading order, avoid color-only meaning, label units and assumptions, and choose a table or diagram only when it materially improves understanding.
Linked text should describe its destination. Figures and diagrams should include useful captions, and source references should remain understandable outside visual styling.
Limits and verification
Release verification includes browser, keyboard, responsive-width, and automated accessibility checks across the route system. Those checks can identify many implementation problems, but they do not constitute an independent accessibility audit. No independent audit has been completed.