E-commerce
October 29, 2026
Wondering how to audit the accessibility of an e‑commerce site dedicated to pets?
In a few steps, you will identify obstacles preventing people with disabilities from navigating, searching for products, and completing purchases.
A well‑conducted audit prevents frustration, improves conversion rates, and protects you legally.
Furthermore, complying with WCAG 2.2 strengthens user trust, reduces the risk of legal complaints, and can even improve organic search rankings through better semantics.
So, how to conduct an accessibility audit for PetsContained? The agenda:
Why start the audit with a blind persona?
What cues force the screen reader to identify the site?
How to evaluate the clarity of search labels?
Why must alt attributes be concise and relevant?
How to detect reading order issues in the code?
What are the warning signals when no 'skip' link exists?
How to verify understanding of add‑to‑cart buttons?
What difficulties do keyboard‑only users encounter?
How does the purchase form structure influence accessibility?
How can Qstomy simplify tracking the customer journey?
How does Qstomy help make the audit more effective?
What checklist to follow before publishing the site?
Let's go.
Throughout this article, you will discover concrete examples, free tools, and how Qstomy automates the recurring part of the process so your teams can focus on high‑value improvements.
Summary
Why start the audit with a blind persona?
Adopting the perspective of a blind user from the start helps identify real barriers encountered by screen readers. By simulating navigation with JAWS or NVDA, you immediately see if the page title clearly indicates the store name, if menus are logically structured, and if navigation landmarks (site map, link to homepage, cart) are accessible. This human approach complements technical checks and reveals drop‑off points that discourage non‑sighted customers. To learn more, read our guide on monthly conversation audits.
Additionally, testing with a blind persona forces you to check heading depth, the presence of an ARIA role 'main', and the relevance of error messages which must be announced proactively. An audit centered on this persona highlights gaps between the visual and auditory experience, giving you the most impactful adjustment priorities.

Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion



Empowering 200+ e-commerce merchants
What cues force the screen reader to identify the site?
A screen reader relies on tags title and heading tags to announce context. If the title does not mention 'PetsContained', the user does not know where they are, even if they entered the correct URL. Ensure you include the store name and product type in each <title> and to prioritize <h1>‑<h2>. Also consult our guide on the support policy which emphasizes clear language.
Also consider adding tags role="navigation" and aria‑label="Menu principal" so that the screen reader immediately identifies the navigation area. A best practice is to limit the number of heading levels to three or four, which avoids cognitive overload and ensures each section quickly finds its place in the auditory flow.
How to evaluate the clarity of search labels?
The search field must be identified by a label or an attribute aria-label. Without this indication, the screen reader simply reads « edit », leaving the user to guess. By adding aria-label="Recherche de produits">, you ensure that every search, even empty, provides audible feedback. A well-labeled search avoids unnecessary back-and-forth and increases conversion chances, especially for visitors using voice input.
To go further, include an attribute role="search"> around the field and expose search filters via aria‑expanded so the user knows they can refine their query. Test with the free tool WAVE to verify the label is correctly perceived.
Why must alt attributes be concise and relevant?
Alt attributes alt must summarize the image in a few words. Descriptions that are too long, like those observed on PetsContained, generate noise and obscure the actual meaning of the link. An alt of « PetSafe Electronic Fence » is enough to inform the user about the product. Keep it concise and avoid keyword repetition. For more best practices, read detect information gaps on the site via support tickets.
Additionally, consider decorative images that provide no information: use alt="" and role="presentation". This eliminates auditory noise. Finally, ensure every image has a unique and descriptive alt text, especially for color or size variants that can be crucial for the purchase decision.
How to detect reading order issues in the code?
The reading order of the HTML code must reflect the visual order. If sub-links of a category appear before the main title, the screen reader lists links in a confusing order, as seen with « Petsafe Dog Fences ». Fix the structure by placing <nav> tags and lists in the correct sequence, or use aria‑order. A logical flow facilitates navigation and reduces abandonment rates.
Also use section and article tags with aria‑label attributes to clearly delineate different parts of the catalog. An automated audit with notre chatbot IA can quickly spot order breaks and suggest a fix in one minute.
What are the warning signals when no 'skip' link exists?
The absence of a « skip to main content » link forces screen reader users to navigate every navigation item before reaching the actual content. Insert an invisible but focusable button at the start of the page: <a href="#main" class="skip-link">Skip to content</a>. This small addition improves the experience and demonstrates your commitment to inclusion.
To maximize impact, ensure the link becomes visible as soon as it receives focus (e.g., by changing the background color). Test it with the keyboard combination Shift+Tab to ensure it appears immediately. This simple gesture reduces navigation time by 30% for users who need to skip repetitive menus.
How to verify understanding of add‑to‑cart buttons?
« Add to Cart » and « Buy Now » buttons displayed as images without alt text are interpreted as file names (e.g., « ec/a2c.gif »). Add alt="Add to Cart" and alt="Acheter maintenant" or, better yet, replace the images with <button> with a readable label. This ensures that every action is clearly understandable, even without a visual view.
En outre, appliquez l’attribut aria‑pressed="false" on « Add to Cart » buttons when they trigger a selection state, and ensure that focus returns to the cart after adding, so that the screen reader announces the confirmation. A best practice is to provide visual and auditory feedback (e.g. : role="alert") for every successful action.
What difficulties do keyboard‑only users encounter?
Users who cannot use a mouse must be able to navigate using the keyboard only. Verify that every link and button is accessible via the Tab key, that :focus states are visible, and that dropdown menus do not get stuck. On PetsContained, the search field was not focusable, which interrupted the journey. A quick audit with notre chatbot IA can identify these friction points.
Consider adding a visual cue (border or shadow) when an element receives focus, and properly manage focus traps in modals. Test navigation by disabling the mouse and advancing only with Tab and Shift+Tab, to ensure that the logical order remains intact, even on mobile pages.
How does the purchase form structure influence accessibility?
The purchase form must follow a linear logic: value field, quantity, purchase button. Each field requires a label linked to id. The correctly labeled « Buy Now » button allowed the blind auditor to complete the purchase, but the quantity fields were not associated with a label, creating ambiguity. By normalizing the tags label, you facilitate input even for screen readers.
Also add the attributes required and aria‑required="true" so that errors are announced automatically. Propose real-time validation with descriptive error messages (e.g. : aria‑describedby="error‑qty") so that the user knows immediately how to correct their field.
How can Qstomy simplify tracking the customer journey?
Qstomy integrates a dashboard that tracks every step of the customer journey, from the first click to package tracking. Thanks to our optimization recommendations, you can display an accessibility compliance indicator directly in the dashboard, identify pages to fix, and automate audit tests. This real-time visibility reduces non-compliance risks and increases conversions. Also consult our article on the use of social media for customer service to highlight user feedback.
The Qstomy module also generates keyboard interaction heat-map reports, showing you where users stop or backtrack. By coupling this data with fix suggestions (e.g. : adding a skip‑link or improving contrast), you transform raw data into concrete actions quickly executable by dev teams.
How does Qstomy help make the audit more effective?
With Qstomy, you benefit from an automated audit that analyzes tags title, alt, aria‑label and DOM order. The report provides concrete actions and copy-paste code examples. Moreover, our AI can suggest labels suitable for product pages, such as cages or fences, to ensure smooth reading for all users. To deepen data collection, read the analysis of e-commerce conversations.
Additionally, Qstomy offers continuous accessibility tests (CI/CD) that run with every deployment. Alerts are sent directly to your Slack or Teams, ensuring that regressions are addressed before production.
What checklist to follow before publishing the site?
Before publishing, check the following checklist :
Title and headings : the site name appears in each
<title>.Labels and aria-labels : all form and search fields are correctly labeled.
Alt texte : every image has concise and relevant text.
DOM order : screen reader reading follows visual logic.
Liens de saut : a
skip‑linkis present and functional.Navigation clavier : all interactions are accessible via Tab.
Tests utilisateurs : complete at least one session with a screen reader.
FAQ rapide
What free tool is used to test accessibility? NVDA or VoiceOver are sufficient.
How often should I audit my site? At least once per quarter or after each major update.
Does Qstomy offer training? Yes, our webinars cover accessibility best practices.
By following this list, your PetsContained store will be accessible to all customers, regardless of their needs.
To go further: Integrating CS responses into a useful e-commerce SEO strategy for customers - Qstomy. Also consider launching A/B tests with user groups with disabilities to validate the real impact of improvements on conversion rates.

Enzo
October 29, 2026


