Accessibility Statement

This accessibility statement applies to matthewdeeprose.github.io.

This website is a personal site created and maintained by Matthew Deeprose. I want as many people as possible to be able to use this website. For example, that means you will be able to:

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

How accessible this website is

This small site has been created with accessibility in mind. It has been tested with both keyboard navigation and a screen reader. Where PowerPoint videos are made available they have been checked for accessibility. Most of the YouTube videos that have been embedded have subtitles. Where subtitles are not available automated subtitles will be available.

Reporting accessibility problems with this website

I'm always looking to improve the accessibility of this website. If you find any problems not listed on this page or think I'm not meeting accessibility requirements, contact me via LinkedIn.

Enforcement procedure

As a private individual there is currently no enforcement procedure in place in relation to the accessibility of this website.

Technical information about this website’s accessibility

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.
Some videos only have automated subtitles, a failure of 1.2.2: Captions (Prerecorded). While none of the videos have an audio description, the videos are based on PowerPoint presentations which are provided separately.
The embedded twitter timeline on the About page uses the dark theme, unfortunately this theme has some contrast issues, a failure of 1.4.3 Contrast (Minimum).

Non-accessible content

Some videos only have automated captions.

What I'm doing to improve accessibility

As someone who is learning each day about accessibility where I gain further understanding of accessibility issues, or create new pages or features on this site I will endeavour to follow best practice guidelines to make this site more accessible.

Preparation of this accessibility statement

This statement was prepared on 26 October 2021. It was last reviewed on 10 October 2023.

Note

This statement is based on the template provided by GDS and adjusted where I felt it was appropriate.