Blog
Practical guides on web accessibility, written for developers and site owners.
-
State of E-commerce Accessibility 2026
Our own scans of 199 e-commerce homepages, updated periodically: 88.4% had at least one critical or serious WCAG failure, 52.3% had at least one critical issue. Full severity breakdown, issue-type ranking, and methodology, with links to the fix for each issue.
-
Screen reader testing for e-commerce: a practical guide
Automated tools catch roughly half of accessibility issues. Screen reader testing finds the rest: focus management gaps, wrong reading order, missing state announcements, and checkout form errors that only surface with real assistive technology. A walkthrough of what to test in each e-commerce flow, with NVDA and VoiceOver setup instructions.
-
Alt text for e-commerce product images: what to write and what to avoid
Image alt text is one of the most common accessibility failures on e-commerce sites. What to write for product photos, gallery thumbnails, color swatches, lifestyle images, and linked images, plus common mistakes and platform-specific implementation in Shopify, WooCommerce, and BigCommerce.
-
Keyboard accessibility in e-commerce: common failures and how to fix them
Keyboard navigation failures are among the most common accessibility issues on e-commerce sites. Covers megamenu keyboard traps, cart drawer focus management, product image lightboxes, filter panels, carousels, custom selects, size variant selectors, and focus indicators. With code examples for each fix.
-
Common accessibility issues in Magento and Adobe Commerce stores and how to fix them
Magento and Adobe Commerce stores built on the Luma theme share a predictable set of accessibility failures: product option swatches with no selected state, mini-cart drawers that do not move focus, megamenus inaccessible by keyboard, filter checkboxes rendered as plain links, and checkout form fields missing labels. With PHTML template and Knockout.js fixes.
-
Color contrast failures on e-commerce sites: what breaks and how to fix it
Color contrast is the most common accessibility failure on e-commerce stores. What WCAG 2.1 requires for text, large text, and UI components; where stores most often fail (price text, sale badges, ghost buttons, placeholder text, footer links); and the specific CSS changes needed to fix each pattern.
-
WCAG 2.2 for e-commerce: what changed and what it means for your store
WCAG 2.2 (published October 2023) added five new AA requirements that directly affect e-commerce stores: visible focus indicators, minimum touch target sizes, alternatives to drag operations, no redundant entry in checkout, and accessible authentication. What each criterion requires in practice, with code examples.
-
Common accessibility issues in BigCommerce stores and how to fix them
The accessibility failures that appear most often in BigCommerce Stencil theme stores: unlabeled product option swatches, category page buttons that do not name the product, cart drawer and off-canvas panel focus management, quantity inputs without labels, and product image gallery controls. With Handlebars template and JavaScript fixes.
-
E-commerce checkout accessibility: what breaks and how to fix it
The accessibility failures that appear most often in e-commerce checkout flows: form fields without labels, error messages that are not announced to screen readers, payment form issues, and checkout progress indicators. With code examples for each fix.
-
Common accessibility issues in Squarespace stores and how to fix them
The accessibility failures that appear most often in Squarespace e-commerce sites: icon-only header buttons, images without alt text, newsletter forms without labels, gallery lightbox focus management, and social icon links. With Code Injection fixes for each.
-
How web agencies add accessibility monitoring to client retainers
How white-label accessibility monitoring fits into an agency service model: what the monthly workflow looks like, what diff reports tell clients, how agencies structure the billing, and what automated scanning covers versus what requires manual testing.
-
How to write an accessibility bug ticket your development team can act on
A practical guide to translating accessibility scan findings into developer-ready tickets, with complete examples for the barrier types that appear most often on e-commerce stores: unlabeled icon buttons and form fields without labels.
-
How to read an accessibility scan report
What the sections of an automated accessibility report mean, how severity levels (critical, serious, moderate, minor) are defined, what WCAG criterion numbers tell you, and how to turn a list of findings into a concrete task list for your developer.
-
Common accessibility issues in WooCommerce stores and how to fix them
The accessibility failures that appear most often in WooCommerce stores: unlabeled variation dropdowns, quantity inputs without labels, broken product tab ARIA structure, archive page add-to-cart buttons that do not name the product, star rating inputs inaccessible by keyboard, and cart drawer focus management. With PHP filter and JavaScript fixes.
-
Common accessibility issues in Shopify stores and how to fix them
The accessibility failures that appear most often in Shopify stores: unlabeled color swatches and variant buttons, icon-only add-to-wishlist buttons, newsletter forms without labels, cart drawer focus management, and gallery navigation. Platform-specific fixes with Liquid code examples.
-
What e-commerce accessibility monitoring costs and what you get for it
A plain breakdown of the three price bands for accessibility tooling: overlay widgets, manual expert audits, and automated scanning. What each covers, what each costs, and what ongoing monitoring produces that a one-time audit does not.
-
Web accessibility for small e-commerce stores
Most accessibility issues on small e-commerce stores come from theme and component choices, not store size. What the most common findings look like, what fixing them costs in developer time, and when monitoring makes sense over a one-time scan.
-
Accessibility monitoring tools compared: overlays, manual audits, and automated scanning
A plain comparison of the three main approaches to web accessibility: overlay scripts, manual expert audits, and automated scanning tools. What each covers, what each costs, and where each fits, with a side-by-side table.
-
The European Accessibility Act: what e-commerce stores need to know
The EAA went into effect June 28, 2025. What it requires, who it applies to including US-based sellers, the microenterprise exemption, and what the EN 301 549 technical standard means in practice for a product page or checkout flow.
-
Why accessibility is good for your e-commerce business
Four concrete business reasons to fix accessibility on your store: broader customer reach, better HTML and SEO, EU compliance requirements under the European Accessibility Act, and improvements that help every shopper, not just those with disabilities.
-
How to spot common accessibility issues on your e-commerce site
Four practical tests you can run in any browser to find the most common accessibility failures: keyboard navigation, image alt text, color contrast, and form labels. No special software required.
-
Why accessibility overlays fail
What overlay scripts actually do to the accessibility tree, why the FTC took enforcement action against accessiBe, and why courts have not treated overlay installation as a defense in ADA web cases.
-
Five accessibility barriers that keep showing up on e-commerce product pages
The WCAG failures we flag most often on product pages, with the exact HTML fix for each one: missing image alt text, unlabeled buttons, unlabeled form fields, color contrast failures, and links with no descriptive name.