Accessibility Information The company defined in the imprint (hereinafter referred to as "We" or "Our" or "Us") is committed to making its digital services on its mobile app Red Bull TV hereinafter referred to as the "Offer") accessible, in accordance with Directive (EU) 2019/882 on accessibility requirements for products and services (hereinafter referred to as the "EAA"). The implementation of the accessibility requirements is based on the guidelines for accessible web content – WCAG 2.1. The Offer provides information about the products of Red Bull GmbH, events, and offers the audiovisual media service Red Bull TV. Non-accessible content The content listed below, which is subject to accessibility requirements, is currently either not accessible or only partially accessible:

• WCAG Success Criterion 1.1.1 Non-text Content
  Some images and buttons do not have alternative texts, or the alternative text does not contain a description of the specific image.
• WCAG Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)
  Some videos on the app do not have a subtitle, which means that deaf users cannot understand the content.
• WCAG Success Criteria 1.2.2 and 1.2.4 Captions (Prerecorded and Live)
  For some videos, closed captions may not be available.
• WCAG Success Criterion 1.3.1 Info and Relationship
  Some buttons act as empty buttons, providing no information to screen readers.
• WCAG Success Criterion 1.3.2 Meaningful Sequence
  The order of the content may not correspond to the visual representation, which will be confusing for screen reader users.
• WCAG Success Criterion 1.3.4 Orientation
  Some parts of the app are designed to work in portrait mode, which can be problematic for some users with motor impairments.
• WCAG Success Criterion 1.3.5 Identify Input Purpose
  Some forms may not use appropriate tags or attributes to indicate the purpose of the input fields, making auto-filling difficult for users who rely on such features.
• WCAG Success Criterion 1.4.1 Use of Color
  Some forms may use color as the only visual means of conveying information, so colorblind users can't interpret the information.
• WCAG Success Criterion 1.4.3 Contrast (Minimum)
  Some images and text have contrast defects.
• WCAG Success Criterion 1.4.5 Images of Text
  Some images contain text without the appropriate contrast ratio which will be difficult for visually impaired users to read.
• WCAG Success Criterion 1.4.10 Reflow
  Certain text may be truncated when the user’s phone text and display sized is increased.
• WCAG Success Criterion 1.4.11 Non-text Contrast
  There are minor contrast deficiencies in images and forms.
• WCAG Success Criterion 1.4.12 Text Spacing
  The app may not allow any adjustment of the text spacing, which can be a hindrance for users with reading disabilities.
• WCAG Success Criterion 1.4.13 Content in Hover and Focus
  Tooltips may be present and cannot be closed with the keyboard. Screen readers do not reach the tooltips.
• WCAG Success Criterion 2.1.1 Keyboard
  Certain functionality on the app cannot be performed through a keyboard interface.
• WCAG Success Criterion 2.1.2 No Keyboard Trap
  Not all elements of this app are accessible through keyboard.
• WCAG Success Criterion 2.1.4 Character Key Shortcuts
  Keyboard shortcuts are not customizable and make it difficult to navigate for users who use other keyboard layouts.
• WCAG Success Criterion 2.2.1 Timing Adjustable
  Some forms have a strict time limit, after which all entered data is deleted, which is frustrating for slow writers.
• WCAG Success Criterion 2.2.2 Pause, Stop, Hide
  An automatically starting carousel on the homepage has no way to stop or pause playback.
• WCAG Success Criterion 2.3.1 Three Flashes or Below Threshold
  Some videos may contain fast-flashing effects that can potentially trigger seizures in people with photosensitivity.
• WCAG Success Criterion 2.4.1 Bypass Blocks
  Since the app menu is very short, we do not offer a skiplink to the content.
• WCAG Success Criterion 2.4.2 Page Titled
  In some forms, the page titles remain unchanged and do not describe the content of the page.
• WCAG Success Criterion 2.4.3 Focus Order
  On some screens, the focus order is not logical.
• WCAG Success Criterion 2.4.4 Link Purpose (In Context)
  For some links, the purpose of each link may not always be determined from the link text alone.
• WCAG Success Criterion 2.4.6 Headings and Labels
  Some screens may not have appropriate heading and labels.
• WCAG Success Criterion 2.4.7 Focus Visible
  Not all elements of this app are accessible through keyboard.
• WCAG Success Criterion 2.5.3 Label in Name
  Some buttons or links have visible labels that do not match the accessible name, which leads to confusion for users who rely on screen readers.
• WCAG Success Criterion 3.1.1 Language of Page
  Some screens of the app are missing the language tag.
• WCAG Success Criterion 3.1.2 Language of Parts
  Some sections of the app are missing the language attribute.
• WCAG Success Criterion 3.2.1 On Focus
  Not all elements of this app are accessible through keyboard.
• WCAG Success Criterion 3.2.2 On Input
  Some screens may initiate page loads or pop-ups without the user prompting the action.
• WCAG Success Criterion 3.2.4 Consistent Identification
  Different screens of the app may label similar features or content differently, which can cause confusion for users.
• WCAG Success Criterion 3.3.1 Error Identification
  Some forms may not display error messages when a user makes incorrect entries, so users will not know how to correct their entries.
• WCAG Success Criterion 3.3.2 Labels or Instructions
  In some forms, some input fields are not labeled correctly.
• WCAG Success Criterion 3.3.3 Error Suggestion
  Some forms do not provide a way to verify or confirm the information before submitting, which can lead to incorrect entries that are not easily corrected.
• WCAG Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data)
  Some sensitive data submission forms do not provide a way to verify or confirm the information before submitting, which can lead to incorrect entries that are not easily corrected.
• WCAG Success Criterion 4.1.2 Name, Role, Value
  Some buttons do not provide names, roles, and values which can cause difficulties for those that user screen readers.
• WCAG Success Criterion 4.1.3 Status Messages
  Some status messages may not be correctly labeled which can cause difficulties for those that user screen readers.

Creation of Accessibility Information This Accessibility Information was prepared on 31/03/2025 based on a WCAG 2.1 assessment conducted by Hilfsgemeinschaft der Blinden und Sehschwachen Österreichs, an independent third party specializing in web accessibility. Our Offer is regularly tested and improved to ensure that all content added or edited meets accessibility requirements. If you encounter any barriers that hinder or restrict your use and that do not comply with the applicable accessibility requirements, we kindly ask you to inform us via the following form https://feedback.redbull.com. In this case, please briefly describe the problem and include screenshots of the affected areas. We will process your message and contact you as soon as possible.