This website is run by Room Of Magic Moon. 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 using browser or device
settings;
zoom in up to 400% without the text spilling off the screen;
navigate most of the website using a keyboard or 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 (https://mcmw.abilitynet.org.uk/) 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:
you cannot modify the line height or spacing of text
most older PDF documents are not fully accessible to screen reader
software
live video streams do not have captions
you cannot skip to the main content when using a screen reader
there’s a limit to how far you can magnify the map on our ‘contact us’
page

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)
(https://www.equalityadvisoryservice.com/).

Technical information about this
website’s accessibility
Room of Magic Moon 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
The website has been tested against the Web Content Accessibility
Guidelines (WCAG) 2.2 AA standard.
​
This website is partially compliant with the Web Content Accessibility
Guidelines version 2.2 (https://www.w3.org/TR/WCAG22/) AA standard, due to
the non-compliances and exemptions listed below.
​
Some images do not have a text alternative, so people using a screen
reader cannot access the information. This fails WCAG 2.2 success
criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images. When we publish new content we’ll make sure our use of images meets accessibility standards.

Non-compliance with the accessibility regulations
Some images do not have a text alternative, so people using a screen
reader cannot access the information. This fails WCAG 2.2 success
criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images by September 2028. When
we publish new content we’ll make sure our use of images meets
accessibility standards.

Navigation and accessing information
There’s no way to skip the repeated content in the page header (for
example, a ‘skip to main content’ option).
It’s not always possible to change the device orientation from horizontal to
vertical without making it more difficult to view the content.
It’s not possible for users to change text size without some of the content
overlapping.
We’ve assessed the cost of fixing the issues with navigation and accessing
information. We believe that doing so now would be a disproportionate
burden within the meaning of the accessibility regulations. We will make
another assessment when the supplier contract is up for renewal, likely to
be in September 2028.

Content that’s 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 January 2025 if they’re not essential to
providing our services. For example, we do not plan to fix.
Any new PDFs or Word documents we publish will meet accessibility
standards.
Live video
We do not plan to add captions to live video streams because live video is
exempt from meeting the accessibility regulations

Preparation of this accessibility statement
This statement was prepared on 26/01/2025. It was
last reviewed on 26/01/2025.
This website was last tested on [date] against the WCAG 2.2 AA standard.
The test was carried out by [add name of organisation that carried out test,
or indicate that you did your own testing]. The most viewed pages were
tested using automated testing tools by our website team. A further audit of
the website was carried out to the WCAG 2.2 AA standard.