Accessibility Statement

Accessibility Statement ‍Last updated on: 20 April 2026.

We are committed to ensuring digital accessibility for all users, in line with the obligations under Regulation (EU) 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies and the applicable European Union Accessibility Act (EUAA) framework. This Accessibility Statement explains the accessibility measures we implement, the standards we aim to meet (including the Web Content Accessibility Guidelines or WCAG), our compliance status, and the steps we take to address known limitations. It also outlines your rights, the feedback and enforcement mechanisms available to you, and how you can contact us regarding accessibility.

1. Measures to support accessibility

Rise Global BV takes the following measures to ensure accessibility of ANY:

  • Include accessibility throughout our internal policies.

  • Integrate accessibility into our procurement practices.

  • Assign clear accessibility goals and responsibilities.

  • Employ formal accessibility quality assurance methods.

‍2. Conformance status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. ANY is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

The main known non‑conformances are:

  1. Colour contrast (WCAG 1.4.3)

    Certain text and user interface elements do not yet reach the required contrast ratio of 4.5:1 for normal text (or 3:1 for large‑scale text), which can make them harder to perceive for users with low vision.

  2. Hero video and motion (WCAG 2.2.2, 2.3.1)

    The hero background video does not currently provide direct controls to pause, stop or hide animated content, and may contain fast motion or flashing that some users cannot fully disable. Users must rely on browser or operating‑system level motion‑reduction settings.

  3. Landmarks and regions (WCAG 2.4.1)

    In some page templates, and in certain third‑party components (such as the cookie‑consent interface), aside and region areas are not consistently provided with clear accessible names or have labels that are not wired correctly. This can make landmark navigation less efficient for screen reader users, although the content remains reachable.

  4. Parsing and technical markup (WCAG 4.1.1)

    On some pages, non‑unique element IDs and obsolete iframe attributes are present. A part of this markup is injected by third‑party components (such as the cookie‑consent platform), which we do not fully control. These technical issues generally do not prevent keyboard or screen‑reader use but do not fully satisfy the parsing requirements of the standard.

Accessibility is checked using a combination of automated checks and manual testing, including keyboard navigation, screen‑reader spot‑checks, and zoom/reflow testing. Remediation work on shared components (colours, layout and landmarks, embeds, and the configurator layout) is planned so that improvements apply consistently across the site.

3. Feedback

We welcome your feedback on the accessibility of ANY. Please let us know if you encounter accessibility barriers on ANY:

We try to respond to feedback within 14 business days.

4. Compatibility with browsers and assistive technology

ANY is designed to be compatible with the following assistive technologies:

  • Google Chromium based browsers + NVDA on Windows 10/11

  • Google Chromium based browsers + JAWS on Windows 10/11

  • Mozilla Firefox + NVDA on Windows 10/11 and macOS Ventura or later

  • Apple Safari + VoiceOver on macOS Ventura or later

  • Google Chromium based browsers + VoiceOver on macOS Ventura or later

  • Apple Safari + VoiceOver on iOS 16.0+

  • Google Chromium based browsers + TalkBack on Android 12.0+

  • Samsung Internet + TalkBack on Android 12.0+

‍ANY is not compatible with:

  • Browsers older than 3 major versions: Chrome/Edge < version 123 (current - 3) Firefox < version 123 (current - 3) Safari < version 16

  • Mobile Operating Systems: iOS < 16.0 (released September 2022) Android < 12.0 (released October 2021)

  • Internet Explorer 11 (not supported) Safari < 16 Browsers that don't support ES2020 features

5. Technical specifications

Accessibility of ANY relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML

  • WAI-ARIA

  • CSS

  • JavaScript

  • Webflow

  • Tally

These technologies are relied upon for conformance with the accessibility standards used.

6. Limitations and alternatives

Despite our best efforts to ensure accessibility of ANY, there may be some limitations. Below is a description of known limitations and, where applicable, potential workarounds. Please contact us if you observe an issue that is not listed here.

Known limitations for the ANY website include, but are not limited to:

  • Hero section video controls and motion:

    The background video in the hero section may not offer direct on‑page controls to pause, stop or hide the animation, and may include motion or flashing that some users find uncomfortable. As a partial workaround, users can enable “reduce motion” or similar settings in their operating system or browser and use content blockers where available.

  • Third‑party components:

    Certain third‑party services (for example, the cookie‑consent platform and embedded forms) inject their own markup and behaviors. In some cases this may result in extra or unlabeled landmark regions, parsing quirks or slightly inconsistent focus behaviour. We regularly review these integrations and raise issues with vendors where we identify accessibility impacts.

We are continuously working to improve the accessibility of ANY and to reduce or remove these limitations over time.

7. Assessment approach

Rise Global BV assessed the accessibility of ANY by the following approaches:

  • Self-evaluation

  • A formal quality assurance process throughout the design and development process with Figma, Webflow, Stark Accessibility, Google Lighthouse and IBM Equal Access Accessibility Checker.

8. Evaluation report

An evaluation report for ANY is available at request

9. Formal complaints

You can send complaints to: support@rideany.com