Guides
What 9,402 Norwegian accessibility statements reveal
An analysis of 9,402 completed accessibility statements in Uutilsynet's open dataset: declared status, freshness, and the WCAG criteria most often reported as non-conforming.
By Eivind Pihl Martinsen, Synli.aiLast updated August 23, 2026
In 2026, Uutilsynet opened a machine-readable dataset containing every completed Norwegian accessibility statement. Our snapshot covers 9,402 statements from 1,323 unique organisation numbers. That makes pattern analysis possible without ranking individual organisations.
Four headline figures
- Completed statements
- 9,4028,692 websites · 710 apps
- Unique organisation numbers
- 1,323The Synli aggregate publishes the count only
- Updated within the last year
- 52.5%4,940 statements
- Declared criterion breaches
- 62,424Sum of the source talBrot field
2,184 statements (23.2%) say “in conformance”, 7,196 (76.5%) say “partially conforming”, and 22 (0.2%) say “not conforming”. These are self-declared statuses, not independent certification.
The WCAG criteria most often declared non-conforming
The table ranks criteria by the number of statements answering no. The share uses statements that answered yes or no for that criterion. Not-relevant answers remain available in the JSON aggregate but stay outside the percentage denominator.
| WCAG criterion | Declared breaches | Assessed | Breach share |
|---|---|---|---|
| 1.1.1 — Non-text Content | 3,812 | 8,919 | 42.7% |
| 1.3.1 — Info and Relationships | 3,522 | 9,242 | 38.1% |
| 1.4.3 — Contrast (Minimum) | 3,090 | 9,320 | 33.2% |
| 4.1.2 — Name, Role, Value | 2,727 | 9,113 | 29.9% |
| 2.4.7 — Focus Visible | 2,722 | 9,270 | 29.4% |
| 4.1.1 — Parsing | 2,470 | 9,071 | 27.2% |
| 2.1.1 — Keyboard | 2,436 | 9,250 | 26.3% |
| 1.4.11 — Non-text Contrast | 2,431 | 8,962 | 27.1% |
| 1.4.12 — Text Spacing | 2,301 | 8,995 | 25.6% |
| 2.5.3 — Label in Name | 2,186 | 8,707 | 25.1% |
What this means for prioritisation
- Non-text content, semantic structure, contrast, component names and visible focus recur. They deserve permanent checks in design, development and editorial workflows.
- Automate what can be measured reliably, but keep human review for areas such as alternative-text quality, meaning, keyboard flow and representative user tasks.
- Treat the accessibility statement as maintained evidence. 52.5% of statements in this snapshot are marked updated within the last year.
- Prioritise using your own findings and current solution state. National patterns are context, not a substitute for testing.
Method and reproducibility
- The snapshot was retrieved on 2026-08-23 from Uutilsynet's open JSON endpoint. Every content page was fetched and checked against the total before the aggregate was written.
- Headline totals use the source talSamsvar, talBrot and talIkkjeRelevant fields. The criterion table uses oppfyllerAltInnhaldKravet; breach share is no divided by yes plus no.
- Organisation names, web addresses, organisation numbers, statement IDs and free-text details are omitted from the public Synli aggregate.
- The snapshot can be rebuilt from the repository with pnpm --filter @synli/landing refresh:uutilsynet. The production build does not call the external API.
FAQ
Are these regulatory audit or automated-test results?
No. The figures are aggregated from completed accessibility statements, which contain organisations' own declared status. They are not Uutilsynet inspection findings, a representative national survey, or a new Synli scan.
Why does the assessed-statement denominator vary by WCAG criterion?
A requirement can be marked not relevant, and website and app statements do not use exactly the same requirement set. The table therefore divides no answers by yes plus no for each criterion; not-relevant answers stay outside the denominator.
Are the figures updated in real time?
No. Uutilsynet describes the source dataset as updated daily, while this page uses a controlled snapshot retrieved on 2026-08-23. The visible snapshot date keeps each figure auditable.
Sources
Related guides

The Norwegian accessibility statement on uustatus.no
What a Norwegian accessibility statement (tilgjengelighetserklæring) is, who must publish one, how to complete it on uustatus.no, and how reviewed Synli evidence can support the manual workflow.
Last updated August 23, 2026
WCAG 2.1 and 2.2 Level AA requirements, explained
Use this WCAG 2.1 and 2.2 AA checklist to understand the requirements, what changed in 2.2, Norway's 48 vs 35 success criteria, and what an accessibility scanner can verify.
Last updated August 23, 2026