This accessibility statement applies to the Celesta Venues website, www.celestavenues.co.uk. The Celesta Venues website is run by Imperial College London. 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:

  • Page regions are not always identified by an ARIA Landmark
  • Related form elements are not appropriately grouped
  • A ‘Skip to Main Content’ link is not present
  • Headings are not appropriately structured across the site
  • Text does not meet sufficient contrast requirements
  • Text cannot be resized by the browser without loss of functionality
  • Rendering issues are observed when viewing content at a high zoom on a limited browser window
  • Some user interface elements do not meet contrast requirements against the background in their normal state and when focused
  • Custom Cascading Style Sheets (CSS) text spacing cannot be applied without content being obscured
  • Content which appears on hover cannot easily be dismissed without removing focus
  • Content which appears on hover disappears before it can be accessed
  • The focus order is not always logical
  • Links with identical text are not distinguished by their accessible label
  • Elements of the page are not accessible using keyboard only or an iOS screen reader
  • The focus indicator is not always visible on page elements
  • Unexpected behaviour occurs when some elements receive tab focus
  • Some mandatory input fields do not display text errors
  • Email format requirements are not specified within error messages
  • Some page elements cannot be accessed using speech recognition software
  • Building preview elements on the page are not accessible and no alternative is provided
  • Zooming and scaling is disabled across all pages
  • 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:

  • Email: hello@celestavenues.co.uk
  • Call: +44 (0)20 7594 9494

We’ll consider your request and get back to you in seven days.

If you cannot view the map on our ‘contact us’ page, please email us for directions on venues@celestavenues.co.uk.

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: hello@celestavenues.co.uk.

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

If you require additional assistance when visiting us in person, please contact us prior to your visit to discuss individual arrangements on: hello@celestvanues.co.uk.

Technical information about this website’s accessibility

Imperial College London 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 partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

  1. Filter checkboxes have duplicate labels which may result in screen readers announcing them incorrectly. This fails WCAG 2.2 success criterion 1.1.1 (Non-Text Content). We plan to resolve this by: February 2024.
  2. 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: February 2024.
  3. Related form elements are within fieldsets which are not defined by an appropriate legend which may cause issues when screen readers announce these elements. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). We plan to resolve this by: February 2024.
  4. The ‘Skip to Main Content’ link is not functional within the site to allow keyboard and assistive technology users to bypass repeated navigational components across the site. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks). We plan to resolve this by: February 2024.
  5. A correctly formed heading structure is not present to facilitate navigation across the site, with skipped heading levels present. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks). We plan to resolve this by: February 2024.
  6. 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: February 2024.
  7. 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: February 2024.
  8. Zooming the page to 400% with a browser width of 1280px results in main page content being obscured by the navigation menu and overlay buttons. This fails WCAG 2.2 success criterion 1.4.10 (Reflow). We plan to resolve this by: February 2024.
  9. Some non-textual content lacks contrast with the background page in its normal state and when focused. This includes navigation buttons on the interactive map element. This fails WCAG 2.2 success criterion 1.4.11 (Non-Text Contrast). We plan to resolve this by: February 2024.
  10. Content within the header menu dropdowns is cut-off when custom Cascading Style Sheets (CSS) test spacing is applied. This results in some text within fields being obscured. This fails WCAG 2.2 success criterion 1.4.12 (Text Spacing). We plan to resolve this by: February 2024.
  11. When focusing the navigation menu with the mouse, content appears that cannot be dismissed without removing focus and disappears before it can be accessed. This fails WCAG 2.2 success criterion 1.4.13 (Content on Hover or Focus). We plan to resolve this by: February 2024.
  12. The navigational menu is within the focus order even when it is not opened or visually present on the page. Users who rely on 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: February 2024.
  13. Links with identical link text are not distinguished by their accessible label. The purpose of these links may be difficult to determine. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context). We plan to resolve this by: February 2024.
  14. Some content is inaccessible when using a keyboard to navigate the site. This includes filter options on searches. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). We plan to resolve this by: February 2024.
  15. Some content is inaccessible when using an iOS screen reader to navigate the site. The newsletter sign-up feature on each page cannot be interacted with. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). We plan to resolve this by: February 2024.
  16. The focus indicator is not visible for some user interface elements, including dropdowns, search fields and footer links. 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: February 2024.
  17. Tabbing to date fields within the Contact Us modal causes a calendar to appear without any additional user input which could cause confusion or distraction. This fails WCAG 2.2 success criterion 3.2.1 (On Focus). We plan to resolve this by: February 2024.
  18. Text errors are not present on all mandatory input fields. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification). We plan to resolve this by: February 2024.
  19. The required format for email fields is not specified within the error text presented. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions). We plan to resolve this by: February 2024.
  20. Some content is inaccessible when using speech recognition software to navigate the site. This includes date fields on the Accommodation pages. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by: February 2024.
  21. The building preview tool is not accessible to all users, and no accessible alternative is provided for this content. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by: February 2024.
  22. Zooming and scaling is disabled, which causes zooming to be disabled on mobile devices. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). We plan to resolve this by: February 2024.
  23. Changes in search results are not announced by screen readers. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages). We plan to resolve this by: February 2024.

What we’re doing to improve accessibility

We are aiming to resolve the know issues of non-compliance as stated above by February 2024. In the meantime, please contact hello@celestavenues.co.uk if you need any support on these or any points that we may be unaware of.

Preparation of this accessibility statement

This statement was prepared on 08/11/2023. It was last reviewed on 08/11/2023.

This website was last tested on 07/11/2023. The test was carried out by Zoonou.

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

Get in touch