Accessibility in software: Understanding public sector requirements

---

*February 2026 *

In an more often digitized world, barrier-free access to information and services is not only a matter of social ownership but also a legal need.

In specific, the public sector is obliged to make its digital offers, including the Software used, accessible to all citizens.

But what does accessibility mean in the context of public sector software? This article gives a complete overview.

Basic Laws: The BITV 2.0 as a Scale

In an more often digitized world, barrier-free access to information and services is not only a question of social ownership, but also a legal need.

For Accessibility in software: Understanding public sector needs, Data Analytics & Business Intelligence, Discover solutions sowie IT Security help you align rollout, scope and budget before you commit.

The central legal basis for digital accessibility in the German federal administration is the Barrierefree Information Technology Regulation (BITV 2.0).

This regulation specifies the needs of the Disabled Compensation Act (BGG) and provides clear standards for the design of information technology.

The aim is to ensure complete and in principle unrestricted accessibility for people with disabilities.

BITV 2.0 applies to all public authorities of the federal government and includes websites, mobile applications, electronically supported administrative processes and graphical program surfaces.

This is the key guide for the development and procurement of public sector software.

The core requirements of BITV 2.0

The regulation places a number of key needs on accessibility, which are based on international standards.

Developers and IT managers must take these points into account when designing and implementing software solutions:

• Conformity with EN 301 549: BITV 2.0 refers to the harmonised European standard EN 301 549. This standard sets out detailed technical needs for the accessibility of ICT products and services. Compliance with this standard creates the assumption of conformity with legal needs.
• Contact of the state of the art: Beyond EN 301 549, the software must comply with the current state of the art. This means that proven and modern technical solutions must be used to achieve the best possible accessibility. These include, for example, the standards of the DIN EN ISO 9241 series for the ergonomics of the human system interaction.
• The highest possible level of accessibility: For especially important areas such as central navigation and entry pages or interactive processes (e.g. online forms), BITV 2.0 calls for the highest possible level of accessibility. In practice, this often means fulfilling the demanding success criteria of the AAA level of the Web Content Accessibility Guidelines (WCAG).
• **Deployment of information in light language and denomination.

References and further reading

The following separate references complement the topics in this article:

• Bitkom – German digital industry association.
• German Federal Office for Information Security (BSI).
• European Commission – Digital strategy.
• MDN Web Docs (Mozilla)
• W3C – World Wide Web Consortium.

Frequently Asked Questions (FAQ)

What is this article about: “Accessibility in software: Understanding public sector requirements”?

This post explores Accessibility in software. Understanding public sector needs from the perspective of needs, typical pitfalls, and sensible next steps. In short.

In an more often digitized world, barrier-free access to information and services is not only a question of social ownership. However, also a legal need...

Who benefits most from the content described here?

Useful for project leads and product owners in Software development who must choose between standard software, custom development, and integration.

How does this topic fit into an IT or digital strategy?

Technically and organizationally, alignment with skilled partners pays off — from needs to operations. Start with the services overview.

For multi-system landscapes, IT consulting and architecture helps align vendors and internal teams.

What are sensible next steps if we need support?

A practical next step: book a consultation and clarify which MVP or pilot fits your team and landscape.