A tilt-to-play game looks compelling in a campaign presentation. But a customer may have a phone fixed to a mount, be unable to move it comfortably or be using an environment where motion input is unavailable. “Try holding it differently” is not a complete participation plan.
For overseas brands commissioning content and development through Chinese partners, decide early whether motion deserves to be the only input. ONCE proposes an entry, switching and outcome walkthrough before expensive animation production.
A recent campaign makes the procurement question concrete
Amazon's October 26, 2026 announcement for The Cat in the Hat describes a mini game where customers tilt a mobile device to catch characters, with desktop access through a QR code.
That establishes the announced mechanic, not general effectiveness for branded games. We have not audited the experience and do not infer missing alternative controls from omissions in its announcement. It is a prompt to ask what your own scope should include.
Distinguish the interaction goal from its input
W3C's explanation of WCAG 2.2 SC 2.5.4 describes interface alternatives for motion-operated functionality and disabling motion response to prevent accidental activation, with exceptions for an accessibility-supported interface or essential motion. The Understanding page is explanatory guidance.
This does not establish which exception applies to a particular game or certify an experience after one button is added. Developers and testers must assess the actual functionality and claimed standard. “More entertaining” should not be treated as an automatic essential-motion exception.
Entry: can someone begin without enabling motion?
First describe the activity: catching objects, making a selection or changing a view. Then separate that purpose from tilting the device. The following checks are proposed methods, not results from an ONCE client test.
In the intended devices and browsing environments, check whether customers understand the controls and can choose a usable mode. Where motion is unsupported or any required permission is declined, provide a workable next step rather than repeating the same instruction.
An appropriate interface control can provide another way to perform a function. A skip route can let someone view campaign content without playing. These are different provisions: a product link alone does not reproduce the game's functionality.
Switching: does the selected mode actually take control?
After disabling motion response, move the device gently and check whether position, view or selection still changes. A visible alternative button is insufficient if motion continues to interfere.
Agree what happens when a player switches mid-round: retained progress, a pause or a restart. Make the behavior and explanation consistent. If modes have different difficulty and scores feed a leaderboard, assess whether comparison is fair rather than hiding the difference.
| Scenario | Expected observation | Insufficient evidence |
|---|---|---|
| Device stays fixed | The applicable alternative completes the agreed function | An automatic demonstration plays |
| Motion is disabled | Device movement no longer triggers that function | Buttons work but motion still interferes |
| Mode changes mid-round | Progress handling matches the explanation | Unannounced loss or rule changes |
| Input is unavailable | A usable mode or accurate next step is available | An endless activation prompt |
Specify the actual device, browser, entry route and build tested. Permission behavior and suitable controls differ; one successful developer demonstration is not universal coverage.
Outcome: follow each route to its result
Check results, replay, return navigation and campaign information after alternative input. For a skip route, explain what was bypassed and what remains available. Do not classify unsupported input, voluntary non-participation and gameplay failure as the same event.
Imagine a travel-organizer brand commissioning a sorting game. Moving items into virtual compartments is a game rule, not proof that the physical bag holds that number of objects. Keep game mechanics and actual product demonstrations distinct.
Record entry, mode choice, start, completion and onward visits separately. Switching mode is not automatically abandonment, and longer play does not establish purchase intent. This article makes no conversion or ROI forecast.
Scope animation, interaction and testing separately
A visual production partner may supply character animation and feedback effects. Developers handle input and state changes; testers check the agreed environments. Even if one supplier handles everything, assign deliverables, revision scope and acceptance responsibility explicitly.
Use a simple prototype to check control behavior before committing to elaborate visuals. Repeat the walkthrough after artwork and localization are added, since control visibility and feedback still need assessment. This sequence can expose issues earlier; it is not a promised cost saving.
The procurement unit becomes a participation route completed under agreed conditions, rather than an animation alone. Related planning is available in the ONCE video marketing articles.
Sources and limits
The Amazon announcement and current W3C Understanding page were checked on October 28, 2026. The walkthrough and hypothetical example are ONCE proposals, not a campaign compliance certification or a claim that ONCE built this game.
