ERROR: The request could not be satisfied

When viewed on small screens (like mobile phones) content should be large enough to 
read without being zoomed-into and scrolled in two dimensions.

WCAG 2.1 specifically requires this for:

+ Vertical scrolling content at a width equivalent to 320 CSS pixels
+ Horizontal scrolling content at a height equivalent to 256 CSS pixels

This issue almost always indicates that the webpage has not been designed
to work on mobile devices at all.

	Title / URL	Issues
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/recycling-and-rubbish	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/housing/getting-involved-your-housing-service	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/news?page=0	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/news?page=7	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/jobs/schools-recruitment-including-nqts	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/news?f%5B0%5D=news_block_date%3A2025	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/news?f%5B0%5D=news_block_date%3A2014	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/holiday-activities-and-food-programme	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/crime/cctv	1
	ERROR: The request could not be satisfiedwww.lbhf.gov.uk/housing/housing-improvement-programme	1

Ensure pages don't require zooming and 2D scrolling on small screens

London Borough of Hammersmith & Fulham Council

Where this issue has occurred