evidoria

← Back to browse

Good practice Imported

Denmark's QualWeb-Powered Web Accessibility Monitoring & Enforcement Regime

Denmark · Copenhagen · See the Denmark profile · See the Copenhagen profile

Evidence: Observational / pre–post Top 9% 96/100 · Ask Evidence Copilot about this practice

Denmark's Agency for Digital Government combines automated WCAG 2.1 scanning via the open-source QualWeb tool with manual in-depth testing of forms and apps, publishes results, and can legally order public bodies to fix inaccessible content.

15
WCAG 2.1 criteria checked under simplified automated monitoring
~70
Authorities in the Government Network for Digital Inclusion (2023)

Details

Maturity
Established
Promoter
Danish Agency for Digital Government (Digitaliseringsstyrelsen)
Period
2018–present
Region (NUTS)
DK01
Keywords
digital government, web accessibility, regulatory enforcement, open-source tooling

Context

Denmark's Web Accessibility Act (2018) transposes the EU Web Accessibility Directive (2016/2102), requiring public-sector websites and apps to meet EN 301 549 (aligned with WCAG 2.1), and Executive Order No. 904/2018 requires every public body to publish an accessibility statement via the Agency for Digital Government's own Web Accessibility Statement tool.

Objectives

To combine scalable automated scanning with targeted manual testing of interactive elements automated tools cannot judge, and to give the supervising agency binding power to order fixes rather than relying on voluntary compliance.

Activities

"Simplified" monitoring runs QualWeb — a free, open-source engine built by the University of Lisbon — against 15 WCAG 2.1 criteria; "in-depth" monitoring adds manual testing of forms, navigation, modals, confirmation steps and error messages for websites and apps, with PDFs assessed separately against EN 301 549 chapter 10. The Danish Agency for Digital Government (Digitaliseringsstyrelsen) can issue binding orders to fix content, correct accessibility statements, or provide an accessible alternative, and publishes its compliance-testing results. In 2023 it also set up a Government Network for Digital Inclusion linking roughly 70 central, regional and municipal authorities.

Results

The agency publishes per-body compliance-testing outcomes and can legally compel remediation, but no aggregate national compliance percentage or cross-sector National Action Plan was found in the sources reviewed — the evidence base for this practice is its published methodology, tooling and statutory enforcement powers rather than a single outcome statistic.

Conclusions

The two-tier automated-plus-manual design, combined with binding enforcement powers, offers a replicable model for other EU member states transposing the Web Accessibility Directive, though its impact is not yet quantified by a published national compliance figure.

Implementation
Indicative cost
Medium (€50k–€500k)
Time to results
Long (> 3 years)
Staffing & skills
Danish Agency for Digital Government (Digitaliseringsstyrelsen) compliance-testing staff, manual accessibility testers for in-depth app/PDF review, Government Network for Digital Inclusion coordinators across ~70 authorities

Conditions for success

  • A statutory mandate (Web Accessibility Act 2018 / Executive Order 904/2018) giving the supervising agency binding enforcement powers
  • Access to an open-source automated testing engine (QualWeb) to make simplified monitoring scalable
  • Dedicated manual-testing capacity for interactive elements (forms, modals, error messages) that automated tools cannot judge
  • A cross-government network (like the 2023 Government Network for Digital Inclusion) to share practice across authorities

Common failure modes

  • Automated-only monitoring would miss the interactive-element failures the in-depth tier is designed to catch
  • Without a published aggregate compliance statistic, it is hard for the public to track national progress over time

Commonly funded by

National / regional programmes

Indicative funding routes for practices of this type — always check each programme's current calls and eligibility rules.

Do you run this practice? Claim it — verified implementers get a public contact pathway and can propose corrections.

Data sources

Where this practice's information was retrieved from, and when.

Similar practices you may find useful