Shopify accessibility: check the complete buying task

Check Shopify accessibility from product choice to checkout, including keyboard access, variants and errors, then separate fixes from compliance claims.

Shopify accessibility depends on whether customers can choose a product and complete checkout using the ways they navigate your store. Assess the complete buying task, then correct the barriers in the theme, apps or checkout step that causes them. A theme label or scan score doesn’t establish that the journey works.

Define the buying task and responsibilities

Choose a representative purchase with a required variant, a delivery choice and the payment path your customers actually use. For a hypothetical clothing store, the task is to buy a navy shirt in medium, select delivery and complete a test payment. Add a second case where the customer attempts to continue before choosing the required size.

Record the theme version and enabled apps before starting. Note the device and browser, plus the assistive technology used. Use authorised test checkout facilities so the assessment doesn’t charge a customer or create a real fulfilment request.

Assign each step to its actual owner. The retailer owns product descriptions and image alternatives. The theme supplier or developer usually owns storefront controls. An embedded sizing app has its own supplier. Route checkout defects to the team responsible for that platform component or extension, with the configuration that triggers them.

Use Web Content Accessibility Guidelines (WCAG) 2.2 as the technical reference and state the conformance level being assessed. A claim of Level AA covers the applicable Level A and AA requirements across the assessed scope. Completing the shirt purchase supplies evidence about that journey, not a whole-site conformance result.

For Australian retailers, the Australian Human Rights Commission’s digital accessibility guidelines explain disability discrimination obligations. The guidelines aren’t legally binding or a shield against a discrimination finding. For a US-facing operation, the US Department of Justice’s ADA guidance explains the Americans with Disabilities Act context. Establish the relevant jurisdiction before describing a Shopify store as ADA compliant.

Check product selection and navigation

Check the product journey with the keyboard before moving to cart. Shopify’s theme accessibility guidance covers keyboard controls and dynamic components. Test the enabled theme and apps together, because a usable theme can still contain an inaccessible added control.

  1. Start at the page entrance and use Tab and Shift+Tab to reach navigation and product controls. Expect a logical sequence and a visible focus indicator throughout.
  2. Open and close the menu without a mouse. Confirm that focus stays visible and returns to the appropriate control when the menu closes.
  3. Choose navy and medium. Check that each control has a meaningful name and exposes its selected state to the screen reader.
  4. Change to an unavailable size. Confirm that the new availability and any price change are communicated without requiring the customer to search the whole page again.
  5. Open the size guide and any embedded app. Confirm that their controls remain reachable and that closing them doesn’t lose the customer’s place.

For a modal size guide, the W3C dialog pattern moves focus inside when it opens. Tab stays within the open dialog, Escape closes it and focus normally returns to its trigger. A dialog that traps the customer after closure blocks the purchase.

Read the product information without relying on colour or the main photo. A swatch needs a colour name, and an image showing a specific product detail needs an appropriate text alternative. Shopify’s merchant accessibility instructions explain product image alternatives and text contrast choices.

Repeat the required-size case with no size selected. Expect the page to identify the missing option and provide a usable route to choose it. A grey button with no explanation leaves the customer unable to understand the next step.

Complete forms, cart and checkout

Complete the same purchase with a supported screen reader and browser combination, using keyboard controls as well as spoken output. For example, select VoiceOver with Safari on macOS when that combination belongs in your customer support coverage. Record the actual combination instead of describing a generic screen-reader pass.

Continue from the chosen shirt through the cart and payment steps. Follow this sequence with fictional customer details.

  1. Change the cart quantity. Confirm that the displayed quantity and total match the announced result and that focus remains usable after the update.
  2. Read field labels and instructions before entering delivery details. Required fields and accepted formats must be understandable before submission.
  3. Leave a required field blank and submit. Expect a clear error that identifies the field and explains how to correct it.
  4. Correct the error using the keyboard. Confirm that valid entries remain available and the customer can continue without starting again.
  5. Select delivery and complete an authorised test payment. Check the selected delivery charge, final total and payment result through the same assistive technology.

The W3C form notification tutorial describes clear error feedback and confirmation of success. Apply that principle to payment failures too. A customer needs to distinguish a rejected attempt from an accepted order before deciding whether to retry.

Include an offsite payment handoff if your store uses one. Confirm that the customer can understand where they are going and return to an understandable result. A successful cart check doesn’t cover the payment provider’s interface.

Choose and verify the fix

Prioritise a barrier by the buying task it prevents. An unreachable size selector blocks product selection. An unnamed payment control blocks checkout. Assign those failures before cosmetic defects that leave the purchase possible.

Give the responsible owner a reproducible case with the route, chosen variant and starting state. Record the expected behaviour beside what happened, with the browser and assistive technology combination. Exclude private customer details from the evidence.

Match the correction to its cause. The content editor can fix an unhelpful image alternative. A theme developer can repair focus handling in the size guide. An app supplier must correct a control generated inside its app. Retest the same failing interaction after the change, then complete the purchase again to check its downstream effect.

Evaluate a WCAG accessibility app against a named barrier. The misspelt phrase “WACG compliant Shopify app” points to the same WCAG question. An app is useful when its enabled feature demonstrably fixes the problem in your store. Installation or a badge alone doesn’t establish compliance.

Use the WCAG checker for its bounded automated checks, then assess interactions and assistive technology separately. Keep a failure open until the changed journey works in the recorded setup. Recheck it when a theme update or app change touches that part of the purchase.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup