Touch Target Checker.

Test Mobile Accessibility. Analyze touch target sizes for WCAG 2.5.5 (AAA - 44×44px) and 2.5.8 (AA - 24×24px) compliance. Test buttons, links, and interactive elements to ensure they're large enough for users with motor disabilities. Get precise measurements, compliance badges, and actionable recommendations.

Loading...

Use cases

Real-world uses.

Mobile App Developers
Ensure all touch targets meet accessibility requirements for iOS, Android, and responsive web applications.
Web Developers & Designers
Verify button sizes, link targets, and interactive elements are large enough for easy touch interaction.
Accessibility Auditors
Test WCAG 2.5.5 and 2.5.8 compliance, document touch target sizes, and identify accessibility issues.
QA & Testing Teams
Add touch target testing to your quality assurance checklist and catch issues before production.
Product Managers
Ensure inclusive design that works for users with motor disabilities and on all device types.
UX Researchers
Study tap accuracy, identify usability issues, and optimize touch target sizes for better user experience.

How it works

Six steps.

  1. 01

    Click 'Analyze Current Page' to scan all interactive elements on the page for touch target sizes

  2. 02

    Review the list showing each element's dimensions with color-coded compliance status

  3. 03

    Check the badges: Green (AAA compliant), Yellow (AA compliant), Red (too small)

  4. 04

    Identify elements that fail WCAG requirements and review the specific fix recommendations

  5. 05

    Use the custom size tester to experiment with different dimensions and see compliance levels

  6. 06

    Download the detailed report for documentation or sharing with your development team

Features

Complete Touch Target Testing Features.

Analyze touch target sizes, verify WCAG compliance, test custom dimensions, and ensure mobile accessibility for all users including those with motor disabilities.
  • Real-Time Analysis

    Scan current page and analyze all interactive elements for touch target size compliance

  • Precise Measurements

    Get exact width and height measurements in pixels for every touch target on the page

  • WCAG Compliance Badges

    Instant visual feedback showing AAA (44×44px), AA (24×24px), or Fail status for each target

  • Mobile-First Testing

    Ensure touch targets meet mobile accessibility standards for finger-friendly interactions

  • Issue Detection

    Automatically identify targets that are too small and get specific recommendations to fix them

  • Detailed Reports

    Export comprehensive JSON reports with all touch target measurements and compliance status

  • Custom Size Tester

    Test any custom dimensions to see if they meet WCAG requirements before implementation

  • Multiple WCAG Levels

    Check compliance against both WCAG 2.5.5 (AAA - 44×44px) and 2.5.8 (AA - 24×24px)

FAQ

Questions.

Can't find an answer? Send us your question.

What is the minimum touch target size for accessibility?

WCAG defines two levels for touch target sizes: WCAG 2.5.5 (Level AAA): Touch targets should be at least 44×44 CSS pixels WCAG 2.5.8 (Level AA): Touch targets should be at least 24×24 CSS pixels Industry standards: Apple iOS: Recommends minimum 44×44 points Android Material Design: Recommends minimum 48×48 density-independent pixels Microsoft: Recommends minimum 44×44 epx For best accessibility, aim for 44×44px or larger, especially for primary actions.

What counts as a touch target?

Touch targets include any interactive element that users can tap or click: Links (<a> tags) Buttons (<button> elements) Form inputs (text fields, checkboxes, radio buttons) Dropdowns (<select> elements) Custom interactive elements with click handlers Icon buttons and action buttons Toggles and switches Pagination controls Social media share buttons Note: The entire clickable area matters, not just the visible icon or text. Padding counts!

How do I make small elements meet the size requirement?

Several techniques to increase touch target size: Add padding: Easiest solution - padding: 12px makes any element bigger Set minimum dimensions: min-width: 44px; min-height: 44px; Expand hit area with pseudo-elements: ::before { content: ''; position: absolute; top: -12px; right: -12px; bottom: -12px; left: -12px; } Increase font size: Larger text = larger default size Use flexbox centering: Centers small icons in larger containers Add spacing between targets: Prevents accidental clicks For icon-only buttons, make the button itself 44×44px even if the icon is 20×20px.

Do touch targets need spacing between them?

Yes! WCAG 2.5.8 (Level AA) requires that targets either: Are at least 24×24 CSS pixels in size, OR Have sufficient spacing so the target can fit within a 24×24px circle without overlapping another target's circle Best practice: Maintain at least 8px spacing between interactive elements to prevent accidental activation. Why spacing matters: Reduces mis-taps and user frustration Helps users with motor disabilities Improves usability on small screens Better experience for users with large fingers Prevents accidental activations while scrolling

Are there exceptions to the size requirements?

Yes, WCAG allows some exceptions: Inline links: Links within sentences don't need to meet the size requirement User agent controls: Browser-provided controls (like video player controls) Essential targets: When a specific size is essential to the information being conveyed However: Just because something is exempt doesn't mean you shouldn't make it accessible! Consider these guidelines: Make inline links at least 24×24px if possible Provide adequate spacing around inline links Use larger text for better default size Test on actual mobile devices

How do I test touch targets on mobile devices?

Testing strategies for mobile touch targets: This tool: Analyze on desktop but check pixel measurements Browser DevTools: Use device emulation mode and toggle device toolbar Real devices: Test on actual phones and tablets (best method) Remote testing: Use BrowserStack or similar for cross-device testing Accessibility scanner: Use mobile accessibility scanners (Android, iOS) Quick test: Can you tap the target accurately with your thumb? If not, it's probably too small. Remember: CSS pixels ≠ physical pixels. A 44×44 CSS pixel target may be larger or smaller on different devices depending on pixel density.

Related tools

More Accessibility tools.