Accessibility

Accessibility Statement

Last updated: 14 July 2026
Short version: NoSuggest is built to be usable by keyboard, screen reader, and touch — every interactive element in the app can be reached and operated without a mouse. This page documents where the app currently stands against WCAG 2.1, and what we're still working on. This is an honest, ongoing account, not a claim of perfection.

1. Our Commitment

NoSuggest aims to be usable by everyone, including people who navigate by keyboard alone, people using screen readers, and people with low vision or color blindness. Accessibility isn't a one-time checklist for us — we treat it as something to keep improving as the app grows, and we welcome feedback from anyone who runs into a barrier.

2. Standard We Reference

We reference the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as our benchmark. Below is an honest account of what's currently in place and what isn't yet.

3. What NoSuggest Currently Supports

4. What We're Still Working On

In the interest of transparency, here's what hasn't been addressed yet:

A note on video content: NoSuggest plays videos through YouTube's own official embedded player. Captions, transcripts, and audio description for any given video are controlled by YouTube's player and by each video's original creator — not by NoSuggest. We have no ability to add, edit, or guarantee captions on content we don't host.

5. Feedback

If you encounter an accessibility barrier, please use our https://nosuggest.com/contact and mention 'Accessibility' in your message. Feedback from users directly shapes what we prioritise — recent improvements including skip links, focus management, reduced-motion support, and the iOS PWA navigation fix were all driven by accessibility testing and feedback.

Found an accessibility issue?

Reach out at
nosuggest.com/contact