What should a keyboard-accessibility review of a gift selector cover?
Review the whole selection journey with a keyboard: opening the selector, understanding options, choosing or declining, closing it and confirming the resulting cart.
A keyboard review should cover earning the gift, opening the selector, identifying a product and variant, making or declining the choice, and confirming the cart. A single successful click test cannot establish that this journey is usable without a mouse.
What evidence should an app comparison request?
Monk Commerce is one documented selection candidate. Monk Commerce documents a manual gift-selection interface; its setup guide alone does not establish keyboard accessibility. (How to give customers an option to choose their free gift? | Helpdesk - Monk Free Gift & Upsell) Request a demonstration of the actual widget and theme combination, with the same questions applied to every alternative. Do not turn the lack of an accessibility statement into proof of failure or treat a general compatibility claim as proof of success.
The W3C modal-dialog pattern describes moving focus into a dialog, containing its tab sequence, closing with Escape and returning focus appropriately. (Dialog (Modal) Pattern | APG | WAI | W3C) Use those requirements when the selector is implemented as a modal. An inline selector has a different interaction structure and should not be forced into modal behavior merely to match a checklist.
Which actions belong in the review?
| Stage | Keyboard review question | Evidence to capture |
|---|---|---|
| Open | Can the trigger be reached and activated? | Focus before and after opening |
| Understand | Is the purpose and gift limit clear? | Visible labels and announced context |
| Choose | Can product and variant controls be operated? | Selected state and confirmation |
| Close or decline | Is there a clear exit? | Focus recovery |
| Confirm | Can the resulting gift be located in the cart? | Item, variant, quantity and price |
Use real option lengths and a narrow screen. Include a gift with size and color rather than relying on a single decorative tile. A visible focus indicator should remain findable as the user moves through the controls.
How should errors and unavailable gifts be handled?
Attempt a selection that the test environment can reject, such as an unavailable variant. Review whether the customer can identify the problem, reach the relevant control and make another choice without losing the rest of the purchase.
Avoid marking the workflow successful because an error appeared somewhere on screen. The reviewer needs to determine whether the state and recovery are understandable with the chosen assistive tools. Record what was tested and which browser, device and technologies were involved.
What should an evaluation report conclude?
Report concrete observations, such as an unreachable close control or a focus return that lands in an unrelated part of the page. Distinguish those observations from suspected causes. Keep a reproduction and the expected behavior beside the report so the app or theme owner can address it.
After a fix, repeat the affected journey and check adjacent actions such as changing a variant or declining the reward. Accessibility work should be assessed on the integrated store interface; a vendor demo and the merchant’s customized cart can differ.
Limits of this guide
This is an editorial review checklist, not an accessibility audit, certification or legal assessment. No app or theme was tested. The W3C pattern covers a particular interaction model; full accessibility evaluation requires broader criteria, appropriate assistive-technology testing and qualified review.
Sources
- Monk Commerce | High Quality Shopify Apps (checked Oct 30, 2026)
- How to give customers an option to choose their free gift? | Helpdesk - Monk Free Gift & Upsell (checked Oct 30, 2026)
- Dialog (Modal) Pattern | APG | WAI | W3C (checked Oct 30, 2026)
Found an error? See the corrections policy.
More research on gift selection & usability
- How should an app replace a chosen gift without granting an extra reward?
Treat gift replacement as a transition with one final intended reward: define how the previous selection is removed, the new one is added and a failed change is recovered.
- How should you compare gift selectors for size and color variants?
A gift selector should add the exact chosen variant, show unavailable choices clearly and preserve the selection into the order; evaluate those outcomes before its visual design.
- What should happen when a shopper checks out without choosing a gift?
Define no selection as an explicit customer state: explain the available gift and let the shopper complete the intended choose, decline or continue path without a misleading promise.