Accessibility Belongs in IT Leadership's Architecture

24.09.2026

7 min read

Since late June 2025, the Accessibility Strengthening Act (BFSG) has applied to many digital products and services. Shops, apps, self-service portals and PDF processes in the existing estate decide whether a transaction runs without assistance. Missing accessibility hits usage, compliance and value all at once.

Key takeaways

The act has applied since late June 2025. Many digital products and services that consumers use to buy, book or pay fall under it.
The existing estate decides access. Online shops, apps, self-service portals and PDF processes belong in the inventory before the next feature list.
Priority follows usage, value and the severity of the barrier. New features without an inventory only postpone the obligation.

What is the Accessibility Strengthening Act? The German act translates European requirements for accessible digital products and services into national law. Since late June 2025 it has applied to many offerings that consumers use to buy, book, pay or close service cases.

What the act has required since June 2025

The Accessibility Strengthening Act has applied since late June 2025 to many digital products and services. The requirement translates European rules into German law and affects digital offerings that consumers use to buy, book, pay or close service cases. That makes it a governance task across the entire customer transaction. A channel delivers only as much value as people can operate it without personal assistance.

Whoever owns a shop, an app or a service portal owns access to the business transaction. Perceivable content, operable interfaces, understandable language and robust technology belong in the architecture of the transaction. They decide whether an order, an account change or a record runs without help. That holds for the first visit just as much as for recurring service processes where routines have grown over years.

The legal obligation does not end at your own application. Payment flows, search, consent layers, dialogs and document generators sit on the critical path as soon as customers have to pass through them. Leadership makes these dependencies visible in the inventory and ties them down contractually. Otherwise your own interface stays polished while the transaction breaks at the embedded third party.

Leadership that delegates accessibility to a single specialist unit and keeps it out of the architecture produces window dressing. The specialist unit can organize training and review templates. It cannot on its own enforce the sequence of remediation, the purchase of modules and the release of critical flows. That remains the job of IT leadership.

Which parts of the existing estate belong in the inventory first

The existing estate drives risk more than the next feature list does. Online shops, native and web-based apps, self-service portals and PDF processes carry the organization’s daily business. That is where the act meets concrete steps taken by customers. Whoever does not know these surfaces can neither audit nor prioritize. These four surfaces form the core of IT leadership’s inventory.

Shops lose transactions when filters, the cart, checkout and error messages work only visually. Apps often lack names for controls, focus stays trapped in dialog layers or gestures have no alternative. Self-service portals pile up complex forms with time limits and dynamic errors that a keyboard and screen readers cannot reliably navigate. These patterns are well known and especially stubborn in legacy systems.

PDF processes are the silent bottleneck. Untagged files, scanned letters without a text layer and forms without a meaningful reading order interrupt the transaction, even when the website still allows entry. Quotes, confirmations, invoices, contracts and application records keep circulating as files in many companies. Testing only the homepage or the app entry point does not test the process. The record is part of the product as soon as the transaction cannot end without the file.

Then there are embedded flows that do not formally look like a channel of their own. Appointment booking, account opening, returns, claims filing or status checks often sit in portals with shifting responsibilities. These shifts make inventory and ownership a leadership task. Without a clear role, every audit remains a snapshot without a remediation mandate.

How priorities emerge in the digital portfolio

Prioritization is a decision about benefit and harm. First come channels with high usage and high business value, where one blocked step stops revenue or the service case. Next in line are flows where people cannot complete the transaction without sight, without a mouse or without complex language comprehension. The sequence thus follows the severity of the barrier and the importance of the transaction.

A solid framework separates entry, core transaction and record. Entry covers sign-in, search and navigation, because no transaction starts without that stage. The core transaction sits in the cart, application, booking or account change. The record, spanning confirmation, invoice, contract and file download, only closes the loop when the document itself is accessible. Hardening only the entry point shifts the drop-off to the end of the transaction.

Organizations love to polish new surfaces and leave legacy systems untouched. Business departments push for new features while the existing estate carries the legal and quality burden. That hands-off approach shifts work into customer service and manual detours. Leadership therefore sets a sequence with deadlines, accountable roles and acceptance criteria. Work on appearance with no effect on the estate has to take a back seat to that sequence.

Transparency about residual risk belongs in the same steering group. Not every surface gets fully remediated in the same wave. Leadership must name which transactions still carry barriers, which workarounds exist and when the next wave takes effect. That naming turns an unmanageable backlog into a governable program.

Why accessibility is product quality

Product quality shows in whether different people can reliably complete the same transaction. Accessibility tests perception, operation, comprehensibility and robustness with a rigor the clickable happy path never delivers. What screen readers, magnification or a keyboard cannot reach often also fails at small font sizes, poor lighting, temporary impairment or high cognitive load. Quality that systematically loses one group has been measured incompletely.

Quality that exists only in a mouse session with perfect eyesight does not hold up in operation. Missing labels, contrast without a second cue and time windows that cannot be extended produce abandonment or contacts to the service center. The costs then show up in the organization and in lost transactions. They do not show up in the product’s story.

Accessibility belongs in the same leadership logic as security and operational reliability. It needs requirements, testing, defect classes and release criteria. A release that leaves the critical user path unusable for part of the user base is incomplete. Teams only learn that when leadership rejects inaccessible flows the same way it rejects open security vulnerabilities.

Who carries responsibility across the supply chain

IT leadership holds the pieces together because accessibility cuts across architecture, procurement, the design system and operations at the same time. Product management defines the business transaction and the acceptable barrier in the flow. Development and design implement semantics, structure and interaction. Operations monitors regressions after changes to content, libraries and platform. Procurement makes criteria enforceable against agencies, platforms and document service providers.

Without that integration, local partial solutions emerge. Checkout flows get hardened while PDF flows and purchased modules keep breaking keyboard focus or document structure. The channel fails at the seam even though local demos count as success. These seams are where leadership has to measure, because customers experience the transaction as one unit.

Contracts need testable criteria instead of a general declaration of intent. Acceptance hinges on concrete transactions completed with a keyboard, magnification and assistive output. Content and document partners belong in the same chain, because an operable shop with unreadable contract documents does not complete the transaction. A clause without a test path creates false confidence in procurement.

Internal ownership without supplier governance stays incomplete as soon as essential parts of the transaction are run by third parties. That applies to shop platforms just as much as to sign-in, search and document generation. The requirement moves into the requirements specification, the acceptance test and the operational interface. Only then does accessibility survive a platform update. Updates without renewed acceptance reintroduce known barriers.

What leadership must concretely govern in the existing estate

Governance starts with an inventory of the digital touchpoints that fall under the act or carry the customer transaction. Every entry needs an accountable person, the technical status, the date of the last audit and the known blocking defects. Without that picture, budget remains a distribution conflict between projects. With it, a nonspecific remediation goal becomes a program with a sequence. The inventory stays alive because new modules, content and document types keep changing the transaction.

The work program runs in waves ordered by harm to users. Blocking defects on revenue-critical and service-critical flows come first because they stop the transaction completely. Next come recurring gaps in shared components, then the breadth of the document flows. Automated checks find patterns in code and markup and are therefore useful as an early warning. They replace neither manual testing with a keyboard and assistive tools nor the assessment of comprehensibility.

Binding rules anchor accessibility in architecture decisions, in acceptance and in supplier governance. A design system with accessible components cuts the cost of repeated rework because the same defects do not reappear in every surface. Training reduces regressions because otherwise teams reproduce known barriers in new surfaces. The governing metric is the critical transaction that succeeds without a workaround. Workarounds in customer service signal unresolved product debt.

Many older people use digital channels as their first route to a provider. Temporary impairments from injury, glare or stress affect sessions far beyond the narrow focus on permanent disability. The legal baseline since late June 2025 and this real-world usage converge. Whoever runs accessibility as a niche topic underestimates the breadth of use. Whoever runs it as product quality keeps channels open and reduces friction across the estate.

Frequently asked questions

Which surfaces go into the inventory first?

Online shops, apps, self-service portals and PDF processes go into the inventory first, because customer access and the business transaction converge there. Embedded flows for payment, search, consent, dialogs and documents join them as soon as the transaction cannot end without them. The act covers many digital products and services; these four surfaces are the solid core for IT leadership.

How do remediation waves take shape without overwhelming the existing estate?

The sequence follows usage, business value and the severity of the barrier along entry, core transaction and record. Blocking defects on critical flows come first, then shared components and document flows. Residual risk must remain explicitly named, because not every surface gets fully remediated in the same wave.

Are automated checks enough for a release?

Automated checks find patterns in code and markup and work well as an early warning. They replace neither manual testing with a keyboard and assistive tools nor the assessment of comprehensibility. The release hinges on the critical transaction succeeding without a workaround.