WCAG 2.1 level AA (EN 301 549 / European Accessibility Act)
Scope
20 pages, automated check
This report does not say you are compliant. No automated tool can
honestly say that. Automated checks find roughly a third of accessibility barriers;
the rest need a human, and some need a person who actually uses a screen reader.
What follows is what a machine could prove, on the date above. Treat it as a starting
list, not a clean bill of health.
Summary
7issue types
20pages scanned
CRITICALhighest severity
These 7 issue types affect 230 elements on 4 of the 20 pages scanned.
Element count is not a measure of work: a single rule in a shared stylesheet or
template can account for hundreds of them.
Since the last scan
Compared with 2026-08-24. “No longer
detected” is not the same as “fixed” — an element can
disappear because a page changed, or because it only shows under conditions this
scan did not reach.
These two scans did not run from the same place.
Sites can serve different content depending on where the request comes from —
region redirects, cookie banners, A/B tests. Some of the differences below may
reflect that, not a change to the site.
The set of pages scanned changed since last time
(15 added, 0 no longer reached).
Some of the differences below may reflect that, not a change to the site.
NEWARIA attributes must conform to valid namesaria-valid-attr18 elements
NEWFrames must have an accessible nameframe-title1 element
WORSEImages must have alternative textimage-alt33 → 34 elements
WORSELinks must have discernible textlink-name7 → 173 elements
3 issue types unchanged.
What to fix first
Ordered by severity, then by how many elements are affected. An issue on
many pages is usually one fix in a shared template. Each one carries its axe-core rule
id, so you can look the rule up and check our count against your own.
On 282 elements the check stopped short of
a verdict. These are not counted in the numbers above — and they are
not cleared either. A rule lands here when it can see something worth questioning but
cannot settle it without a person: the element carries its own text, or its meaning
depends on context a machine does not have.
ARIA attributes must conform to valid valuesaria-valid-attr-value18 elements
<video> elements must have captionsvideo-caption3 elements
Links must be distinguishable without relying on colorlink-in-text-block235 elements
Elements must only use permitted ARIA attributesaria-prohibited-attr18 elements
Elements must meet minimum color contrast ratio thresholdscolor-contrast4 elements
Table headers in a data table must refer to data cellsth-has-data-cells4 elements
This is also the usual reason a count here differs from what you
get by searching your own source for the same pattern. Counts are per rule, and a rule
weighs conditions the pattern alone does not capture — an element’s own text,
its role, its ancestors. If a number looks off by a few, check it against the rule id
rather than against the description.
Pages
Pages ordered by how many elements are affected. A page can have few
issue types but many affected elements, or the reverse.