Mobile audit

The header call-to-action button (168×26 px) is present on 6 of the 7 checked pages. On one landing page there are seven CTA buttons of the same class, 26–35 px tall. The header of the home page also holds “Log in” (61×26) and “Sign up” (69×26) with a 6 px gap between them.

At 26–35 px of height, the mandatory AA minimum (24 px) is met, but the 44 px platform norm is missed by 9–18 px. Every one of these elements is on the product’s primary conversion path, and their generous width makes the vertical shortfall easy to overlook in a mockup.

We have no direct data on the conversion impact — that is a question for the owner’s analytics; what we record is an elevated risk of missed taps, not a measured effect.

aria-expanded, aria-haspopup and aria-controls are set on an svg element with no corresponding role — a decorative icon rather than the controlling button. 72 nodes on 6 of 7 pages, with the pricing page (47 nodes) and the changelog (21) affected most.

Consequence: the expanded/collapsed state and the connection to the dropdown are not communicated to assistive technology — a screen-reader user does not learn whether the menu opened after pressing.

Three buttons on two pages — one on the home page, two on the AI features page — have neither text nor aria-label: icon only. A screen reader announces them as just “button”.

Adjacent control pairs with gaps under 8 px are spread across the key pages: an editor button pair on the home page sits 1 px apart, plan switchers on the pricing page are 2 px apart, mode and action switchers in the free tool 2–6 px, and header buttons 5–6 px. Plan and mode switchers are exactly what a finger hits most often; at a 2 px gap, a miss means switching to the wrong plan.

A note on the standard, stated precisely: the Spacing exception of WCAG 2.5.8 applies only to targets smaller than 24×24 px, and what it requires is that a 24 px circle centred on the target not intersect its neighbours. Practically every pair in this list is 24×24 or larger, so these controls pass 2.5.8 by size regardless of the gap. This finding records a touch-ergonomics problem, not a standards violation.

Measurement limits, disclosed: the detector records at most one pair per element, drops touching targets and caps at 20 records — “all pairs” here means “all found”, not an exhaustive list.

Buttons and input fields under 44 px concentrate on the pages that matter: 32 on the home page (social sign-in buttons at 97×36), all 20 buttons of the changelog page (135×32 — there are no other buttons on it), 18 on the AI features page, 17 on pricing, 10 in the free tool. The pricing “get started” buttons are 323 px wide at 32 px tall — they look large while falling short vertically.

The smallest controls on the site are two tool buttons at 42×16 and 48×16 on the AI features page, plus an unnamed 17×14 button on the home page. Formally they do not break the AA minimum: distance measurement (see M-6) shows enough free space around them for the criterion’s exception to apply. But 14–16 px of height is a third of the platform norm, and tapping them stays a lottery regardless of formal compliance.

In a list of tools on one landing page, two adjacent 17 px-tall links sit so close that a 24 px circle centred on the first one touches the second one’s box. This is the only spot on the site where criterion 2.5.8 fails both by size and through the distance exception.

How this was verified — and why the other small targets are not violations. Across the seven pages there are 319 controls smaller than 24×24 px: menu and footer items around 20 px tall, tool buttons, list links. That alone does not violate the criterion: WCAG 2.5.8 accepts sufficient spacing as an alternative to size. A direct measurement pass, run specifically for this question, checked every one of the 319 targets: 318 pass through the spacing exception, one does not.

A mechanical count of “319 AA violations” would be wrong in 318 cases out of 319 — this is exactly the class of error our false-positive triage exists for.

On the home and pricing pages axe reports scrollable-region-focusable: a horizontally scrollable section does not receive focus. In a mobile browser with a connected keyboard — or on a tablet with a keyboard case — the content of that area is unreachable.

color-contrast (serious): 115 nodes on 6 of 7 pages. On mobile this bites harder than on desktop — the screen is far more often used in bright outdoor light.

Elements with 11–11.5 px font size: four on the AI features page (interface examples at 11 px), one each on the home and pricing pages (11.5 px).