Transparency

Sample Accessibility Report

This static example shows the kind of report our automated scanner can generate: specific findings, WCAG references, affected context, and guidance your team can adapt.

Clear, actionable findings

Reports show the affected selector, severity, WCAG mapping, and affected pages so a developer can decide what to fix first.

Example finding: Missing alt text

HTML: <img src='logo.png'> Finding: An informative image has no text alternative. WCAG: 1.1.1 Non-text Content.

Example guidance

The report can suggest adding a meaningful alt attribute, for example <img src='logo.png' alt='Company name logo'>. Your team still reviews whether the text is accurate in context.

Beyond automation

The report also flags checks that need manual review, such as logical focus order, meaningful alternative text, and behavior across interaction states.

Annotated context example

When available, the report can show the affected UI context alongside the rule result, helping teams connect an automated finding to the page they need to inspect.

1.4.3 Contrast (Minimum)

1.4.3Contrast (Minimum)AA
Serious
Issue scope
Affects 12 pages24 elements
e.g./about/contact+10 more
Evidence

Fix any of the following: Element has insufficient color contrast of 2.94 (foreground color: #9ca3af, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1

How to fix

Ensure that text has a contrast ratio of at least 4.5:1 against its background color to be legible for people with moderately low vision.

Technical details
color-contrastwcag2aawcag143.header > .nav-link
Failing markup → example fix
Failing markup:
<a href="/about" class="nav-link text-gray-400 bg-white">About Us</a>
Example fix:
<a href="/about" class="nav-link text-gray-700 bg-white">About Us</a>

Example fix: guidance for your code, not applied to your site.

Read the axe guidance: 1.4.3(opens in a new tab)