# BITV 2.0: Germany's Accessibility Ordinance

Source: https://allyway.ai/glossary/bitv

BITV 2.0 (Barrierefreie-Informationstechnik-Verordnung) is the German federal ordinance under the Disability Equality Act (BGG) that sets the accessibility requirements for websites, mobile apps, electronic administrative processes and graphical user interfaces of federal public bodies.

BITV 2.0 is the German ordinance that tells federal public bodies how to make their websites, apps and digital services accessible. Its full name is "Verordnung zur Schaffung barrierefreier Informationstechnik nach dem Behindertengleichstellungsgesetz" (Barrierefreie-Informationstechnik-Verordnung). It was issued on 12 September 2011 and last amended in October 2023. The BITV covers the public sector; private companies with consumer services fall under the [BFSG](https://allyway.ai/glossary/bfsg) instead.

## What it means

The ordinance builds on the Disability Equality Act (BGG), which sets the obligations and deadlines for public bodies (§§ 12a to 12c BGG). The BITV fills in the technical details (source: [BITV 2.0 on gesetze-im-internet.de](https://www.gesetze-im-internet.de/bitv_2_0/BJNR184300011.html)).

| Section | What it regulates |
|---|---|
| § 2 Scope | Websites and mobile apps, electronically supported administrative processes including e-files, and graphical user interfaces – intranets and extranets included |
| § 3 Standards | Content must be perceivable, operable, understandable and robust; conformity with harmonised standards is presumed to meet this |
| § 3 Abs. 4 | Central navigation and entry points, forms, authentication and payment should reach the highest possible level of accessibility |
| § 4 | Explanations in German Sign Language and in easy-to-read language (Leichte Sprache) on the homepage |
| § 7 | Accessibility statement and feedback mechanism |
| § 8 | Monitoring based on the EU method of Implementing Decision (EU) 2018/1524 |

The harmonised standard for public-sector websites is [EN 301 549](https://allyway.ai/glossary/en-301-549), which refers to [WCAG](https://allyway.ai/glossary/wcag) Level A and AA for web content; the [W3C WCAG overview](https://www.w3.org/WAI/standards-guidelines/wcag/) recommends the latest version, WCAG 2.2. On top of that, § 4 goes beyond WCAG: the homepage must explain the main content, how to navigate, the key points of the accessibility statement and where more content in sign language and easy-to-read language can be found. Annex 2 sets details, for example sign language videos of at least 320 × 240 pixels and 25 frames per second, and easy-to-read text in a font size of at least 1.2 em.

> **Note:** > **BITV or BFSG?**
> The BITV applies to public bodies of the federal government. The German states have their own rules for their authorities. Shops, banks and other businesses with consumer services follow the BFSG, Germany's implementation of the [European Accessibility Act](https://allyway.ai/glossary/european-accessibility-act).

## Examples

§ 7 requires an [accessibility statement](https://allyway.ai/glossary/accessibility-statement) in an accessible, machine-readable format that is reachable from the homepage and every page, plus a feedback mechanism. A footer that meets both:

```html title="Example"
<footer>
  <a href="/barrierefreiheit">Erklärung zur Barrierefreiheit</a>
  <a href="/barriere-melden">Barriere melden</a>
  <a href="/leichte-sprache">Leichte Sprache</a>
  <a href="/gebaerdensprache">Gebärdensprache</a>
</footer>
```

The statement must say whether the assessment was carried out by a third party or by the body itself, and it must be updated every year and after every significant change.

**Do:** Do

Test against WCAG 2.2 AA, link the statement and feedback from every page, provide homepage explanations in sign language and easy-to-read language, write the rest in [plain language](https://allyway.ai/glossary/plain-language) and review the statement once a year.

**Don't:** Don't

Treat the statement as a one-off document, skip the sign language and easy-to-read pages, or test only the homepage while forms and payment flows stay untested.

## How to meet BITV 2.0



## Questions

Q: Who has to comply with BITV 2.0?
A: Public bodies of the German federal government, such as ministries and federal agencies, for their websites, apps, intranets and electronic administrative processes. Private businesses are not covered by the BITV.

Q: Which WCAG version does BITV 2.0 require?
A: The BITV names no WCAG version. It presumes conformity with harmonised standards, and for websites that is EN 301 549, which refers to WCAG Level A and AA. Building for WCAG 2.2 AA covers it because WCAG 2.2 is backwards compatible.

Q: What is the difference between BITV 2.0 and the BFSG?
A: The BITV applies to federal public bodies, the BFSG to businesses offering certain products and services to consumers. Both rely on EN 301 549 for websites.

Q: How often must the accessibility statement be updated under BITV 2.0?
A: Every year and after every significant change to the website or mobile app (§ 7 Abs. 6).

Q: How do I start testing for BITV 2.0?
A: Start with a quick automated check, then test forms and key journeys by hand. The [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) checks a page against WCAG 2.2 AA in seconds.
