Free learning resources from arts, cultural and heritage organisations.


Accessibility statement for

This accessibility statement applies to the website The website has undergone an accessibility audit and we are currently implementing recommendations. We aim for the updates to be completed by Summer 2021.

This website is run by MyLearning. 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 300% without the text spilling off the screen
  • 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.

AbilityNet has advice on making your device easier to use if you have a disability.


How accessible this website is

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

  • some older PDF and office format documents are not fully accessible to screen reader software
  • there are some colour contrast ratio issues we are in the process of fixing
  • some images do not contain alternative text descriptions


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:

We’ll consider your request and get back to you within 15 working 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:


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).


Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

You can contact us by:

Technical information about this website’s accessibility

MyLearning 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 is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the following non-compliances and exemptions listed below. We are aiming to fix these issues by Summer 2021.

Non-accessible content


When viewing some pages at 400% zoom on mobile devices content does reflow, however the main navigation header can prevent users from being able to scroll down. This fails WCAG criteria 1.4.10 (AA). We plan to fix this issue by stopping the header being sticky and repositioning some of its content.

Text spacing

When increasing line height, letter spacing and word spacing of some content over laps due to the container having a fixed height and not auto expanding with the content. This fails WCAG criteria 1.4.12 (AA). We plan to fix this issue by allowing the footer boxes to expand to accommodate changes in line height and font size and spacing.

Bypass blocks

As a keyboard or screen reader user, there is no mechanism to skip past the header and navigation to the main content which is repeated across multiple pages. This fails WCAG criteria 2.4.1 (A). We plan to rectify this issue by adding a "skip to main content" link that is accessible when using a keyboard or screen reader.

Multiple ways to navigate

The only way to navigate between pages is by using the navigation or links in the header and footer. Although there is a search bar it only searches stories on the explore section and not all pages. This fails WCAG criteria 2.4.5 (AA). We plan to fix this issue by making a site map with clickable links availalbe from all pages.

Visible focus

Some elements which can be accessed using only a keyboard do not receive focus styling. This fails WCAG criteria 2.4.7 (AA). We plan to fix this issue by ensuring items that can be navigated to using a keyboard have focus styling.

Consistent identification

The search bar has different text to the search bars on other pages. This fails WCAG criteria 3.2.4 (AA). We plan to fix this issue by ensuring that search bars display the same text throughout the site.

Non text content

Some images are missing alternative text or haven’t being marked as decorative. This fails WCAG criteria 1.1.1 (A). We plan to fix this issue by adding alternative text tags to images on the homepage even if these are for decorative purposes only, and by removing the embedded Twitter feed.

Minimum colour contrast ratio

Some text has insufficient colour contrast against the background colour behind it. This can make the text hard to read for users with low vision or colour blindness. This fails WCAG criteria 1.4.3 (AA). We plan to fix this issue by ensuring that affected text has a minimum contrast ratio of 4.5 against its background colour.

Resize text

When using a browser extension to increase the font size to 200%, on some pages some of the content overlaps over content making it difficult to read. This fails WCAG criteria 1.4.4 (AA). We plan to fix this issue by ensuring that there are no fixed height elements so that font size can be increased without content overlapping.

Label in name

The visible text of some elements does not correspond to the function behind them. Some examples include:

  • “Discover more” link cannot be accessed using speech recognition software when the user says “Click discover more”.
  • After clicking “All subjects” a popup appears with a list of subjects. The close button on the popup cannot be selected using speech recognition software as it has no accessible name.
  • The left and right arrows on all sliding content cannot be clicked using terms such as “click left” “left arrow” “previous” etc. as there is no accessible name on the arrows.

This fails WCAG criteria 2.5.3 (A). We plan to fix this by ensuring that all interactive elements can be accessed using speech recognition software.

Parsing does not use valid HTML. This fails WCAG criteria 4.1.1 (A). We plan to fix this issue by running the website through the W3C validator tool to identify and fix them.

Keyboard navigation

Some elements on the page cannot be accessed or selected using only a keyboard. These include:

  • The open and close filters button cannot be accessed using a keyboard
  • The filters in the filter section cannot be selected using only a keyboard

This fails WCAG criteria 2.1.1 (A). We plan to fix this issue by rebuilding actions which do not have focusable links.

Removing keyboard trap

After tabbing to the plus icon on an article a popup appears. There is no way to close the popup using only a keyboard. This fails WCAG 2.1 (A). We plan to fix this issue by rebuilding the close mechanism on affected popup elements.

Link purpose

It is not possible to determine where a link will take a user to from reading the link text alone. This fails WCAG criteria 2.4.4 (A). We plan to fix this issue by adding in title attributes to buttons that will be picked up by screen readers.

Name, Role & Value and Info & Relationships

There is a list of categories at the top of some pages that when selected changes the content on the page. The list of categories act as a tab list but are not using the appropriate aria role such as tab and tablist. This fails WCAG criteria 4.1.2 (A).

The open and close text is contained in a div and is used as a button to open and close the filters. The appropriate aria information has not been included. Screen reader users will need to know that the text acts as a button and when the content is expanded or collapsed. The search button has no accessible text inside it. The search text is actually created using CSS so is not available to screen reader users or users who disable CSS. This fails WCAG criteria 1.3.1 (A).

We plan to fix the aforementioned issues by improving the Aria implementation and by enforcing a focus operation for the filters.


Disproportionate burden

Not applicable


Content that is not within the scope of the accessibility regulations


PDFs and other documents

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.

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


Preparation of this accessibility statement

This statement was prepared on March 29 2021.

As our website contains a large volume of pages, we selected a sample of pages to test based on average content type. The following pages were tested as they contain our main features used across the site: