Accessibility approach
Built for equal access from the start.
OneWeb targets WCAG 2.2 Level AA. That target guides design and testing; it is not, by itself, proof that this site is accessible to every person in every context.
Current safeguards
- Semantic landmarks, headings, lists, descriptions, and meaningful links.
- Keyboard-visible focus, a skip link, and no pointer-only interaction.
- Layouts designed to reflow at high zoom and on narrow screens.
- Text labels accompany every status; color is never the only indicator.
- Reduced-motion and forced-color preferences are respected.
- The interactive map and synchronized HTML state list use the same records, search, filter results, profile links, and comparison actions.
- Search and filter result counts are announced, active filters are removable, and comparison uses a captioned table with scoped headers.
Known launch-readiness limitations
- Manual browser, screen-reader, and disabled-participant testing is not yet complete. The project is not approved for public launch.
- The tile map is a compact visual enhancement rather than geographic boundary geometry; every state action remains available in the synchronized HTML list.
- Some external source pages may be broken, restricted, or inaccessible.
- The current correction form creates a local draft and transmits nothing. A staffed, monitored public accessibility-feedback channel still needs an owner and service procedure.
- Research summaries still require human legal, plain-language, and accessibility review.
Testing is not certification
Automated checks help catch regressions, but they cannot establish practical accessibility. Manual keyboard, zoom, forced-colors, screen-reader, and disabled-user testing remain part of launch readiness.