Volusion Accessibility Checklist 2026 | WCAG 2.1 AA & EAA
Last updated: 2026-05-31
Volusion is one of the older hosted e-commerce platforms, and that history is the single most important fact for accessibility. Many live Volusion stores still run on templates that predate the platform's responsive themes, which means table-based layouts used for visual structure, deeply nested markup, and JavaScript-driven widgets that were never built with keyboard or screen reader users in mind. Even on newer themes, the platform's customization model encourages merchants to edit HTML templates directly, so the accessibility of a Volusion store is largely whatever the merchant and their original theme left behind. The failure patterns are exactly the ones that generate ADA demand letters against online retailers. Product images - the most important content on a store - routinely ship without meaningful alt text, so screen reader users cannot tell one product from another. Product galleries and zoom widgets often cannot be operated with the keyboard. Category and faceted navigation menus expand on hover with no keyboard equivalent and no expanded-state information. The cart and the multi-step checkout, where the law cares most because that is where money changes hands, frequently contain form fields labeled only by adjacent text or placeholders, error messages that are shown in color alone, and 'continue' controls that are links or divs styled as buttons. Layered on top is the contrast problem common to retail design: sale badges, 'low stock' warnings, and price strike-throughs rendered in light reds and grays that fall below the required ratios. Volusion provides no built-in accessibility checker, so every item here is verified with external tooling and a manual pass. This checklist follows the shopper's path from category page to completed order.
Common Accessibility Issues
Volusion pulls product images from the catalog, and the alt text is commonly left as the file name, the product code, or blank. On a store, the product image is the primary content, so a screen reader user browsing a category hears a list of meaningless filenames and cannot distinguish products, compare options, or decide what to buy.
Populate a descriptive alt attribute for every catalog image that identifies the product as a shopper would describe it ('Navy wool overcoat, front view'). Where the product name is already adjacent as real text, keep gallery thumbnails' alt concise to avoid duplication, and mark purely decorative images with empty alt. If the template hard-codes alt from a field, ensure that field is populated for every product.
<img src="/v/vspfiles/photos/SKU-1042-2.jpg" alt="SKU-1042-2"> <img src="/v/vspfiles/photos/SKU-1042-2.jpg" alt="Navy wool overcoat, front view"> Older Volusion templates use HTML <table> elements to position page regions visually rather than to present tabular data. Screen readers may announce these as data tables ('table with 4 columns'), and the resulting reading order can diverge from the visual layout, confusing non-visual users and breaking the logical structure of category and product pages.
Migrate layout tables to CSS-based layout (flexbox or grid) so tables are reserved for genuine tabular data such as specification charts. Where a full re-theme is not feasible immediately, add role="presentation" to layout tables so assistive technology does not announce them as data tables, and verify the DOM reading order matches the visual order.
<table width="100%">
<tr><td>Sidebar</td><td>Product details</td></tr>
</table> <div class="product-layout">
<aside>Sidebar</aside>
<main>Product details</main>
</div>
<!-- CSS grid/flex handles the two-column layout --> Volusion category menus and filter/facet controls frequently expand on mouse hover or rely on click handlers attached to non-interactive elements (spans, divs). Keyboard users cannot open submenus or apply filters, and screen reader users get no information about whether a section is expanded or collapsed.
Ensure menu and filter controls are real buttons or links reachable by Tab and operable with Enter/Space. Expose expanded/collapsed state with aria-expanded, and make sure applying a filter that updates the product grid announces the change (for example via a polite live region reporting the new result count).
The cart and multi-step checkout are the highest-risk surfaces on any store. In Volusion checkouts, fields are often labeled only by adjacent text or placeholder text with no programmatic association, required fields are indicated by color or an asterisk with no text, and autocomplete attributes are missing - so screen reader users cannot reliably identify each field or use browser autofill.
Associate every field with a <label> using for/id, add visible 'required' text (not color alone), and apply correct autocomplete tokens (name, email, address-line1, postal-code, cc-number). Confirm the tab order through checkout is logical and that the final 'place order' control is a real button.
Card number <input type="text" name="cc"> <label for="cc">Card number (required)</label>
<input type="text" id="cc" name="cc" autocomplete="cc-number" inputmode="numeric" aria-required="true"> When a Volusion checkout or contact form rejects input, the error is often shown only by turning the field border or label red. Users who are colorblind or using a screen reader receive no indication of which field failed or why, and the messages are usually not programmatically tied to the field.
Pair every error with text that names the problem ('Enter a valid ZIP code'), associate it with the field via aria-describedby, and move focus to or announce the first error on submit. Do not rely on red color as the only signal; add an icon or text marker as well.
Retail templates lean on light-red 'Sale' badges, gray strike-through original prices, and pale 'Only 2 left' warnings that frequently fall below 4.5:1. These carry real purchasing information, so failing the contrast threshold puts price and availability out of reach for low-vision shoppers.
Darken badge and warning colors until text passes 4.5:1 against its background, and never communicate a discount or low-stock state through color alone - keep the text label ('Sale', 'Only 2 left') so the meaning survives in grayscale and for screen reader users.
Volusion-Specific Tips
- Identify which template generation your store runs first: legacy table-based themes need a layout migration before finer fixes matter, while newer responsive themes mostly need content-level fixes (alt text, labels, contrast).
- Volusion exposes HTML/template editing, so most structural fixes - real buttons, label associations, role="presentation" on layout tables - can be made directly in the template files; keep a backup before editing.
- Treat the cart and checkout as the priority path; e-commerce demand letters most often cite an inability to complete a purchase, so a fully keyboard- and screen-reader-operable checkout is the highest-value work.
- Populate alt text at the catalog level so it flows to every page the product appears on (category grid, search results, related products) rather than fixing images page by page.
- Because Volusion has no built-in scanner, schedule a recurring axe or WAVE check after any theme update, since template changes can silently reintroduce layout tables or strip attributes.
Recommended Tools
axe DevTools (browser extension)
Scan category, product, cart, and checkout pages of a live Volusion store for missing alt text, label associations, contrast, and table-role issues that the platform will not flag itself.
WAVE Browser Extension
WAVE's inline annotations make it easy to see which product images lack alt text and which checkout fields lack labels directly on the rendered store.
WebAIM Contrast Checker
Validate sale badges, strike-through prices, and low-stock warnings against the 4.5:1 threshold for normal text and 3:1 for large text and UI components.
Volusion Accessibility: Shopper Path vs. Common Failures
| Plugin / Tool | Page / Step | Common Failure | WCAG Criterion | Priority |
|---|---|---|---|---|
| Category grid browsing products | Product images with filename or blank alt | 1.1.1 Non-text Content | High | |
| Navigation / filters menus and facets | Hover-only menus, non-keyboard filters | 2.1.1 Keyboard | High | |
| Product page gallery and layout | Layout tables; gallery zoom not keyboard operable | 1.3.1 Info and Relationships | Medium | |
| Checkout highest legal risk | Unlabeled fields; missing autocomplete | 3.3.2 Labels or Instructions | Critical | |
| Validation form errors | Errors shown by color only | 1.4.1 Use of Color | Critical |
Frequently Asked Questions
Why do older Volusion stores fail accessibility audits more often?
Many long-running Volusion stores still use templates built before responsive, semantic design was standard. Those themes use HTML tables for visual layout, attach click handlers to non-interactive elements, and omit alt text and form labels. Screen readers then announce layout tables as data, keyboard users cannot operate menus or checkout, and the reading order diverges from the visible order. The fix usually starts with a layout migration on legacy themes, then content-level work on alt text, labels, and contrast.
Can I edit Volusion templates to fix accessibility issues?
Yes. Volusion gives you access to HTML template files, so you can convert layout tables to CSS layout, replace fake buttons with real
Which Volusion pages should I fix first for ADA risk?
Prioritize the cart and checkout. E-commerce ADA demand letters most commonly allege that a screen reader or keyboard user could not complete a purchase, so a fully operable, properly labeled checkout reduces the most legal exposure. After that, fix product image alt text and category navigation, since those block shoppers from getting to checkout in the first place. This is not legal advice.
Further Reading
- Accessible Ecommerce Checkout Guide
- Product Variant Swatches Screen Reader Accessibility
- Alt Text Guide
- Color Contrast Guide
- Shopify Store Accessibility Guide
Other CMS Checklists
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.