1. Home
  2. Accessibility statement

Accessibility Statement for DevTracker

This website is run by the Foreign, Commonwealth and Development Office (FCDO). We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 500% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We've also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

  • aid activity information and descriptions may not be written in a way that is easy to read
  • documents attached to aid activities may not be accessible to screen reader software
  • some graphics showing aid activity data do not have alternate text or captions
  • some of our pages may be difficult to navigate without a mouse
  • interactive maps on aid activity pages may not be accessible to screen reader software, or navigable without a mouse
  • some tables may not be fully navigable without a mouse

What to do if you cannot access parts of this website

You can email website-team@fcdo.gov.uk if you need information on this website in a different format like:

  • accessible PDF
  • large print
  • easy read
  • audio recording
  • braille

We'll consider your request and get back to you in 5 days.

Reporting accessibility problems with this website

We're always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we're not meeting accessibility requirements, contact: website-team@fcdo.gov.uk.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations'). If you're not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website's accessibility

FCDO is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Some images, and the maps available on activity pages, do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

We plan to add text alternatives for all images by September 2020. When we publish new content, we'll make sure our use of images meets accessibility standards.

Disproportionate burden

Navigation and accessing information

There's no way to skip the repeated content in the page header (for example, a ‘skip to main content' option). This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

There's no way to skip the repeated content in the page header (for example, a ‘skip to main content' option). This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

It's not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content. This fails WCAG 2.1 success criterion 1.3.4 (orientation).

Interactive tools and transactions

Our maps are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label' tag.

Our maps are built and hosted through third party software and ‘skinned' to look like our website. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships).

We've assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment in late 2020.

Content that's not within the scope of the accessibility regulations

PDFs and other documents

Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they're accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they're not essential to providing our services. For example, we do not plan to fix Programme documents.

How we tested this website

This website was last tested on8 November 2019. The test was carried out by FCDO (The Department for International Development, at the time).

We tested every page type on DevTracker using WAVE.

What we're doing to improve accessibility

We are currently working to continue to improve DevTrackers accessibility. In particular we are looking to engage our users more, to understand what remaining accessibility issues are affecting them most, so we can better prioritise.

This statement was prepared on 11 November 2019. It was last updated on 11 August 2020.