What is BITV 2.0?
The Barrierefreie-Informationstechnik-Verordnung (BITV 2.0)
is Germany’s federal regulation for accessible information and communication
technology. It defines digital accessibility requirements for federal public
sector bodies and supports the implementation of the German Disability Equality
Act (Behindertengleichstellungsgesetz – BGG).
BITV 2.0 applies to websites, mobile applications, electronic administrative
processes, intranets, extranets, and certain graphical user interfaces operated
by federal public bodies. Its technical requirements are based primarily on the
harmonized European standard EN 301 549.
BITV 2.0 primarily concerns Germany’s federal public sector. German states have
their own accessibility legislation and regulations. Private-sector products and
consumer services may instead fall under the
European Accessibility Act and Germany’s BFSG.
Who must comply with BITV 2.0?
BITV 2.0 applies primarily to public bodies of the German federal government.
Depending on the organization, procurement conditions, contractual requirements,
or state-level legislation may extend similar accessibility obligations to
contractors and other service providers.
- Federal ministries, authorities, and government agencies
- Federal public bodies covered by the German Disability Equality Act
- Organizations and institutions attributable to the federal government
- Service providers delivering digital systems under applicable public procurement requirements
- Websites, applications, and digital services subject to comparable state accessibility laws
What digital services are covered?
The requirements are broader than public-facing websites. Depending on the
organization and use case, the following digital assets may be included:
- Public websites and web applications
- Mobile applications
- Electronic administrative processes and online forms
- Intranets and extranets
- Internally used mobile applications
- Digital documents, including relevant PDF and office documents
- Certain software interfaces and information and communication technology
Key BITV 2.0 requirements
EN 301 549
BITV 2.0 refers to the applicable harmonized European standard for accessible
ICT. EN 301 549 covers websites, mobile applications, documents, software,
and other digital technologies.
WCAG 2.1 Level AA
The web and mobile requirements within EN 301 549 are largely aligned with
WCAG 2.1 Level AA. Content must be perceivable, operable, understandable,
and robust.
Accessibility Statement
Public bodies must publish an accessibility statement explaining the
accessibility status of their website or application and identifying any
known limitations.
Feedback Mechanism
Users must have an accessible way to report barriers and request accessible
information. The feedback mechanism should be directly reachable from every
page of a website.
DGS and Leichte Sprache
Required core information must be made available in German Sign Language
(Deutsche Gebärdensprache – DGS) and Easy Language
(Leichte Sprache).
Ongoing Review
Accessibility is not a one-time task. Statements, content, interfaces, and
essential user journeys should be reviewed whenever material changes are made.
Accessibility statement and feedback obligations
A BITV accessibility statement should clearly describe the current level of
accessibility, identify non-accessible content, explain the reason for any
limitations, and provide an accessible contact method for reporting barriers.
The statement should also include:
- The method used to evaluate accessibility
- The date of the evaluation and the statement’s latest update
- Known accessibility issues and available alternatives
- A feedback and contact mechanism
- Information about the applicable enforcement or conciliation procedure
For federal public-sector websites, the statement and feedback mechanism should
be directly accessible from every page. The statement must be reviewed annually
and following substantial changes to the website or application.
BITV 2.0, BGG, BFSG, and the European Accessibility Act
These laws and standards are related, but they do not have the same scope:
- BGG: Germany’s Disability Equality Act provides the legal
foundation for accessibility obligations affecting federal public bodies. - BITV 2.0: Defines detailed digital accessibility requirements
for federal public-sector information technology. - BFSG: Germany’s Accessibility Strengthening Act implements
the European Accessibility Act for covered private-sector products and services. - European Accessibility Act: Establishes accessibility
requirements for selected products and consumer services across the European Union.
An organization may be affected by more than one framework, depending on its
legal status, services, customers, and procurement obligations.
How to approach BITV 2.0 accessibility
- Define the scope: Identify relevant websites, applications,
documents, administrative processes, and essential user journeys. - Run automated testing: Detect recurring technical issues
across pages, templates, and components. - Perform manual and behavioral testing: Test keyboard access,
focus management, forms, dynamic content, and assistive-technology interactions. - Prioritize remediation: Organize findings by impact, severity,
affected components, and user journeys. - Fix and verify: Correct issues in the website or application
and verify that each remediation resolves the original barrier. - Publish the required information: Provide an accessibility
statement, feedback mechanism, DGS content, and Easy-Language information where required. - Monitor continuously: Retest after releases and content
changes to reduce the risk of accessibility regressions.
How Pluro supports a BITV accessibility workflow
Pluro helps organizations manage accessibility as a continuous and verifiable
workflow. It connects automated scanning, expert findings, behavioral evidence,
remediation, verification, and ongoing monitoring in one platform.
- Scan websites for detectable WCAG and accessibility issues
- Document manual and behavior-based findings that automated scans may miss
- Assign, prioritize, and track remediation work
- Connect accessibility findings with developers and product teams
- Preserve evidence and verification results for each issue
- Monitor websites for new findings and regressions
- Maintain reports that support internal governance and accessibility reviews
Automated testing alone cannot determine full BITV 2.0 conformity. Pluro supports
the technical and operational workflow, while final evaluation may also require
expert review, user testing, legal assessment, and organization-specific documentation.
Discuss your BITV accessibility requirements
View a sample accessibility report
Frequently asked questions
Is BITV 2.0 the same as WCAG?
No. WCAG is an international technical standard for accessible web content.
BITV 2.0 is a German federal regulation that refers to the applicable harmonized
European standard, EN 301 549, which incorporates WCAG requirements for web
content and mobile applications.
Does BITV 2.0 apply to private companies?
BITV 2.0 primarily applies to federal public bodies. Private companies may still
face accessibility requirements through public procurement, contractual
obligations, sector rules, the BFSG, or the European Accessibility Act.
Is automated scanning enough for BITV 2.0?
No. Automated tools can identify many technical issues, but they cannot reliably
assess every accessibility requirement. Manual testing, keyboard testing,
assistive-technology testing, and expert judgment remain necessary.
How often should accessibility be tested?
Accessibility should be reviewed regularly and after significant changes to
content, templates, components, or user journeys. The accessibility statement
should also be reviewed at least annually and following substantial changes.
Official references
Official text of BITV 2.0
German Federal Accessibility Centre: BITV 2.0
EN 301 549 accessibility requirements
Web Content Accessibility Guidelines 2.1
European Accessibility Act and BFSG overview
This page provides general information and does not constitute legal advice.
Applicability should be assessed according to the organization, digital service,
jurisdiction, and applicable procurement or contractual requirements.