We are committed to making our websites and mobile applications accessible, in accordance with The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 No.952.

This accessibility statement applies to all website, mobile applications and relevant digital content that we own, that falls within the remit of the above mentioned legislation and the Equality Act 2010 as appropriate.

Compliance Status

This website is partially compliant with The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 No.952, due to the non-compliance on our Moodle Known Issues page.

Non-accessible content

We work to achieve and maintain WCAG 2.1 AA standards, but it is not always possible for all our content to be accessible. Where content is likely to create a barrier, we’ll state a reason, warn users and offer alternatives – see our Moodle Known issues page for more details.

If we have failed to identify a barrier, please contact us

Web standards

Moodle is developed using valid HTML, CSS, PHP and JavaScript to the standards laid out in the Web Content Accessibility Guidelines (WCAG 2.1) – Level AA.

The website content works with assistive technologies that visitors might use. For example, screen readers or text only browsers.

We list below further areas within Moodle that we know are not fully accessible. We plan to fix or provide alternatives for all issues that we are made aware of alongside our periodic internal testing and auditing processes:

  • Content inserted with CSS is not read by some screen readers, and not available to people who turn off style sheets
  • CSS animations that run for more than 5 seconds without giving the user a way to turn them off
  • Underline links not always present making it hard for colour-blind users to see them
  • Semantic markup like strong  used instead of the CSS font-weight property
  • Information about the general layout of a site using a site map or table of contents missing
  • The CSS outline or border style on some elements makes it difficult or impossible to see the dotted link focus outline
  • Some links have a new window as the target of a link with target=_blank
  • CSS animations or transitions in interactions without giving the user a way to turn them off
  • Some pages contain images that flash more than three times in any one second period
  • Link text replaced by aria-label attribute doesn’t work in some screen readers
  • Some fieldset elements not labeled with legend elements
  • Some decorative and spacer images using descriptive alt attributes
  • Some documents without titles
  • Duplicate attributes
  • The same ID is used on more than one element
  • Not all elements contain text or an image with an alt attribute
  • Div element as child element in some contexts
  • Tags violating nesting rules
  • Issues with <A> tags
  • Attributes not linking correctly with various elements
  • Issues with elements
  • Some text and background colours do not have enough contrast
  • Some headings are empty
  • Some pages without headings
  • Several links on a page share the same link text, but go to different destinations
  • Link text replaced by attributes that don’t work in some screen readers

If we have failed to identify a barrier, please contact us.

Preparation of this accessibility statement

This statement was prepared on 19/09/2019.

The declaration made in this statement regarding compliance with The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 No.952 is accurate and based on an evaluation of the website’s compliance with the Web Content Accessibility Guidelines 2.1 (WCAG) to AA standard.

For information on our self-assessment auditing process and to see how our checks align with the WCAG 2.1 AA please contact us.

Feedback and contact information

Please contact us if you have any problems; be as specific and detailed as you can. Please also tell us what you like and find useful.

The World Wide Web Consortium (W3C) has useful tips on contacting organisations about inaccessible websites.

When you contact us by email or phone there is a process in place that will acknowledge your contact, tell you who is dealing with it and give you a timescale by which you can expect a reply.

Complaints / enforcement procedure

Once you have reported a problem with our website or asked for an alternative format, but you are not happy with our response, you can use our complaints process to register your difficulty by contacting Xavier Briche, Head of Digital Learning, by email at x.briche@roehampton.ac.uk. This helps us improve our systems.

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

This page was last updated on 20/09/19