The German Accessibility Strengthening Act: What Does It Mean for Businesses?

The German Accessibility Strengthening Act: a practical guide for businesses

The German Accessibility Strengthening Act is reshaping how businesses in Germany must think about digital and physical access. This guide explains who is affected, which technical standards to follow, the concrete steps to comply, and common mistakes to avoid.

Who does the Act affect?

Businesses that offer services or goods to the public in Germany are most likely to be affected. That includes online services such as websites and mobile apps, public-facing kiosks, ticket machines, and customer portals. Public sector organisations are already subject to accessibility duties, but the Act broadens expectations for many private organisations that serve the public.

Quick way to check if it applies to you

• Do you sell to or serve consumers in Germany? If yes, assess digital access.
• Do you operate physical customer touchpoints in Germany? If yes, assess built environment access.
• Do public contracts or procurement apply to your organisation? Then accessibility requirements usually apply.

What accessibility covers under the Act

Accessibility is not just visual changes. The Act covers barriers across senses and cognition. Expect requirements for:

• Websites and mobile apps
• Digital documents and forms
• Customer-facing hardware such as ATMs and ticket machines
• Physical access in service locations where customers interact
• Information provided by phone or email where digital alternatives are offered

Which technical standards to use

Follow established, recognised accessibility standards. Use them as your checklist when you audit and fix content.

• WCAG 2.1 level AA is a common benchmark for websites and apps. It covers contrast, keyboard access, labels, and predictable operation.
• WCAG 2.2 introduces additional criteria relevant to cognitive and mobile accessibility. Consider it for new projects.
• EN 301 549 is often referenced for procurement and public sector digital products in the EU. It maps to WCAG and specific product requirements.
• Use WAI-ARIA to make dynamic web content operable for assistive technologies, but use it only where semantic HTML is insufficient.

How enforcement typically works

Enforcement can be administrative complaints, ordered remediation, or litigation. Expect requirements for an accessibility statement and a way for users to report barriers. Remedies commonly include fixing the accessibility issue and demonstrating compliance steps.

I will not list fines or deadlines here because those can change. Check official government guidance or legal counsel for exact penalties and timeframes that apply to your organisation.

A practical compliance roadmap (6 steps you can start today)

1. Assign responsibility. Appoint an accessibility lead and give them budget and authority.
2. Inventory. List public-facing websites, apps, documents, machines, and physical points of service.
3. Audit. Use automated tools for a first pass and follow with manual checks and user testing with people who have disabilities.
4. Fix. Prioritise high-traffic and high-impact user journeys. Fix code, content, and interface patterns that block access.
5. Document. Publish an accessibility statement that lists coverage, standards used, and how to report problems.
6. Maintain. Include accessibility in procurement, design systems, release checklists, and staff training.

Testing and validation: methods that work

Do not rely only on automated scanners. A robust testing program uses three layers.

• Automated testing for quick detection of missing alt text, contrast failures, and markup errors.
• Manual expert review to check keyboard navigation, focus order, labels, and ARIA usage.
• Real user testing with people who have diverse disabilities. This finds issues that tools and experts miss.

What to measure

• Percentage of pages meeting WCAG level AA for core user journeys
• Number of open accessibility defects by priority
• Time to acknowledge and resolve reported accessibility problems

Procurement and third-party software

Contracts should require accessibility clauses. For SaaS, plugins, and vendor-supplied kiosks, ask vendors for an accessibility conformance report and remediation commitments. Do not assume a vendor is compliant without documentation and testing evidence.

Common mistakes businesses make

• Relying only on automated tools and declaring a site accessible.
• Fixing single pages instead of core user journeys like registration and checkout.
• Using ARIA to solve layout issues instead of fixing semantic HTML.
• Not training content teams on accessible writing, headings, and images.
• Publishing an accessibility statement that is empty or promises fixes without a process to deliver.

Accessibility statement: what to include

• Which parts of your services are in scope
• The standards you used for assessment, for example WCAG 2.1 level AA
• How users can report accessibility barriers and the contact channel
• Response times and remediation process, at least in general terms
• Known exclusions or planned improvements

Costs, benefits and business risks

Accessibility work has upfront costs for audits, fixes, and training. But benefits include a larger market of customers, fewer customer service calls, and lower legal risk. Risk grows if public-facing services remain inaccessible and users file complaints.

Decision framework: prioritise what to fix first

Use this simple rule to triage work:

• Impact on user ability to complete a task. Fix tasks that block purchase or sign-up first.
• Frequency of use. Fix high-traffic pages before rarely used ones.
• Effort to fix. Some high-impact fixes are low effort. Tackle those early.

Next steps for your organisation

Start with a short internal briefing so leaders understand scope and risk. Run an inventory and a basic automated scan this month. Then budget for a mixed audit with manual checks and user testing. Publish an accessibility statement before launching major campaigns or new public services.

Resources and support

Use the WCAG documentation for technical criteria and consult EN 301 549 if procurement rules apply. Consider hiring an accessibility specialist for audits and training. Legal counsel can clarify specific obligations under the Act for your sector.

Final checklist

• Appoint an accessibility lead
• Complete an inventory of public-facing services
• Run automated and manual accessibility tests
• Prioritise fixes using impact and frequency
• Publish an accessibility statement with contact details
• Include accessibility in procurement and release governance

If you want a tailored 6 to 12 month plan based on your site or product, I can outline one after you tell me your main public-facing channels and team size.