After the EAA: why checkout accessibility is now a maintenance task

Accessibility is still treated by many website teams as a redesign task: check some colors, add a few alt texts, and leave the hard parts for later. Since the European Accessibility Act and national implementation laws such as Germany's BFSG, that mindset is risky. For shops, booking flows, and digital services, accessibility is now an operations and maintenance topic.

The European Commission lists e-commerce among the services covered by the European Accessibility Act. Germany's BMAS describes the BFSG as the implementation of EU Directive 2019/882 and points to common accessibility requirements for certain products and services. For website teams, this does not mean panic. It means critical digital journeys need to become traceable, testable, and maintainable.

The checkout is the hardest test

A homepage can feel accessible while the actual purchase or booking flow fails. That is why an accessibility audit should not start with whether the website looks modern. The better question is: can a person using a keyboard, screen reader, zoom, limited motor control, or working under cognitive load actually complete the process?

The critical points are usually:

• navigation to the product or offer
• variants, quantities, prices, and availability
• cart or booking summary
• address, contact, and payment forms
• error messages and required fields
• consent banners, CAPTCHAs, and third-party widgets
• payment providers, redirects, and confirmation pages
• email confirmation after completion

If one of these steps blocks users, the site is not practically usable. Accessibility is therefore not only a design value. It is part of conversion and service quality.

WCAG as the technical working base

The W3C Web Content Accessibility Guidelines (WCAG) 2.2 define testable criteria for more accessible web content. W3C explains that WCAG 2.2 applies to web content across device types and extends WCAG 2.0 and WCAG 2.1 rather than replacing them. For teams, that matters because accessibility does not only mean screen readers. It includes focus management, contrast, error tolerance, target size, clear labels, and robust semantics.

In practice, an audit should not rely only on automated tools. Tools catch some issues, but they do not understand a full checkout. A useful test combines automated checks, manual keyboard testing, screen reader sampling, and real process walkthroughs.

Practical checklist for website teams

A pragmatic checkout audit can start with these questions:

1. Keyboard: can every step be reached and operated without a mouse?
2. Focus: is it always visible where the user currently is?
3. Forms: are labels, help text, and errors programmatically connected?
4. Errors: can input errors be found and corrected clearly?
5. Zoom: does the flow work at 200 percent zoom without horizontal chaos?
6. Contrast: are text, buttons, hints, and error states readable enough?
7. Components: do dropdowns, modals, accordions, and tabs use semantic patterns?
8. Third parties: are payment, CAPTCHA, calendar, chat, and consent tools also usable?
9. Language: are instructions clear and not only explained visually?
10. Regression: are there checks so updates do not break the flow again?

The last point is easy to underestimate. An accessible checkout does not stay accessible by itself. New payment widgets, consent settings, theme updates, or marketing scripts can change behavior.

What agencies and developers should document

For handover and maintenance, a sentence like "accessibility checked" is not enough. A small accessibility record is much more useful:

• pages and user flows tested
• browsers, devices, and assistive tools used
• known limitations and technical debt
• decision on the WCAG target level
• list of third-party widgets and related risks
• responsible person for retesting after changes
• date of the last review

This does more than reduce confusion. It shows which parts of the site were actually controlled and which were not.

Conclusion

Accessibility is not a nice add-on for a relaunch. For shops and digital services, it is part of technical operability. Teams that regularly test checkout, forms, and third-party widgets reduce legal uncertainty, support load, and lost conversions. The best time for an accessibility check was before the relaunch. The second-best time is before the next broken checkout.

Sources

• European Commission: European Accessibility Act
• BMAS: Barrierefreiheitsstärkungsgesetz
• W3C: Web Content Accessibility Guidelines (WCAG) 2.2

Note: This article is a technical overview and does not constitute legal advice.