Find the barriers. Fix the code. Verify the fixes.
Accessibility barriers can make everyday shopping interactions difficult for people with disabilities. Zalynt identifies and remediates accessibility issues across Shopify, WooCommerce and BigCommerce storefronts, then verifies the fixes through repeat testing against WCAG 2.2 A/AA.
Why it matters
More than 1 in 4 U.S. adults have some type of disability.
Removing accessibility barriers can make everyday digital experiences easier to use for more people.
Source: CDC
Platforms
Shopify · WooCommerce · BigCommerce
Testing
Independent multi-engine testing
Remediation
Code-level storefront remediation
Reference standard
WCAG 2.2 A/AA
How Zalynt works
Find it. Fix it. Verify it.
Zalynt assesses the agreed storefront scope across pages, reusable components, interface states and shopping flows. Confirmed accessibility issues are remediated in the underlying code, then affected areas are retested and documented.
01
Define the scope
Pages, templates, components, shopping flows, price, timeline and required access are agreed before work begins.
02
Test the storefront
The agreed scope is evaluated using multiple independent accessibility testing engines against WCAG 2.2 A/AA.
03
Remediate the findings
Confirmed accessibility issues are fixed directly in the storefront implementation — templates, markup, styles and scripts.
04
Retest and document
Affected areas are tested again. Resolved findings, remaining limitations and completed changes are documented clearly.
What we fix
Remove barriers from the shopping experience.
Navigation, product selection, forms, dynamic interfaces and cart interactions can all create accessibility barriers. Zalynt identifies and remediates those issues across the storefront.
- 01
Navigation, keyboard and focus
Menus, drawers, controls, focus visibility and keyboard interaction.
- 02
Forms, labels and validation
Form names, instructions, required fields, validation and error states.
- 03
Product selection and media
Variants, swatches, galleries, controls and meaningful alternatives.
- 04
Modals and dynamic interfaces
Popups, quick views, app blocks, drawers and dynamically updated content.
- 05
Structure, semantics and ARIA
Headings, landmarks, names, roles, states and relationships.
- 06
Colour contrast and visual states
Text contrast, controls, focus indicators and important visual information.
- 07
Cart and shopping flows
Cart controls, quantity changes, status messages and other customer interactions.
- 08
Third-party storefront components
Remediated where the merchant's implementation gives technical control. Anything outside that control is documented clearly.
Sample finding
See exactly what gets changed.
Before
Issue detected
Cart button has no accessible name.
WCAG 4.1.2 · Name, Role, Value
Fix
Code remediated
Accessible naming and relevant control semantics implemented in the storefront code.
After
Verified
Finding no longer detected during repeat testing.
Illustrative example. Real findings are always tied to the client’s own storefront and testing results.
Deliverables
Clear work. Clear results.
Every remediation engagement includes the following.
- 01
Prioritised findings
Confirmed findings, affected locations and relevant WCAG references.
- 02
Agreed code-level remediation
Accessibility issues included within the agreed project scope are remediated directly in the storefront implementation.
- 03
Repeat testing
Affected pages, interface states and components are tested again after remediation.
- 04
Remaining limitations
Anything unresolved, outside scope or controlled by a third party is documented clearly.
- 05
Remediation summary
A written record of what was identified, what changed and what remained.
Before testing begins
You know exactly what Zalynt is working on.
Every engagement is scoped before testing begins. Pages, flows, access, price and timeline are confirmed in writing before work starts. Testing then determines the confirmed accessibility findings within that agreed scope.
- Storefront scope
- Pages, templates, components and shopping flows included in the engagement.
- Testing approach
- The testing scope and WCAG 2.2 A/AA reference standard are confirmed.
- Access required
- Only the permissions necessary to safely test and remediate the relevant storefront implementation.
- Price and timeline
- Commercial terms are agreed before work begins.
Work is performed in a staging, duplicate or appropriate development environment whenever the platform allows it.
FAQ
Questions Zalynt gets asked first.
Request a remediation quote
Tell Zalynt about your store.
Send us your store URL and a few project details. We’ll review the request and reply with any scope questions, recommended next steps and pricing.
Usually a reply within 2 business days.
Prefer email? hello@zalynt.com