This is what an Axively audit looks like.

Finding 1, Touch target too small

Rule:

target-size

Severity:

serious

WCAG:

2.5.8 Target Size (Minimum), level AA (new in WCAG 2.2)

Occurrences:

252 occurrences

Element:

phone link in the header, touch target smaller than 24 × 24 px, close to other links

People 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.

Finding 2, Form field without a visible label

Rule:

label-title-only

Severity:

serious

WCAG:

3.3.2 Labels or Instructions (A) + 4.1.2 Name, Role, Value (A)

Occurrences:

64 occurrences

Element:

a search field labelled only by a title attribute, no <label>

With no visible <label>, a screen reader can't reliably say what the field is for. title and placeholder are not enough. 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">

Finding 3 — Content outside landmark regions

Rule:

region

Severity:

moderate

WCAG:

1.3.1 Info and Relationships, level A

Occurrences:

6,400 occurrences

Element:

content sitting outside landmark regions — a single template element repeated on every page

Screen 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.