Accessibility

What this page covers#

Use this page for the current public accessibility posture across the UAIX launch surface. It explains what launch-ready readability, keyboard use, mobile layout, and manual QA mean on the current public standards site.

Current published accessibility posture#

• Launch-ready pages should use readable real text, keyboard-reachable interactions, contrast-safe presentation, and mobile-safe layouts across the public surface.
• When a release changes navigation, search, validator workflows, machine-reference pages, downloadable packets, or other primary reading surfaces, manual accessibility QA should travel with the release evidence.
• The current posture is operational and release-led rather than a separate certification or accessibility-office program.

What reviewers should verify now#

1. Check primary reading routes such as Home, Get Started, UAI-1, and Governance with keyboard-only navigation.
2. Check whether code blocks, tables, support panels, and validator surfaces remain readable on mobile and at narrower widths.
3. Check whether contrast, heading hierarchy, and real-text structure remain intact after content or template updates.
4. Check whether the release trail documents accessibility-significant changes when observable behavior shifted.

What is not claimed#

• UAIX does not currently publish a separate accessibility office, certification badge, or formal legal statement program beyond the current public posture.
• Do not imply automated accessibility guarantees across all future content; the current claim is a release-facing commitment to readable, reviewable public pages.
• Do not imply wider institutional support channels unless they are formally published on canonical UAIX pages.

How accessibility-significant changes should travel#

• Update the affected template, page copy, and public guidance together.
• Keep manual QA notes attached to the release evidence when keyboard flow, readability, or mobile behavior changes.
• Record the change through Governance, the Changelog, and News when outside readers need dated context.
• Use Policy and Security when the same release also changes licensing or security-significant posture, and use References and Contributors when another reviewer needs the durable public handoff packet.

Next step#

Continue to Policy and Security for the trust-policy hub, or read Analytics when a release changes measurement scripts, embeds, or other observable front-end behavior beside accessibility.