Cookie Consent by

Accessibility statement

We're committed to making our online services as accessible as possible for all customers. To find out more about how our website meets accessibility guidelines please see:

This statement applies to content published on the domain.

This website is run by Mansion House.

Accessibility of our online services

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, known as 'WCAG 2.1 AA'. Get details of online services which don't meet accessibility standards, and online services exempt from accessibility standards.

Top of page

Requesting services in an accessible format

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

Reporting accessibility problems with this website

If you find any accessibility problems that are not listed on this page, or you think we’re not meeting the accessibility requirements, email: [email protected] in the first instance so that we can work to resolve the issue. If you contact Mansion House 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.

The Equality and Human Rights Commission is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations.

Top of page

How accessible this website is

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

  • you cannot modify the line height or spacing of text
  • older PDF documents are not fully accessible
  • live video streams do not have captions
  • there’s a limit to how far you can magnify the map on our ‘contact us’ page

Top of page

Compliance status

The content on Mansion House is committed to making our website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the following non-compliances listed below.

Top of page

Non-accessible content

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

Non-compliance with the accessibility regulations

  • There may be some failure conditions when a change in the appearance of text conveys meaning without using appropriate semantic mark up. This failure also applies to images of text that are not enclosed in the appropriate semantic mark up.
    This relates to WCAG 2.1 AA success criterion F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text.
  • There may be some HTML pages that don’t have a valid title element in the head section that defines in a simple phrase the purpose of the document. This helps users to orient themselves within the site quickly without having to search for orientation information in the body of the page.
    This relates to WCAG 2.1 AA H25: Providing a title using the title element, Success Criterion 2.4.2 (Page Titled)
  • There may be some failure conditions failing to allow for the technique to use HTML and XHTML according to their respective specifications. Technology specifications define the meaning and proper handling of features of the technology. Using those features in the manner described by the specification ensures that user agents, including assistive technologies, will be able to present representations of the feature that are accurate to the author's intent and interoperable with each other.
    This relates to WCAG 2.1 AA error H88: Using HTML according to spec.
  • Some pages or content may contain key errors that are known to cause problems for assistive technologies when they are trying to parse contents. Well-formedness is checked by parsing the document with a conforming XML parser and checking if the validation report mentions well-formedness errors. Every conforming XML parser is required to check well-formedness and stop normal processing when a well-formedness error is found (a conforming XML parser does not need to support validation).
    This relates to WCAG 2.1 AA success criterion H75: Ensuring that Web pages are well-formed.
  • There may be some occurrences of mark-up languages not used in a way that fully conforms to their specifications, all of the requirements in 4.1.1 are met. Therefore, while fully conforming to specifications is not required to conform to WCAG 2.0, it is a best practice and is sufficient to meet Success Criterion 4.1.1
    This relates to WCAG 2.1 AA error G192: Fully conforming to specifications
  • There may be some web pages that contain ambiguities in Web pages that often result from code that does not validate against formal specifications. Each technology's mechanism to specify the technology and technology version is used, and the Web page is validated against the formal specification of that technology. If a validator for that technology is available, the developer can use it.
    Validation will usually eliminate ambiguities (and more) because an essential step in validation is to check for proper use of that technology's markup (in a markup language) or code (in other technologies). Validation does not necessarily check for full conformance with a specification but it is the best means for automatically checking content against its specification.
    This technique relates to WCAG 2.1 AA Success Criterion 4.1.1: Parsing - relates to error code G134.
  • There may be some failure conditions where the purpose of a link by providing descriptive text as the content of the element is unavailable. The description lets a user distinguish this link from other links on the Web page and helps the user determine whether to follow the link. The URI of the destination is generally not sufficiently descriptive.
    This relates to WCAG 2.1 AA error H30: Providing link text that describes the purpose of a link for anchor elements
  • There may be some PDF documents that don’t show how a descriptive title for a PDF document can be specified for assistive technology by using the /Title entry in the document information dictionary and by setting the DisplayDocTitle flag to True in a viewer preferences dictionary. This is typically accomplished by using a tool for authoring PDF.
    This relates to WCAG 2.1 AA code PDF18: Specifying the document title using the Title entry in the document information dictionary of a PDF document.
  • Some failure conditions may occur where techniques have failed to ensure that sections have headings that identify them.
    This relates to WCAG 2.1 AA Success Criterion 1.3.1 which requires that the headings be marked such that they can be programmatically identified (error code G141).
  • There may be some web pages that contain failures to use HTML and XHTML heading markup to provide semantic code for headings in the content. Heading markup will allow assistive technologies to present the heading status of text to a user, this failure may prevent a screen reader from recognizing the code and announce the text in a more efficient way.
    This relates to WCAG 2.1 AA H42: Using h1-h6 to identify headings, Success Criterion 1.3.1 (Info and Relationships)
  • There may be some web pages without a descriptive title. Descriptive titles help users find content, orient themselves within it, and navigate through it. A descriptive title allows a user to easily identify what Web page they are using and to tell when the Web page has changed. The title can be used to identify the Web page without requiring users to read or interpret page content.
    This relates to WCAG 2.1 AA G88: Providing descriptive titles for Web pages, Success Criterion 2.4.2 (Page Titled)
  • There may be some PDF documents that contain errors to ensure specification of a document's default language by setting the /Lang entry in the document catalog. This is normally accomplished using a tool for authoring PDF.
    This relates to Success Criterion 3.1.1 (Language of Page) - PDF16: Setting the default language using the /Lang entry in the document catalog of a PDF document
  • There may be some PDF documents that contain errors to ensure that users can navigate through content in a logical order that is consistent with the meaning of the content. Correct tab and reading order is typically accomplished using a tool for authoring PDF.
  • For sighted users, the logical order of PDF content is also the visual order on the screen. For keyboard and assistive technology users, the tab order through content, including interactive elements (form fields and links), determines the order in which these users can navigate the content. The tab order must reflect the logical order of the document.
    This technique relates to PDF3: Ensuring correct tab and reading order in PDF documents

Top of page

Disproportionate burden

We’ve assessed accessibility issues within a number of our online systems and believe that fixing them now would be a disproportionate burden (within the meaning of the accessibility regulations). In some cases this is because a system will be retired or replaced soon. We'll retire or replace systems in a way that causes minimum disruption and also make further assessments when supplier contracts renewed or suppliers are changed. Any replacement systems will be as accessible as possible.

Top of page

What we’re doing to improve accessibility

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

Preparation of this accessibility statement

Our online services are currently being (and will continue to be) reviewed for compliance with WCAG 2.1 AA This statement was prepared in April 2023. It was last reviewedin May 2023, by City of York Council.

Top of page

Also see