Accessible Playable Ads: Contrast, Tap Targets, Motion and Colour

Accessibility in advertising is usually framed as compliance, which is the least interesting reason to care about it. The interesting reason is arithmetic: roughly one in twelve men has some form of colour vision deficiency, a large share of your audience is holding the phone one-handed on a moving bus, and a playable that only works for people with perfect vision, steady hands and full attention is an ad that fails a measurable slice of every impression you buy.

Contrast, and why ad contrast is worse than web contrast

The WCAG thresholds are a reasonable starting point — 4.5:1 for body text, 3:1 for large text and meaningful graphics. Playables should aim above them, for two reasons that do not apply to a website. Your ad is viewed outdoors in daylight far more often than a web page is, and it is frequently viewed at reduced brightness because the phone is conserving battery.

The specific thing that fails most often is text laid over artwork. A headline that clears 4.5:1 against the average of a background image can drop below 2:1 over the light part of it. Either put text on a solid or scrimmed panel, or check contrast against the lightest and darkest regions it actually crosses rather than against an average.

Tap targets sized for thumbs, not cursors

Apple's guidance is 44×44pt, Android's is 48×48dp, and both are minimums rather than targets. In a playable the relevant number is often larger, because the interaction is happening at speed and frequently one-handed, and because a missed tap in an ad does not get a second chance the way a missed tap in an app does.

The two failures worth checking: interactive elements smaller than the guidance, and interactive elements that are large enough individually but sit close enough together that a thumb cannot reliably pick one. The second is much more common in match-style mechanics, where a grid tuned on a desktop with a mouse becomes genuinely difficult on a phone.

Do not make colour the only signal

This is the constraint that bites hardest in playable ads, because so many casual mechanics are literally about colour matching. If the mechanic is "match three of the same colour" and the only difference between pieces is hue, then for a meaningful share of your audience the game is unplayable — and they will not tell you, they will simply not convert.

The fix is standard in games and rare in ads: give each piece a second distinguishing property. A shape, a symbol, a pattern, a distinct silhouette. Well-made match-3 art does this so naturally that most players never notice — the pieces are a jelly, a wrapped sweet, a striped ball — and the same technique costs nothing when you are producing the art anyway.

The quickest check is to convert a screenshot to greyscale. If you cannot tell the pieces apart, neither can a portion of your audience.

Motion, and the people it makes ill

Vestibular disorders make large-field motion genuinely unpleasant — parallax that moves the whole background, aggressive screen shake, rapid zooming, spinning transitions. In an app this is handled by respecting the system reduce-motion preference. In a playable you often cannot read that preference reliably inside the container, which argues for restraint by default rather than for an opt-out.

Practical version: keep large-field motion brief and infrequent, prefer moving objects to moving the camera, and avoid full-screen shake as a feedback device when a local effect on the object would do. None of this weakens the creative; most of it makes the interaction easier to read.

Flashing, which is a safety issue rather than a preference

Content flashing more than three times per second can trigger photosensitive seizures. This is not a design nicety, and several ad policies address it directly. Rapid strobing, high-contrast alternating frames and aggressive particle flashes on a success moment are the usual culprits in playables, where a celebration effect is often the busiest thing in the creative.

Text size and the temptation to shrink

Playables are size-constrained and text is cheap to shrink, so it gets shrunk. Aim for a 16px equivalent minimum for anything the player is expected to read, and treat anything under about 12px as decorative — because that is how it will function. This interacts badly with localisation. Published guidance puts German at roughly 30–50% longer than English for running text, and short UI strings — exactly what a headline or a CTA label is — expand much further, because a short English word often maps to a long German compound noun. A headline auto-shrunk to fit that has quietly become unreadable in the market it was translated for.

What it costs

Almost nothing, if it is decided early. Larger tap targets, a second distinguishing property on game pieces, text on a scrim, and restraint with full-screen motion are all free at design time and expensive as a retrofit. The one genuine trade-off is screen density: accessible sizing means fewer elements on screen, which most playables benefit from anyway.

One-handed reach, and what falls outside it

Most phones are used one-handed most of the time, and the reachable area for a thumb is not the screen — it is an arc sweeping up from the bottom corner on the holding side. The top corners are the hardest to reach on a large device, and the top corner opposite the holding hand is effectively out of range without changing grip.

For a playable that has two consequences. Interactive elements belong in the lower two-thirds wherever the mechanic allows it, and anything demanding precision — a small drag target, a tightly spaced grid — belongs in the comfortable centre rather than at an edge. Decorative and informational elements can sit anywhere; only the things a thumb must hit are constrained.

This interacts with the safe-area rules in a way that is easy to get wrong. The bottom edge is within easy reach but partly reserved for the system home indicator, so the sweet spot is the band just above it rather than the very bottom of the canvas.