Skip to content
https://redbullshop.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
8 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 8 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
8 of 8 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error, page does not exist ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
15 icon(s) detected
REVIEW
15 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

4 pass 16 fail WCAG AA 4 pass AA only
h1 Ready up for the Miami GP
1.18:1
#000000
on
#15181E
needs 3.0:1 (large text)
32px · above the fold · over background image/gradient
h1 Fearless in Black
1.13:1
#000000
on
#0D131B
needs 3.0:1 (large text)
32px · above the fold
h1 Ready to Ride
1.09:1
#000000
on
#060F18
needs 3.0:1 (large text)
32px · mid-page
h2 End of Season Sale
2.03:1
#000000
on
#37414D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Playoffs Collection
2.03:1
#000000
on
#37414D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Season Sale
2.03:1
#000000
on
#37414D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 End of Season Sale
2.03:1
#000000
on
#37414D
needs 3.0:1 (large text)
24px · bottom of viewport
title Official Red Bull Online Shop | Be Part …
4.48:1
#000000
on
#6D757A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Sale
1.58:1
#000000
on
#392D26
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div Teams/Events
1.44:1
#000000
on
#242932
needs 4.5:1 (normal text)
16px · above the fold
p Buy any Miami GP Cap and get 25% off the…
1.03:1
#000000
on
#010509
needs 4.5:1 (normal text)
16px · above the fold
a Discover now
1.03:1
#000000
on
#02060A
needs 4.5:1 (normal text)
16px · above the fold
p The new Red Bull Ring Black Collection i…
1.11:1
#000000
on
#0A111A
needs 4.5:1 (normal text)
16px · above the fold
a Discover now
1.09:1
#000000
on
#080F19
needs 4.5:1 (normal text)
16px · mid-page
p With The New Red Bull SPECT Cycling Styl…
1.15:1
#000000
on
#0C1621
needs 4.5:1 (normal text)
16px · mid-page
a Discover now
1.21:1
#000000
on
#101B26
needs 4.5:1 (normal text)
16px · mid-page

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Ready up for the Mia…1.18:13.0:1
#000000
#15181E
Fail
h1 Fearless in Black1.13:13.0:1
#000000
#0D131B
Fail
h1 Ready to Ride1.09:13.0:1
#000000
#060F18
Fail
h2 End of Season Sale2.03:13.0:1
#000000
#37414D
Fail
h2 Playoffs Collection2.03:13.0:1
#000000
#37414D
Fail
h2 Season Sale2.03:13.0:1
#000000
#37414D
Fail
h2 End of Season Sale2.03:13.0:1
#000000
#37414D
Fail
title Official Red Bull On…4.48:14.5:1
#000000
#6D757A
Fail
a New Arrivals5.49:14.5:1
#000000
#7D838A
Pass
div Jerseys5.84:14.5:1
#000000
#878786
Pass
div Apparel6.11:14.5:1
#000000
#978879
Pass
div Accessories6.14:14.5:1
#000000
#9C8775
Pass
a Sale1.58:14.5:1
#000000
#392D26
Fail
div Teams/Events1.44:14.5:1
#000000
#242932
Fail
p Buy any Miami GP Cap…1.03:14.5:1
#000000
#010509
Fail
a Discover now1.03:14.5:1
#000000
#02060A
Fail
p The new Red Bull Rin…1.11:14.5:1
#000000
#0A111A
Fail
a Discover now1.09:14.5:1
#000000
#080F19
Fail
p With The New Red Bul…1.15:14.5:1
#000000
#0C1621
Fail
a Discover now1.21:14.5:1
#000000
#101B26
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 23 passed
REVIEW
84

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#CMSMiniCartPopupComponent-6 > div.cf1814aab0e92211666c > div.b20c5839078f07325c61 > button.btn-reset div#CMSMiniCartPopupComponent-6 > div.cf1814aab0e92211666c > div.b20c5839078f07325c61 > button.btn-reset

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.a3add2b291915cd6411e > div.f65dfbc615e9dbc3d366 > div.b26d86dde9a74bb0016e > a div.a3add2b291915cd6411e > div.f65dfbc615e9dbc3d366 > div.b26d86dde9a74bb0016e > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Men div.product-tile > a > div.b2cc51cd3b150524a14a > div.c63f784317a69f75e108
Men div.product-tile > a > div.b2cc51cd3b150524a14a > div.c63f784317a69f75e108
Men div.product-tile > a > div.b2cc51cd3b150524a14a > div.c63f784317a69f75e108
15% voucher div.f3da4f4124cb351ee9dc > div.eef68344034129b3fd08 > span > strong
© AlphaTauri GmbH 2026 div.b75e15c78ce169f39297 > div.d3ce52fbc967f6d07450 > div.a78e569cca48bc27f808 > span.a2b2600f76513996600e
© AlphaTauri GmbH div.d3ce52fbc967f6d07450 > div.a78e569cca48bc27f808 > span.a2b2600f76513996600e > span

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Heading Hierarchy
7 headings
PASS
7 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Ready up for the Miami GP
  • H1 Fearless in Black duplicate H1
  • H1 Ready to Ride duplicate H1
  • H2 End of Season Sale
  • H2 Playoffs Collection
  • H2 Season Sale
  • H2 End of Season Sale

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 113 images OK
PASS
All 113 images OK
Info::
49 decorative image(s) correctly marked
Info::
64 image(s) with good alt text
113 images 64 good alt text 49 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputemailemail for newsletteraria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback