FAQs Archive - Digivante

Q: Why is checkout accessibility particularly important for ecommerce retailers?

Accessibility barriers during checkout can prevent customers from completing purchases, even when they can browse the rest of the website successfully. Testing the full purchase journey helps identify issues with forms, payment options, error messages and navigation that could otherwise lead to abandoned transactions.

Q: How do you test whether checkout can be completed using only a keyboard?

Testing involves completing the purchase journey without using a mouse, checking that customers can navigate product options, basket controls, delivery forms and payment steps using a keyboard. Testers assess whether focus follows a logical order, remains visible and doesn't become trapped within forms or third-party components.

Q: Can third-party payment or checkout providers cause accessibility problems?

Yes. Address lookup tools, payment forms and buy now, pay later options can introduce accessibility barriers, even when the retailer's main website has been tested. These components need to be assessed as part of the complete checkout journey, including keyboard navigation, screen reader compatibility and error handling.

Q: Is accessibility testing a legal requirement for UK ecommerce retailers?

UK ecommerce retailers have responsibilities under the Equality Act 2010 to make reasonable adjustments for disabled customers. In Northern Ireland, the Disability Discrimination Act 1995 applies instead. UK businesses selling to customers in the EU may also need to comply with requirements under the European Accessibility Act, depending on their circumstances. Accessibility testing helps retailers identify barriers that could prevent disabled customers from using their websites and completing purchases. WCAG provides a recognised framework for assessing accessibility, although meeting a particular WCAG level does not automatically establish legal compliance.

Q: What should retailers look for in an exploratory testing service?

Retailers should look for an exploratory testing service that combines real-user and real-device coverage with managed QA, clear evidence and verified, prioritised findings. It should be flexible enough to focus on high-risk customer journeys and work alongside existing functional, regression and automated testing.

Q: How can exploratory testing reduce production bugs in ecommerce?

Exploratory testing can uncover issues that scripted and automated tests may miss, including unexpected customer behaviours, device-specific problems and breaks between different parts of the buying journey. Running exploratory testing before release gives ecommerce teams an opportunity to identify and fix these issues before they reach customers in production.