E-commerce
October 31, 2026
Are you wondering how to ensure that every visitor, regardless of their disability, can navigate and shop without hindrance on your Shopify store? Thanks to a small Python infrastructure, you can set up an automated process that examines each page, detects accessibility issues, and alerts you before these problems translate into lost sales or legal disputes. This article guides you step by step: configuring tools, writing the Scrapy spider, calling the audit API, interpreting results, setting up continuous reporting, and integrating with the Qstomy platform to turn gaps into optimization opportunities. You will also discover development best practices, budget constraints, and technical limits to know to keep your store up to date with WCAG 2.1 standards. This step ensures continuous compliance and minimizes legal risks related to accessibility. In addition to legal compliance, good accessibility improves search engine optimization, as search engines favor well-structured and semantic sites. Users using screen readers or text-based browsers benefit from smoother navigation, which reduces bounce rates and increases time spent on the site. Commercially, studies show that a 10% improvement in the accessibility score can lead to a 5% increase in average revenue. Thus, every investment in automating accessibility checks generates a quick return on investment. We will also see how to monitor accessibility metrics over time using Qstomy dashboards, and how to define proactive alerts to act before issues impact visitors.
Summary
What are the prerequisites for using Scrapy and the WAVE API?
Before launching the project, ensure you have a functional installation of Python 3.7 or higher. Create an isolated environment with python -m venv .venv then activate it (source .venv/bin/activate sous Linux/macOS ou .venv\Scripts\activate sous Windows). Installez Scrapy via pip install scrapy and check the version with scrapy version. Then register for the accessibility audit service to obtain your API key: fill out the registration form, confirm your email address, and retrieve the key from your user dashboard. Keep this key in a file .env or in the server environment variables so you never expose it in the source code. Finally, prepare your preferred IDE, VS Code, PyCharm, or a text editor, to benefit from Python autocompletion and linting. This step ensures continuous compliance and minimizes legal risks related to accessibility.

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
How to create a Scrapy spider that explores all pages of your store?
Scrapy is based on the concept of spider which systematically explores URLs of a domain. Start by creating the skeleton with scrapy genspider shopaccess shop.myshopify.com. In the generated file, expand allowed_domains to include your store and the audit API domain. Remove the filters allow so the spider follows every internal link, including collection pages, product pages, checkout pages, and blog posts. Add a depth rule (DEPTH_LIMIT) to avoid infinite loops and define DOWNLOAD_DELAY to respect the request limits of the audit service. You can also implement a custom middleware that adds a header User-Agent adapted to scraping best practices and logs every visited URL in a dedicated log file. This step ensures continuous compliance and minimizes legal risks related to accessibility.
How to call the WAVE API and interpret the JSON results?
In the method parse from the spider, first retrieve response.url then encode it for transmission to the audit API. Construct the full request in the form https://wave.webaim.org/api/request?key=VOTRE_CLE&url=URL_ENCODEE and launch it with scrapy.Request. Remember to handle rate limits by including meta={’dont_retry’: True} and to capture HTTP errors (429, 500). When the response arrives, use the module json to decode it, then extract the arrays alerts, errors and contrast. Create a AccessItem containing the URL, number of errors, severity, and a page ID, then pass it to the Scrapy pipeline which will write it to a CSV file or a SQLite database. This flow guarantees complete traceability of each analysis. This step ensures continuous compliance and minimizes legal risks related to accessibility.
How to leverage error reports to improve accessibility?
Once the CSV is generated, each row groups the URL, the number of warnings and errors, as well as the nature of each issue. Sort pages by severity: contrast errors, tags alt Missing or unlabeled form fields should be prioritized as they directly impact user experience and conversion rates. Import the CSV into the Qstomy dashboard, where accessibility metrics are cross-referenced with performance indicators (abandonment rate, average order value). This allows you to quickly visualize correlations between an increase in errors and a drop in sales, and assign each anomaly to the relevant development or design team. A monthly audit helps detect regressions after every theme or product update. This step ensures continuous compliance and minimizes legal risks related to accessibility.
How to automate reporting and receive real-time alerts?
To automate reporting, configure Scrapy to export results directly to Google Sheets via the Sheets API. Create a service account in your Google Cloud console, download the JSON key, and then use the library gspread to open the shared spreadsheet. Each spider execution updates the corresponding rows and adds a column execution date. Then cut the flow with a Slack webhook: when the number of errors on a page exceeds a defined threshold (e.g., 5 errors), trigger sending a message containing the link to the relevant page and a summary of the issues. You can also configure email alerts via SendGrid or your internal SMTP server. This notification chain ensures teams respond quickly to new violations. This step ensures continuous compliance and minimizes legal risks related to accessibility.
What coding best practices limit errors detected by WAVE?
Adhering to WCAG 2.1 specifications starts with clean HTML semantics: use tags header, nav, main, section and footer to structure content. Each image must have an attribute alt description, even decorative images that may receive a alt="". Ensure color contrast meets the 4.5:1 ratio for normal text and 3:1 for large graphical elements. Limit ARIA roles to cases where native semantics are insufficient, and ensure every form field has an label explicitly linked via the for. Before pushing changes, run the built-in audit extension in your browser to visualize errors in real time. This step ensures continuous compliance and minimizes legal risks related to accessibility.
How to integrate this solution into a CI/CD process?
Integrate accessibility crawling into your continuous integration pipeline. In a file .github/processus/accessibility.yml, define a job that runs after the build, installs project dependencies, activates the virtualenv, and runs the spider with the option --nolog. Utilisez l’action actions/upload-artifact to save the generated CSV as a run artifact. Then add a script that compares the new report to previous results using diff or a small Python library. If the number of critical errors has increased, the job fails and automatically creates a JIRA ticket or a GitHub issue, blocking the merge until the issues are resolved. This step ensures continuous compliance and minimizes legal risks related to accessibility.
What is the actual cost of using the WAVE API?
The pricing model for the audit API is based on a credit system: each request consumes 2 to 3 credits, with each credit costing between €0.025 and €0.04. For an average store with 200 pages, a full crawl therefore costs between €10 and €12 in operational expenses. Depending on the frequency of your audits (weekly, bi-weekly), you can subscribe to credit packs with tiered pricing, which lowers the unit cost. Compare this amount to potential costs associated with non-compliance lawsuits or lost conversion due to accessibility barriers; the return on investment is generally very fast. This step ensures continuous compliance and minimizes legal risks related to accessibility.
How to validate improvements after correction?
After each fix, rerun the same spider on the affected URLs to verify the disappearance of errors. The new CSV should show a decrease in the number of warnings or their total removal. Additionally, perform a manual test using the built-in audit tool in your browser to visually inspect the rendering, particularly contrast and keyboard navigation. Archive both reports (before and after) in your ticketing system or Git repository to ensure full traceability of improvements. This continuous validation approach ensures that every theme or content modification does not reintroduce new violations. This step ensures ongoing compliance and minimizes legal risks related to accessibility.
What technical limitations should you be aware of?
Scrapy does not render JavaScript, meaning dynamically generated content (e.g., SPA carousels, cart areas updated via AJAX) will not be analyzed. To address this limitation, insert a rendering step beforehand using a headless engine like Playwright or Splash: the spider sends the URL to this service, retrieves the rendered HTML, and then passes the result to the audit API. Also, ensure you respect the rate limits imposed by the audit service; implement an exponential backoff mechanism in case of a 429 response to avoid blocking. Using rotating proxies can also distribute the load and reduce the risk of exceeding quotas. This step ensures ongoing compliance and minimizes legal risks related to accessibility.
How does Qstomy help monitor and fix accessibility errors?
Qstomy offers a dedicated dashboard that aggregates Scrapy-WAVE reports with your e-commerce performance metrics (abandonment rate, average order value). The dashboard highlights pages where an increase in accessibility errors coincides with a drop in conversion, allowing you to quickly identify critical points. The platform also generates automated suggestions: insertion of relevant attributes alt relevant, improved color contrast, addition of missing labels. Thanks to its integrated AI, Qstomy provides ready-to-copy-paste code snippets, reducing compliance time from several days to just a few hours. This step ensures ongoing compliance and minimizes legal risks related to accessibility.
What checklist should you follow before launching an accessibility crawl?
To go further: E-commerce SEO strategy for category pages - Qstomy, How to optimize an e-commerce site for Google (step-by-step guide) - Qstomy, Which free website builder should you choose for e-commerce? - Qstomy, Can you create an e-commerce site for free? - Qstomy, Can you use Wix for an e-commerce site? - Qstomy, Integrating CS responses into a useful e-commerce SEO strategy for customers - Qstomy, Feedback loop: follow feedback to optimize your products - Qstomy. This step ensures ongoing compliance and minimizes legal risks related to accessibility.

Enzo
October 31, 2026


