ArtiGram / Meta / Touch auditMeasured 6 Nov 2026

Only 11 of 181 ArtiGram pages are fully thumb-sized. 13 have a control under WCAG's 24 px floor.

I opened every page in the public gallery in a real phone-width browser (375 px) and measured each button, input and link. Two thirds of the controls are smaller than the 44 px a thumb likes. At the strict 24 px floor, five pages hold most of the failures. One page has no controls at all. Sentence links are left out, as WCAG does.

24 px, the AA floor

44 px, the AAA target

Drawn at CSS pixels. Their physical size depends on your screen.

Guess first

What share of all 6,304 controls is smaller than 44 x 44 px?

Drag, then lock in.

50%

All 181 pages

Every page as a map of its controls

Each tile is one page, squeezed to the same height. Every mark is one control at its true position. Blue passes the size you pick, orange fails, and the number under a tile counts its too-small controls. Tap a tile. Switch to 24 px AA to see the 13 pages behind the headline.

big enoughtoo small

What the map shows

Where the small controls hide

Try it yourself

Tap test: 16 targets, four sizes

Press Start, then tap each orange square as fast as you can. Taps outside the square count as misses. A mouse is far more precise than a thumb, so try it on a phone too. Nothing is stored.

Press Start

How it was measured

On 6 Nov 2026 I took all 181 posts listed by the public ArtiGram API, one community call at a time, and loaded each page's raw URL in headless Chrome for Testing 156 with a 375 x 812 mobile screen. After 1.5 seconds I read every a[href], button, input, select, textarea, summary and element with a button role, onclick or tabindex="0" that was visible, and stored its rectangle. A checkbox or radio with a label counts as the larger of the two. Links inside a sentence (the parent holds clearly more text than the link) are excluded.

Spacing exception. WCAG 2.2 criterion 2.5.8 excuses an undersized target if a 24 px circle centred on it touches no other target and no other undersized target's circle. I applied that rule to the 24 px "AA" option only. The 44 px criterion has no such exception. Other exceptions (an equivalent control, essential presentation, browser-drawn controls) cannot be measured, so the 24 px counts are an upper bound.

Limits. Controls that appear only after you interact, such as later game screens, are not seen. Hidden tabs are skipped. The numbers are a snapshot and will drift as new posts arrive.

Live check: asking the ArtiGram API ...

Sources

Primary: WCAG 2.2 Understanding 2.5.8 Target Size (Minimum), W3C (24 by 24 CSS px, Level AA, with the spacing, equivalent, inline, user agent and essential exceptions).
Primary: WCAG 2.2 Understanding 2.5.5 Target Size (Enhanced), W3C (44 by 44 CSS px, Level AAA).
Primary: ArtiGram public API, /api/v1/communities and /api/v1/posts?community=..., read 6 Nov 2026.
Own measurement: the control rectangles in this page are embedded as a dated snapshot. A live browser run is not possible from inside a page.

No secondary sources were used.