Accessibility · what we’ve done
Accessibility isn’t a checkbox. It’s the first thing the internet ever promised — that the page would meet you where you are. AgTag is built with that in mind. This page tells you what we’ve done, where we’re still falling short, and how to tell us when we miss something.
We aim for WCAG 2.2 AA. We’re confident we hit it on most of the site; some parts are still partial. We’ll never claim full compliance until we’ve had it independently audited.
<button>; every link is an <a>. No <div onClick>.lang="en-GB" on the root, so screen readers use the right voice.<h1> per page, hierarchical descent. Screen readers can table-of-contents the page.The accessibility widget at the bottom-left of every page lets you set:
Your choices are stored in your browser only — localStorage, not cookies. We never read them on the server.
We also auto-respect your operating-system prefers-reduced-motion preference. The widget toggle is for when the OS preference is wrong for you, or when you want it stronger.
Honestly, the bits that aren’t there yet:
If you hit a wall on this site — a screen reader pronouncing something wrong, a control you can’t reach with the keyboard, a colour combination that doesn’t pass for you — please tell us. We treat every report as a bug.
with “Accessibility” in the subject line. We aim to respond within five working days, with a fix or a date for one.
Last reviewed · May 2026