ERROR: The request could not be satisfied

UKHO announces the release of the Seabed Mapping Service

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.admiralty.co.uk/about-us/our-people	1
ERROR: The request could not be satisfiedwww.admiralty.co.uk/ukho/careers/apprenticeships	1
ERROR: The request could not be satisfiedwww.admiralty.co.uk/charts/planning-charts/maritime-security-charts	1
ERROR: The request could not be satisfiedwww.admiralty.co.uk/terms-and-conditions	1
ERROR: The request could not be satisfiedwww.admiralty.co.uk/charts/digital-charts/admiralty-raster-chart-service	1
ERROR: The request could not be satisfiedwww.admiralty.co.uk/news/supporting-precision-navigation-milford-haven	1
ERROR: The request could not be satisfiedwww.admiralty.co.uk/decarbonisation	1
ERROR: The request could not be satisfiedwww.admiralty.co.uk/access-data/marine-data	1
UKHO announces the release of the Seabed Mapping Servicewww.admiralty.co.uk/news/ukho-announces-release-seabed-mapping-service	1
ERROR: The request could not be satisfiedwww.admiralty.co.uk/access-data/tidal-data	1

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

Admiralty

Where this issue has occurred