Accessibility

Anchor interfaces should be navigable by keyboard, readable at common zoom levels, and understandable without relying only on color, animation, or sound.

Public surfaces use semantic HTML, visible focus states, reduced-motion support, and restrained layouts that preserve reading order across screen sizes.

Continuity language can become abstract quickly. We write headings, labels, and support content so people can understand what is being remembered, shared, archived, or disputed.

When a product surface contains dense operational state, it should expose the same meaning in text as it does visually.

Accessibility review is part of product infrastructure. New components should be checked for keyboard operation, focus order, contrast, motion, form labels, and responsive behavior.

Known issues are prioritized by user impact and by whether they block access to privacy, consent, security, or account controls.

If an Anchor page or workflow is difficult to use, contact support with the page, device, browser, assistive technology, and the task you were trying to complete.

We treat accessibility feedback as product feedback, not as an exception process.