Skip to main content

Accessibility Statement

Accessibility · Last updated 15 October 2026

How we are working to make ComplyEur usable by people of all abilities, and how to tell us when something gets in the way.

1. Our Commitment

ComplyEur is committed to ensuring digital accessibility for people of all abilities. We believe that everyone should have equal access to information and functionality on our platform, regardless of any disabilities or impairments.

We use accessibility standards to guide improvements and test key user journeys. The known limitations below describe areas that still need work.

2. Accessibility Standards

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards. These guidelines explain how to make web content more accessible for people with disabilities, and more user-friendly for everyone.

The guidelines have three levels of accessibility (A, AA, and AAA). We have chosen Level AA as our target as it addresses the major accessibility barriers while remaining achievable for our application type.

3. What We're Doing

We use the following practices to improve accessibility. These are design goals, rather than a claim that every page or interaction has passed an independent audit:

Semantic HTML

  • We use proper HTML elements to convey meaning and structure
  • Headings are used in a logical, hierarchical order (H1, H2, H3)
  • Lists are marked up using appropriate list elements
  • Form fields are properly labeled and associated with their labels

Keyboard Navigation

  • We design interactive elements for keyboard access; known calendar limitations are listed below
  • Focus indicators are visible when navigating with a keyboard
  • Tab order follows a logical sequence through the page
  • Skip links allow users to bypass repetitive navigation

Visual Design

  • We aim for WCAG 2.1 AA colour contrast, including at least 4.5:1 for normal text
  • Information is not conveyed by color alone
  • We aim to support text resizing up to 200% without loss of content or functionality
  • We aim for touch targets of at least 44 by 44 pixels where practical

Forms and Inputs

  • All form fields have clear, descriptive labels
  • Error messages are clear and provide guidance on how to fix issues
  • Required fields are clearly indicated
  • Form validation messages are announced to screen readers

Screen Reader Compatibility

  • ARIA attributes are used where necessary to enhance accessibility
  • Dynamic content updates are announced to assistive technologies
  • Images have appropriate alt text descriptions
  • Icons used for functionality have accessible labels

4. Known Limitations

While we strive to make ComplyEur as accessible as possible, some areas may have limitations. We are actively working to address these:

  • Calendar view: The interactive calendar for viewing travel dates may have limited keyboard navigation in some complex scenarios. We are working on improving this functionality.
  • Data tables: Some complex data tables may not be fully optimized for screen readers. We are reviewing and enhancing table markup.
  • Third-party content: Some third-party integrations (such as payment processing) may have their own accessibility limitations outside our direct control.

We are committed to addressing these limitations as part of our ongoing accessibility improvement efforts.

5. Feedback and Contact

We welcome your feedback on the accessibility of ComplyEur. If you encounter any accessibility barriers or have suggestions for improvement, please let us know:

When Contacting Us

To help us address your feedback effectively, please include:

  • A description of the accessibility issue you encountered
  • The page or feature where the issue occurred
  • The assistive technology you were using (if applicable)
  • Your browser and operating system

Our Ongoing Commitment

Accessibility is an ongoing effort. We regularly review our platform to identify and fix accessibility issues. We include automated accessibility checks and keyboard testing in our development process.

Related Documents