We hope that you find this website highly accessible.
We have used the Web Content Accessibility Guidelines (WCAG) 2.1 to help us achieve this. To this end, the site has the following site accessibility features:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols, or simpler language.
- Alt text descriptions are added to images.
Provide alternatives for time-based media.
- Closed captions and transcripts are provided for embedded video (using YouTube features ‘CC’ and ‘open transcript’).
- Sign language interpretation of the homepage and ‘About the Project’ page are provided by means of a video.
- Audio content does not contain background sounds.
- An alternative for time-based media of the pre-recorded video content is provided for synchronized media,
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
- Images (apart from headers) can be enlarged by clicking on them.
- Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, colour, size, visual location, orientation, or sound.
- Except for captions and images of text, text can be resized up to 200 percent without loss of content or functionality.
- Text can be resized up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window with the ‘One Click Accessibility’ tool.
- Text can be resized such that width is no more than 80 characters with the ‘One Click Accessibility’ tool.
- No loss of content or functionality occurs if users change the line height (up to at least 1.5 times the font size), spacing following paragraphs (to at least 2 times the font size), letter spacing (to up to 0.12 times the font size) and/ or word spacing (to up to 0.16 times the font size).
- Content shown on hover (i.e. the menu) is hover-able at all magnifications of text. (AA)
- Chunks of italic text are avoided; italics are used just to highlight words – when they appear in the glossary.
Make it easier for users to see and hear content including separating foreground from background.
- The focus indicator has been enhanced so that people can clearly see where on the page they are.
- Minimal use of images of text, and where we have used them (project title and infographics), there is a text alternative.
- Sufficient colour contrast is ensured by ‘One Click Accessibility’ tool.
- Foreground and background colours can be selected by the user with the ‘One Click Accessibility’ tool.
- Text is not justified.
- Links have a non-colour indicator (underline) in addition to a different colour.
- Links have an easily distinguishable ‘hover style’ to give an extra cue when a mouse is over a link.
- Additional content on hover (i.e., the menu) does not obscure any content. (AA)
Make all functionality available from a keyboard.
- All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Provide users enough time to read and use content.
- Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.
Do not design content in a way that is known to cause seizures or physical reactions.
- There is no animation on the site.
- Web pages do not contain anything that flashes.
Provide ways to help users navigate, find content, and determine where they are.
- The site has been designed to support simple navigation and a logical site structure.
- Headings have been used to communicate the organisation of the content on the page.
- The purpose of each link can be determined from the link text alone without the surrounding sentences or content.
- Link text is unique and easy to speak out loud.
- Skip’ links are available to bypass blocks of content that are repeated on multiple Web pages.
- Minimal redundant links.
- Minimal images as links.
- ARIA document structure roles have been used.
- Web pages have titles that describe topic or purpose.
- Web pages can be navigated sequentially, and focusable components receive focus in an order that preserves meaning and operability.
- A sitemap is provided to help users find content (AA).
- There is a breadcrumb feature to make information available about the user’s location within webpages. (AAA)
Make it easier for users to operate functionality through various inputs beyond keyboard.
- Drop-down menus are navigable using tab.
- No single-key shortcuts are necessary to use the site.
- The site uses no path-based or multipoint gestures.
- For functionality that can be operated using a single pointer (i.e., contact page form), the down-event of the pointer is not used to execute any part of the function
- Motion actuation is not used on the site.
- Web content does not restrict use of input modalities available on a platform – users can switch between keyboard and mouse as they wish.
- Visible labels and programmatic names for controls match (in the contact form).
Information and the operation of the user interface must be understandable.
Make text content readable and understandable.
- The language of the site is identified as English, to facilitate AT. Currently no languages other than English are used on the site. If that changes, we will identify any changes in language on a page by using the
- Easy to Read versions of some webpages are available.
- A glossary is provided, for unusual words, abbreviations and pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (AAA)
Make Web pages appear and operate in predictable ways.
- When any user interface component receives focus, it does not initiate a change of context, i.e., when you hover over the ‘submit button’ it does not submit until you have clicked on it.
- Links do not unexpectedly take you to a new page.
- Consistent navigation – the site has a logo, a title, and a navigation bar at the top of each page; these appear in the same relative order on each page where they are repeated.
- Components that have the same functionality within a set of Web pages are identified consistently e.g., ‘Continue reading’ is phrased consistently throughout the site.
- Changes of context – there are no pop-up windows on the site.
- If an image functions as a link, the image has alt text that conveys the location and purpose of the link rather than describing the image.
Help users avoid and correct mistakes.
- Labels and instructions are provided when content requires user input (contact form).
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
Maximize compatibility with current and future user agents, including assistive technologies.
- No custom controls have been created or interface elements programmed to have a different role and/or function than usual.
- The site should have good quality parsing in the coding. The only changes to the coding we have used have been to colour and size and we trust WordPress to have developed good quality coding.
We have checked the site using the following methods:
- Comprehensive review of Web Content Accessibility Guidelines (WCAG) 2.1
- Site tested with WAVE (Website Accessibility Evaluation) tool every six months.
- Navigating the site using only the keyboard to interact with all controls, links, and menus (arrow keys, tab, enter and shift tab) – i.e., unplugging the mouse,
- Turning on high contrast mode through the One Click Accessibility tool and navigating the site,
- Turning off the images through browser settings to ensure that links still function, and that content still makes sense,
- Turning off CSS using disable-HTML to ensure that the site is still easy to read and navigate,
- Site tested with Chromevox screen-reader.
- Site tested on a mobile device and tablet.
We are still working through the following:
- Easy to Read and audio versions of all web pages. (AAA)
Please notify us of any accessibility issues or improvements we might make. We will be glad to hear from you. firstname.lastname@example.org.