Accessibility
Built toward WCAG 2.2 AA.
The portal is built for the researchers who rely on screen readers, keyboards, and slow connections. Your procurement will ask for a VPAT; ours is in progress, and we would rather set that expectation here than in the final round.
Last reviewed July 2026
- Target
- WCAG 2.2 AA
- VPAT
- In progress
- Motion
- Reduced-motion support
- Feedback
- hello@archively.ai
Where accessibility stands
The target, and the work behind it.
An inaccessible archive portal is a contradiction. Institutions serve researchers who use screen readers, keyboards, and slow connections. The portal is built with that audience in mind, not as an audit afterthought.
The target
WCAG 2.2 AA is the working target for the public portal and this site. It is the standard the product is built toward, not a claim of finished conformance.
TARGET · WCAG 2.2 AA
Semantic structure
Pages use real headings, landmarks, and labeled controls, in a logical order. Assistive technology gets a page it can read, not a wall of unnamed boxes.
SEMANTIC HTML · HEADING ORDER
Keyboard access
Interactive elements are reachable and operable with a keyboard alone. A mouse is a convenience here, not a requirement.
KEYBOARD OPERABLE
Focus visibility
Focus is always visible, so a keyboard user can see where they are on the page. Focus styles are not suppressed.
VISIBLE FOCUS
Reduced motion
Animation respects the reduced-motion setting in your operating system. When motion is turned off, the site stops moving.
PREFERS-REDUCED-MOTION
Captions and transcripts
The media pipeline produces captions and reviewed transcripts for audio and video, so recordings are usable without sound.
CAPTIONS · TRANSCRIPTS
Run your own accessibility pass on a live archive.
A working setup using your records, not a sales presentation.