Generated from the live rule set

Exactly what we check

All 50 Level A and AA success criteria in WCAG 2.1, and what Reachcanon does about each one. We test 24. This table is generated from the live rule set rather than maintained by hand, so it cannot drift from what the product actually does.

24/50

criteria tested

72

automated tests

9

possible, not done yet

17

need a person

9 criteria on this list could be checked automatically and we do not check them yet. They are marked as such below, because "a machine cannot decide this" and "we have not done it yet" are very different admissions, and merging them would flatter us at your expense.

Criterion by criterion

1Perceivable· 20

CriterionName
1.1.1Non-text Content

ATested

1.2.1Audio-only and Video-only (Prerecorded)

ATested

1.2.2Captions (Prerecorded)

ATested

1.2.3Audio Description or Media Alternative

ANeeds a person

1.2.4Captions (Live)

AANeeds a person

1.2.5Audio Description (Prerecorded)

AANeeds a person

1.3.1Info and Relationships

ATested

1.3.2Meaningful Sequence

ANot tested yet

1.3.3Sensory Characteristics

ANeeds a person

1.3.4Orientation

AATested

1.3.5Identify Input Purpose

AATested

1.4.1Use of Color

ATested

1.4.2Audio Control

ATested

1.4.3Contrast (Minimum)

The engine gives up whenever text sits on a gradient. We measure the rendered pixels instead.

AATested — measured by us

1.4.4Resize Text

AATested

1.4.5Images of Text

AANeeds a person

1.4.10Reflow

Needs the viewport resized to 320px and the layout re-measured — not decidable from the DOM.

AATested — measured by us

1.4.11Non-text Contrast

AANot tested yet

1.4.12Text Spacing

AATested

1.4.13Content on Hover or Focus

AANeeds a person

2Operable· 17

CriterionName
2.1.1Keyboard

ATested

2.1.2No Keyboard Trap

ANot tested yet

2.1.4Character Key Shortcuts

ANeeds a person

2.2.1Timing Adjustable

ATested

2.2.2Pause, Stop, Hide

ATested

2.3.1Three Flashes or Below Threshold

ANeeds a person

2.4.1Bypass Blocks

ATested

2.4.2Page Titled

ATested

2.4.3Focus Order

ANot tested yet

2.4.4Link Purpose (In Context)

ATested

2.4.5Multiple Ways

AANeeds a person

2.4.6Headings and Labels

AANot tested yet

2.4.7Focus Visible

Needs a control actually focused and its computed style compared — not decidable from the DOM.

AATested — measured by us

2.5.1Pointer Gestures

ANeeds a person

2.5.2Pointer Cancellation

ANeeds a person

2.5.3Label in Name

ATested

2.5.4Motion Actuation

ANeeds a person

3Understandable· 10

CriterionName
3.1.1Language of Page

ATested

3.1.2Language of Parts

AATested

3.2.1On Focus

ANeeds a person

3.2.2On Input

ANot tested yet

3.2.3Consistent Navigation

AANeeds a person

3.2.4Consistent Identification

AANeeds a person

3.3.1Error Identification

ANot tested yet

3.3.2Labels or Instructions

ATested

3.3.3Error Suggestion

AANeeds a person

3.3.4Error Prevention (Legal, Financial, Data)

AANeeds a person

4Robust· 3

CriterionName
4.1.1Parsing

ANot tested yet

4.1.2Name, Role, Value

ATested

4.1.3Status Messages

AANot tested yet

And what no scan reaches at all

These parts of EN 301 549 are outside the reach of scanning a page, whatever the tool. Their absence from a report is not evidence that they are satisfied.

  • EN 5Generic requirements

    Hardware, closed functionality and biometrics — not a web page.

  • EN 6Two-way voice communication

    Real-time text and caller ID behaviour cannot be observed by a page scan.

  • EN 7Videos with audio

    Whether captions are accurate and synchronised is a human judgement.

  • EN 11Software

    Native applications outside the browser are not in a web crawl's reach.

  • EN 12Documentation and support services

    Whether your help desk can serve a disabled customer is an operational fact, not a technical one.

  • EN 13ICT providing relay or emergency service access

    Out of scope for a website scan entirely.

Request an invitation