Browser Games for Seniors: What Actually Works at 70+

In January 2025, Bramwell ran a fifteen-game browser testing session with a group of seven players aged 68–82 at a community centre in South London. The brief was simple: play each game for ten minutes, rate it on a five-point enjoyment scale, and describe what frustrated you. Here is what he observed.

The frustration hierarchy (most common to least):

1. Text too small to read comfortably (eleven of fifteen games) 2. Too many things happening at once in the tutorial 3. Ambiguous goals — 'I don't know what I'm trying to do' 4. Clicking targets too small (affecting players with reduced fine motor precision) 5. Sound effects that provided no useful information

Games that rated 4 or 5 stars from the majority:

Solitaire (any implementation): 6/7 players, average 4.4 stars. Familiar mechanic, clear goal, patient interface. One player noted: "The computer can cheat. Mine cheated. But I enjoyed it anyway."

2048 (gabrielecirulli.github.io): 5/7 players, average 4.1 stars. Simple goal (get to 2048), unlimited time, no advertising, large number tiles. One player played it for the full ten minutes and asked to continue.

Chess (lichess.org, computer opponent): 3/7 players, average 4.6 from those players. High ceiling game; three players were regular chess players who found the browser experience genuinely good. Four players had never played chess and found it overwhelming with no assistance.

Games that frustrated:

Any platformer: 1/7 players enjoyed it. The combination of timing requirements and small targets produced consistent frustration. The speed wasn't the problem — it was the precision.

Any .io multiplayer game: 0/7 players found these enjoyable. The visual noise, the small collision hitboxes, and the competitive environment produced anxiety rather than engagement.

The clearest design signal from this test: older players respond strongly to games where the game waits for them. 2048 waits. Solitaire waits. Chess waits. Everything else hurried.