Accessibility

Built to be readable by everyone.

Last reviewed June 10, 2026

Our commitment

mention.report publishes a monthly, sourced reading on AI search. A report about being findable should itself be findable, by every reader and every reading technology. We build this site to be usable with a keyboard alone, with screen readers, at high zoom, and with reduced motion, and we treat accessibility as part of editorial quality rather than a compliance checkbox. Every page also carries an accessibility options panel, powered by ax4e, that lets you adjust text size, contrast, spacing, and motion to your preference; it adjusts presentation only, because the page underneath is built to work without it.

The standard we build to

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. In practice that means semantic HTML structure, sufficient color contrast against our white and ink palette, visible focus states, text alternatives on meaningful graphics, form fields with proper labels, and no content that depends on color alone to carry meaning.

How the site is reviewed

The site is reviewed on a recurring basis with a combination of automated scanning and manual checks, with audits run through ax4e, an accessibility practice within the Mention Group family. We publish what the audits find rather than only what passes, and each statement update carries its review date.

Known limitations

The PDF editions of the report are print-oriented documents and have not yet completed full WCAG remediation. The HTML edition at its dated URL is the canonical, accessible version of every report, and it contains everything the PDF does. If you need a figure from a PDF edition in an accessible format, contact us and we will provide it.

If something is in your way

If any part of this site is difficult to use with assistive technology, we want to know about it, and we will fix it or provide the content another way. Reach us through the contact page and mention which page and what got in the way. Accessibility feedback goes to the top of the queue.