Accessibility Statement

This accessibility statement applies to:

and is managed by LYNX B.V.

Our goal is to make the websites accessible and inclusive to as many people as possible.

We recognize the importance of an accessible digital environment and are committed to ensuring equal access for all users.

This means you should be able to:

We are actively working to improve the accessibility of our websites and aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, in line with the European standard EN 301 549.

Despite our ongoing efforts, some parts of the website may not yet be fully accessible.

We are working to address these limitations and will update this statement as improvements are made.

Your feedback is valuable and helps us make further progress, please don’t hesitate to contact us if you encounter any issues or have suggestions.

1. Purpose

The purpose of this accessibility statement is to provide clear information and practical guidance on the accessibility of this website and how users can maximize the accessibility according to their individual needs.

The statement also explains how you get the most accessible experience, how to get into contact, how we manage known accessibility limitations, and outlines our ongoing plans for improvement.

2. General description of the service

LYNX operates as an introducing broker, facilitating client access to global financial markets through the infrastructure of Interactive Brokers.

2.1 Which services are involved

While the underlying trading and account systems are provided by Interactive Brokers, LYNX develops and maintains its own trading platform “WebTrader LYNX+” to deliver an optimized and localized experience tailored to the needs of our clients.

Clients onboarding via LYNX gain access to the following digital environments:

2.2 How does the service work and which products are included

2.2.1 Access and Onboarding

Clients begin the onboarding process directly via the LYNX website. LYNX is responsible for handling the complete onboarding journey, including:

Once these checks are successfully completed and the application is approved internally, LYNX initiates the account creation within the infrastructure of Interactive Brokers.

As part of this process, Interactive Brokers conducts a mandatory Client Account Protection (CAP) check prior to final activation.

Once the account is fully approved, clients receive login credentials for the digital platforms relevant to their use, including WebTrader LYNX+, the Client Portal, TWS (Trader Workstation) and the Mobile App.

2.2.2 Platform Operation

WebTrader LYNX+ is tailored to offer a simplified and localized trading experience.

Its core functionality includes:

Clients may also choose to use the Interactive Brokers Client Portal, TWS, or Mobile App, depending on their personal preference or platform needs.

2.2.3 Customer Support and Interaction

LYNX provides localized and multilingual customer support through live chat, phone, and email.

Our support teams assist clients with navigating the platforms, resolving account-related questions, and explaining procedures.

If a request involves system components or compliance matters directly managed by Interactive Brokers, LYNX may coordinate with Interactive Brokers to provide a resolution on behalf of the client.

3. How you get the most accessible experience

This section outlines how you can get the most accessible experience when using an ICT system by customizing it to meet your individual needs.

It covers the use of accessibility controls available in operating systems, browsers, and hardware, as well as any built-in customization options the system provides.

3.1 Customizing Accessibility Settings

You can improve your experience by enabling accessibility settings available in your operating system, web browser, and hardware.

These settings support you with visual, auditory, motor, or cognitive impairments.

3.1.1 Operating Systems

3.1.2 Browsers

3.1.3 Accessibility Settings Guidance

For tailored accessibility guidance, see:

3.2 Adjusting System Preferences

Our websites aim to support a range of customization options, such as adjusting font size, contrast, or navigation settings to better align with individual accessibility needs.

We recognize how important this is and are actively working to expand and improve support for system and user preferences.

Providing a flexible and inclusive experience is a priority for us, and we continue exploring ways to better accommodate diverse user requirements, like:

3.4 Using Third-Party Tools for Enhancement

Our system partially supports integration with widely used assistive technologies, allowing you to personalize their setup using tools they already know.

Commonly supported tools include:

To explore more assistive tools or get tutorials on using them, visit: W3C WAI List of Accessibility Tools.

We have set goals to improve the compatibility with ARIA landmarks, semantic HTML, and WAI-ARIA roles, improving the reliability of screen reader interpretation.

4. Directives, Standards, and Guidelines

Accessibility is supported by a framework of directives, standards, and guidelines that together ensure digital products and services are usable by everyone, including people with disabilities.

References can be found at Annex A.

4.1 Directives

The European Accessibility Act (EAA) mandates that digital products and services provided in the European Union (EU) are accessible to people with disabilities.

By adhering to this directive, LYNX will ensure compliance with EU regulations and demonstrates our commitment to creating an inclusive digital experience that aligns with the principles of a Design For All approach.

4.2 Standards and Guidelines

Accessibility standards are guidelines that help ensure digital environments are usable by everyone, including people with disabilities and the elderly.

Based on the goals and vision of LYNX, standard conformance goals are set for:

4.3 Compliance

The websites audits are outsourced to Allxs.tech.

At this moment, the websites are partially compliant.

We recognize that not all content or functionality fully meets accessibility standards yet, but we are actively working to address these limitations.

Improving accessibility is a priority for us, and we are continuously updating the sites to better align with WCAG 2.2 Level AA and the European standard EN 301 549.

We welcome feedback to help us identify and resolve the remaining barriers.

5. Accessibility and Improvements

5.1 Accessibility Log

At LYNX we keep track of the accessibility of these websites by maintaining accessibility activities logs based on the ISO 30071-1 standard methodology.

The log organizes key requirements into actionable, accessibility-focused activities to ensure ongoing compliance and inclusivity.

Detailed information can be found at Annex B.

5.1.1 The purpose of our accessibility activities log

“To keep a clear record of all accessibility decisions made during the website’s life, so it’s easy to track changes, know who was responsible, and keep improving the experience for all users.”

5.1.2 The first 5 activities

The first 5 activities of our log lead to the inclusion of accessibility requirements into ICT development.

5.1.3 The last 3 activities

The last 3 activities of our log lead to ensuring that the required activities are carried out.

5.2 Accessibility Status

While our accessibility log tracks our ongoing procedural milestones, this section provides a transparent snapshot of the live user experience across our digital platforms.

We celebrate where we have successfully removed barriers, but we are equally committed to open accountability regarding our gaps.

By mapping out our current limitations alongside concrete remediation timelines and temporary workarounds, we ensure that users with disabilities are supported today while we build a more inclusive tomorrow.

5.2.1 What we did already

This subsection highlights the proactive features we have successfully implemented to ensure equitable access.

By building in features like flexible inputs and simple navigation, we ensure our platform works for everyone.

When limitations occur, we commit to transparency and provide effective alternatives, so no user is left behind.

Detailed information can be found at Annex C.

5.2.2 Identified Accessibility issues

True inclusivity requires honesty about where we fall short.

This subsection details our known accessibility limitations with direct impact on the user experience.

Detailed information can be found at Annex C.

6. Contact us for feedback or information

If you have questions about the accessibility of this application, or if you’d like to share a suggestion, make a comment, or lodge a complaint, we’re here to help.

You can contact us using the options below to get more information or let us know how we can improve your experience.

6.1 Getting Support from Others

If you’re having trouble identifying or describing an accessibility issue, consider reaching out to someone you trust such as a friend, family member, colleague, or support worker for help.

They may assist in understanding whether the issue relates to the website, your device settings, or any assistive technology you use.

You can also ask them to help contact the website owner on your behalf.

Alternatively, our organization may be able to support you in explaining the problem and ensure your concerns are heard.

6.2 Available Contact Methods

6.2.1 Primary Contact Options

You can reach our Accessibility Support Team through the following methods:

6.3 Guidelines for Submitting Feedback

6.3.1 Requesting Further Information

If you’d like more details about accessibility features, design decisions, or current limitations in our system, please contact us through any method above.

We can also provide links to technical documentation or additional support materials upon request.

6.3.2 Providing Suggestions or Reporting Issues

We welcome feedback and suggestions.

When reporting an accessibility issue, please try to include:

After sending you will automatically receive a confirmation of receipt.

Even if you only know a little, that’s perfectly fine. Just tell us what you can!

We aim to respond within 5 business days.

6.3.2.1 The page, view, or document where you found a problem

Please include the exact location or a clear description of where the issue occurred. This helps us understand and address your feedback more effectively.

Examples of website addresses (URLs):

Examples of website page descriptions

Examples for native apps:

Examples of digital documents

6.3.2.2 A brief description of the issue

Tell us what you were trying to do, and what made it difficult.

Understanding what task you were attempting—and why it didn’t work—helps us fix the issue.

Please describe:

6.3.2.3 The device and browser or assistive technology used

Sharing some basic information about your computer and software can help us understand and fix accessibility issues more effectively.

If you’re not sure about the details, you can ask someone you trust, like a friend, family member, or coworker, for help.

But don’t worry: if you’re unsure, you can still submit your feedback without this part.

Please include any of the following that you know:

6.3.2.4 Screenshots or recordings of the pages or views, if helpful

If you’re comfortable, include a screenshot or screen recording that shows the part of the page where the issue happened.

This helps us see exactly what you saw.

Please include:

Don’t worry if you can’t include a screenshot, your written description is still valuable!

6.3.2.5 Anything else you would like to share

Feel free to include any additional details that might help us understand your experience.

Please include:

6.3.2.6 The date and time you experienced the problem

Knowing when the issue occurred helps us understand the context—such as which version of the system was running or whether it was during a system update.

Please provide the date and time as accurately as possible.

6.3.2.7 Writing us an email

If you’ve encountered an accessibility issue or have a suggestion to help us improve, you can let us know by email.

Your feedback helps us make our services more usable for everyone.

Please include as many details as you’re comfortable sharing so we can better understand and address the issue.

Email Template

Email Example

6.4 Handling and Response Process

6.4.1 Processing of Accessibility Feedback

All feedback is reviewed by our Accessibility Coordinator and categorized by urgency and impact.

Identified issues are logged, tracked, and used to inform future updates and improvements to our system.

6.4.2 Escalation and Follow-Up Options

If you are not satisfied with our response, you may:

Annex A

A1 Directives and Standards Reference

Based on the European Accessibility Act (EAA) and the goals and vision of LYNX the following compliance and conformance information can be found at:

A2.1 Directives

A2.2 Standards and Guidelines

Annex B

B1 Accessibility Log

This section outlines a summary on the inclusion of accessibility activities of the website, highlighting how accessibility has been considered during development.

B1.1 We specified the following

B1.1.1 Widest range of potential users

The website will be developed to include the widest possible range of users by ensuring no one is excluded due to disability, transparently justifying any accessibility limitations, and addressing diverse needs through inclusive design, alternative access, accommodation processes, and user consultation during procurement and development.

B1.1.2 User goals and tasks

The organization is defining and prioritizing user goals and tasks by distinguishing core from non-core activities, incorporates context-specific constraints such as device or assistive technology limitations, and will ensure these factors guide accessible design decisions.

B1.1.3 User accessibility needs

The organization will identify user accessibility needs to guide all design and development decisions, aligning with accessibility standards and legislation, applying technical, effective, efficient, and satisfying criteria for user goals, and documenting where only technical accessibility is feasible.

B1.1.4 Accessibility requirements

The organization will evaluate user accessibility needs and transform them into clear accessibility requirements with defined outcomes, success criteria, and conditions, ensuring these are understandable by developers and explicitly referenced in procurement documentation and contracts.

B1.1.5 Accessibility design approach

The organization will apply an inclusive design approach supported by user-personalization where appropriate, ensuring accessibility across device types, development tools, and assistive technology combinations, with clear boundaries and a consistent user experience.

B1.2 We ensured the following

B1.2.1 Accessibility requirements are met

The organization will ensure accessibility requirements are met by embedding accessibility testing into system test plans, justifying chosen methods, allocating resources for remediation, requiring developer adherence, and balancing launch timing decisions against accessibility risks.

B1.2.2 Communication about accessibility

The organization will plan clear communication about accessibility at launch by creating and publishing a detailed accessibility statement that transparently documents both the system’s accessibility features and any known issues.

B1.2.3 Ensuring integration of accessibility in system updates

The organization will ensure ongoing accessibility by maintaining regular post-launch monitoring and testing, promptly addressing pre-launch issues within set timelines, considering accessibility impacts in release schedules, and actively monitoring and responding to user feedback.

Annex C

C1 Accessibility Status

This section outlines a summary of the inclusion of accessibility activities on the websites.

C1.1 What we did already

C1.1.1 Marketing Website

C1.1.2 DOF

C1.2 Identified Accessibility issues

C1.2.1 Marketing Website

C1.2.2 DOF