Accessibility Statement

What we aim for

We target WCAG 2.1 Level AA. We are not claiming to have reached it across the whole site, and this page is more useful to you as an honest status report than as a compliance badge.

What works today

• • The analyzer can be operated entirely by keyboard, from pasting a URL through to triggering an export.
• • Analysis progress is exposed as a progress bar with a live status region, so a screen reader announces completion rather than leaving you waiting in silence.
• • Navigation menus expose their expanded state, can be closed with Escape, and return focus to their trigger.
• • Reference tables in the guides and policy pages use real table markup with header cells, so screen-reader table navigation works.
• • The interface respects your system light/dark preference, and animations are collapsed when you have asked your operating system for reduced motion.
• • Page structure uses genuine headings in order, so heading navigation is reliable.

Known problems

These are real and we would rather name them than let you find them the hard way.

• • The results view is built from cards, not tables. It is readable in sequence with a screen reader, but you cannot navigate it by row and column the way a data table allows. Converting the results to real table markup is planned.
• • Long playlists produce long result lists. Pagination helps, but reviewing a 500-video playlist with a screen reader remains tedious. Exporting to CSV is currently the better route for that case.
• • Third-party advertising is injected by Google and we do not control its markup or its focus behaviour.
• • Non-English interface text is machine-assisted and has not been reviewed by a native speaker. It may read oddly with a screen reader.

Reporting a barrier

If something here blocks you, please tell us through the contact form. Knowing which page, which assistive technology, and what you were trying to do makes a fix much more likely. Accessibility reports are treated as bugs, not as feature requests.