Accessible Juice: Designing Polish for All Players

Game juice should be available for every player. Many juice effects -- screen shake, flashing lights, chromatic aberration, strong motion blur -- are not optional embellishments for some players. They are migraine triggers, vestibular disorder aggravators, and epilepsy risks. Every game with significant juice should ship with accessibility options for these effects. Not as an afterthought, and not as a degraded experience.

The Minimum Required Options

Screen shake: offer off, reduced, and full options (or a continuous slider). Motion sickness and vestibular disorders are common. Screen shake is the highest-risk effect for these conditions.

Flashing lights: a reduce flash intensity toggle is required for any game with screen-wide flashing or rapidly alternating colours. This is an epilepsy risk and a legal requirement in some jurisdictions for commercial games.

Chromatic aberration: an off/on toggle. Chromatic aberration causes migraines and visual fatigue in a meaningful portion of players. It is purely aesthetic -- there is no gameplay information in it -- making it a straightforward toggle.

Motion blur: an off/on toggle. Nausea and visual disorientation are common reactions. Like chromatic aberration, it carries no gameplay information.

Strong vignette: an off/reduced toggle. Vignette can cause claustrophobia and visual anxiety, particularly in long play sessions or for players with anxiety disorders.

Damage colour flash: an off/reduced toggle specifically for screen-wide red flashes on damage. Photosensitivity to red-dominant flashes is well-documented.

Particle density: a low/medium/high preset, or a slider. This addresses both performance on low-end hardware and cognitive overload for players with attention difficulties.

Controller rumble: an off/reduced/full slider. Discomfort from sustained rumble is real for some neurological conditions, and some players simply do not want it.

VR locomotion: snap turn and comfort mode options. Screen movement in VR causes motion sickness at a much higher rate than flat-screen games.

The Replace, Don't Remove Principle

Accessibility options should not feel like a lite mode. The game should be no less legible or satisfying with effects reduced. The key principle is replace rather than remove: when screen shake is off, substitute a brief camera micro-shift or HUD edge flash. The player still gets a signal; it just does not move the camera. The feedback event is preserved; only the delivery mechanism changes.

Similarly, reduce amplitude rather than category. When particle density is set to low, reduce particle count and scale -- do not remove particles entirely. The event is still communicated. The hit still registers. The visual feedback still exists. It is just quieter.

Implementation Approach

The cleanest implementation uses a global accessibility scalar that multiplies all amplitude values. Define a JuiceSettings ScriptableObject (or equivalent) with a global intensity multiplier per effect category: shakeMultiplier, flashMultiplier, particleMultiplier, rumbleMultiplier. Every juice system reads these values before triggering effects. Changing the accessibility slider changes the multiplier. No bespoke handling required per effect.

This architecture also solves the separate problem of tuning: you can test your game at different global intensities quickly and find the right baseline before individual effect calibration begins.

The Default Intensity Problem

Never default to maximum juice and require opt-out. Start with moderate settings and let players opt into more intensity. This matters for two reasons. First, it is better for first impressions -- players who find the default overwhelming will leave before they discover the accessibility menu. Second, it reduces the stigma of accessibility settings: if the default is moderate, using the accessibility options does not feel like admitting a limitation.

The No-Juice Legibility Test

Test your game with all juice disabled. Make sure it is still understandable and playable. This has a dual benefit: it validates that your accessibility options work correctly, and it reveals whether your juice is communicating information or just decoration. If turning off screen shake makes it impossible to tell whether your hit connected, the issue is that screen shake is doing work that should be done by the hit animation, audio, or gameplay state change. Fix the underlying communication problem; do not make players choose between legibility and comfort.

The best-designed accessible juice systems make players ask whether they have accessibility options on -- the game feels complete either way. That is the standard. Accessible juice is not compromised juice. It is juice that includes everyone.