Accessibility Statement
Last Update:
| Organisation: LYNX |
| LYNX B.V. |
| Contact: info@lynxbroker.com |
This accessibility statement applies to: https://www.lynxbroker.com/ and is managed by LYNX B.V.
Our goal is to make the website 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:
- Navigate most of the website also when using a keyboard or speech recognition software.
- Adjust the colors, contrast, and fonts using your browser or device settings.
- Use screen readers to access most content on desktop, laptop, mobile, and tablets.
- We also focus on writing content of the website in plain language to make it easier to understand.
We are actively working to improve the accessibility of our website 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:
- WebTrader LYNX+: A proprietary, web-based trading platform developed by LYNX. It integrates with Interactive Brokers’ execution and data infrastructure and offers a streamlined interface designed for intuitive use, including multilingual support.
- Client Portal (Interactive Brokers): A secure environment maintained by Interactive Brokers, where clients can manage their account information, retrieve statements and tax documents, upload verification documents, and initiate deposits or withdrawals.
- TWS and Interactive Brokers Mobile App: Advanced trading tools developed by Interactive Brokers, also available to LYNX clients depending on their trading needs and experience level.
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:
- Identity verification (KYC)
- Customer due diligence (CDD)
- Regulatory compliance checks
- Risk rating assignment
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:
- Instrument search, price data (via Interactive Brokers), and order placement
- Real-time account and portfolio data
- Multilingual interface and customizable layout
- Portfolio tracking, order history, and performance overview
- Trade execution routed through Interactive Brokers infrastructure
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
| Operating System | Description |
|---|---|
| Windows | You can activate:
|
| macOS | You can enable:
|
| iOS (iPhone/iPad) | Navigate to Settings > Accessibility to enable:
|
| Android | You can use:
|
3.1.2 Browsers
| Browsers | Description |
|---|---|
| Chrome | Supports extensions like Screen Reader (ChromeVox) and High Contrast, and respects OS-level zoom or color preferences. |
| Firefox | Offers advanced zoom, caret browsing, and ARIA landmark support. |
| Edge and Safari | Fully compatible with system accessibility tools and support reader modes. |
3.1.3 Accessibility Settings Guidance
For tailored accessibility guidance, see:
3.2 Adjusting System Preferences
Our website aims 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:
- User-controlled preferences
- Color Contrast Themes: Options like Dark Mode, High Contrast, or Soft Contrast help improve readability.
- Keyboard Navigation Support: Full support for tabbing, arrow key movement, and visible focus indicators.
- Accessibility Profiles
- Reduced Motion Mode: Minimizes animations and transitions for users with motion sensitivity.
- Screen Reader Optimized Mode: Structures content for improved compatibility with assistive technologies.
- Alternate Platform Modes
- Keyboard-Only Mode: Full application functionality via keyboard, including skip links and focus order.
- Mobile & Touch Accessibility: Optimized compatibility with screen readers and accessibility tools on iOS and Android.
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:
| Tools | Description |
|---|---|
| Screen Readers |
|
| Magnification and Visual Tools |
|
| Speech-to-Text Tools |
|
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.
- Directives: Are legal requirements, often set by governments or international bodies, that mandate how accessibility must be addressed in digital products and services.
- Standards: Define technical criteria, such as WCAG 2.1, that must be met to ensure accessibility for users with disabilities.
- Guidelines: Provide recommended practices and techniques to help designers, developers, and organizations implement accessibility effectively and consistently.
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:
- EN 301 549: The EU standard that defines ICT accessibility requirements, harmonized with the EAA.
- WCAG AA: The Web Content Accessibility Guidelines (WCAG) 2.1 AA and 2.2 AA represents the global benchmark for web accessibility.
- WAI ARIA: The Web Accessibility Initiative – Accessible Rich Internet Applications (WAI-ARIA) is a technical specification that defines ways to make dynamic content and advanced user interface controls accessible to people using assistive technologies by adding semantic information to HTML.
- ISO 30071-1: This process standard is a holistic approach to the accessibility of information and communications technology (ICT) by combining guidance on implementing the accessibility on both the organizational and system development levels.
4.3 Compliance
This website audit is outsourced to Funka.com.
At this moment the website is 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 site 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 this website by maintaining an accessibility activities log 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 Our Commitment
We are committed to ensuring no user is excluded due to disability by delivering inclusive accessibility features, documenting and justifying any limitations transparently, and providing effective alternatives to guarantee equitable access for all.
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:
- Email: info@lynxbroker.com
- Contact Form: Submit an idea, challenge, or request
- Phone: +31 (0)20 6251524. (Available Monday to Friday, from 8:00 a.m. to 10:00 p.m.)
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:
- The page or view where you found a problem.
- A brief description of the issue.
- The device and browser or assistive technology used.
- Screenshots or recordings of the pages or views, if helpful.
- The date and time you experienced the problem.
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.
Important Reminder!
For your safety and privacy, never share sensitive information like passwords in emails or messages. Only provide details you are comfortable sharing and that are necessary for your request.
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):
- https://www.example.org/about/team
- http://www.example.org/products/view-item?id=1234
Examples of website page descriptions
- “The ‘Portfolio Overview’ page under ‘Dashboard’, where my investment holdings and performance are summarized.”
- “The trade confirmation screen that appears after I submit a buy order for stocks.”
- “The ‘Account Settings’ page where I tried to update my contact information.”
Examples for native apps:
- “On the mobile app’s home screen, where my portfolio balance and key market indices are displayed.”
- “In the ‘Trade’ section of the app, while entering order details for buying shares.”
- “On the ‘Order Preview’ screen right before submitting a limit order.”
Examples of digital documents
- “In the PDF statement, on page 2 under the heading ‘Quarterly Portfolio Performance’.”
- “In the Word document titled ‘Client Meeting Notes – Q1’, in the section outlining investment decisions.”
- “In the Excel file, under the ‘Dividend History’ tab, column C showing payout dates.”
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:
- What you were trying to accomplish
- What happened instead
- How it made the experience difficult or impossible
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:
- Your operating system and version (e.g. Windows 11, macOS Ventura, Ubuntu 22.04)
- Your web browser and version (e.g. Chrome 114, Safari 16, Firefox 102, Microsoft Edge)
- Any special settings you’ve changed (e.g. larger font size, high contrast mode)
- Any assistive tools you use (e.g. screen reader, magnifier, voice control, alternative keyboard or mouse)
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:
- A screenshot or video of the problem area
- Any error messages, missing labels, or confusing layout you noticed
- Any assistive technology (e.g., screen reader) running at the time
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:
- Any workarounds you tried
- How the issue affected your tasks
- Any assistive technology in use
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:
- Request escalation by emailing info@lynxbroker.com with “Escalation Request” in the subject line.
- Contact the national accessibility authority or relevant regulatory body (e.g., the Netherlands Institute for Human Rights (College voor de Rechten van de Mens) or The Netherlands Authority for the Financial Markets (De Autoriteit Financiële Markten – AFM).
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
- European Accessibility Act info – European Accessibility Act
- European Accessibility Act – Directive (EU) 2019/882 of the European Parliament
A2.2 Standards and Guidelines
- Accessibility requirements for ICT products and services – EN 301 549
- Web Content Accessibility Guidelines (WCAG) 2.1 AA – W3C WCAG 2.1
- Web Content Accessibility Guidelines (WCAG) 2.2 AA – W3C WCAG 2.2
- ISO version of WCAG 2.0 AA – ISO/IEC 40500:2012
- Accessible Rich Internet Applications (WAI-ARIA) – W3C WAI ARIA 1.2
- Information technology — Development of user interface accessibility – Part 1: Code of practice for creating accessible ICT products and services – ISO 30071-1
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.