Accessibility
Last updated: March 25, 2026
Our Commitment
Mirage is a privacy tool — and privacy should be accessible to everyone. We are committed to ensuring our website and products conform to WCAG 2.2 Level AA standards.
We don't use a third-party overlay or automated "fix" service. Instead, we build accessibility into our design and development process from the start. This page is our honest account of where we are and where we're headed.
What We Do
- ✓ Semantic HTML throughout — proper headings, landmarks, and form labels
- ✓ Keyboard navigable — skip link, focus management in modals, visible focus indicators
- ✓
prefers-reduced-motionrespected — all animations are disabled or minimized for users who prefer reduced motion - ✓ Color contrast checked against WCAG AA standards (minimum 4.5:1 for normal text)
- ✓ ARIA attributes on interactive elements — modals, forms, and live regions for dynamic content
- ✓ Decorative elements marked
aria-hidden="true"so screen readers skip them
Known Limitations
We're being transparent about areas that still need work:
- ○ Braille background animation — the interactive hover-to-reveal effect on the homepage is mouse-only. Screen reader users and keyboard users are not affected (the element is hidden from assistive technology), but the visual interaction is not available via keyboard.
- ○ VPN comparison table — the table on the Why Mirage page uses color (red/green) to indicate yes/no values. The text labels provide the same information, but we plan to add icons as an additional visual cue.
How We Test
- 1. Automated scans — axe-core and Lighthouse accessibility audits on every deploy
- 2. Keyboard testing — manual tab-through of all pages and interactive elements
- 3. Screen reader testing — VoiceOver (macOS/Safari) for primary validation
Supported Assistive Technology
This site is tested and intended to work with:
| Platform | Screen Reader | Browser |
|---|---|---|
| macOS | VoiceOver | Safari, Chrome |
| Windows | NVDA | Firefox, Chrome |
| iOS | VoiceOver | Safari |
| Android | TalkBack | Chrome |
Report an Issue
If you encounter an accessibility barrier on this site, we want to hear about it. We take every report seriously and will work to resolve issues promptly.
- → Email us at [email protected]
- → Open an issue on our GitHub repository
Please include the URL, a description of the issue, and what assistive technology you were using. We aim to respond within 5 business days.
Conformance Status
This site is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means that some parts of the content do not fully conform to the accessibility standard, as documented in the Known Limitations section above. We are actively working to reach full conformance.