Accessible Gift Cards and Store Credit: The Pages Stores Forget to Test
Gift card purchase, balance checks, and store credit redemption involve codes, forms, and third party pages that rarely get tested. A practical pass over the whole gift card journey.
Gift cards are a large share of holiday revenue and a small share of testing time. The journey looks simple: buy a card, send it, the recipient checks a balance and spends it. Underneath sit code entry fields, balance check forms served by apps, email templates, and redemption steps inside checkout, each built by a different tool and each capable of shutting a disabled shopper out of money that belongs to them.
Testing the gift card journey end to end, once before the holiday season and again after any app change, catches the failures that ordinary product page tests never reach.
Buying and sending the card accessibly
The purchase form needs labeled fields for amount, recipient, and message, with preset amount buttons that announce their value and selected state. Custom amount fields are a frequent failure: a beautiful unlabelled box that a screen reader calls only edit text. The delivery choice, email or printable, should be a real choice with clear consequences, and error messages for a mistyped recipient address must be announced and specific.
Balance checks are the weakest link
Balance check pages are often the oldest, least designed pages connected to a store, sometimes hosted by a provider with a CAPTCHA that has no accessible alternative and a code field that rejects pasted text. A recipient who cannot check a balance cannot plan a purchase. Test the checker with keyboard only, paste the code instead of typing it, and confirm the balance result is announced as text, not just displayed in a styled graphic.
Redemption inside checkout
At checkout, the gift card field competes with discount codes, Shop Pay style wallets, and store credit, and the labeling decides whether shoppers apply the right one. The field needs a clear label, an apply action that confirms the new total in text, and an error for an invalid code that explains the problem without wiping what the shopper typed. Store credit that appears automatically needs an announcement too, or a screen reader user may never know it was used.
The emails and printable cards count
A gift card delivered as an image inside an email, with the code as part of the picture, is unusable for a blind recipient. The code must exist as real text in the email, the printable version must print that text clearly, and the help route for a lost code must be stated in words. Test by forwarding the delivery email to a text only view and trying to complete a purchase from what survives.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: How to Make Shopify Size Charts and Fit Guides Accessible, Accessible Shopify Loyalty and Rewards Pages: Points, Tiers, and Sign In, and Accessible Gift Card and Store Credit Flows on Shopify Stores.
Frequently asked questions
Why do gift card flows fail accessibility checks so often?
Because they are assembled from several tools: the store theme, a gift card app, a balance check provider, and email templates. Each part gets tested, if at all, in isolation, so the barriers appear at the joins between them.
What is the most serious gift card barrier?
A balance check or redemption step a shopper cannot complete at all, such as an inaccessible CAPTCHA with no alternative or a code that only exists inside an image. That is not an inconvenience. It is money the recipient cannot use.
Should gift card codes be available as text in emails?
Yes. The code should be selectable, copyable text in the email and on the printable card, never only part of an image. Recipients using screen readers, magnification, or translation all depend on that text existing.
When should a store test its gift card journey?
Before the holiday season, after changing any gift card or checkout app, and at least once a year otherwise. Test the full journey: buy, receive, check balance, redeem, and recover a lost code.