Accessibility

We aim for WCAG 2.2 Level AA conformance for this site’s templates. Accessibility and good measurement hygiene share a theme: people must be able to perceive the same evidence. In AI visibility tracking, that means analysts with assistive technology should be able to read excerpts, tables, and glossary definitions without loss of meaning—parallel to how your internal dashboards should expose alt text for charts and semantic structure for screen-reader users.

What we test

Templates use semantic HTML landmarks (header, main, footer), visible focus styles, and sufficient color contrast for body text. Navigation exposes an accessible name and state for the mobile menu button, with aria-expanded updated on toggle. Skip links let keyboard users bypass repeated chrome.

Known limits

Long tables and dense glossary sections can challenge small screens. We use responsive layout and skip links to reduce friction. Some code samples or URLs may wrap awkwardly in narrow viewports; if that blocks comprehension, tell us via the contact page. Dense definition lists are the native structure for glossary entries; we keep definitions readable by avoiding walls of unbroken text inside single cells.

Relationship to monitored products

When your team builds internal tools for AI visibility tracking, apply the same accessibility discipline to review UIs: human validators need accessible diff views, keyboard shortcuts for accept or reject actions, and captions for any embedded media tutorials. Poor internal accessibility slows review queues and silently biases metrics toward whatever subset of analysts can use the UI comfortably.

Feedback

Use the contact page if you cannot access content. Include the page URL, browser, and assistive technology so we can reproduce the issue.

Plain-language summaries

Where pages describe complex mechanics—parser versioning, append-only observation stores, refusal classification—we keep prose linear and define acronyms at first use. If jargon still blocks understanding, that is a bug: measurement concepts should be teachable to a motivated PM without a statistics degree, even when the implementation requires one.

Compatibility testing

Layouts are tested in recent evergreen browsers at common breakpoints. If you rely on high zoom or forced colors, tell us when something clips or loses contrast; we treat those reports as seriously as a broken link because inaccessible review UIs in your internal tracker would skew which observations get human labels.

PDFs and exports

If we publish downloadable PDFs in the future, they will need tagged structure and reading order checks. Many teams export AI visibility PDF reports for executives; those exports should inherit the same accessibility expectations as web dashboards so blind stakeholders are not excluded from governance conversations.