Accessibility notice

The FCDO digital and Chevening teams are committed to making sure our online services are accessible to all users and comply with level AA of the Web Content Accessibility Guidelines – WCAG 2.1, in line with The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

In order to help us achieve and maintain our objective we commissioned The Digital Accessibility Centre (DAC) to carry out WCAG 2.1 AA level technical compliance audits, that also included extensive testing by users with a wide range of disabilities.

Chevening website

This accessibility statement applies to https://www.chevening.org/website.

This website is run by the Chevening Secretariat on behalf of the Foreign, Commonwealth and Development Office. 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 200% without the text spilling off the screen
  • view the browser in a one column format (1280px browser width and Zoom in to 400%)
  • 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.

Accessibility

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

  • Non-descriptive alt text has been used on some images.
  • Form fields have been used that are not labelled.
  • Form labels are not always descriptive.
  • Form elements have been customised and are not accessible.
  • Headings have not been used to introduce content.
  • The order in which headings are presented is not hierarchical and logical.
  • Content is added to the page after a search has been performed but does not inform people that use a screen reader.
  • The contrast of non-text content did not meet the expected ratio of 1.3:1 where borders on form fields were used.
  • There are no skip links on the pages throughout the service.
  • There are some skip links that should let people skip between different areas of the page. These are not functioning as they should.
  • The focus order of interactive elements is not logical.
  • iFrames do not have titles.
  • Links are not always descriptive of their intended purpose or destination.
  • Links that open in a new window do not inform users that this will happen.

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please email: [email protected]

We’ll consider your request and get back to you in 3 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 our communications team at: [email protected]

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

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

Compliance status

Currently, the website does not meet all requirements of the WCAG 2.1 AA standard, and is therefore not yet compliant.

Non-accessible content

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

Non-compliance with the accessibility regulations

Images

Non-descriptive alt text has been used on some images so people using a screen reader cannot understand the purpose of the image. This fails WCAG 2.1 success criterion 1.1.1 Non-text Content (Level A).

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

Forms

Form fields have been used that are not labelled so screen reader users may find it difficult to determine its purpose when browsing both in and out of context. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships (Level A) and 4.1.2 Name, Role, Value (Level A).

We plan to make sure that all form fields are labelled and done so descriptively by December 2020. When we publish new content, we will make sure our use of form elements meets accessibility standards.

Form labels are not always descriptive. This means that it is difficult for people to understand the purpose of the form field or button. This fails WCAG 2.1 success criterion 2.4.6 Headings and Labels (Level AA).

We plan to make sure that all form fields are sufficiently clear and descriptive by December 2020. When we publish new content, we will make sure our use of form elements meets accessibility standards.

Form elements have been customised and are not accessible. This means that people that use assistive technologies are unable to use them. This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value (Level A).

We plan to make sure that all form fields are accessible by December 2020. When we publish new content, we will make sure our use of form elements meets accessibility standards.

Structure

Headings have not been used to introduce content. This means that people using a screen reader may not be able to determine the layout of the page and quickly navigate to different sections. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships (Level A).

We plan to include headings to all sections of all pages by December 2020. When we publish new content, we will make sure our use of headings meets accessibility standards.

The order in which headings are presented is not hierarchical and logical. This means that the structure of the page content is not clear for people that use a screen reader. This fails WCAG 2.1 success criterion 2.4.10 Section Headings (Level AAA).

We plan to ensure that all heading structures are marked up in a hierarchical and logical order by December 2020. When we publish new content, we will make sure our use of heading structure meets accessibility standards.

Lists have not been marked up correctly.  This means that relationships between content will not be clear to people using a screen reader. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships (Level A) and 4.1.1 Parsing (Level A).

We plan to ensure that all lists are marked up correctly by December 2020. When we publish new content, we will make sure our use of lists meets accessibility standards.

Updating content

Content is added to the page after a search has been performed but does not inform people that use a screen reader. This means that people that use a screen reader are unaware that the search has been successful and results are displayed. This fails WCAG 2.1 success criterion 4.1.3 Status Messages (Level AA).

We plan to ensure that all content that is dynamically added to the page informs people that use screen readers as soon as the search results appear by December 2020. When we publish new content, we will make sure updating content meets accessibility standards.

Colour

The contrast of non-text content did not meet the expected ratio of 1.3:1 where borders on form fields were used. This means that it may be difficult for people with low vision and/or colour deficiencies to know where to input information. This fails WCAG 2.1 success criterion 1.4.11 Non-text Contrast (Level AA).

We plan to make all non-text content clearly visible by December 2020. When we publish new content, we will make sure our use of colour contrast of non-text content meets the accessibility standards.

Navigation

There are no skip links on the pages throughout the service. This means that people that navigate with a keyboard are unable to jump straight to the main content. This fails WCAG 2.1 success criterion 2.4.1 Bypass Blocks (Level A).

We plan to ensure that all pages will have a functioning skip link by December 2020. When we publish new content, we will make sure that bypassing blocks of content meets the accessibility standards.

There are some skip links that should let people skip between different areas of the page. These are not functioning as they should which means that people that use a keyboard to navigate are unable to skip to the relevant area. This fails WCAG 2.1 success criterion 2.4.1 Bypass Blocks (Level A).

We plan to ensure that all pages will have functioning in-page skip links by December 2020. When we publish new content, we will make sure that bypassing blocks of content meets the accessibility standards.

The focus order of interactive elements is not logical. This means that people who use a keyboard to navigate may find it difficult to understand or operate the Web page. This fails WCAG 2.1 success criterion 2.4.3 Focus Order (Level A).

We plan to ensure that all pages will display a logical focus order by December 2020. When we publish new content, we will make sure that the focus order of interactive elements is logical to meet the accessibility standards.

Links

Links are not always descriptive of their intended purpose or destination. This means that people with motion impairment are unable to skip links that they are not interested in, people with cognitive limitations may be disoriented and people with visual disabilities are unable to determine the purpose of a link without leaving the link to explore its context. This fails WCAG 2.1 success criterion 2.4.4 Link Purpose – in context (Level A) and 2.4.9 Link Purpose – Link Only – (Level AAA).

We plan to ensure that all links are descriptive of their purpose and destination both in and out of the context of the page content by December 2020. When we publish new content, we will make sure that links are descriptive and meet the accessibility standards.

Links that open in a new window do not inform users that this will happen. This means that people can be disorientated when the new window appears. This fails WCAG 2.1 success criterion 3.2.5 Change on Request (Level AAA).

We plan to ensure that all links that result in a new window opening inform people prior to selecting by December 2020. When we publish new content, we will make sure that links inform people that a new window will open prior to selecting to meet the accessibility standards.

Disproportionate burden

Interactive tools and transactions

Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.

Our forms are built and hosted through third party software and ‘skinned’ to look like our website.

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 when the supplier contract is up for renewal, likely to be in August 2021.

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

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By December 2020, we plan to either fix these or replace them with accessible HTML pages.

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 [example of non-essential document].

Any new PDFs or Word documents we publish will meet accessibility standards.

Preparation of this accessibility statement

This statement was prepared on 23 September 2020. It was last reviewed on 23 September 2020.

This website was last tested on 16th April 2020. The test was carried out by The Digital Accessibility Centre and covered the following journeys, which are representative of the main templates used on the website.

Website: www.chevening.org