An accessible checkout starts with the complete purchase journey.
Test one purchase or booking journey with a keyboard and screen reader, prioritise barriers and fix the agreed issues.
Read the German originalAn accessible button is not enough
A purchase often starts with product selection and ends only with an understandable confirmation. Variants, addresses, error messages and sometimes a payment provider's interface lie in between. If one stage cannot be operated, the entire task fails.
Bundesfachstelle Barrierefreiheit explains the relevance of the BFSG to online services within its scope and identifies exemptions for certain microenterprises. Independently of the legal classification, a technical assessment can establish whether people can complete a specifically defined customer journey.
Test keyboard operation and feedback
Start with the keyboard: is the order understandable, does focus remain visible and can a dialog be closed again? Then use a screen reader to check whether labels, required fields and error messages provide the information needed.
Automated checks complement this work but do not replace the complete journey. Document each finding with its starting state, action and observed result. A developer can then make a targeted correction and another person can independently verify it.
Validate corrections across the journey
After a change, repeat the entire agreed journey. A better-labelled field helps little if the next step loses keyboard focus. With external payment or booking services, responsibilities and the available technical interventions must be clear beforehand.
A limited assessment gives a dependable picture of that journey in the tested environment. Other pages, documents and device combinations need additional checks. Recurring tests should follow relevant changes to the customer journey.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
Assess and improve an accessible checkout · Packages