Accessibility statement.

What this means in practice

• All interactive elements reachable by keyboard. Focus rings visible at AAA contrast.
• Skip-to-content link on every page.
• Semantic HTML: one <h1> per page, ordered headings, named landmark regions (<header>, <nav>, <main>, <footer>).
• All images carry descriptive alt text or alt="" when decorative.
• The site renders fully with JavaScript disabled. JavaScript is used only to enhance the press-kit copy-buttons.
• prefers-reduced-motion is honoured. No autoplay video, no autoplay audio, no carousels.

Tested on

Keyboard-only navigation; NVDA on Windows; VoiceOver on macOS and iOS; TalkBack on Android; Orca on Linux. CI pipeline runs axe-core and Pa11y against every page on every push to main; the build fails on any new violation.

Reporting issues

If something doesn't work for you, please write to media@anivar.net or open an issue at github.com/anivar/anivar.net/issues. Include the URL, your assistive technology and version, and what you expected to happen.

A plain-text version of this statement lives at /.well-known/accessibility.txt.

Last audit: 2026-04-30.