Accessibility Statement
This accessibility statement applies to www.ytlgroup.co.uk.
The website is managed by the YTL Group UK Digital team. 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 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 has advice on making your device easier to use if you have a disability.
How accessible this website is
Parts of this website are not fully accessible. For example:
- there is no skip to content
- the link within the logo has a non-empty accessible name.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please email: digital@ytlgroup.co.uk.
When contacting us, please include:
- the web address (URL) of the content
- your email address and name
- details of any problems you have experienced.
Technical specifications
Accessibility of www.ytlgroup.co.uk relies on the following technologies to work with the particular combinations of web browser or any assistive technologies or plugins installed on your computer:
- HTML
- WAI-ARIA
- CSS
- JAVASCRIPT
These technologies are relied upon for conformance with the accessibility standards used.
What we’re doing to improve accessibility
We are working alongside agencies to fix content which fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard.
Preparation of this accessibility statement
This statement was prepared on 31 October 2024. It was last reviewed on 31 October 2024.
This website was last tested in October 2024 against the WCAG 2.2 AA standard. This test of a representative sample of pages was carried out using Acquia Optimize.
We also used findings from our own testing when preparing this accessibility statement.
Last updated 31 October 2024