Accessibility statement

We strive for compliance with the Web Content Accessibility Guidelines version 2.1 AA standard. However we know that some aspects of this website are not fully accessible and we are constantly looking for ways to improve this. For example, information that resides in PDF formats are often not accessible to screen readers. 

If you have any feedback or require further assistance, please contact us on [email protected].

Content

• Use plain language and avoid figures of speech, idioms and complicated metaphors

• Make sure that button, a, and label element content is unique and descriptive

Global code

• Use semantic and validated HTML with appropriate regions, landmarks and ARIA attributes

• Add a lang attribute to the html element

• Provide a unique title for each page

• Ensure viewport is not disabled

• Ensure a linear content flow

• Avoid using the autofocus attribute

Keyboard

• Provide a high-contrast style to elements when focused to using a keyboard (such as links, buttons and form elements)

• Keyboard focus should follow visual layout

Images

• Provide an alt attribute for descriptive text on image elements, where appropriate

• Provide an empty alt attribute on decorative images

• Provide visually hidden extra instructions for screen reader users where required (such as when using an icon to indicate functionality or context)

Headings

• Use headings in logical sequence without skipping heading levels

• Only use one h1 element per page

Lists

• Use appropriate list elements (ol, ul, and dl) for list content

Links

• Use a element for links and ensure they are identifiable as links

• Add high contrast visible focus state to link elements

• Use button element for button actions

• First keyboard focusable element is a ​‘skip to content’ link to allow keyboard users to get past the header content

• Identify links that open in a new tab or window with an appropriate icon or supportive text

Tables

• Use a table element to describe tabular data, with appropriate semantic markup to dictate table header and body content

Forms

• All inputs in a form are associated with a corresponding label element

• Use fieldset and legend elements where appropriate

• Inputs use autocomplete where appropriate

• Summarise form errors above the form as well as an associated error message alongside the offending form input

• Don’t just communicate error, warning or success states purely through colour

Media and Animation

• Make sure media does not autoplay

• Check media can be paused

• Use appropriate media controls. Native video will use the HTML video element whilst we will often embed third-party content hosted on YouTube

• Strive to provide video captions where possible and appropriate

• Aim to remove any seizure triggers and respect the prefers-reduced-motion media query

• Only use subtle animation

Appearance

• Site content should be legible and usable in specialised browsing modes such as high contrast or inverted

• Make sure users can zoom the page at least 200% without breaking the layout, content or functionality

• Use a simple, straightforward and consistent layout across page templates

Colour contrast

• Normal sized text always passes a 4.5:1 contrast ratio against its background colour

• Large sized text always passes a 3:1 contrast ratio against its background colour

• Icons, and input borders pass a 3.0:1 contrast ratio

• Provide a high contrast selection colour

Mobile and touch

• Site can be rotated to any orientation and should display responsively at all viewport sizes

• Make sure that buttons are easily activated using touch

• Provide enough space between interactive items to provide a suitable scroll area