EU Accessibility Act Testing and Conformance Evidence

Testing should match the interfaces users actually rely on. That usually means a combination of automated checks, manual keyboard review, screen reader testing, zoom and reflow checks, colour and contrast review, media access review, and category specific hardware or communication testing where relevant.

For services, test core user journeys first because they are where harm and abandonment show up fastest. For products, test the user interface, setup flow, instructions, packaging information where relevant, and any linked app or service needed to use the product.

For products, the evidence pack should align with Annex IV technical documentation and the declaration of conformity workflow. That means design and operation information, the standards or specifications applied in full or in part, and the records needed to assess conformity. For services, the pack should include scope records, requirement mappings, test methodology, findings, fixes, statement copies, and exception records.

Keep the evidence indexed by offering and release. When someone asks whether a specific app version, checkout flow, or terminal model was assessed, the answer should be available in minutes, not reconstructed from chat messages and slide decks.