404 Page | Verisk

Catastrophe Claims Data | Verisk

Anti-Fraud Claims Solutions | Verisk

Contact Verisk | Verisk

Reinsurance Software Solutions | Verisk

Fast, Precise Insurance Claims Estimation & Valuation | Verisk

Specialty Markets | Verisk

Underwriting and Risk Rating Solutions | Verisk

Leading source of information about insurance risk

Optimize Claims Analytics and Decision Support | Verisk

All interactive components on a page, such as buttons or menus, should be far enough apart 
from other interactive areas, to avoid them being used by mistake. 

This ensures people with motor impairments can easily click or tap on the right element.

## How to fix

* Ensure all interactive elements are at least 24 CSS pixels wide and tall
* OR ensure there is at least 24 CSS pixels (minus the width and height of the element)
  between each interactive element

## Methodology

This check is run on both the mobile and desktop versions of every page. Results
for each may differ.

1. All interactive elements are identified, including buttons, links, and form controls.
2. If an element is not normally visible, it is ignored. This includes elements which
   are positioned offscreen or cropped (e.g. for 'screen-reader only' text).
3. If an element is larger than 24 CSS pixels in both dimensions, it passes.
4. Otherwise, the element is compared to all other elements on the page.
5. The minimum horizontal gap between the element is calculated as 24 CSS pixels,  
   minus the width of the element.
6. The minimum vertical gap between the element is calculated as 24 CSS pixels,  
   minus the height of the element.
7. If another element falls within the minimum horizontal or vertical gap, the 
   element fails, unless both are links that point to the same place.

## Further reading

* [Target Size (Minimum)](https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html)
* [Technique C42 - Using min-height and min-width to ensure sufficient target spacing](https://www.w3.org/WAI/WCAG22/Techniques/css/C42)

ensure-minimum-target-size

February 2026

January 2026

Verisk Analytics

	Title / URL	Issues
	404 Page \| Veriskwww.verisk.com/invented-url-for-404-page	16
	Catastrophe Claims Data \| Veriskwww.verisk.com/solutions/claims/investigation/catastrophe-claims-data/	16
	Anti-Fraud Claims Solutions \| Veriskwww.verisk.com/solutions/claims/anti-fraud/	16
	Contact Verisk \| Veriskwww.verisk.com/company/contact/	16
	Reinsurance Software Solutions \| Veriskwww.verisk.com/insurance/reinsurance/	16
	Fast, Precise Insurance Claims Estimation & Valuation \| Veriskwww.verisk.com/solutions/claims/estimation-valuation/	16
	Specialty Markets \| Veriskwww.verisk.com/insurance/specialty-markets/	16
	Underwriting and Risk Rating Solutions \| Veriskwww.verisk.com/solutions/underwriting-rating/	16
	Leading source of information about insurance riskwww.verisk.com/	16
	Optimize Claims Analytics and Decision Support \| Veriskwww.verisk.com/solutions/claims/investigation/decision-support-analytics/	16

Ensure interactive components are far enough apart

Verisk Analytics

Where this issue has occurred