Skip to content
SilktideHelp

Interactive component distance

Silktide measures the size and spacing of buttons, links, and form controls on your pages. Small controls packed closely together are easy to press by mistake, so each one should either be at least 24 by 24 pixels or have enough clear space around it.

Why this matters

Anyone can miss a small button, but for people with tremors, arthritis, or limited fine motor control, tightly packed controls make a page genuinely hard to use - tapping the wrong link, submitting the wrong form, or giving up entirely. The problem is worst on touch screens, where a fingertip is far less precise than a mouse pointer.

This is success criterion 2.5.8 (Target Size Minimum), a requirement in WCAG 2.2, so it is part of the conformance target most organizations aim for.

How to fix it

  1. Make each interactive element at least 24 by 24 pixels. Setting min-width and min-height, or adding padding, is usually enough.
  2. Alternatively, add space between controls. Picture a circle 24 pixels across centered on each small control: it must not overlap any other control, or the circle around another small control. Smaller targets are acceptable when nothing else is that close.
  3. Pay particular attention to icon buttons, pagination links, and social media icons, which are commonly undersized and tightly grouped.
/* Problem: 16px icon buttons touching each other */
.toolbar button {
  width: 16px;
  height: 16px;
}

/* Fix: enlarge the clickable area to at least 24x24 */
.toolbar button {
  min-width: 24px;
  min-height: 24px;
}

How Silktide tests this

  1. Test both the mobile and desktop versions of every page; results may differ between the two.
  2. Find the interactive elements: links, buttons, form fields, and image map areas.
  3. Ignore elements that are not normally visible, such as content positioned off screen for , and any elements you have excluded from checking.
  4. Pass any element at least 24 pixels wide and 24 pixels tall.
  5. Ignore controls that sit inside a sentence or block of text, which WCAG exempts from this rule.
  6. For each remaining small element, draw a circle 24 pixels across centered on it, as WCAG describes.
  7. Report the element if its circle overlaps another control, or the circle around another small control, unless both are links to the same destination. Positions are measured to the nearest 0.1 pixel, so overlaps of 0.2 pixels or less are not reported. Elements pinned to the screen, such as sticky headers, are compared with other pinned elements rather than with the content that scrolls underneath them.

Troubleshooting

A small control passed the check

Size alone is not a failure: a small control passes when it has enough clear space around it, sits inline in text, or only neighbors links pointing to the same place. This mirrors the exceptions WCAG itself allows.

The controls have room on my phone

The mobile test uses a phone 320 pixels wide, the narrowest width WCAG expects a page to work at (see Why does Silktide test with an iPhone 5?). Controls placed over a picture or a map, such as markers on a floor plan, usually move closer together as the page narrows. They can collide at 320 pixels and have room to spare on a wider phone.

The position of the control matters

WCAG exempts a control whose size and position are essential to what it shows, such as pins on a map, and a control whose action is also offered by another control on the same page that is large enough. Silktide cannot judge either automatically. If one applies, record a on the finding.

Only some failures are listed

Silktide reports up to the 10 most severe examples per page. Fixing a shared style usually resolves many findings at once.

I want the stricter standard

This check tests the Level AA minimum of 24 by 24 pixels. The related Large enough controls check tests the stricter Level AAA recommendation of 44 by 44 pixels.

Learn more

Last updated

Was this page helpful?