Skip to navigation Skip to main content Skip to footer

Accessibility Statement for Escode

 

This accessibility statement applies to the Escode website. 

This website and app are run by Escode. We want as many people as possible to be able to use them. 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 the text spilling off the screen or requiring horizontal scrolling
  • navigate most of the website and app using a keyboard or speech recognition software
  • listen to most of the content using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
  • access the website and app on smaller devices

We’ve also made the text as simple to understand as we can.

Compliance Status and Accessibility Summary

We know some parts of this website are not fully accessible: 

  • Some buttons lack meaningful text, some links have missing or confusing names, and some pages have multiple buttons with the same name.  
  • Some pages skip heading levels, and some headings look different from other headings at their same level.  
  • Some forms fail to indicate which fields are mandatory and which are optional, and some autocomplete form elements have no labels.
  • The reading order of the main navigation area doesn't match the visual layout.
  • Some elements are not contained within a landmark.  
  • Some parts of the site cannot be operated via keyboard.
  • Some elements fail to provide a clear and consistent visual indication of when they have focus.
  • More information on the accessibility issues appears in the section on non-accessible content, below.

Accessibility Feedback and Contact Details

If you need information on this website in a different format such as accessible PDF, large print, easy read, audio recording or Braille: 

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

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems that we haven't listed on this page, or if you think we’re not meeting accessibility requirements, we would love to hear from you. Please send us an email in which you describe the problem and tell us which page you were using when it happened. Send this email to marketing@escode.com

Technical Standards and Regulatory Compliance

Escode is committed to making its website accessible in accordance with the European Accessibility Act of 2025.

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-compliance with the accessibility regulations

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

WCAG 2.2 Non-compliance Issues

This section lists the key ways in which this website app fails to meet the WCAG 2.2 success criteria. It includes all violations of levels A and AA success criteria and all issues that the testing found to be serious or critical. It includes minor issues only if they relate to a Level A criterion. The issues appear in numerical order of the applicable success criteria.

  • Some buttons lack meaningful text. This fails WCAG 2.2 success criteria 1.1.1 (Non-Text Content) and 2.4.4 (Link Purpose (In Context)). We plan to ensure that all buttons have meaningful text by 31 May 2026.
  • Some autocomplete elements have no labels. This fails WCAG 2.2 success criteria 1.1.1 (Non-Text content), 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels), and 3.3.2 (Label or Instructions). We plan to ensure that all form elements have appropriate labels by 31 May 2026.
  • Some parts of the site skip heading levels (including Heading 1), and some headings have a visual appearance different from their assigned heading level. This fails WCAG 2.2 success criteria 1.3.1 (Info and Relationships), 2.4.1 (Bypass Blocks), and 2.4.6 (Headings and Labels). We plan to ensure that all headings follow a clear structure and are coded correctly by 31 May 2026.
  • Some forms fail to indicate which fields are mandatory and which are optional. This fails WCAG 2.2 success criteria 1.3.1 (Info and Relationships) and 3.3.2 (Label or Instructions). We plan to ensure that all forms indicate mandatory and optional fields by 31 May 2026.
  • The reading order of the main navigation area doesn't match the visual layout. This fails WCAG 2.2 success criterion 1.3.2 (Meaningful Sequence). We plan to ensure that, by 31 May 2026, all parts of the site will provide a reading order that matches the visual layout.
  • Some parts of the site cannot be operated via keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard) and 2.4.1 (Bypass Blocks). We will ensure that all parts of the site can be operated via keyboard by 31 May 2026.
  • Some links have no names, some have names that don't indicate or don't match the link's purpose, and some pages have multiple links/buttons with the same name. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)). We plan to ensure that all links and buttons have meaningful and accurate names by 31 May 2026.
  • Some elements do not provide a clear and consistent visual indication of when they have focus. This fails WCAG 2.2 success criteria 2.4.7 (Focus Visible) and 2.4.7 (Consistent Identification). We plan to ensure that, by 31 May 2026, all elements will provide a clear and consistent visual indication of when they have focus.

What we’re doing to improve accessibility

These websites and mobile application underwent a full third-party accessibility audit on 3 February 2026, and this accessibility statement has been prepared to reflect its results. We are working to correct the issues the audit found.

We are continually working to improve the accessibility of our website. We conduct regular accessibility audits and inclusive usability testing, and we act on their findings. We learn from these audits and other accessibility information, and we continually apply new knowledge to all updates we make.

Audit Methodology and Statement Preparation

This statement was prepared on 13 February 2026. It was last reviewed on 20 February 2026.

This website was last tested via audit on 3 February 2026 against the WCAG 2.2 AA standard.

The audit was carried out by Nexer Digital Ltd.

We chose the pages to test from a list of key pages approved by the Escode team. We tested the following pages:

  1. Homepage: https://www.escode.com/
  2. Main Navigation: The top navigation bar that is visible across all pages.
  3. Cookie Preferences: Pop-up window
  4. Products: https://www.escode.com/products/
  5. Logo and Colour Palette [Brand Guidelines]: https://www.escode.com/escode-logo-and-colour-palette/
  6. Sample Agreements: https://www.escode.com/software-escrow/software-escrow-agreement-sample/
  7. Resources: https://www.escode.com/resources/
  8. Blog post: https://www.escode.com/resources/bridging-the-confidence-gap-turning-assumptions-into-evidence-in-saas-supply-chains/
  9. Why Escode? [About Us]: https://www.escode.com/about-escode/
  10. FAQs: https://www.escode.com/frequently-asked-questions/
  11. Introduction to Software Escrow: https://www.escode.com/introduction-to-software-escrow/
  12. Contact Us: https://www.escode.com/contact-us/
  13. Careers: https://www.escode.com/careers-at-escode/
  14. Web Chat: [no URL available]
  15. Search: In Main Navigation
  16. Search Results: https://www.escode.com/search/?q=test&p=1#search

We did a quick check of many other pages, but not in enough depth to call it an audit.  

The audit used the Web Content Accessibility Guidelines V2.2, levels A and AA, to determine how well the Escode website meets the WCAG standard.  

Skip to navigation Skip to main content Skip to footer