Accessibility

This accessibility statement applies to the Image Library.

This website is run by Historic Royal Palaces. 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 decorative imagery contains inappropriate alternative attributes.
  • Buttons do not always have an appropriate accessible label.
  • Form input fields do not have an appropriate accessible label.
  • Some form labels are not correctly associated with a form control.
  • Visually grouped fields are not contained within a fieldset.
  • Headings and lists are not always marked up correctly.
  • Page regions are not always identified by an ARIA Landmark.
  • Autocomplete functionality is not available on expected input fields.
  • The tabbing order of the website may not always be logical.
  • Identical accessible labels are used on image links.
  • Text does not meet sufficient contrast requirements.
  • Text cannot be resized by the browser without loss of functionality.
  • Images of text are present.
  • Two-dimensional scrolling is present on some pages.
  • Some user interface elements do not meet contrast requirements against the background.
  • Focused user interface components do not always have sufficient contrast against adjacent colours.
  • You are unable to stop, pause or hide moving content.
  • Page titles are not consistent with website navigation.
  • The focus indicator is not always visible.
  • Format requirements for input fields are not descriptive.
  • Mandatory fields are not specified within the field’s label.
  • Fields which have an error do not provide suggestions about how to fix the error.
  • Login forms do not have an accessible method for authenticating passwords or codes.
  • Not all functionality on the website can be controlled using speech recognition tools.
  • Invalid ARIA values are present.
  • Some elements on the page lack accessible names.
  • Elements of the page are not accessible to mobile screen readers.
  • Status messages are not always announced.

 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 in 14 days.

If you cannot view the map, on our contact us page, call or email us for directions.

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 [email protected]  and our Image Library team will deal with your report.

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.

Find out how to contact us.

Technical information about this website’s accessibility

Historic Royal Palaces 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

This website is not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances are listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Decorative images have been given alternative attributes, resulting in unnecessary information being announced to users of screen readers. This fails WCAG 2.2 success criterion 1.1.1 (non-text content)

We plan to resolve this by: 31 July 2024

Buttons do not have appropriate labels. Buttons without labels do no provide information about the functionality of the button to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content.

We plan to resolve this by: 31 July 2024

Form input fields lack an associated text label or descriptive title. Incorrectly associated labels do not provide functionality or information about the form control to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content.

We plan to resolve this by: 31 July 2024

Form labels that are present are not properly associated with its corresponding form control. Incorrectly associated labels do not provide functionality or information about the form control to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content.

We plan to resolve this by: 31 July 2024

Grouped fields are not contained within a fieldset element, which may result in confusing announcements by screen readers. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships.

We plan to resolve this by: 31 July 2024

Headings and lists are not marked up appropriately which may cause screen readers to announce them incorrectly. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships.

We plan to resolve this by: 31 July 2024

ARIA Landmarks aren’t used to identify all page content. This may cause content to be missed by screen reader users. This fails WCAG 2.2 success criterion 1.3.1 Info and Relationships.

We plan to resolve this by: 31 July 2024

A valid autocomplete attribute is not present, which may make completing logins and forms more time consuming. This fails WCAG 2.2 success criterion 1.3.5 Identify Input Purpose.

We plan to resolve this by: 31 July 2024

Text does not meet sufficient contrast requirements against the page background. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum).

We plan to resolve this by: 31 July 2024

Rendering issues are present with text when zooming text only to 200% using browser zoom controls. This fails WCAG 2.2 success criterion 1.4.4 Resize Text.

We plan to resolve this by: 31 July 2024

Images of text are present on the page which cannot be resized or styled by browsers. This fails WCAG 2.2 success criterion 1.4.5 Images of Text.

We plan to resolve this by: 31 December 2024

Two-dimensional scrolling is required to access page content when zooming the page to 400% with a browser width of 1280px. This fails WCAG 2.2 success criterion 1.4.10 Reflow.

We plan to resolve this by: 31 July 2024

Some non-textual content lacks contrast against the background page. This includes the search field present in the website's header. This fails WCAG 2.2 success criterion 1.4.11 Non-Text Contrast.

We plan to resolve this by: 31 July 2024

When in a focused state, some non-textual content lacks contrast against the background page. This includes the close button on the login page and the filter user interface component present next to the search field. This fails WCAG 2.2 success criterion 1.4.11 Non-Text Contrast.

We plan to resolve this by: 31 July 2024

Content that moves automatically is present on the homepage, with no mechanism available to be able to pause, stop, or hide the moving content by the user. This fails WCAG 2.2 success criterion 2.2.2 Pause, Stop, Hide.

We plan to resolve this by: 31 July 2024

Page titles are not sufficiently descriptive or informative which may cause navigation issues between tabs. This fails WCAG 2.2 success criterion 2.4.2 Page Titled.

We plan to resolve this by: 31 July 2024

The focus order of the page is not logical. Users who rely on a keyboard access for operating a page benefit from a logical, usable focus order. This fails WCAG 2.2 success criterion 2.4.3 Focus Order.

We plan to resolve this by: 31 December 2024

Image links have identical accessible labels. This could cause confusion for screen reader users. This fails WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context).

We plan to resolve this by: 31 July 2024

The focus indicator is not visible for some user interface elements. This can make it difficult for keyboard only users to keep track of the elements currently in focus. This fails WCAG 2.2 success criterion 2.4.7 Focus Visible.

We plan to resolve this by: 31 July 2024

Format requirements are not specified for email fields which may cause confusion for some users. This fails WCAG 2.2 success criterion 3.3.1 Error Identification.

We plan to resolve this by: 31 July 2024

Mandatory fields do not have this information specified within field labels which may cause confusion to some users. This fails WCAG 2.2 success criterion 3.3.2 Labels or Instructions.

We plan to resolve this by: 31 July 2024

Fields which have an error do not provide adequate suggestions on how to fix the error. This fails WCAG 2.2 success criterion 3.3.3 Error Suggestion.

We plan to resolve this by: 31 July 2024

Cognitive function tests are present and have no accessible alternative or assistive mechanism. This may result in some users being unable to complete the test.  This fails WCAG 2.2 success criterion 3.3.8 Accessible Authentication.

We plan to resolve this by: 31 July 2024

Image carousels are unable to be interacted with using any known voice command whilst navigating with Dragon Naturally Speaking. This fails WCAG 2.2 success criterion 4.1.2 Name, Role, Value.

We plan to resolve this by: 31 December 2024

Invalid values have been attributed to some ARIA controls. This may result in some functionality to be unable to be controlled by assistive technologies. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

We plan to resolve this by: 31 July 2024

Some uses of ARIA are not appropriately labelled and may result in some content being announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

We plan to resolve this by: 31 July 2024

Android screen readers announcements do not always correctly reflect the content and interactions on the page. This may cause confusion for some users. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

We plan to resolve this by: 31 July 2024

Success messages after submission are not announced by screen readers. This may result in users being unable to correct input errors. This fails WCAG 2.2 success criterion 4.1.3 Status Messages.

We plan to resolve this by: 31 July 2024

Preparation of this accessibility statement

This statement was prepared on 30 April 2024. It was last reviewed on 30 April 2024.

This website was last tested on 29 April 2024. The test was carried out by Zoonou.

Zoonou used WCAG-EM to define the pages tested and test approach.

Loading...

Your download will start shortly, please do not navigate away from this page until the download prompt has appeared. Doing so may cause your download to be interrupted.