Website Accessibility and Speed Audit - Content Cucumber

Accessibility, mobile speed and Agentic Browsing audit for your website. WCAG 2.2 AA and Core Web Vitals checks, failures traced to their source, and a ranked fix list.

Source: https://contentcucumber.com/accessibility-audit/

Accessibility Audits For AI Agents and Humans

People reach your site with screen readers and keyboards, on phones and tablets with weak signals, and AI agents open your pages to answer a question or finish a task for someone.

We test your site at phone and desktop width, against WCAG 2.2 AA, Core Web Vitals and the Agentic Browsing checks in Google Lighthouse, then we trace each failure back to the template or setting that causes it so the fix happens once.

Why Your Site Needs an Accessibility Audit

Your site serves visitors you don't see, people using screen readers and keyboards, buyers on phones with a weak signal, and AI agents acting on behalf of someone else.

What the Audit Covers

Checks run in a real Chrome browser on the URLs in your sitemap.

Agentic Browsing

The Lighthouse category for AI agents checks whether software can make sense of your accessibility tree, whether the layout holds still while it loads, and whether an llms.txt file points agents at the content you want read.

Accessibility, WCAG 2.2 AA

Color contrast, link names, image alt text, keyboard access to scrolling tables, heading order and tap target size, checked with axe-core, the engine behind the accessibility score in Lighthouse.

Mobile Speed and Core Web Vitals

Load time, layout shift and blocking time measured on a phone connection, with the scripts, images and stylesheets that slow you down ranked by cost.

Third-Party Scripts

Tag managers, chat widgets, form embeds and testing tools that load before your content. We show what each one costs and how to delay it while tracking keeps working.

Templates and Shared Elements

One link color in your theme settings or one sidebar widget can fail hundreds of pages. We group failures by where they come from, so you fix a handful of sources instead of a thousand pages.

Content-Level Fixes

Missing alt text, empty links left over from old imports, posts with no author and broken screenshots. On WordPress sites running the RequestDesk Connector, we fix these in bulk.

We Practice What We Preach (Tested on our own site)

Before we offered this audit to anyone, we ran the audit on contentcucumber.com, and the first scan found accessibility failures on nearly every page of our own site. The bulk of them traced back to a handful of shared sources, a link color in the theme settings, a green button style, icon links in a sidebar widget and an author box on posts whose author had been deleted.

We fixed those sources, cleaned up the content the templates could not reach, and rescanned the site at phone and desktop width until the scan came back clean. The same work got our homepage loading in under three seconds on a phone, and the audit we run on your site is the one we ran on ours.

How the Audit Works

How the Audit Works

Scan the Site

We load the URLs in your sitemap at phone and desktop width in a real Chrome browser and run the accessibility, speed and Agentic Browsing checks on each one.

Trace Failures to Their Source

We group the results by the template, setting or shared block that produces them, so you see the short list of sources behind the long list of pages.

Fix or Hand Off

You get a ranked fix list. On WordPress we can make the theme and content fixes ourselves, and for other platforms we write the fixes up for your developers.

Rescan and Confirm

After the fixes go live we scan the site again past the page cache and show you the before and after numbers side by side.

Frequently Asked Questions

What is Agentic Browsing?

Agentic Browsing is an experimental category in Google Lighthouse that checks how well AI agents can read and use a page. It looks at the accessibility tree, layout stability and llms.txt, and it reports WebMCP and ai-catalog.json support on sites that offer them.

Why does accessibility matter for AI search?

AI agents read a page through much of the same structure a screen reader uses, labeled links, real headings and text alternatives for images. A page that works for a screen reader gives an agent less to guess about.

Is this an ADA compliance certification?

No. The audit tests against WCAG 2.2 AA with automated checks in a real browser, plus a look at the spots automated tools skip, such as text over gradient backgrounds, and it gives you a record of what was found and fixed. Legal compliance is a question for your attorney.

Which platforms do you work with?

The scan works on any public website. We make fixes ourselves on WordPress, and we write up fixes for Shopify, Magento, BigCommerce and custom builds.

How long does it take?

Our own site, about 950 URLs, took three days from first scan to a clean rescan, with the fixes included. Timing for your site depends on page count and how fast fixes can ship.

Get the Fix List for Your Site

Send us your URL and we will scan it at phone and desktop width, then show you the sources behind the failures.