Skip to main content
How it worksPricingGuides

Product

Quick audit25 pages and a PDF report, €29 onceCompliance packageA documented one-off auditPublic sectorA yearly package, paid by invoiceStatement generatorFilled in from your scan resultsAPI & CIAccessibility checks in every releaseWordPress pluginFree homepage check in wp-adminSample reportThe PDF with its evidence logLog in

Methodology

What EqualVia tests, and what it can't

Every WCAG 2.2 Level A and AA success criterion, and how we cover it: an automated test, a guided manual check, or nothing of ours, where an expert has to judge. This page is generated from the lists the scanner runs, so it changes when the engine does.

Engine version 5 · axe-core 4.13.0 · updated 7 October 2026

Coverage at a glance

  • Automated test

    24 of the 55 WCAG 2.2 A/AA criteria

    At least one test whose findings we report as certain.

  • Automated hint, needs review

    3 of the 55 WCAG 2.2 A/AA criteria

    Only tests whose findings need a human look before you act on them.

  • Guided manual check only

    10 of the 55 WCAG 2.2 A/AA criteria

    No automated test; a step in the guided checklist walks you through it.

  • Not covered: needs an expert

    18 of the 55 WCAG 2.2 A/AA criteria

    Neither: a scanner can't judge these, so they need an expert or user testing.

What an automated test can tell you

  • A test finds failures of a criterion. None proves a criterion is met: “automated test” means we look for the problems a machine can recognise, not that the page passes.
  • Deque's study of real audits put automated testing at about 57% of accessibility issues by volume. The rest needs a person: the guided manual checks cover the most important part of it.
  • EN 301 549, the standard the European Accessibility Act points to, takes WCAG one to one in clause 9 (web pages) and clause 10 (documents such as PDFs).

The coverage matrix

Rows are WCAG 2.2 success criteria; the EN 301 549 clause is 9. followed by the same number. Criteria WCAG 2.2 added have a clause only in EN 301 549 V4.1.1.

1 Perceivable

CriterionCoverageAutomated testsGuided manual check
1.1.1 Non-text ContentLevel A · EN 301 549 9.1.1.1Automated test
  • axe-core: 7 rules

    aria-meter-namearia-progressbar-nameimage-altinput-image-altobject-altrole-img-altsvg-img-alt

  • PDF documents: 2 checks
  • Image descriptions actually describe the image
1.2.1 Audio-only and Video-only (Prerecorded)Level A · EN 301 549 9.1.2.1Automated test
  • axe-core: 1 rule

    audio-caption

—
1.2.2 Captions (Prerecorded)Level A · EN 301 549 9.1.2.2Automated test
  • axe-core: 1 rule

    video-caption

  • Videos have captions, and moving content can be paused
1.2.3 Audio Description or Media Alternative (Prerecorded)Level A · EN 301 549 9.1.2.3Not covered: needs an expert——
1.2.4 Captions (Live)Level AA · EN 301 549 9.1.2.4Not covered: needs an expert——
1.2.5 Audio Description (Prerecorded)Level AA · EN 301 549 9.1.2.5Not covered: needs an expert——
1.3.1 Info and RelationshipsLevel A · EN 301 549 9.1.3.1Automated test
  • axe-core: 11 rules

    aria-hidden-bodyaria-required-childrenaria-required-parentdefinition-listdlitemlistlistitemtable-fake-captiontd-has-headertd-headers-attrth-has-data-cells

  • PDF documents: 1 check
  • Headings match the page's real structure
1.3.2 Meaningful SequenceLevel A · EN 301 549 9.1.3.2Not covered: needs an expert——
1.3.3 Sensory CharacteristicsLevel A · EN 301 549 9.1.3.3Not covered: needs an expert——
1.3.4 OrientationLevel AA · EN 301 549 9.1.3.4Automated hint, needs review
  • axe-core: 1 rule

    css-orientation-lock

—
1.3.5 Identify Input PurposeLevel AA · EN 301 549 9.1.3.5Automated test
  • Personal-data fields without autocomplete
  • axe-core: 1 rule

    autocomplete-valid

—
1.4.1 Use of ColorLevel A · EN 301 549 9.1.4.1Automated test
  • axe-core: 1 rule

    link-in-text-block

  • Nothing is communicated by color alone
1.4.2 Audio ControlLevel A · EN 301 549 9.1.4.2Automated test
  • axe-core: 1 rule

    no-autoplay-audio

  • Videos have captions, and moving content can be paused
1.4.3 Contrast (Minimum)Level AA · EN 301 549 9.1.4.3Automated test
  • Low contrast over images or gradients(Needs review)
  • axe-core: 1 rule

    color-contrast

—
1.4.4 Resize TextLevel AA · EN 301 549 9.1.4.4Automated test
  • axe-core: 1 rule

    meta-viewport

  • The page still works zoomed to 200%
1.4.5 Images of TextLevel AA · EN 301 549 9.1.4.5Not covered: needs an expert——
1.4.10 ReflowLevel AA · EN 301 549 9.1.4.10Automated hint, needs review
  • Content doesn't reflow at 320px(Needs review)
—
1.4.11 Non-text ContrastLevel AA · EN 301 549 9.1.4.11Automated test
  • Form fields with a faint border
—
1.4.12 Text SpacingLevel AA · EN 301 549 9.1.4.12Automated test
  • Text clipped when spacing is increased
  • axe-core: 1 rule

    avoid-inline-spacing

—
1.4.13 Content on Hover or FocusLevel AA · EN 301 549 9.1.4.13Not covered: needs an expert——

2 Operable

CriterionCoverageAutomated testsGuided manual check
2.1.1 KeyboardLevel A · EN 301 549 9.2.1.1Automated test
  • Clickable elements the keyboard can't reach(Needs review)
  • axe-core: 3 rules

    frame-focusable-contentscrollable-region-focusableserver-side-image-map

  • Everything works with the keyboard alone
2.1.2 No Keyboard TrapLevel A · EN 301 549 9.2.1.2Automated test
  • Keyboard focus gets stuck
  • Everything works with the keyboard alone
  • Cookie banner, pop-ups and menus can be handled by keyboard
2.1.4 Character Key ShortcutsLevel A · EN 301 549 9.2.1.4Not covered: needs an expert——
2.2.1 Timing AdjustableLevel A · EN 301 549 9.2.2.1Automated test
  • axe-core: 1 rule

    meta-refresh

  • Login and time limits don't lock people out
2.2.2 Pause, Stop, HideLevel A · EN 301 549 9.2.2.2Automated test
  • Moving content without a pause button
  • axe-core: 2 rules

    blinkmarquee

  • Videos have captions, and moving content can be paused
2.3.1 Three Flashes or Below ThresholdLevel A · EN 301 549 9.2.3.1Not covered: needs an expert——
2.4.1 Bypass BlocksLevel A · EN 301 549 9.2.4.1Automated test
  • axe-core: 1 rule

    bypass

—
2.4.2 Page TitledLevel A · EN 301 549 9.2.4.2Automated test
  • axe-core: 1 rule

    document-title

  • PDF documents: 1 check
—
2.4.3 Focus OrderLevel A · EN 301 549 9.2.4.3Guided manual check only—
  • Focus moves in a logical order and stays visible
  • Cookie banner, pop-ups and menus can be handled by keyboard
2.4.4 Link Purpose (In Context)Level A · EN 301 549 9.2.4.4Automated test
  • axe-core: 2 rules

    area-altlink-name

  • Links and buttons say where they go or what they do
2.4.5 Multiple WaysLevel AA · EN 301 549 9.2.4.5Not covered: needs an expert——
2.4.6 Headings and LabelsLevel AA · EN 301 549 9.2.4.6Guided manual check only—
  • Headings match the page's real structure
2.4.7 Focus VisibleLevel AA · EN 301 549 9.2.4.7Automated test
  • No visible keyboard focus
—
2.4.11 Focus Not Obscured (Minimum)Level AA · new in 2.2 · EN 301 549 9.2.4.11 (V4.1.1)Guided manual check only—
  • Focus moves in a logical order and stays visible
2.5.1 Pointer GesturesLevel A · EN 301 549 9.2.5.1Not covered: needs an expert——
2.5.2 Pointer CancellationLevel A · EN 301 549 9.2.5.2Not covered: needs an expert——
2.5.3 Label in NameLevel A · EN 301 549 9.2.5.3Automated hint, needs review
  • axe-core: 1 rule

    label-content-name-mismatch

  • Links and buttons say where they go or what they do
2.5.4 Motion ActuationLevel A · EN 301 549 9.2.5.4Not covered: needs an expert——
2.5.7 Dragging MovementsLevel AA · new in 2.2 · EN 301 549 9.2.5.7 (V4.1.1)Guided manual check only—
  • Anything you drag also works without dragging
2.5.8 Target Size (Minimum)Level AA · new in 2.2 · EN 301 549 9.2.5.8 (V4.1.1)Automated test
  • axe-core: 1 rule

    target-size

—

3 Understandable

CriterionCoverageAutomated testsGuided manual check
3.1.1 Language of PageLevel A · EN 301 549 9.3.1.1Automated test
  • Page language doesn't match its text(Needs review)
  • axe-core: 3 rules

    html-has-langhtml-lang-validhtml-xml-lang-mismatch

  • PDF documents: 1 check
—
3.1.2 Language of PartsLevel AA · EN 301 549 9.3.1.2Automated test
  • axe-core: 1 rule

    valid-lang

—
3.2.1 On FocusLevel A · EN 301 549 9.3.2.1Not covered: needs an expert——
3.2.2 On InputLevel A · EN 301 549 9.3.2.2Not covered: needs an expert——
3.2.3 Consistent NavigationLevel AA · EN 301 549 9.3.2.3Not covered: needs an expert——
3.2.4 Consistent IdentificationLevel AA · EN 301 549 9.3.2.4Not covered: needs an expert——
3.2.6 Consistent HelpLevel A · new in 2.2 · EN 301 549 9.3.2.6 (V4.1.1)Guided manual check only—
  • Help is in the same place on every page
3.3.1 Error IdentificationLevel A · EN 301 549 9.3.3.1Guided manual check only—
  • Forms explain what to enter and what went wrong
3.3.2 Labels or InstructionsLevel A · EN 301 549 9.3.3.2Automated test
  • axe-core: 1 rule

    form-field-multiple-labels

  • Forms explain what to enter and what went wrong
3.3.3 Error SuggestionLevel AA · EN 301 549 9.3.3.3Guided manual check only—
  • Forms explain what to enter and what went wrong
3.3.4 Error Prevention (Legal, Financial, Data)Level AA · EN 301 549 9.3.3.4Not covered: needs an expert——
3.3.7 Redundant EntryLevel A · new in 2.2 · EN 301 549 9.3.3.7 (V4.1.1)Guided manual check only—
  • Nobody has to type the same thing twice
3.3.8 Accessible Authentication (Minimum)Level AA · new in 2.2 · EN 301 549 9.3.3.8 (V4.1.1)Guided manual check only—
  • Login and time limits don't lock people out

4 Robust

CriterionCoverageAutomated testsGuided manual check
4.1.2 Name, Role, ValueLevel A · EN 301 549 9.4.1.2Automated test
  • axe-core: 29 rules

    area-altaria-allowed-attraria-braille-equivalentaria-command-namearia-conditional-attraria-deprecated-rolearia-hidden-bodyaria-hidden-focusaria-input-field-namearia-prohibited-attraria-required-attraria-roledescriptionaria-rolesaria-tab-namearia-toggle-field-namearia-tooltip-namearia-valid-attraria-valid-attr-valuebutton-nameduplicate-id-ariaframe-titleframe-title-uniqueinput-button-nameinput-image-altlabellink-namenested-interactiveselect-namesummary-name

  • Cookie banner, pop-ups and menus can be handled by keyboard
  • A screen reader can complete the main task
4.1.3 Status MessagesLevel AA · EN 301 549 9.4.1.3Guided manual check only—
  • A screen reader can complete the main task

How sure each finding is

axe-core's standard rules are built to report no false findings. Our own checks and axe's experimental rules are measured instead: we check their findings by hand on real webshops, and a rule's findings count as certain only when at least 95% of at least 20 were real issues. Below that, findings are marked “needs review”.

CheckSourceFindings reported asHand-checked on real sites
Low contrast over images or gradientscs-bg-contrast · WCAG 1.4.3EqualViaNeeds review94% of 32 were real
Page language doesn't match its textcs-lang-mismatch · WCAG 3.1.1EqualViaNeeds reviewNot measured yet
No visible keyboard focuscs-focus-visible · WCAG 2.4.7EqualViaCertain100% of 22 were real
Keyboard focus gets stuckcs-keyboard-trap · WCAG 2.1.2EqualViaCertainNot sampled: each finding is confirmed directly (real key presses, the file's structure)
Text clipped when spacing is increasedcs-text-spacing · WCAG 1.4.12EqualViaCertain95% of 41 were real
Content doesn't reflow at 320pxcs-reflow · WCAG 1.4.10EqualViaNeeds review100% of 10 were real
Form fields with a faint bordercs-field-contrast · WCAG 1.4.11EqualViaCertain95% of 42 were real
Moving content without a pause buttoncs-autoplay · WCAG 2.2.2EqualViaCertain100% of 25 were real
Clickable elements the keyboard can't reachcs-click-only · WCAG 2.1.1EqualViaNeeds review81% of 37 were real
Personal-data fields without autocompletecs-autocomplete · WCAG 1.3.5EqualViaCertain100% of 34 were real
Untagged PDF documentscs-pdf-untagged · WCAG 1.3.1EqualVia (PDF)CertainNot sampled: each finding is confirmed directly (real key presses, the file's structure)
Scanned PDFs without a text layercs-pdf-no-text · WCAG 1.1.1EqualVia (PDF)CertainNot sampled: each finding is confirmed directly (real key presses, the file's structure)
PDF images without alternative textcs-pdf-figure-alt · WCAG 1.1.1EqualVia (PDF)CertainNot sampled: each finding is confirmed directly (real key presses, the file's structure)
PDF documents without a languagecs-pdf-no-lang · WCAG 3.1.1EqualVia (PDF)CertainNot sampled: each finding is confirmed directly (real key presses, the file's structure)
PDF documents without a displayed titlecs-pdf-no-title · WCAG 2.4.2EqualVia (PDF)CertainNot sampled: each finding is confirmed directly (real key presses, the file's structure)
Display locked to one orientationcss-orientation-lock · WCAG 1.3.4axe-core, experimentalNeeds reviewNot measured yet
Accessible name doesn't include the visible labellabel-content-name-mismatch · WCAG 2.5.3axe-core, experimentalNeeds review100% of 11 were real
Table cells used as a captiontable-fake-caption · WCAG 1.3.1axe-core, experimentalNeeds reviewNot measured yet
Data cells without headers in large tablestd-has-header · WCAG 1.3.1axe-core, experimentalNeeds review100% of 2 were real

Which pages we test

A crawl picks pages the way W3C's WCAG-EM methodology samples a site: key pages first (home, a category, a product, cart, checkout, contact, search results), then one page of every template found through links and the sitemap, then more of each. Key pages are also tested with the cookie banner still open and at a phone's width (390 px); every page is tested as it looks once the banner is accepted. A free scan tests one page.

How our scanner visits a site

Engine versions

Every scan records the engine version it ran with, and reports name it. The rules we keep to:

  • Anything that changes what the engine reports gets a new version: a rule added, rewritten or retired, or an axe-core upgrade. An upgrade also means rerunning our test pages and real-shop benchmark before it ships.
  • A rescan doesn't count findings of a check added or rewritten since the previous scan as new issues, nor the ones it no longer makes as fixed.
  • Numbers we publish keep the engine version they were measured with. We don't recompute them with a later engine; a new measurement is a new publication.

  1. Version 5 · 7 October 2026 · axe-core 4.13.0

    Four new own checks: form field contrast (1.4.11), autoplaying carousels and video (2.2.2), controls only a mouse can use (2.1.1, needs review) and missing autocomplete on personal data fields (1.3.5).

  2. Version 4 · 7 October 2026 · axe-core 4.13.0

    Crawls sample pages the way W3C's WCAG-EM methodology does: key pages first (home, category, product, cart, checkout, contact, search results), then one page per template. Key pages are also tested with the cookie banner open and at a phone's width; the rest after the banner is accepted.

  3. Version 3 · 7 October 2026 · axe-core 4.13.0

    Reflow, text spacing and label-in-name measure what a reader actually sees; the “paragraph styled as a heading” rule was retired (too many false findings); what axe-core can't decide is kept as a separate list to check by hand.

  4. Version 2 · 7 October 2026 · axe-core 4.13.0

    A fixed list of rules per version; every finding gets a fingerprint, so a rescan reports only real changes; findings are labelled standard, EqualVia or experimental, and those inside another company's embed are listed apart and not counted.

  5. Version 1 · 6 October 2026 · axe-core 4.13.0

    axe-core with all its WCAG 2.0–2.2 A/AA rules, plus our first own checks (text over images, keyboard focus, text spacing, reflow at 320 px, keyboard trap, page language). The 2026 Hungarian webshop survey was measured with this version.