Colquhoun.AI
← All guides

Research Guides

Measure the Clickable Control, Not Just Its Icon

· Colquhoun.shop editorial

A small icon can sit inside a generous button, while a large-looking label can have a surprisingly small clickable area. A research toolbar review should measure what a pointer can activate, not just what the designer drew.

This is a manual review worksheet for an authorized interface or prototype. It does not describe measured Colquhoun.shop controls or establish overall accessibility conformance.

1. Start with controls where a miss matters

List the actions a reader uses to inspect evidence: opening a source, expanding a result, changing a filter and downloading a file. Include neighboring actions that could be activated by mistake. Record the page, control label and expected outcome.

Use a safe test environment for actions that change data or contact someone. Do not test a destructive control on a real research record just to find its clickable boundary. A non-destructive fixture can expose a targeting problem without creating a second problem.

2. Inspect the actual activation area

Compare the visible icon or text with its containing interactive element and the area that responds to input. Padding may enlarge the target; empty space beside an element does not necessarily do so. Check the delivered interface rather than relying only on a design file.

W3C's Target Size (Minimum) guidance specifies a 24-by-24 CSS-pixel minimum for pointer targets, with exceptions covering spacing, equivalent controls, inline text, unmodified browser controls and essential presentation. The spacing exception uses a defined circle-based test, not a general claim that a control looks far enough from its neighbors. W3C: Understanding Target Size (Minimum)

Record measurements in CSS pixels. Do not estimate them from a screenshot's physical pixels without understanding its scale. When relying on an exception, identify the applicable condition and evidence instead of treating every small target as either automatically acceptable or automatically failing.

3. Separate the artwork from the button

In an invented toolbar, an 18-pixel download symbol sits inside a rectangular 36-by-36 CSS-pixel button whose whole area activates the download. The symbol's size alone does not describe the target. In another version, only the symbol is clickable even though a decorative background looks larger.

Those versions need different findings. The first review should verify the actual button area and surrounding layout. The second should identify the mismatch between the apparent control and its behavior before proposing a fix.

4. Check every relevant layout and open state

A toolbar may wrap into two rows on a narrow screen. Review neighbors above and below as well as those to the left and right. Open menus and expanded panels can introduce controls that were absent from the initial view.

After enlarging a target, check that it does not cover another action or capture a click intended for adjacent content. Retest the label, focus behavior and expected result. Increasing size should not make the interface less predictable.

A comfortable pointer test is useful evidence, but it does not replace keyboard or assistive-technology testing. Likewise, a size measurement does not establish that the control has a meaningful name or performs the right action.

5. Save a target-to-action record

Close the review with measured findings rather than “icons made accessible.” The useful outcome is a control whose apparent purpose and actual activation area agree, with the limits of testing clearly recorded.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.