Accessibility statement

Our target

We aim at WCAG 2.2 level AA across the site, and we treat accessibility as a build requirement rather than a later fix. Every page is checked before it is published.

What is built in

• Semantic HTML: one h1 per page, headings in order, and real lists, tables and landmarks.
• A skip link as the first focusable element, so keyboard users can jump straight to the content.
• Visible focus styles that meet the minimum contrast and size requirements.
• Colour contrast checked against the AA thresholds, including on muted text and badges.
• Text that reflows without horizontal scrolling, and touch targets sized for a thumb.
• Motion that respects prefers-reduced-motion, and no animation that carries meaning.
• Every table has a real header row, so a screen reader can announce which column a cell belongs to.
• Every image has an alternative text description that says what the image shows.
• The site works with JavaScript disabled. The only script on the site moves a card rail, and the rail scrolls without it.
• Fonts are self-hosted and sized in relative units, so browser text-size settings are honoured.

How it is measured

Accessibility is measured with Lighthouse against the published site on mobile and desktop, on the home page, a category page and a review page. The current result is 100 in the accessibility category on all six runs, measured on 10 October 2026. We also check pages by keyboard alone, because automated tools catch only part of what matters.

Known limitations

• Long pricing tables scroll horizontally on very narrow screens rather than shrinking the text to an unreadable size. The table itself remains fully readable by a screen reader.
• Vendor screenshots are images of other companies’ pages. The prices they show are always repeated in the surrounding text, so nothing depends on reading the image.
• The FAQ sections use details elements, which are announced correctly by current screen readers but can be inconsistent in older ones. Every answer is also present in the page’s structured data.

Tell us about a problem

If any part of this site is difficult or impossible for you to use, write to hello@agencysoftwarereport.com and describe the page and what happened. Accessibility reports are treated as bugs and are fixed before other work.

Last reviewed: 10 October 2026.