Shopware Checkout BFSG Finding to Developer Ticket
For DACH ecommerce teams, checkout accessibility issues deserve precise tickets: they affect customers directly and can involve Shopware themes, payment plugins, validation behavior, or custom storefront components.
This is implementation guidance for backlog quality, not legal advice or a BFSG certification statement.
Typical Shopware / BFSG finding
Finding: When the customer submits checkout with a missing required invoice address field, Shopware shows a visual error near the field, but focus stays on the submit button and the error is not announced. Flow: Checkout address / payment step Evidence: Keyboard and screen reader test; visual error appears after submit, but NVDA does not announce it.
Developer-ready ticket
# [Critical] Shopware checkout: required address errors are not announced ## Summary for product / agency lead Customers using a screen reader may not know why checkout cannot continue. Because the issue appears in the purchase flow, it should be treated as a conversion and accessibility blocker. ## Developer ticket **Area / flow:** Shopware checkout address / payment step **Component:** Storefront checkout form, validation template, or checkout extension **Assistive technology context:** NVDA / keyboard **Suggested severity:** Critical **User impact:** Blocks task completion ### Expected behavior After submitting checkout with missing required address data, the customer is informed about the error programmatically and can move directly to the affected field or error summary. ### Actual behavior The visual error appears, but keyboard focus remains on the submit button. The screen reader does not announce the new error, so the user may not know what must be corrected. ### Evidence - Finding source: manual keyboard and screen reader test - Affected flow: checkout address validation - Observed result: error visible after submit; no focus move, no live/status announcement, unclear field association ### Likely WCAG references to verify - 3.3.1 Error Identification - 3.3.2 Labels or Instructions - 3.3.3 Error Suggestion - 4.1.3 Status Messages ### Acceptance criteria - Checkout validation errors are announced after submit or focus moves to a clear error summary. - Each field-level error is associated with the affected form control. - The first invalid field can be reached and corrected using keyboard only. - Retesting with NVDA confirms the error message and required field context are announced. ### Fix direction Add an error summary with programmatic focus after failed submit, or use a reliable status/live-region pattern for validation results. Associate field errors with inputs via aria-describedby and preserve visible labels/help text for required fields.
Why this wording helps
- It keeps BFSG urgency connected to a concrete customer journey instead of vague compliance panic.
- It points developers toward Shopware checkout validation and template behavior.
- It gives QA a screen-reader retest path, not only a WCAG label.