Should gift wrap price be in the checkbox label?

Yes, or immediately next to it in text. A buyer should not have to select an extra to discover its cost in the total, and screen reader users in particular need the price associated with the control itself.

How should a gift message character limit work?

State the limit in the field's description before typing, provide a count that can be checked on demand, and announce when the limit is reached. Never silently stop accepting characters with no explanation.

What belongs on the review step for gifts?

The wrapping choice, the full message text, and its cost inside the total. If any of those is missing at review, the buyer has no accessible way to verify a paid extra before paying for it.

Are per item gift options harder to make accessible?

They need more care, not different principles. Group each item's options under that item's name, label every control in context, and make the total wrapping cost readable as text before checkout.

Accessible Gift Card Balance Checkers: A Small Page With Every Problem

October 30, 2026

Balance checker pages combine CAPTCHA, unlabelled card and PIN fields, and results announced as images. How to make this minor page work for everyone.

The gift card balance page is an afterthought on most stores, built once and never audited. It asks for a long card number and a PIN hidden under a scratch panel, then gates the whole thing behind a visual CAPTCHA. For a screen reader or keyboard user, that is three barriers stacked on a page whose only job is to show one number.

It also tends to break WCAG 3.3.8, accessible authentication, and plain labelling under 3.3.2 and 4.1.2. The fix list is short, because the page does almost nothing. That is what makes its state hard to defend.

Labels, instructions, and the PIN problem

Card number fields on these pages are routinely identified by placeholder text alone, which disappears on typing and is not a label. Give the field a permanent visible label, state the expected format, and allow spaces in the number, because people copy card numbers in groups and a field that rejects spaces punishes careful typing.

PIN entry has its own trap. Some checkers clear the card number when the PIN is wrong, forcing full re-entry of a nineteen digit number. Keep the card number, name the actual problem, and put focus on the field that needs correcting. Error handling is an accessibility feature, not a courtesy.

CAPTCHA and the result

A visual puzzle CAPTCHA with no accessible alternative ends the task for many users outright. If bot pressure on balance checks is the concern, address it with rate limiting and monitoring, and use a challenge that offers a non visual route. A balance checker is a low value target that is often guarded like a bank vault.

When the balance returns, announce it. A result that appears silently on screen, or worse, inside an image, fails 4.1.3 status messages for screen reader users. Put the balance in text, in a status region, with the last four digits of the card so the shopper knows which card was checked.

Why this page matters commercially

Gift card recipients are often new to the store. This page may be their first interaction, days before they spend. A recipient who cannot check a balance frequently does not spend the card at all, and the store keeps a liability while losing a customer it already paid to acquire through the gift giver.

Put the balance checker on the standard audit list. It is one page, one form, one result. There is no cheaper page on the site to bring up to standard, and no excuse for it being the worst one.

Frequently asked questions

Why do balance checkers have CAPTCHA at all?

Stores add it to stop automated balance probing, where stolen card numbers are tested in bulk. Rate limiting, monitoring, and challenges with an accessible alternative handle that risk without locking out disabled customers.

Should card number fields accept spaces?

Yes. People read and type long numbers in groups. Accepting spaces and stripping them on submission costs nothing and removes a common, pointless error.

How should the balance be announced to screen readers?

In text inside a status region, with the cards last four digits, so it is announced when it appears and can be found again on the page afterwards.

What is the most common labelling fault on these pages?

Placeholder text used as the only label. Placeholders vanish when typing starts and are not a substitute for a permanent, programmatically associated label.