WebsiteDesignOutsource.com research

Target Size Accessibility Evidence for Website Design Review

A scoped review of WCAG target-size criteria and what outsourced teams should record during interface acceptance.

Target Size Accessibility Evidence for Website Design Review editorial illustration

**Published: September 4, 2026**

Small links and tightly packed controls can be difficult to activate, yet a screenshot rarely captures the clickable area or spacing exceptions. This WebsiteDesignOutsource.com review examines W3C sources for target-size acceptance. Sources were reviewed on September 4, 2026.

Research question

What evidence should an outsourced design team provide when reviewing pointer target size under WCAG 2.2?

Evidence synthesis

WCAG 2.2 includes Target Size (Minimum) at Level AA and Target Size (Enhanced) at Level AAA, with different thresholds and exceptions. W3C understanding documents explain intent, exceptions, spacing, and examples. Conformance depends on the normative success-criterion wording, not a generalized claim that every visible icon must share one dimension.

Reviewers need the rendered activation area, spacing to nearby targets, applicable exception, input method, zoom, and viewport. Inline links, equivalent controls, user-agent-controlled targets, and legally essential presentations require careful criterion-specific interpretation.

Practical interpretation

Inference: a component inventory with measured interactive bounds and exception notes produces more reviewable evidence than visual estimates from design files alone.

Verification approach

  • Inventory interactive controls on representative templates and states.
  • Measure the operable target, not only the visible glyph.
  • Record spacing calculations when used to meet the minimum criterion.
  • Check repeated controls at narrow widths and enlarged content.
  • Route uncertain exceptions to a qualified accessibility reviewer.
  • Evidence scope and limitations

    This note summarizes W3C material and does not provide legal advice or certify conformance. Target size is one accessibility concern; keyboard operation, names, focus visibility, contrast, semantics, and gesture alternatives require their own checks.

    Key takeaways

  • Use the exact WCAG version, level, and criterion wording.
  • Measure rendered targets in relevant states.
  • Document exceptions rather than assuming them.
  • Do not treat target size as a complete accessibility review.
  • Sources

    1. WCAG 2.2 Recommendation Normative accessibility requirements.

    2. Understanding SC 2.5.8: Target Size (Minimum) Intent, exceptions, and examples for Level AA.

    3. Understanding SC 2.5.5: Target Size (Enhanced) Intent and examples for Level AAA.

    4. WAI: WCAG 2 overview W3C context for WCAG versions and supporting materials.

    Related research

    Focus obscuration in sticky interfaces

    Link name accessibility research

    Ready to plan your next step?

    Contact WebsiteDesignOutsource.com

    Philippines staffing

    Build a clearer work lane.

    Share the role, tools, schedule, and approval needs. We will use those details to shape a practical Philippines staffing request.

    Contact Us