kittynex aims to be usable by as many people as possible, including readers who use screen readers, keyboard navigation, magnification, or reduced-motion settings.
Last updated: September 21, 2026
Our target standard
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG is the internationally recognised standard for web accessibility, and Level AA covers the requirements most commonly referenced by accessibility law, including the Americans with Disabilities Act in the United States and the European Accessibility Act in the EU.
What we do to meet it
| Area | What we implement |
|---|---|
| Structure | Semantic headings in a logical order, one main heading per page, landmark regions so screen readers can jump between sections |
| Text alternatives | Descriptive alt text for informative images; decorative images marked so they are skipped |
| Colour and contrast | Body text and interface elements designed to meet AA contrast ratios; information never conveyed by colour alone |
| Keyboard use | Every link, control, and form field reachable and operable by keyboard, with a visible focus indicator |
| Tables | Comparison tables use real header cells with scope, so screen readers can associate data with its column |
| Motion | No auto-playing animation or carousels that cannot be paused |
| Zoom and reflow | Content remains readable and usable when zoomed to 200% and reflows to a narrow viewport |
| Language | The primary language of each page is declared in the page markup, so screen readers use the right voice |
| Forms | Every field has a programmatically associated label, and errors are described in text |
Known limitations
We would rather state these than pretend they do not exist:
- Third-party content. Some images or embedded media originate with manufacturers. Where a manufacturer publishes an image with inadequate alternative text, we add our own description; this takes time, and older articles may lag behind.
- Data tables. Our comparison tables are dense by design. They are marked up with proper headers, but a very large table can still be slow to navigate with a screen reader on a small device. We are working on providing an equivalent summary in text.
- PDF documents. We avoid them, and where a manufacturer’s own manual is a PDF, its accessibility is outside our control.
Feedback
If you encounter a barrier on this site, tell us. Email contact@kittynex.com with the page URL, what you were trying to do, and the assistive technology or browser you were using. Accessibility reports go to the front of the queue, and we aim to respond within five business days.
If you are not satisfied with our response, you are welcome to say so in the same thread; unresolved reports are reviewed again rather than closed.