PrestaShop accessibility testing
Your customers don't all browse, search and shop in the same way. Some use a mouse. Some use a keyboard. Others use screen readers or different assistive technologies. Zylyn helps you find accessibility barriers across your PrestaShop store, understand what needs attention and give your team a practical way to fix them. You don't have to figure accessibility out on your own.
Why accessibility matters
The store can look completely fine and still create a barrier for some customers.
That's why accessibility needs to be part of keeping your store healthy, rather than something you check once and move on from.
What we test
Can customers browse products, open menus, use filters and complete their purchase without a mouse?
Can customers using NVDA, JAWS or VoiceOver understand the page structure, product information and controls?
Can customers understand product names, prices, descriptions, images, combinations and availability?
Can customers move through product listings and understand where they are on the page?
Can customers search for products and narrow their results without getting stuck?
Can customers understand fields, instructions, errors and controls throughout the purchasing process?
Do forms, menus, popups, sliders and other interactive components work with assistive technology?
Have installed modules, widgets or integrations introduced new accessibility barriers?
PrestaShop has its own accessibility challenges
It's the theme, modules, product catalog, navigation, filters, checkout, custom code and content your team manages. Each part can affect the customer experience.
Theme changes can affect headings, navigation, buttons, forms and keyboard focus.
Product names, descriptions, images, combinations and other information need to remain understandable to customers using assistive technology.
Customers need to understand the page structure and move through product listings without unnecessary barriers.
Product filters can become difficult to use when controls, focus or changes in results aren't communicated properly.
A module can add useful functionality while also introducing a new accessibility problem.
Customers need to understand fields, instructions, errors and controls as they move through the purchase process.
Custom code can change how an otherwise accessible component behaves.
Automated and expert testing
Automated testing is a useful starting point. It can find many common accessibility problems and help your team understand where to look.
But a scan can't tell you everything about what it's actually like to shop on your store using a keyboard or screen reader.
That's why Zylyn combines automated checks with expert testing using:
We look beyond the number of errors and focus on the experience behind them.
Schedule a discovery callThe process
Six steps. The first three give you a clear starting point. The last three help you keep things moving.
We identify the important pages and customer journeys across your PrestaShop store, from navigation and product pages to cart and checkout.
Automated checks and expert testing give you a starting point and show where accessibility barriers exist.
We review the results and focus on issues that can meaningfully affect your customers.
Your team gets practical guidance on what needs to change and where to start.
Once fixes are made, we check them again using the appropriate testing methods and assistive technologies.
Your PrestaShop store continues to change through product updates, theme changes, modules and new functionality.
Regular testing helps catch new accessibility problems as they appear.
A week in practice
The filter works with a mouse, but keyboard users can't easily move through all of its controls.
Testing identifies the problem and documents the affected interaction.
Your team gets clear guidance on what needs to change.
The filter is updated and tested again using keyboard and screen reader testing.
Without that check, some customers could have struggled to find the products they wanted.
What you get
You get something your team can actually work with.
Who it's for
For teams that want their PrestaShop store to work for more people.
Who does the testing
Technical expertise meets real-world experience.
CPACC: IAAP Certified Professional in Accessibility Core Competencies
WAS: IAAP Web Accessibility Specialist
Trusted Tester: DHS Section 508 conformance testing
Backed by people with lived experience of disability. Screen reader, keyboard, switch and magnification testing is performed by people who understand how these tools are used in the real world.
FAQ
It is a review of how accessible your PrestaShop store is for people with different disabilities and assistive technology needs. Testing can include automated checks, manual review, keyboard testing and screen reader testing.
Your store can change through theme updates, new modules, product changes, custom development and content updates. Those changes can introduce accessibility barriers that aren't obvious during a normal visual review.
Automated tools can identify many common issues, but they cannot evaluate everything. Manual testing is important for keyboard interaction, focus, screen reader output and important customer journeys.
Yes. Themes can affect navigation, headings, buttons, forms, product layouts and other parts of the customer experience.
Yes. Modules can add useful functionality while also introducing new accessibility barriers.
Yes. Product filters can be included in the testing scope, including keyboard access, focus, state changes and screen reader usability.
Yes. Checkout can be tested for fields, labels, instructions, errors, focus and the ability to complete a purchase using assistive technology.
Yes. Custom features can be included when they affect important customer interactions.
WCAG 2.2 AA is the working standard for Zylyn's accessibility testing.
You receive documented findings with practical information about what needs attention. Your team can then make the changes, followed by retesting where required.
It depends on how frequently your store changes. Stores with regular theme updates, module changes, product updates or new functionality can benefit from ongoing accessibility testing rather than relying on a single audit.
