LogoLogo
OS Docs HomeOS NGDOS APIsOS Download ProductsMore than MapsContact Us
  • More than Maps
  • Geographic Data Visualisation
    • Guide to cartography
      • Introduction to cartography
      • Types of maps
      • Symbology
      • Colour
      • Text on maps
      • Generalisation
      • Coordinate reference systems
      • Projections
      • Scale
      • Map legends
      • Map layout
      • Relief representation
      • North arrows
    • Guide to data visualisation
      • Introduction to data visualisation
      • GeoDataViz design principles
      • Types of visualisation
      • Thematic mapping techniques
      • Data visualisation critique
      • Accessible data visualisation
      • Ethical data visualisation
      • Software
      • Data
    • GeoDataViz assets
      • GeoDataViz basemaps
      • Stylesheets
      • GeoDataViz virtual gallery
      • Equal area cartograms
      • How did I make that?
        • Apollo 11 Landing
        • North York Moors National Park, 70 years
        • Snowdonia National Park, 70 years
        • Great Britain's National Parks
        • Great Britain's Islands
        • Great Britain's AONB's and National Scenic Areas
        • Famous shipwrecks of Pembrokeshire
        • Trig pillars today
        • Britain's most complex motorway junctions
      • #30DayMapChallenge
  • Data in Action
    • Examples
  • Demonstrators
    • 🆕Product Viewer
    • Addressing & location demonstrators
      • Address Portfolio overview
      • Which address product should you use?
      • AddressBase
      • AddressBase Core
      • AddressBase Plus
      • AddressBase Premium
      • Address Classifications
      • Addressing Lifecycle
      • OS Emergency Services Gazetteer
      • What are Vertical Streets?
      • Why are there differences in boundaries?
    • Contextual demonstrators
    • Customer best practice
      • Channel Shift
      • Data Management and OS Data Hub
      • End User Licence vs Contractor Licence
      • 🆕 IDs vs Spatial Relationships
      • Why we should capture good quality addresses at source
      • Why we Snap and Trace
    • Network Demonstrators
      • OS Detailed Path Network
      • OS Multi Modal Routing Network
        • OS Multi Modal Routing Network
      • Water Networks overview
      • OS MasterMap Highways Network and OS NGD Speeds
      • OS MasterMap® Highways Network and OS Open Roads™
    • OS MasterMap Generation APIs
      • Using the OS Features API
      • Using the OS Features API Archive
      • Using the OS Downloads API
      • Using OS APIs in ESRI Software
    • 🆕OS NGD (National Geographic Database)
      • OS NGD Address
      • OS NGD Boundaries
      • 🆕OS NGD Buildings
        • 🆕Building and Building Access Feature Types
        • Building Part and Building Line Feature Types
      • 🆕OS NGD Geographical Names
      • OS NGD Land
      • OS NGD Land Cover enhancements
      • 🆕OS NGD Land Use
      • OS NGD Land Use enhancements
      • 🆕OS NGD Structures
        • 🆕OS NGD Structures
        • Field Boundaries
      • 🆕OS NGD Transport Features
      • 🆕OS NGD Transport Network
      • OS NGD Transport RAMI
      • OS NGD Water Features
      • OS NGD Water Network
      • OS NGD API - Features
      • Ordering OS NGD data
      • Change only updates
      • OS NGD Versioning
      • Creating a topographic map from OS NGD Data
      • Analytical styling for OS NGD data
    • OS MasterMap® demonstrators
    • 🆕Product & API Comparisons
      • 🆕Comparison of Water Network Products
  • Tutorials
    • GeoDataViz
      • Thematic Mapping Techniques
      • Downloading and using data from the OS Data Hub
      • How to download and use OS stylesheets
      • How to use the OS Maps API
      • Creating a bespoke style in Maputnik
    • GIS
      • Analysing pavement widths
      • Basic routing with OS Open Data and QGIS
      • Walktime analysis using OS Multi-modal Routing Network and QGIS
      • Creating 3D Symbols for GIS Applications
      • Constructing a Single Line Address using a Geographic Address
      • Creating a Digital Terrain Model (DTM)
      • Visualising a road gradient using a Digital Terrain Model
      • Visualising a road gradient using OSMM Highways
    • 🆕APIs
      • 🆕Using OS APIs with EPC API
      • 🆕OS APIs and ArcGIS
  • Deep Dive
    • Introduction to address matching
    • Guide to routing for the Public Sector
      • Part 1: Guide to routing
      • Part 2: Routing software and data options
      • Part 3: Building a routable network
    • Unlocking the Power of Geospatial Data
    • Using Blender for Geospatial Projects
    • A Guide to Coordinate Systems in Great Britain
      • Myths about coordinate systems
      • The shape of the Earth
      • What is position?
        • Types of coordinates
        • We need a datum
        • Position summary
      • Modern GNSS coordinate systems
        • Realising WGS84 with a TRF
        • The WGS84 broadcast TRF
        • The International Terrestrial Reference Frame (ITRF)
        • The International GNSS Service (IGS)
        • European Terrestrial Reference System 1989 (ETRS89)
      • Ordnance Survey coordinate systems
        • ETRS89 realised through OS Net
        • National Grid and the OSGB36 TRF
        • Ordnance Datum Newlyn
        • The future of British mapping coordinate systems
        • The future of British mapping coordinate systems
      • From one coordinate system to another: geodetic transformations
        • What is a geodetic transformation?
        • Helmert datum transformations
        • National Grid Transformation OSTN15 (ETRS89–OSGB36)
        • National Geoid Model OSGM15 (ETRS89-Orthometric height)
        • ETRS89 to and from ITRS
        • Approximate WGS84 to OSGB36/ODN transformation
        • Transformation between OS Net v2001 and v2009 realisations
      • Transverse Mercator map projections
        • The National Grid reference convention
      • Datum, ellipsoid and projection information
      • Converting between 3D Cartesian and ellipsoidal latitude, longitude and height coordinates
      • Converting between grid eastings and northings and ellipsoidal latitude and longitude
      • Helmert transformation worked example
      • Further information
  • Code
    • Ordnance Survey APIs
    • Mapping
    • Routing with pgRouting
      • Getting started with OS MasterMap Highways and pgRouting
      • Getting started with OS MasterMap Highways Network - Paths and pgRouting
      • Getting started with OS NGD Transport Theme and pgRouting
      • Getting started with OS NGD Transport Path features and pgRouting
  • RESOURCES
    • 🆕Data Visualisation External Resources
Powered by GitBook

Website

  • Ordnance Survey

Data

  • OS Data Hub
On this page
  • Colour
  • Labelling and Descriptive Text
  • Access to software and cost implications
  • Other accessibility considerations
  • Bringing it all together…

Was this helpful?

  1. Geographic Data Visualisation
  2. Guide to data visualisation

Accessible data visualisation

PreviousData visualisation critiqueNextEthical data visualisation

Last updated 1 year ago

Was this helpful?

Data visualisation is a powerful way to spot patterns and trends in data, tell stories with data and turn raw data into actionable insight. However, to maximise the benefits of data visualisation we need to ensure that it is accessible to our intended audience. After spending significant amounts of time cleaning, prepping, analysing and visualising a dataset, you want it to be seen and understood by as many people as possible.

Accessibility can range from ensuring that audiences have access to the right software to view the visualisation to ensuring our maps and visualisations are optimised for those with colour vision deficiency. As cartographers and data visualisation designers, we need to think carefully about accessibility and remove as many barriers as possible. This is a key part of the design process and often requires thought before you even start to make your map or data visualisation.

Although there aren’t specific regulations for creating accessible data visualisations, a good place to start for general advice and principles relating to accessibility are the .

Colour

Colour has a big impact on accessibility, particularly with regard to those who have a form of Colour Vision Deficiency (often known as colour blindness). Almost 10% of the population in the UK have some form of CVD, so it’s an important consideration. We discuss the types of CVD and implications for design and how this can be addressed fully in our section on .

One simple way of increasing accessibility for those with CVD is to use patterns or symbols in addition to colour to help distinguish between features. Don’t rely on a colour difference alone to distinguish between feature or prompt a response or action. This could simply be adding a tree fill to woodland areas and a marsh symbol to marshland.

Another way to make your data visualisation accessible, related to colour, is ensuring sufficient contrast between features and also between symbols/text and the background. It is this contrast which makes your visualisation legible and understandable. The WCAG recommend a minimum contrast ratio of 4.5:1.

Labelling and Descriptive Text

Adding labels to your data visualisation is a great way to improve accessibility. Not only does it reduce the reliance on visually perceiving differences in colour but can also add much needed explanation to those who are not familiar with the subject you are visualising.

When adding labels, it’s also important to think about their legibility in terms of contrast with the background, size and placement. We discuss the function of labels and how to make them legible in significant depth in our section on .

For both printed and online content, a title and short description of the take-away message of your data visualisation can often help those who have CVD, other visual impairments or are neurodiverse to understand your visualisation. If designing for an online audience, you might want to consider providing some alternative text alongside your visualisation to help those who use screen readers to understand the message of your visualisation.

Access to software and cost implications

To ensure our data visualisations are as accessible to the target audience as they can be, it’s worth thinking carefully about the software that you create it in and format you then publish it in. Do people need a specific piece of software or a specific licence or account to view your data visualisation? If they do, is there a cost implication? Could you produce your data visualisation in a different way to remove these barriers?

Other accessibility considerations

Bringing it all together…

Although colour and the use of labelling are great for those who suffer with CVD, there are many other accessibility considerations, such as those who are neurodiverse or have physical disabilities. For example, some major mapping platforms have developed maps which can be used by those who struggle to make precise mouse clicks. They allow users to click in a vague area and then use a screen reader or keyboard shortcuts to select the feature they want. To cater better for those who are neurodiverse, try to keep your data visualisation and remove any unnecessary information. A further consideration for accessibility is the technical literacy of the audience and level of knowledge and understanding on the topic you’re visualising.

Another nice example of increasing accessibility is the work done by Ordnance Survey in collaboration with British Cycling in Birmingham. In early 2023, British Cycling published a set of cycle routes on OS Maps aimed at encouraging people from disadvantaged backgrounds to get out on their bikes and explore the green spaces around Birmingham – improving physical and mental wellbeing. However, not everyone has access to a smartphone and not everyone can afford an OS Maps subscription. So, to increase accessibility, specially designed printed maps have been created which can either be downloaded and printed at home or picked up for free at specific sites around the city. These maps do not need a specific software to view them, they do not need a subscription and have a simple playful design, aimed at novice map users. They also use a CVD friendly colour pallet! You can view and download the maps .

Web Content Accessibility Guidelines (WCAG)
colour
text
simple
here