ORLOV GAMES

Blog · Big Ben Blocks ·

Reduced motion: why some players switch animations off

A sliding, bouncing, shaking interface looks lively to most people. For some it is a reason to put a game down, which is why operating systems let you ask for less.

Most puzzle games lean on motion: pieces slide into place, cleared lines burst, the screen shakes on a big combo. For many players that is part of the fun. For others it is uncomfortable, and the setting that turns it down is one of the more useful accessibility options a game can have.

Why motion bothers some people

The sense of balance depends on the vestibular system in the inner ear, working together with vision. In a vestibular disorder, or in people who are simply sensitive to motion, that system can be thrown off by what the eyes see on a screen. The usual symptoms are dizziness, nausea, headache and a sense of the room moving. Motion sickness works on the same mismatch: the eyes report movement while the body is still.

The motion that tends to cause trouble is large or covers much of the screen: zooming, spinning, sliding transitions, parallax (layers moving at different speeds to suggest depth) and shaking. A small icon changing colour rarely does. Reactions vary from person to person, so there is no single safe amount of animation, which is why this is a setting and not a design rule.

Vestibular sensitivity is not the same thing as photosensitive epilepsy. The second is about rapid flashing, and it has its own limits, covered next.

What the accessibility guidelines say

The Web Content Accessibility Guidelines (WCAG) are written for the web, but their wording is the usual reference for apps too. Three success criteria in version 2.1 bear on animation.

The three differ in who they protect. 2.3.1 sets a hard ceiling for everyone. 2.2.2 is about things that keep moving while you try to read. 2.3.3 is about the response to your own taps, which is the case for a puzzle game: you press, and the board answers with movement.

3 flashes in 1 second: within the limit 0 s 1 s 4 flashes in 1 second: over the limit 0 s 1 s
WCAG 2.3.1 allows no more than 3 flashes in any one-second period. Four in a second fails unless every flash is below the general flash and red flash thresholds. Each filled block is one flash; the layout is a schematic, not a measured animation.

The settings that switch animation off

On Android, the accessibility settings include Remove animations. Turning it on shortens or removes the transitions the system itself plays, such as opening an app or switching screens, and apps can read the preference and follow it. Where it sits in the menu varies by phone maker and Android version, so search the settings for “animation”.

On the web the equivalent is the CSS media query prefers-reduced-motion. It has two values, no-preference and reduce, and it reflects a setting made once at operating system level. A page that respects it can swap its movement for something calmer when the value is reduce. Other platforms have similar switches, and the idea is the same everywhere: the player says it once, and software is meant to listen.

What a reduced-motion design typically swaps

Reduced motion does not mean no feedback. Players still need to know a piece landed or a line cleared. The usual approach is to keep the information and change the way it arrives:

  1. Fades instead of movement. A cleared cell fades out in place rather than flying off or bursting.
  2. No parallax. Background layers stay still, so there is no depth effect to track.
  3. No screen shake. Emphasis comes from a static change, such as a highlight or a number appearing.
  4. No zooming or spinning. Scale and rotation changes are replaced by an instant switch or a short fade.
  5. Nothing that loops on its own. Ambient animation is removed, in the spirit of 2.2.2.

None of this makes a puzzle easier or harder. A row of nine cells is complete whether it flashes, fades or simply disappears. That is one reason block puzzles suit the setting well: the rules are about which cells are filled, and the animation is decoration on top.

WCAG 2.3.1: no more than three flashes in any one second. WCAG 2.2.2: a way to stop auto-moving content that lasts more than five seconds. WCAG 2.3.3: motion from your own actions can be turned off.

What Big Ben Blocks says

The Google Play listing for Big Ben Blocks: Block Puzzle says the game includes screen-reader labels and reduced-motion support. The listing does not say how reduced motion is switched on or which effects it changes, so this post does not either. What it does show is that the option sits alongside the other accessibility features it names: blocks carry shape symbols as well as colours, and tap-to-place controls are an alternative to dragging. Those are covered in the posts on colour-blind players and tap-to-place.

If you are choosing a game with motion in mind, three checks are worth making. Does it follow the system setting, or have its own switch? Does the feedback still make sense with the movement removed? And does anything flash? If you are prone to dizziness, try a short session with the Android setting on before a long one, and stop if symptoms start.

Big Ben Blocks: Block Puzzle offers untimed Classic play or a three-minute Time Attack, and the Daily Challenge changes at midnight UK time. The ten Adventure levels run from Westminster to Piccadilly. The listing names screen-reader labels and reduced-motion support among its accessibility options. It plays offline with no ads and no in-app purchases, and the coins you earn have no cash value.

Get it on Google Play