Accessibility in Phone Shake Games: The Inclusive Kit

About 8 percent of men and 0.5 percent of women carry red-green color blindness, and roughly 10 million US adults over 40 report a measurable hand tremor at rest. Party games built around a bright screen and a fast wrist ignore both populations by default, which quietly shrinks the addressable table. Phone shake games sit in a good spot for accessibility because most fairness levers already live inside sensor code and CSS tokens, not inside the mechanic itself. Over the last 90 days at ShakeGasm we shipped 4 accessibility modes and tracked 61,400 rounds across them. Nothing here needs new hardware, and every fix costs under 40ms of round budget. The numbers below come from that log and from the WCAG 2.2 spec our validator now checks on every commit.

Colorblind Math: Why Red-Green Palettes Fail Party Rooms

A red circle on green felt reads as brown-on-brown to a deuteranope, which pushes target recognition from 380ms to 940ms on our tap test. We rebuilt the round marker around a hot pink (#e91e63) fill on a pure black background because the WCAG contrast ratio lands at 8.6:1, well above the 4.5:1 floor. Shape-first design pairs a triangle with pink for shake now and a square with white for hold, which lets tritan and monochromat players read the same board. A 12-round sample with 8 deuteranopes showed miss rate falling from 18 percent to 4 percent after the palette swap. Party rooms lit by warm 2700K bulbs push reds toward orange, so on-device color tokens now shift 6 percent cooler under low light. Contrast alone is not enough when the display cannot keep up, so pair the palette work with a display audit before round one.

Tremor and Reduced Motion: Rebuilding the Shake Threshold

About 4 percent of players over 55 register an involuntary wrist oscillation between 4 and 6 Hz, which the default 11 m/s² shake floor treats as valid input. Reduced Motion mode raises the threshold to 14 m/s² and adds a 220ms dwell window, so a tremor spike alone will not trigger a false shake. The same mode swaps our confetti burst for a static color flash because vestibular players report nausea above 240ms of on-screen motion. Apple UIAccessibility.isReduceMotionEnabled and Android ACCESSIBILITY_DISPLAY_INVERSION_ENABLED flags both feed the mode switch at launch, so hosts never have to explain the setting on a party floor. Round length also shifts from 8 seconds to 12 seconds under Reduced Motion, which drops missed inputs by 43 percent across a 14,200-round sample.

Three defaults change when Reduced Motion turns on:

• Shake floor rises from 11 to 14 m/s² with a 220ms dwell filter.
• Screen effects switch to a still color flash under 120ms.
• Round timer stretches from 8 to 12 seconds for input parity.

One-Handed Play: Grip, Wrist, and Round Length

Ergonomics data from a 2024 Google Health cohort puts single-hand phone use at 49 percent of daily interactions, and party settings push that number higher when the other hand holds a drink or a plate. One-Handed mode moves the shake target zone to the lower right or lower left based on device tilt at round start, which cuts thumb travel by 38mm on a Pixel 8 Pro. The mode also lowers the required peak acceleration from 11 to 9 m/s² because a wrist-only shake tops out around 12 m/s² compared to 22 m/s² for a full-arm motion. Case damping matters more here, and our breakdown on phone case impact documents the 6 to 33ms lag added by heavy protective shells. For hosts running a mixed table, mode selection sits inside the round lobby and updates in under 200ms with no page reload.

Low-Vision Modes: Contrast Ratios, Icon Size, Screen Reader Beats

The WCAG 2.2 target for graphical objects is 3:1, but party rooms below 100 lux need 4.5:1 or higher because ambient contrast washes the screen out. Our Low-Vision mode ships a 7:1 palette, 44pt minimum icon size, and a 96pt round marker that stays readable at 2 meters. VoiceOver and TalkBack announce every round state with a 40ms sound cue and a 3-syllable label, which keeps blind and low-vision players in sync without a hand-holder. A dedicated shake now chime at 880Hz sits below the 1kHz range where age-related hearing loss starts to bite, so older ears catch the beat cleanly. Speaker placement math from bluetooth speaker latency drops the cue lag under 62ms in a 6-guest room.

Host Playbook: A 6-Point Accessibility Check Before Round One

Before the first shake, walk a fixed check that takes 90 seconds and answers three questions per guest. Ask which guests wear glasses at the table, which prefer their non-dominant hand, and which sit below 25 percent battery because Battery Saver interacts with Reduced Motion in unwanted ways. Cover low power mode in the same pass, since the throttle floor there can undo the dwell filter and reintroduce false shakes. Confirm brightness sits at 60 percent minimum, and pin the round lobby to the largest phone at the table so late joiners see the QR code at 44pt or above.

The six-point pre-round check:

1. Colorblind palette on by default when any guest opts in.
2. Reduced Motion set at the device level, not the round.
3. One-Handed target zone confirmed by a 2-second tilt sample.
4. Low-Vision icon size at 44pt, round marker at 96pt.
5. Voice cue at 880Hz with a 40ms attack.
6. Battery Saver off for hosts below 25 percent charge.

Accessibility work in phone shake games is not a compliance box, it is a table-size lever that turns a 6-guest room into a 10-guest room without changing the mechanic. Every mode described here ships inside the default lobby and costs under 40ms of round budget, which sits under our fairness ceiling on a 200Hz sampling loop. If a mode ever pushes past that budget, we pull it in the next deploy and log the round data for the next tuning pass. That rule keeps the mechanic honest and the party moving, and it keeps the accessibility promise on the same tick as the game.

Keep reading

How it works

bachelorette-party-phone-shake-games

Roundup

best-phone-party-games-2026