Mansion House Accessibility statement

Mansion House Accessibility Statement

Technical information about this website’s accessibility.

This statement applies to content published on the mansionhouseyork.com domain.

Mansion House is committed to making our website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No.2) Accessibility Regulations 2018.

To find out more about how our website meets accessibility guidelines please see:

It is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:

  • zoom in up to 300% without problems
  • navigate most of the website using just a keyboard
  • use most of our online services with screen reader software

Most of our online services work when scripts, applets or other programmatic objects are turned off, or aren't supported by a device. However, your experience using online services without scripts running may degrade.

Our online services are partially compliant with the latest Web Content Accessibility Guidelines (WCAG). Get details of online services which don't meet accessibility standards, and online services exempt from accessibility standards.

Top of page

If you need information in a different format email: [email protected], and tell us:

  • the location of the information (copy and paste the URL/address from your browser address bar)
  • your name and email address (so we can respond)
  • the format you need (for example, audio CD, braille, British Sign Language (BSL), large print, accessible PDF)

Top of page

You can report accessibility problems with this website if you find any issues that are not listed on this page, or you think we’re not meeting accessibility regulations. Email: [email protected] in the first instance, so that we can work to resolve the issue. If you contact us with a complaint about the accessibility of our online services, and you’re not happy with our response the Equality Advisory and Support Service may be able to help you.

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. If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Top of page

Parts of this website are not fully accessible. For example:

  • some lists are marked up incorrectly
  • some lists or groups of links may not be written semantically
  • some PDF documents may not be tagged
  • some instances of inappropriate colour contrast exist
  • some links may be aimed toward anchors that do not exist
  • there may be cases of form controls that don't contrast sufficiently with their surroundings
  • there may be cases where the purpose of fields can't be identified programmatically
  • some PDF documents don't specify headings for accessibility
  • the use of language may not have been specified on every page
  • some headings on the website may fail accessibility as they do not provide text within the header tag
  • there may be some link text that is directed to more than one different destination
  • there may be some interactive components on a page, such as buttons or fields, which are not large enough
  • there may be some cases where the first heading in a PDF is a H1
  • there may be cases where links in a new tab or window where the destination is not explained
  • there may be failures to comply with the strictest accessibility standard (WCAG AAA)
  • some long PDFs may not use bookmarks to help aid navigation

Top of page

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG), due to the following non-compliances listed below.

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations:

  • some lists are marked up incorrectly which can prevent screen readers accurately reporting the number of items contained in the list - this relates to success criterion WCAG (A) 4.1.1
  • some lists or groups of links may not be written semantically - this relates to success criterion WCAG (A) 1.3.1
  • some PDF documents may not be tagged to ensure accessibility and compliance with digital standards - this relates to success criterion WCAG (A) 1.3.1
  • some instances of inappropriate colour contrast exist, meaning potential reduced readability if you have low vision (if not using contrast-enhancing assistive technology) - this relates to success criterion WCAG (AA) 1.4.3
  • some links may be aimed toward anchors that do not exist - this relates to success criterion WCAG (A) 2.4.1
  • there may be cases of form controls that don't contrast sufficiently with their surroundings so that people with visual impairments are still able to clearly see them - this relates to success criterion WCAG (AA) 1.4.11
  • there may be cases where the purpose of fields can't be Identified programmatically - this relates to success criterion WCAG (AA) 1.3.5
  • some PDF documents don't specify headings for accessibility. Headings are crucial for screen readers and other assistive technologies - this relates to success criterion WCAG (A) 1.3.1
  • the use of language may not have been specified on every page, preventing assistive technologies from accurately interpreting their contents - this relates to success criterion WCAG (A) 3.1.1
  • some PDF documents don't specify headings for accessibility. Headings are crucial for screen readers and other assistive technologies - this relates to success criterion WCAG (A) 1.3.1
  • some headings on the website may fail accessibility as they do not provide text within the Header tag - this relates to success criterion WCAG (A) 1.3.1
  • there may be some link text that is directed to more than one different destination, which will create confusion for Screen reader users - this relates to success criterion WCAG (A) 2.4.4
  • there may be some interactive components on a page, such as buttons or fields, which are not large enough to be easily used by people with motor impairments - this relates to success criterion WCAG (AAA) 2.5.5
  • there may be some cases where the first heading in a PDF is a H1 - this relates to success criterion WCAG (A) 1.3.1
  • there may be cases where links in a new tab or window where the destination is not explained - this relates to success criterion WCAG (AAA) 3.2.5
  • there may be failures to comply with the strictest accessibility standard (WCAG AAA), the colour of text must strongly contrast with its background colour, so that people with significant visual impairments can read it - this relates to success criterion WCAG (AAA) 1.4.6
  • some long PDFs may not use bookmarks to help aid navigation - this relates to success criterion WCAG (AA) 2.4.5

Where downloads (in PDF, and other file formats) do not meet accessibility standards we plan to fix or replace them, either when they are next reviewed, or as part of our ongoing programme of review work, whichever is sooner.

Top of page

Parts of our online services are exempt from accessibility standards:

  • the accessibility regulations do not require us to 'fix' downloads if they were published before 23 September 2018 (if they’re not essential to providing services); we will not edit downloads that are supplied to us by other organisations or members of the public to make them accessible
  • we do not plan to add captions to live video streams, because live video is exempt from meeting the accessibility regulations, as are pre-recorded audio and videos published before 23 September 2020
  • maps are exempt from accessibility regulations, but we're working to provide essential information in accessible ways; email us about requesting services in an accessible format. We don’t yet have a way of presenting geographical information (maps and site plans etc.) in a fully accessible format. However, as new technologies emerge, we'll review our online services

Accessibility exemptions in our work with third-parties

We brief suppliers on our requirement to meet accessibility regulations; while some elements remain beyond our control, we aim to procure services with accessible outcomes in mind, and to highlight potential improvements suppliers need to consider.

Software linked from our website, which is under the control of our suppliers, may not be accessible if our contract with them does not cover accessible development of 'out of the box' functionality. However, we aim to work with suppliers whose products are as accessible as possible, when contracts are reviewed/renewed. If we create content hosted on external platforms (for example, national databases, social media, video-hosting or survey platforms) we endeavour to ensure the content we upload meets accessibility requirements, and is configured in the most accessible way the platform allows. However, we're not responsible for the accessibility of third-party platforms.

Top of page

We’re committed to being a fair and inclusive website, and we're passionate about providing accessible services, ensuring they’re properly designed and coded, so more people can use them, more easily, regardless of their hardware, software, language, location, or ability.

Top of page

This statement was prepared on April 2023 and last reviewed on October 2025.

Our online services are currently being (and will continue to be) reviewed for compliance with WCAG standards by City of York Council's Web Services Team, who carry out manual checks, alongside weekly automated sample testing which (together with usage data) informs and prioritise our actions for improving accessibility across online services.

Online services are re-assessed for accessibility whenever a major modification is undertaken; 'page content' is checked every time it is updated. Our current estimate is that further accessibility fixes to address non-accessible content on this site, will be undertaken during 2026.

Top of page

Terms and conditions