Accessibility

Why Now is the Right Time for Accessibility

Q: When is accessibility required for websites?

In Europe, accessibility becomes relevant through the European Accessibility Act and in Germany through the Barrierefreiheitsstärkungsgesetz (BFSG)—it has been mandatory for many companies since June 28, 2025. Which offerings are exactly affected depends on the product, industry, and context. In practice, it’s worth checking even if you do not (yet) clearly fall under an obligation: You reduce risks and improve UX. We recommend: Treat 2025 as an occasion to determine a clear status now—instead of reacting under time pressure later.

Q: What is the difference between WCAG, BITV, and BFSG?

WCAG are the technical guidelines that describe how digital content becomes accessible. They provide the principles and success criteria tested. BITV is the German regulation for accessible information technology (primarily in the public sector). BFSG is the law that strengthens accessibility in the private sector for certain products and services. In short: WCAG describes "how," BITV/BFSG regulates "who must" and "under what conditions."

Q: Is an accessibility overlay or plugin sufficient?

Overlays can temporarily help individual users (for example, for contrast switching or larger fonts). However, they do not usually address root causes in code, design, or content. Additionally, there is the danger of self-deception: Automated solutions do not cover all problems. Automated testing detects only about 57 percent of accessibility issues according to research. Deque If you take accessibility seriously, you cannot avoid proper implementation and manual tests.

Q: How much does it cost to make a website accessible?

The honest answer: It depends on how your site is built, how complex the interactions are, and how much you need to fix afterward. Our experience: If accessibility is considered from the start, the additional effort is often manageable. If it’s "added" at the end, it can become significantly more expensive because navigation and component logic are affected. A good entry point is an audit with prioritization—then you invest first where impact and risk are greatest.

Q: Which WCAG level should I aim for?

Many legal and organizational requirements are oriented towards WCAG 2.1 Level AA. digitalagenten.com For some content, AAA can make sense (for example, for particularly critical offerings). In other cases, AA is a very realistic target with a major impact. We recommend not formulating the goal only as a level but as usable user flows: "Contact form without barriers," "Checkout without dead ends."

Q: How do I prove accessibility without overwhelming myself?

You need a combination of documentation and tests. Tools provide reports, but they do not replace manual verification of the most important flows. In practice, it helps to define accessibility as a QA step and to document findings comprehensibly: What was tested, with which tools, which issues have been resolved, which remain open, and why. If you are working with an agency or in-house team, a set of acceptance criteria per feature is worthwhile—then proof emerges "along the way" in the process.

Q: What tools are suitable for a quick start?

For a first overview, three tools work very well: WAVE for visual hints, Lighthouse for a quick check in the browser, and axe DevTools for technically sound findings. It is important not to be lulled by scores. Use tools to find obvious problems—and always complement them with keyboard tests and at least one screenreader quickcheck. If you are uncertain, a professional audit is often the fastest shortcut to real priorities.