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. 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. Decide
- You:
- confirm what a scan cannot decide.
- NormLedger:
- records who decided, when, why.
- You get:
- a complete picture, not just failures.
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. 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
- A public tender asks for EN 301 549 or a conformance reportACR / VPAT
- You offer a consumer service in the EU (European Accessibility Act)EAA (opens in a new tab)
- You are a public body (Web Accessibility Directive, DL 83/2018)Public sector
- You received a complaint or a problem reportReport a problem flow
- You are relaunching or redesigning your siteFree scan
- An agency is handing a site over to youPartners
- An audit or due diligence is comingDossier
Compared with the usual approaches
| What you need | Overlay widget | Free scanner | One-off audit | NormLedger |
|---|---|---|---|---|
| Fixes the code | No | No | Lists fixes | Tracks fixes and retests |
| Every criterion has an outcome | No | Automated only | Yes, once | Yes, every scan |
| Record of who decided what | No | No | In the report | Evidence log, timestamped |
| Statement kept current | No | No | No | Versions + 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
| Criterion | Name | Outcome |
|---|---|---|
| 1.1.1 | Non-text Content | Failures found by the scan - you confirm the pass |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | Possible problems flagged - you decide |
| 1.2.2 | Captions (Prerecorded) | Failures found by the scan - you confirm the pass |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | Possible problems flagged - you decide |
| 1.3.1 | Info and Relationships | Failures found by the scan - you confirm the pass |
| 1.3.2 | Meaningful Sequence | Possible problems flagged - you decide |
| 1.3.3 | Sensory Characteristics | Possible problems flagged - you decide |
| 1.4.1 | Use of Color | Failures found by the scan - you confirm the pass |
| 1.4.2 | Audio Control | Decided by the scan |
| 2.1.1 | Keyboard | Failures found by the scan - you confirm the pass |
| 2.1.2 | No Keyboard Trap | Decided by the scan |
| 2.1.4 | Character Key Shortcuts | Failures found by the scan - you confirm the pass |
| 2.2.1 | Timing Adjustable | Failures found by the scan - you confirm the pass |
| 2.2.2 | Pause, Stop, Hide | Failures found by the scan - you confirm the pass |
| 2.3.1 | Three Flashes or Below Threshold | Possible problems flagged - you decide |
| 2.4.1 | Bypass Blocks | Decided by the scan |
| 2.4.2 | Page Titled | Failures found by the scan - you confirm the pass |
| 2.4.3 | Focus Order | Failures found by the scan - you confirm the pass |
| 2.4.4 | Link Purpose (In Context) | Failures found by the scan - you confirm the pass |
| 2.5.1 | Pointer Gestures | Possible problems flagged - you decide |
| 2.5.2 | Pointer Cancellation | Failures found by the scan - you confirm the pass |
| 2.5.3 | Label in Name | Decided by the scan |
| 2.5.4 | Motion Actuation | Possible problems flagged - you decide |
| 3.1.1 | Language of Page | Decided by the scan |
| 3.2.1 | On Focus | Decided by the scan |
| 3.2.2 | On Input | Failures found by the scan - you confirm the pass |
| 3.2.6 | Consistent HelpNew in WCAG 2.2 | Failures found by the scan - you confirm the pass |
| 3.3.1 | Error Identification | Failures found by the scan - you confirm the pass |
| 3.3.2 | Labels or Instructions | Failures found by the scan - you confirm the pass |
| 3.3.7 | Redundant EntryNew in WCAG 2.2 | Possible problems flagged - you decide |
| 4.1.2 | Name, Role, Value | Failures found by the scan - you confirm the pass |
Level AA
| Criterion | Name | Outcome |
|---|---|---|
| 1.2.4 | Captions (Live) | Possible problems flagged - you decide |
| 1.2.5 | Audio Description (Prerecorded) | Possible problems flagged - you decide |
| 1.3.4 | Orientation | Decided by the scan |
| 1.3.5 | Identify Input Purpose | Failures found by the scan - you confirm the pass |
| 1.4.3 | Contrast (Minimum) | Decided by the scan |
| 1.4.4 | Resize Text | Failures found by the scan - you confirm the pass |
| 1.4.5 | Images of Text | Possible problems flagged - you decide |
| 1.4.10 | Reflow | Decided by the scan |
| 1.4.11 | Non-text Contrast | Failures found by the scan - you confirm the pass |
| 1.4.12 | Text Spacing | Failures found by the scan - you confirm the pass |
| 1.4.13 | Content on Hover or Focus | Failures found by the scan - you confirm the pass |
| 2.4.5 | Multiple Ways | Failures found by the scan - you confirm the pass |
| 2.4.6 | Headings and Labels | Possible problems flagged - you decide |
| 2.4.7 | Focus Visible | Decided by the scan |
| 2.4.11 | Focus Not Obscured (Minimum)New in WCAG 2.2 | Decided by the scan |
| 2.5.7 | Dragging MovementsNew in WCAG 2.2 | Possible problems flagged - you decide |
| 2.5.8 | Target Size (Minimum)New in WCAG 2.2 | Decided by the scan |
| 3.1.2 | Language of Parts | Failures found by the scan - you confirm the pass |
| 3.2.3 | Consistent Navigation | Failures found by the scan - you confirm the pass |
| 3.2.4 | Consistent Identification | Possible problems flagged - you decide |
| 3.3.3 | Error Suggestion | Possible problems flagged - you decide |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | Possible problems flagged - you decide |
| 3.3.8 | Accessible Authentication (Minimum)New in WCAG 2.2 | Failures found by the scan - you confirm the pass |
| 4.1.3 | Status Messages | Possible problems flagged - you decide |
Level AAA
| Criterion | Name | Outcome |
|---|---|---|
| 1.2.6 | Sign Language (Prerecorded) | Checked by you with a guided list |
| 1.2.7 | Extended Audio Description (Prerecorded) | Checked by you with a guided list |
| 1.2.8 | Media Alternative (Prerecorded) | Checked by you with a guided list |
| 1.2.9 | Audio-only (Live) | Checked by you with a guided list |
| 1.3.6 | Identify Purpose | Possible problems flagged - you decide |
| 1.4.6 | Contrast (Enhanced) | Failures found by the scan - you confirm the pass |
| 1.4.7 | Low or No Background Audio | Checked by you with a guided list |
| 1.4.8 | Visual Presentation | Failures found by the scan - you confirm the pass |
| 1.4.9 | Images of Text (No Exception) | Possible problems flagged - you decide |
| 2.1.3 | Keyboard (No Exception) | Failures found by the scan - you confirm the pass |
| 2.2.3 | No Timing | Possible problems flagged - you decide |
| 2.2.4 | Interruptions | Failures found by the scan - you confirm the pass |
| 2.2.5 | Re-authenticating | Checked by you with a guided list |
| 2.2.6 | Timeouts | Possible problems flagged - you decide |
| 2.3.2 | Three Flashes | Checked by you with a guided list |
| 2.3.3 | Animation from Interactions | Failures found by the scan - you confirm the pass |
| 2.4.8 | Location | Checked by you with a guided list |
| 2.4.9 | Link Purpose (Link Only) | Possible problems flagged - you decide |
| 2.4.10 | Section Headings | Possible problems flagged - you decide |
| 2.4.12 | Focus Not Obscured (Enhanced)New in WCAG 2.2 | Failures found by the scan - you confirm the pass |
| 2.4.13 | Focus AppearanceNew in WCAG 2.2 | Failures found by the scan - you confirm the pass |
| 2.5.5 | Target Size (Enhanced) | Failures found by the scan - you confirm the pass |
| 2.5.6 | Concurrent Input Mechanisms | Checked by you with a guided list |
| 3.1.3 | Unusual Words | Checked by you with a guided list |
| 3.1.4 | Abbreviations | Possible problems flagged - you decide |
| 3.1.5 | Reading Level | Possible problems flagged - you decide |
| 3.1.6 | Pronunciation | Checked by you with a guided list |
| 3.2.5 | Change on Request | Failures found by the scan - you confirm the pass |
| 3.3.5 | Help | Checked by you with a guided list |
| 3.3.6 | Error Prevention (All) | Possible problems flagged - you decide |
| 3.3.9 | Accessible Authentication (Enhanced)New in WCAG 2.2 | Failures 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].