A sample report showing exactly what you get: the format, prioritisation and fix suggestions from a real Axively scan workflow. The site shown is a fictional example; your own audit has the same structure.
WCAG level-AA failures or critical functional barriers (cart, checkout, forms). A strong indicator of non-conformance with accessibility law — subject to manual review.
WCAG level-A failures and other serious or moderate issues. Level A is equally required for conformance — the tiers rank user impact and fix priority, not legal weight.
No WCAG level-A or AA failures detected by the automated scan — best-practice recommendations and minor findings only.
A high finding count is not a disaster, it's an inventory. Of the 6,752 occurrences here, 267 are WCAG violations and 6,485 are best-practice advice — and all of it traces back to just 5 distinct causes.
target-sizePeople with motor or visual impairments and touch-device users struggle to hit a small target and make errors. Enlarge the clickable area with padding:
/* before */
<a href="tel:..." class="page-header--link">+33 1 00 00 00 00</a>
/* after */
<a href="tel:..." class="page-header--link"
style="padding:10px; display:inline-block;">+33 1 00 00 00 00</a>In practice we recommend fixing this with a CSS class rather than an inline style, the suggestion shows the principle.
link-nameScreen readers announce these links as just "link", so their destination cannot be known. Give the link an accessible name and hide the decorative icon:
/* before */
<a class="social-link" href="https://example.com/rss">
<svg class="icon"></svg>
</a>
/* after */
<a class="social-link" href="https://example.com/rss" aria-label="RSS">
<svg class="icon" aria-hidden="true" focusable="false"></svg>
</a>These findings come from axe best-practice rules. They improve usability for assistive-technology users but map to no WCAG success criterion, so they are not counted as compliance violations and do not affect the audit price.
label-title-onlyWith only a title attribute and no visible <label>, assistive technology announces the field inconsistently and sighted users get no label at all. Add a linked label:
/* before */
<input class="search" title="address" type="text">
/* after */
<label for="locality">Address</label>
<input id="locality" class="search" type="text">regionScreen readers can't reliably navigate or skip content that sits outside landmark regions. Because it's a template element, wrap it in a single landmark:
/* before */
<div class="page-content">
...
</div>
/* after */
<main class="page-content">
...
</main>A single template fix removes all ~6,400 occurrences: fixed per template, not per page.
empty-headingScreen-reader users navigating by headings land on an item that announces nothing. Render the heading only when there is a title, or fill it in:
/* before */
<h3 class="teaser-title"></h3>
/* after */
<h3 class="teaser-title">Horaires d'ouverture en aout</h3>A high number of occurrences doesn't mean thousands of different problems: usually it's a handful of causes repeated across templates. So an audit is handled per template and per cause, not page by page: one template fix clears all of its occurrences at once.
A note on the scale: the summary above sorts findings into 3 risk levels (high / medium / low) by compliance impact, which also drives the price. The report below breaks them into 4 technical levels (critical / serious / moderate / minor) by defect severity as rated by the scanning engine. Two views of the same data, not a mismatch.
PDF report, the same data ready to hand to a lawyer, management or a regulator: summary, breakdown by severity and rule, recommended fix order.
Accessibility statement, generated in the format for your country, with the sample’s findings in the inaccessible-content section.
Draft statement, verify all details before publishing. Axively does not provide legal advice.
Every AI audit includes a free verification re-scan within 30 days. The team fixes the templates per the suggestions, runs the re-scan and sees a direct before and after comparison on the same visualisation.
one-time payment based on site size, verification re-scan included with the AI audit