WCAG 2.2 AA
New public pages and key SaaS workflows must be reviewed against keyboard access, focus visibility, labels, contrast, motion, responsive layout, and translated text overflow.
TrueLink targets WCAG 2.2 AA for new user-facing pages and product workflows. This statement records current status, known limits, and how users can report accessibility barriers.
This is an internal readiness statement, not a third-party accessibility certification.
New public pages and key SaaS workflows must be reviewed against keyboard access, focus visibility, labels, contrast, motion, responsive layout, and translated text overflow.
The `/trust/` page has been smoke checked for skip link, focusable controls, semantic sections, image handling, console errors, and horizontal overflow.
Older shared navigation and legacy public pages still require encoding cleanup, translated text checks, and broader keyboard/focus audits.
These checks are mandatory for international SaaS-ready public surfaces.
| Area | Requirement | Current evidence |
|---|---|---|
| Keyboard | Important links and controls must be reachable without a mouse. | `/trust/` includes skip link, ordinary links, details/summary FAQ controls, and no custom keyboard traps. |
| Focus visibility | Keyboard focus must be visually apparent. | `/trust/` and `/accessibility/` include visible focus styling for links and summary controls. |
| Responsive layout | Translated or long English text must not overlap or create unmanaged overflow. | Local smoke checks found no horizontal overflow on the Trust Center viewport tested. |
| Images | Decorative images should be empty alt; meaningful images need descriptive alt. | The logo image is decorative in the nav link and uses empty alt; OG image alt is provided in metadata. |
| Claims | Do not claim formal accessibility certification without audit evidence. | This page states a target and internal readiness status only. |
The first audit wave focuses on pages that affect trust, signup, and international conversion.
Accessibility reports should include the page, device, browser, assistive technology if used, and the barrier encountered.