Accessibility
We aim for WCAG 2.2 AA for this site and want the beta to be usable with different ways of navigating and viewing the web.
Current approach
The site uses semantic headings, landmarks, visible keyboard focus, a skip link, responsive layouts, and text that remains readable when enlarged. The interface avoids required animation and respects a reduced-motion preference where motion is present.
What this does not mean
The site and extension have not been certified as fully compliant with WCAG 2.2 AA. Browser permissions, microphone controls, page-specific behavior, and the websites where Eyekit runs can affect the experience.
Tell us what got in the way
If you find a barrier, use the email contact on the Support page. Share the page, browser, operating system, and action that was difficult when you can do so safely. Please leave out private page content, audio, screenshots, and API keys.