NormLedger

How NormLedger works

How NormLedger works

Know what was tested, what was fixed and retested, and what was still open when each statement was published.

The flow

NormLedger is the governance layer after scanners and advisors: one place to record outcomes, decisions, fixes and published statements.

Four steps

  1. 1. Scan

    You:
    add your site, choose the laws that apply.
    NormLedger:
    checks every WCAG A/AA criterion on each scheduled scan.
    You get:
    one outcome per criterion.
  2. 2. Decide

    You:
    confirm what a scan cannot decide.
    NormLedger:
    records who decided, when, why.
    You get:
    a complete picture, not just failures.
  3. 3. Fix and retest

    You:
    assign tasks to your team or agency.
    NormLedger:
    retests on the next scan.
    You get:
    fixed, new, came back - per scan.
  4. 4. Publish and prove

    You:
    publish the statement.
    NormLedger:
    keeps every version and a record no one can alter unnoticed.
    You get:
    statement, dossier, auditor access.

When teams start

Compared with the usual approaches

Comparison of overlay widgets, free scanners, one-off audits and NormLedger
What you needOverlay widgetFree scannerOne-off auditNormLedger
Fixes the codeNoNoLists fixesTracks fixes and retests
Every criterion has an outcomeNoAutomated onlyYes, onceYes, every scan
Record of who decided whatNoNoIn the reportEvidence log, timestamped
Statement kept currentNoNoNoVersions + out-of-date notice

Every NormLedger claim must be true today; reviewed by the product team before publish.

Where your data goes

Hosted in the EU (database: Neon EU; app: Cloudflare). What we store: page addresses, findings, decisions, statements. What we never store: passwords in logs; personal data from your pages beyond what a finding needs. Full list of sub-processors on Security and trust.

Technical detail

Scanner coverage, limits and allowlist facts - the same content formerly on How we scan.

What each scan covers (criteria by WCAG version and level)

Each scheduled scan records one outcome per WCAG A/AA criterion in scope for your target. Open the full technical detail

What a scan cannot decide

Some criteria need a person. NormLedger records who decided and why - it does not invent a pass. Open the full technical detail

How the automated score works

The automated score is a transparent method sheet for automated checks only - not a legal conformance claim. Open the full technical detail

Our scanner on your site (user agent, IPs, rate limit, robots.txt, bot protection)

User agent, egress IPs, rate limit, robots.txt and allowlist guidance are kept verbatim below. Open the full technical detail

Laws we map to

You declare which laws apply. NormLedger maps WCAG outcomes to those laws; it does not decide legal applicability for you.

Full technical detail (coverage, criteria table, score, scanner)

What each scan covers

  • WCAG 2.1 AA: all 50 criteria have an automated check (11 decided, 24 find failures, 15 flag for review) + AAA: 16 automated checks and 12 guided checks
  • WCAG 2.2 AA: all 55 criteria have an automated check (12 decided, 26 find failures, 17 flag for review) + AAA: 19 automated checks and 12 guided checks

AAA checks say "find failures" or "flag for review" until our accuracy review is complete. A check counts as automated once it is proven on test pages. The other AAA criteria are guided checks that you complete with a list.

What each outcome means
Decided by the scan
Example, 3.1.1 Language of Page: the page language is missing. The scan sees this and records the failure itself.
Failures found by the scan - you confirm the pass
Example, 1.1.1 Non-text Content: the scan finds an image with no alt text. When an alt text already exists, only you can say whether its meaning fits the image, so you confirm the pass.
Possible problems flagged - you decide
Example, 1.3.3 Sensory Characteristics: an instruction says 'use the button below'. The scan flags it and you decide whether the instruction still works without seeing the layout.
Checked by you with a guided list
Example, 1.2.6 Sign Language (AAA): no scanner can judge sign language in a video, so you get a guided checklist.

Criteria by WCAG version and level

Choose a WCAG version. Each row shows the outcome the scan records. AAA rows show an automated outcome only for the criteria proven today.

WCAG 2.2: 86 criteria

Level A

WCAG 2.2 Level A criteria and outcomes
CriterionNameOutcome
1.1.1Non-text ContentFailures found by the scan - you confirm the pass
1.2.1Audio-only and Video-only (Prerecorded)Possible problems flagged - you decide
1.2.2Captions (Prerecorded)Failures found by the scan - you confirm the pass
1.2.3Audio Description or Media Alternative (Prerecorded)Possible problems flagged - you decide
1.3.1Info and RelationshipsFailures found by the scan - you confirm the pass
1.3.2Meaningful SequencePossible problems flagged - you decide
1.3.3Sensory CharacteristicsPossible problems flagged - you decide
1.4.1Use of ColorFailures found by the scan - you confirm the pass
1.4.2Audio ControlDecided by the scan
2.1.1KeyboardFailures found by the scan - you confirm the pass
2.1.2No Keyboard TrapDecided by the scan
2.1.4Character Key ShortcutsFailures found by the scan - you confirm the pass
2.2.1Timing AdjustableFailures found by the scan - you confirm the pass
2.2.2Pause, Stop, HideFailures found by the scan - you confirm the pass
2.3.1Three Flashes or Below ThresholdPossible problems flagged - you decide
2.4.1Bypass BlocksDecided by the scan
2.4.2Page TitledFailures found by the scan - you confirm the pass
2.4.3Focus OrderFailures found by the scan - you confirm the pass
2.4.4Link Purpose (In Context)Failures found by the scan - you confirm the pass
2.5.1Pointer GesturesPossible problems flagged - you decide
2.5.2Pointer CancellationFailures found by the scan - you confirm the pass
2.5.3Label in NameDecided by the scan
2.5.4Motion ActuationPossible problems flagged - you decide
3.1.1Language of PageDecided by the scan
3.2.1On FocusDecided by the scan
3.2.2On InputFailures found by the scan - you confirm the pass
3.2.6Consistent HelpNew in WCAG 2.2Failures found by the scan - you confirm the pass
3.3.1Error IdentificationFailures found by the scan - you confirm the pass
3.3.2Labels or InstructionsFailures found by the scan - you confirm the pass
3.3.7Redundant EntryNew in WCAG 2.2Possible problems flagged - you decide
4.1.2Name, Role, ValueFailures found by the scan - you confirm the pass

Level AA

WCAG 2.2 Level AA criteria and outcomes
CriterionNameOutcome
1.2.4Captions (Live)Possible problems flagged - you decide
1.2.5Audio Description (Prerecorded)Possible problems flagged - you decide
1.3.4OrientationDecided by the scan
1.3.5Identify Input PurposeFailures found by the scan - you confirm the pass
1.4.3Contrast (Minimum)Decided by the scan
1.4.4Resize TextFailures found by the scan - you confirm the pass
1.4.5Images of TextPossible problems flagged - you decide
1.4.10ReflowDecided by the scan
1.4.11Non-text ContrastFailures found by the scan - you confirm the pass
1.4.12Text SpacingFailures found by the scan - you confirm the pass
1.4.13Content on Hover or FocusFailures found by the scan - you confirm the pass
2.4.5Multiple WaysFailures found by the scan - you confirm the pass
2.4.6Headings and LabelsPossible problems flagged - you decide
2.4.7Focus VisibleDecided by the scan
2.4.11Focus Not Obscured (Minimum)New in WCAG 2.2Decided by the scan
2.5.7Dragging MovementsNew in WCAG 2.2Possible problems flagged - you decide
2.5.8Target Size (Minimum)New in WCAG 2.2Decided by the scan
3.1.2Language of PartsFailures found by the scan - you confirm the pass
3.2.3Consistent NavigationFailures found by the scan - you confirm the pass
3.2.4Consistent IdentificationPossible problems flagged - you decide
3.3.3Error SuggestionPossible problems flagged - you decide
3.3.4Error Prevention (Legal, Financial, Data)Possible problems flagged - you decide
3.3.8Accessible Authentication (Minimum)New in WCAG 2.2Failures found by the scan - you confirm the pass
4.1.3Status MessagesPossible problems flagged - you decide

Level AAA

WCAG 2.2 Level AAA criteria and outcomes
CriterionNameOutcome
1.2.6Sign Language (Prerecorded)Checked by you with a guided list
1.2.7Extended Audio Description (Prerecorded)Checked by you with a guided list
1.2.8Media Alternative (Prerecorded)Checked by you with a guided list
1.2.9Audio-only (Live)Checked by you with a guided list
1.3.6Identify PurposePossible problems flagged - you decide
1.4.6Contrast (Enhanced)Failures found by the scan - you confirm the pass
1.4.7Low or No Background AudioChecked by you with a guided list
1.4.8Visual PresentationFailures found by the scan - you confirm the pass
1.4.9Images of Text (No Exception)Possible problems flagged - you decide
2.1.3Keyboard (No Exception)Failures found by the scan - you confirm the pass
2.2.3No TimingPossible problems flagged - you decide
2.2.4InterruptionsFailures found by the scan - you confirm the pass
2.2.5Re-authenticatingChecked by you with a guided list
2.2.6TimeoutsPossible problems flagged - you decide
2.3.2Three FlashesChecked by you with a guided list
2.3.3Animation from InteractionsFailures found by the scan - you confirm the pass
2.4.8LocationChecked by you with a guided list
2.4.9Link Purpose (Link Only)Possible problems flagged - you decide
2.4.10Section HeadingsPossible problems flagged - you decide
2.4.12Focus Not Obscured (Enhanced)New in WCAG 2.2Failures found by the scan - you confirm the pass
2.4.13Focus AppearanceNew in WCAG 2.2Failures found by the scan - you confirm the pass
2.5.5Target Size (Enhanced)Failures found by the scan - you confirm the pass
2.5.6Concurrent Input MechanismsChecked by you with a guided list
3.1.3Unusual WordsChecked by you with a guided list
3.1.4AbbreviationsPossible problems flagged - you decide
3.1.5Reading LevelPossible problems flagged - you decide
3.1.6PronunciationChecked by you with a guided list
3.2.5Change on RequestFailures found by the scan - you confirm the pass
3.3.5HelpChecked by you with a guided list
3.3.6Error Prevention (All)Possible problems flagged - you decide
3.3.9Accessible Authentication (Enhanced)New in WCAG 2.2Failures found by the scan - you confirm the pass

WCAG 2.0 AA is fully included in WCAG 2.1 AA. WCAG 1.0 (1999) was replaced in 2008, no current law or EN 301 549 uses it, so it is not scanned.

What no scanner can do

  • Does not replace a legal assessment.
  • A pass is not a guarantee of conformance.
  • Never submits forms or completes purchases.
  • Logged-in areas only when you set them up.
  • PDF checks are limited to linked documents within size and time caps.
  • Native apps are not tested.

How the automated score works

The automated score runs from 0 to 10, with one decimal. It averages every scanned page. For each page we take the share of applicable criteria that passed, among those the scan decides or can fail, weighted so level A counts more than AA and higher-impact failures weigh more. Flagged items and criteria that need a person do not move the score. A top score never means compliant.

Shown on free samples, prospect summaries, emails and Website Scans.

For the full score method, write to [email protected].

Our scanner on your site

NormLedger's scanner checks the web pages it is asked to check for accessibility barriers.

User agent

Every request sends this user agent. VERSION is the Chrome version of the scanner's browser. To match the scanner, look for NormLedger/ in the user agent:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/VERSION.0.0.0 Safari/537.36 NormLedger/1.0 (+https://www.normledger.com/how-we-scan#our-scanner)

Egress IP addresses

Traffic leaves from the addresses published at scanner-ips.json. Update your allowlist when the updated date changes.

Rate limit

The scanner paces itself per site and honours the Crawl-delay set in robots.txt between pages.

robots.txt

On multi-page crawls the scanner reads robots.txt and skips disallowed paths. A scan of a page or site you entered or declared in your account is a consented request.

Allow the scanner through your bot protection

Allow requests where the user agent contains NormLedger/ AND the source IP is in the published list. Expand a vendor for steps.

Cloudflare

Create a WAF custom rule: user agent contains NormLedger/ AND source IP is in the published list, with action Skip (Bot Fight Mode and managed rules). Place it before other bot rules.

Akamai

In Bot Manager, allowlist requests whose user agent contains NormLedger/ and whose IP is in scanner-ips.json.

DataDome

In DataDome, allowlist requests whose user agent contains NormLedger/ and whose IP is in scanner-ips.json.

Contact

Questions: [email protected].

See pricing

Questions compliance owners actually ask

What can a scan not prove?

A scan cannot prove full legal conformance, judge complex interactions alone, or replace a human review of criteria that need judgement. See How it works.

Who decides the criteria the scan cannot decide?

Your team (or your agency) records the decision in NormLedger, with who, when and why. See How it works.

Do you offer an overlay widget?

No. Overlays do not fix the underlying code. NormLedger tracks real fixes and retests so you can show what changed.

How NormLedger works | NormLedger