Black History Month - Cambridge City Council

Planning applications - Cambridge City Council

Privacy notice - Cambridge City Council

Check for constraints on development - Cambridge City Council

Cookies - Cambridge City Council

Volunteering - Cambridge City Council

Grants and funding - Cambridge City Council

Local Plan 2018 - Cambridge City Council

Terms of use - Cambridge City Council

Development plan for Cambridge - Cambridge City Council

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

December 2025

November 2025

Cambridge City Council

	Title / URL	Issues
	Black History Month - Cambridge City Councilwww.cambridge.gov.uk/black-history-month	3
	Planning applications - Cambridge City Councilwww.cambridge.gov.uk/planning-applications	2
	Privacy notice - Cambridge City Councilwww.cambridge.gov.uk/privacy-notice	2
	Check for constraints on development - Cambridge City Councilwww.cambridge.gov.uk/check-for-constraints-on-development	2
	Cookies - Cambridge City Councilwww.cambridge.gov.uk/cookies	2
	Volunteering - Cambridge City Councilwww.cambridge.gov.uk/volunteering	2
	Grants and funding - Cambridge City Councilwww.cambridge.gov.uk/grants-and-funding	2
	Local Plan 2018 - Cambridge City Councilwww.cambridge.gov.uk/local-plan-2018	2
	Terms of use - Cambridge City Councilwww.cambridge.gov.uk/terms-of-use	2
	Development plan for Cambridge - Cambridge City Councilwww.cambridge.gov.uk/development-plan-for-cambridge	2

Ensure interactive components are far enough apart

Cambridge City Council

Where this issue has occurred