Why does the warning ‘Touch target is too small’ sometimes result in unclear error messages?

In certain cases, server-side scanning may produce different results for this specific test step. This is due to technical factors such as dynamic loading, responsive layouts or the specific position in the DOM, which can influence the result.

An important aspect here is the Viewport:

The display size of elements may vary depending on the size of the viewport. By default, Eye-Able Report checks pages in a viewport of 1920×1080 pixels. If the size of an element in this viewport is below the minimum values specified in the WCAG, the warning ‘Touch target is too small’ is issued.

In practice, this may lead to queries because the error appears in the report but cannot be reproduced during a manual audit check. This is often because a larger screen or a different viewport is used during manual testing, which displays the element larger than during testing with 1920×1080.

For this reason, this test step is deliberately marked as a warning in the scan and has a very minor impact on the overall rating.

If the error cannot be reproduced even with the adjusted viewport size (1920×1080), this is usually due to technical factors such as dynamic loading, responsive layouts or the specific position in the DOM, which can influence the result. The scroll position does not usually have a direct impact on the rating – unless it changes the display of the elements through layout changes or dynamic reloading.

How to deal with false positive reports:

In Eye-Able Audit, you can use the ‘Hide’ function to hide individual notes if they do not apply after review. Instructions on how to do this can be found in the corresponding help centre article.