Public accessibility assessment

Accessibility issues detected on racket-company.de

Evolize inspected 5 publicly accessible pages on racket-company.de and detected 35 automatically identifiable accessibility findings. 10 findings were classified as critical or high priority. The findings map to 10 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve links lack accessible text, interactive controls are not keyboard-accessible, hidden elements can still receive keyboard focus.

35findings detected

10critical + high

5pages inspected

22 Aug 2026assessed

Independent public assessment. racket-company.de is not necessarily affiliated with or a customer of Evolize.

MONITOR THIS WEBSITE RUN A FREE ASSESSMENT

01 · Accessibility summary

02 · Priority findings

Critical Links lack accessible textWCAG 2.4.4 (A) · 1 page · 1 instance
High Interactive controls are not keyboard-accessibleWCAG 2.1.1 (A) · 5 pages · 9 instances
High Hidden elements can still receive keyboard focusWCAG 2.4.3 (A) · 5 pages · 27 instances
High Hidden elements can still receive keyboard focusWCAG 2.4.3 (A) · 5 pages · 45 instances
High Hidden elements can still receive keyboard focusWCAG 2.4.3 (A) · 5 pages · 9 instances

03 · WCAG criteria affected

Criterion	Name	Level	Findings	Pages
2.5.8	Target Size (Minimum)	AA	13	5
2.4.3	Focus Order	A	11	5
1.4.3	Contrast (Minimum)	AA	2	5
2.1.1	Keyboard	A	2	5
4.1.2	Name, Role, Value	A	2	5
1.1.1	Non-text Content	A	1	5
1.4.10	Reflow	AA	1	1
2.1.2	No Keyboard Trap	A	1	2
2.4.1	Bypass Blocks	A	1	5
2.4.4	Link Purpose (In Context)	A	1	1

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

04 · All detected findings

Critical

Links lack accessible text

WCAG 2.4.4 (A)1 instance1 affected page

ComponentRef 1M4GCH

Links expose no accessible name, so their destination is unknown to screen reader users.

Affected pagehttps://www.racket-company.de/

Element#amslider_id8198-item-3 > .flex-col

Markup

<a href="https://www.racket-company.de/forza" class="flex flex-col">

How to fixThis link exposes no accessible text. Add visible text that identifies its destination, or remove the link if it serves no purpose. For an icon-only link, provide an aria-label describing where it goes. The link points to https://www.racket-company.de/forza.

High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)19 instances5 affected pages

ComponentRef 23SAFE

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Affected pagehttps://www.racket-company.de/

Elementbutton#minimized-trustbadge-98e3dadd90eb493088abdc5597a70810 > div:nth-of-type(4) > div

Accessible nameTrstd Login

Roleswitch

Markup

<div data-testid="trstd-login-toggle-rail" aria-label="Trstd Login" aria-checked="false" role="switch" class="_accjg1"><div data-testid="trstd-login-toggle-knob" class="_6aw7rh"><img alt="" width="20" height="20" src="https://widgets.trustedshops.com/assets/images/sprite.6b83167aeea54f81c755d67d609fd23a61b5b620.svg#e-in-circle-light" class="_130vnx3"></div></div>

How to fixTo fix this issue, add a tabindex attribute to the element with the role="switch" attribute, so it can receive keyboard focus. Ensure the tabindex value is 0 or a positive integer, allowing the element to be focusable by default or when navigating via keyboard. Additionally, consider adding event listeners for keyboard events (e.g., keydown, keyup) to handle keyboard interactions appropriately.

Affected pages/ /faqs /contact /checkout /payment-methods

ComponentRef FZB3Z4

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Affected pagehttps://www.racket-company.de/

Elementsection#cart-drawer > div > div:nth-of-type(1)

Accessible nameMini-Warenkorb schließen

Rolebutton

Markup

<div class="backdrop" x-show="open" x-transition:enter="ease-in-out duration-500" x-transition:enter-start="opacity-0" x-transition:enter-end="opacity-100" x-transition:leave="ease-in-out duration-500" x-transition:leave-start="opacity-100" x-transition:leave-end="opacity-0" role="button" @click="closeCartDrawer" aria-label="Mini-Warenkorb schließen" style="display: none;"></div>

How to fixAdd a tabindex attribute to the element or replace the div with a native button element to make it focusable by keyboard.

Affected pages/ /faqs /contact /checkout /payment-methods

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)100 instances5 affected pages

ComponentRef 6QREJD

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementinput#CybotCookiebotDialogBodyLevelButtonPreferences

Roleswitch

Markup

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferences" class="CybotCookiebotDialogBodyLevelButton CybotCookiebotDialogBodyLevelConsentCheckbox" data-target="CybotCookiebotDialogBodyLevelButtonPreferencesInline" checked="checked" tabindex="0" role="switch">

How to fixRemove the tabindex attribute or set it to -1 for the hidden checkbox input, or make the element visible when it receives focus.

Affected pages/ /faqs /contact /checkout /payment-methods

ComponentRef HYMDLF

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementdiv#CybotCookiebotDialogDetailBodyContentCookieTabsNecessary > div > ul > li:nth-of-type(1) > a:nth-of-type(1)

Accessible nameCookiebot1

Rolebutton

Markup

<a class="CybotCookiebotDialogDetailBodyContentCookieProvider CybotCookiebotDialogCollapsed" role="button" aria-expanded="false" href="#">Cookiebot<div class="CybotCookiebotDialogDetailBodyContentCookieInfoCount CybotCookiebotDialogDetailBulkConsentCount">1</div></a>

How to fixTo fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using CSS to set 'display: none' or 'visibility: hidden' when it's not visible.

Affected pages/ /faqs /contact /checkout /payment-methods

ComponentRef A4HLN4

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementbutton#CybotCookiebotDialogDetailBodyContentCookieContainerNecessary

Accessible nameNecessary (10)

Markup

<button id="CybotCookiebotDialogDetailBodyContentCookieContainerNecessary" class="CybotCookiebotDialogDetailBodyContentCookieContainerButton CybotCookiebotDialogCollapsed" lang="en" data-target="CybotCookiebotDialogDetailBodyContentCookieTabsNecessary" aria-label="Necessary (10)" aria-controls="CybotCookiebotDialogDetailBodyContentCookieTabsNecessary" aria-expanded="false"><span id="CybotCookiebotDialogBodyLevelButtonNecessaryInlineLabel" role="heading" aria-level="3">Necessary </span> <span class="CybotCookiebotDialogDetailBulkConsentCount">10</span></button>

How to fixTo fix this issue, ensure that elements which are not visible do not remain in the tab order. This can be achieved by setting the 'tabindex' attribute to '-1' or by removing the element from the DOM when it is not visible.

Affected pages/ /faqs /contact /checkout /payment-methods

ComponentRef 4XI4NE

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementa#CybotCookiebotDialogNavDeclaration

Accessible nameConsent

Roletab

Markup

<a id="CybotCookiebotDialogNavDeclaration" class="CybotCookiebotDialogNavItemLink CybotCookiebotDialogActive" href="#" data-target="CybotCookiebotDialogBody" tabindex="0" role="tab" aria-selected="false" aria-controls="CybotCookiebotDialogBody" lang="en">Consent</a>

How to fixRemove the element from the tab order by setting tabindex to -1 or remove the element altogether if it's not intended to be interacted with. Ensure that only visible elements are focusable.

Affected pages/ /faqs /contact /checkout /payment-methods

ComponentRef 30A4KP

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementdiv:nth-of-type(1) > div:nth-of-type(1) > div:nth-of-type(1) > nav > div > a:nth-of-type(1)

Accessible nameEnglisch

Markup

<a href="https://www.racket-company.de/stores/store/redirect/___store/en/uenc/aHR0cHM6Ly93d3cucmFja2V0LWNvbXBhbnkuY29tL2VuLw~~/___from_store/de/" class="block px-4 py-2 lg:px-5 lg:py-2 hover:bg-container-darker hover:rounded-lg" title="Zu Englisch wechseln">Englisch</a>

How to fixTo fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using 'display: none' or 'visibility: hidden' CSS properties to make it invisible. Alternatively, make the element visible when it receives focus.

ComponentRef DOMIT3

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementul > li:nth-of-type(1) > div:nth-of-type(2) > ul > li:nth-of-type(1) > button

Accessible nameZurück zu den Hauptkategorien

Markup

<button type="button" class="flex items-center px-8 py-4 border-b cursor-pointer bg-container border-container
                                               w-full border-t text-primary font-bold
                                        " @click="backToMainCategories('category-node-2-main')" aria-label="Zurück zu den Hauptkategorien">
                                        <svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke-width="2" stroke="currentColor" width="24" height="24" aria-hidden="true">
  <path stroke-linecap="round" stroke-linejoin="round" d="M15 19l-7-7…

How to fixTo fix this issue, ensure that the element is either removed from the tab order or made visible when it receives focus. This can be achieved by adding a `display: none` or `visibility: hidden` style when the element is not intended to be interacted with, or by using JavaScript to dynamically update the element's visibility and focusability.

ComponentRef EQER5F

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementa#customer\.header\.register\.link

Accessible nameEin Konto erstellen

Markup

<a id="customer.header.register.link" class="block px-4 py-2 lg:px-5 lg:py-2 hover:bg-container-darker hover:rounded-lg" href="https://www.racket-company.de/customer/account/create/" title="Ein Konto erstellen">
        Ein Konto erstellen    </a>

How to fixKeep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

ComponentRef OTGDGR

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementnav > div > ul > li:nth-of-type(1) > div:nth-of-type(1) > button

Accessible nameBadminton Unterkategorien öffnen

Markup

<button @click="openSubcategory('category-node-2')" class="flex items-center justify-between w-full mr-8 cursor-pointer
                                       bg-container-lighter border-container text-primary
                                " aria-label="Badminton Unterkategorien öffnen" aria-haspopup="true" :aria-expanded="mobilePanelActiveId === 'category-node-2'" aria-expanded="false">
                                <span class="flex items-center w-full px-8 py-4 border-b                                             bg-container-lighter border-container level-0 text-primary font-bold" titl…

How to fixTo fix this issue, ensure that the element is removed from the tab order when it's not visible. This can be achieved by setting the 'tabindex' attribute to '-1' or by using a technique like visually hiding the element while maintaining its accessibility. Consider using CSS to set 'display: none;' or 'visibility: hidden;' on the element when it's not intended to be interacted with.

ComponentRef 8V8WAE

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementdiv#header > div:nth-of-type(1) > nav > button

Accessible nameMenü öffnen

Markup

<button type="button" class="block" aria-label="Menü öffnen" :aria-expanded="open" x-ref="mobileMenuTrigger" x-show="!open" @click="openMenu()" aria-expanded="false">
        <svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke-width="2" stroke="currentColor" width="50" height="50" aria-hidden="true">
  <path stroke-linecap="round" stroke-linejoin="round" d="M4 6h16M4 12h16M4 18h16"></path>
</svg>
    </button>

How to fixTo fix this issue, ensure that the button is not focusable when it's not visible. You can achieve this by setting the 'tabindex' attribute to '-1' or by removing the button from the DOM when it's not needed. Alternatively, you can make the button visible when it receives focus, so sighted keyboard users can track the focus.

ComponentRef 7YW1K1

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://www.racket-company.de/

Elementa#customer\.header\.sign\.in\.link

Accessible nameAnmelden

Markup

<a id="customer.header.sign.in.link" class="block px-4 py-2 lg:px-5 lg:py-2 hover:bg-container-darker hover:rounded-lg" onclick="hyva.setCookie &amp;&amp; hyva.setCookie(
       'login_redirect',
       window.location.href,
       1
   )" href="https://www.racket-company.de/customer/account/index/" title="Anmelden">
    Anmelden</a>

High

Modal dialog does not trap keyboard focus

WCAG 2.4.3 (A)10 instances5 affected pages

ComponentRef O1ZGIL

An open modal leaves the content behind it keyboard-focusable, so keyboard and screen reader users can tab out of the dialog into hidden page content.

Affected pagehttps://www.racket-company.de/

Elementsection#cart-drawer > div

Accessible nameMein Warenkorb 10 von 0 Produkten im Warenkorb angezeigt

Roledialog

Markup

<div role="dialog" aria-labelledby="cart-drawer-title" aria-modal="true" :aria-hidden="!open" class="fixed inset-y-0 right-0 z-30 flex max-w-full" aria-hidden="true">
        <div class="backdrop" x-show="open" x-transition:enter="ease-in-out duration-500" x-transition:enter-start="opacity-0" x-transition:enter-end="opacity-100" x-transition:leave="ease-in-out duration-500" x-transition:leave-start="opacity-100" x-transition:leave-end="opacity-0" role="button" @click="closeCartDrawer" aria-label="Mini-Warenkorb schließen" style="display: none;"></div>
        <div class="relative w-screen max-…

How to fixTo fix this issue, ensure that the modal dialog traps keyboard focus. You can achieve this by setting the `tabindex` attribute to `-1` on the dialog container and programmatically managing focus within the dialog. Additionally, consider using a library or framework that provides built-in support for accessible modals.

Affected pages/ /faqs /contact /checkout /payment-methods

High

Elements must only use permitted ARIA attributes

WCAG 4.1.2 (A)15 instances5 affected pages

ComponentRef G0IJGU

Elements must only use permitted ARIA attributes

Affected pagehttps://www.racket-company.de/

Elementdiv[aria-labelledby="collapse-id-1"]

Accessible nameShop

Markup

<div class="lg:block" :class="{ 'hidden': isMobile && !open }" :aria-labelledby="isMobile ? $id('collapse-id') : null" :aria-hidden="isMobile && (open ? 'false' : 'true')" aria-labelledby="collapse-id-1" aria-hidden="false">

How to fixRemove or replace the 'aria-label' attribute on the 'div' element with a permitted ARIA attribute or provide an alternative text description for screen readers.

Affected pages/ /faqs /contact /checkout /payment-methods

High

ARIA hidden element must not be focusable or contain focusable elements

WCAG 4.1.2 (A)10 instances1 affected page

ComponentRef 376AKP

ARIA hidden element must not be focusable or contain focusable elements

Affected pagehttps://www.racket-company.de/

Elementdiv[aria-describedby="slide-desc-74405-slider-id-1"]

Accessible namePosten 7

Rolegroup

Markup

<div class="js_slide flex flex-c..." role="group" :aria-hidden="7 > active && 7 <= (..." aria-label="Posten 7" :aria-describedby="`slide-desc-74405-${..." aria-hidden="true" aria-describedby="slide-desc-74405-sli...">

How to fixReview the affected element and correct the reported accessibility issue.

Medium

No skip link to main content

WCAG 2.4.1 (A)9 instances5 affected pages

ComponentRef YK3M4X

The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.

Affected pagehttps://www.racket-company.de/

Elementbody#html-body

Accessible nameConsentDetails[#IABV2SETTINGS#]AboutThis website uses cookiesWe use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. [#GPC_BANNER_ICON#][#GPC_TOAST_TEXT#]Consent SelectionNecessary Preferences Statistics Marketing Show detailsDetailsNecessary 10 Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.Cookiebot1Learn more about this providerCookieConsentStores the user's cookie consent state for the current domainMaximum Storage Duration: 1 yearType: HTTP CookieGoogle1Learn more about this providerSome of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization.test_cookieUsed to check if the user's browser supports cookies.Maximum Storage Duration: 1 dayType: HTTP Cookiewww.racket-company.de8form_keyEnsures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. Maximum Storage Duration: 1 dayType: HTTP Cookiemage-cache-sessidThis cookie is used in context with load balancing - This optimizes the response rate between the visitor and the site, by distributing the traffic load on multiple network links or servers. Maximum Storage Duration: 1 dayType: HTTP Cookiemage-cache-storageUsed to optimize the loading speed on the website. This is done by pre-loading some procedures in the visitors' browser.Maximum Storage Duration: PersistentType: HTML Local Storagemage-cache-timeoutThis cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.Maximum Storage Duration: PersistentType: HTML Local Storagemage-messagesNecessary for the functionality of the website's chat-box function. Maximum Storage Duration: SessionType: HTTP CookiePHPSESSIDPreserves user session state across page requests.Maximum Storage Duration: 1 dayType: HTTP Cookieprivate_content_versionThis cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.Maximum Storage Duration: 400 daysType: HTTP Cookieprivate_content_versionThis cookie is necessary for the cache function. A cache is used by the website to optimize the response time between the visitor and the website. The cache is usually stored on the visitor’s browser.Maximum Storage Duration: PersistentType: HTML Local StoragePreferences 2 Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.Klaviyo1Learn more about this providerklaviyoOnsiteThe cookie is used to manage the mailing list, if the visitor has subscribed to any newsletters or blog posts. Maximum Storage Duration: PersistentType: HTML Local Storagewww.racket-company.de1section_data_idsUsed in context with the shopping cart functionality. Remembers any wish-list products and visitor credentials when checking out. Maximum Storage Duration: 1 dayType: HTTP CookieStatistics 2 Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.Klaviyo1Learn more about this provider__kla_idThis cookie is used to collect information on the visitor's behavior. This information will be stored for internal use on the website – internal analytics is used to optimize the websites or to register if the visitor has subscribed to a newsletter.Maximum Storage Duration: 2 yearsType: HTTP Cookiewww.racket-company.de1last_visited_storeDetermines when the visitor last visited the different subpages on the website, as well as sets a timestamp for when the session started.Maximum Storage Duration: 1 dayType: HTTP CookieMarketing 27 Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. Meta Platforms, Inc.3Learn more about this providerlastExternalReferrerDetects how the user reached the website by registering their last URL-address.Maximum Storage Duration: PersistentType: HTML Local StoragelastExternalReferrerTimeDetects how the user reached the website by registering their last URL-address.Maximum Storage Duration: PersistentType: HTML Local Storage_fbpUsed by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.Maximum Storage Duration: 3 monthsType: HTTP CookieGoogle5Learn more about this providerSome of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization.pagead/1p-user-list/#Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites.Maximum Storage Duration: SessionType: Pixel Tracker_gaUsed to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.Maximum Storage Duration: 2 yearsType: HTTP Cookie_ga_#Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.Maximum Storage Duration: 2 yearsType: HTTP Cookie_gcl_auUsed by Google AdSense for experimenting with advertisement efficiency across websites using their services. Maximum Storage Duration: 3 monthsType: HTTP Cookie_gcl_lsTracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. Maximum Storage Duration: PersistentType: HTML Local StorageKlaviyo6Learn more about this providerklaviyoPagesVisitCountV2This cookie is used to determine which products the visitor has viewed. This information is used to promote related products and optimize ad-efficiency. Maximum Storage Duration: SessionType: HTML Local Storage$last_referrerThis cookie is used to determine which products the visitor has viewed. This information is used to promote related products and optimize ad-efficiency. Maximum Storage Duration: PersistentType: HTML Local Storage$referrerThis cookie is used to determine which products the visitor has viewed. This information is used to promote related products and optimize ad-efficiency. Maximum Storage Duration: PersistentType: HTML Local Storage__kl_keyThis cookie is used to determine which products the visitor has viewed. This information is used to promote related products and optimize ad-efficiency. Maximum Storage Duration: PersistentType: HTML Local Storage__kla_viewedCollects information on the user's website navigation and preferences - This is used to target potential newsletter based upon this information. Maximum Storage Duration: PersistentType: HTML Local Storagekl-post-identification-syncThis cookie is used to determine which products the visitor has viewed. This information is used to promote related products and optimize ad-efficiency. Maximum Storage Duration: PersistentType: HTML Local StorageMicrosoft8Learn more about this provider_uetsidUse…[truncated by Evolize: exceeded D1 value limit]

Markup

<body id="html-body" class="cms-homepage page-layout-1column cms-index-index page-layout-cms-full-width" style="min-height: auto; padding-top: 0px;"><div id="CybotCookiebotDialog" name="CybotCookiebotDialog" role="region" aria-labelledby="CybotCookiebotDialogBodyContentTitle" tabindex="-1" lang="en" dir="ltr" ng-non-bindable="" style="display: flex; font-size: 0.9375rem;" data-template="slideup" class="CybotEdge CybotCookiebotDialogActive"><div class="CybotCookiebotDialogContentWrapper"><div id="CybotCookiebotDialogHeader"><div id="CybotCookiebotDialogHeaderLogosWrapper"><div id="CybotCookiebo…

How to fixAdd a "Skip to main content" link as the first focusable element, targeting the id of the <main> region.

Affected pages/ /faqs /contact /checkout /payment-methods

Medium

Touch targets are too small

WCAG 2.5.8 (AA)12 instances5 affected pages

ComponentRef 3MO2Y1

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/

Elementa[href$="friendlycaptcha.com/"]

Accessible nameFriendlyCaptcha ⇗

Markup

<a lang="en" href="https://friendlycaptcha.com/" rel="noopener" target="_blank"><b>Friendly</b>Captcha ⇗</a>

How to fixIncrease the size of the touch target to at least 24x24 pixels to ensure users can reliably activate it by touch.

Affected pages/ /faqs /contact /checkout /payment-methods

Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)46 instances5 affected pages

ComponentRef U93TLC

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/payment-methods

Elementbody#html-body > div:nth-of-type(2) > header > a

Accessible nameDirekt zum Inhalt

Markup

<a class="action skip sr-only focus:not-sr-only focus:absolute focus:z-40 focus:bg-white
   contentarea" href="#contentarea">
    <span>
        Direkt zum Inhalt    </span>
</a>

How to fixIncrease the touch target size of the interactive element to at least 24x24px to make it easier for users to activate by touch.

Affected pages/ /faqs /contact /checkout /payment-methods

ComponentRef 19H8DF

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/payment-methods

Elementdiv#imi_friendly_captcha_newsletter > div > div > button

Accessible nameHier klicken

Markup

<button type="button" class="frc-button">Hier klicken</button>

How to fixTo improve the accessibility of this element, ensure that the touch target is at least 24x24 pixels in size. Consider increasing the size of the button or adding padding around it to make it easier to tap on mobile devices.

Affected pages/faqs /contact /checkout /payment-methods

ComponentRef QB3B1U

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/payment-methods

Elementdiv#imi_friendly_captcha_newsletter > span > a

Accessible nameFriendlyCaptcha ⇗

Markup

<a lang="en" href="https://friendlycaptcha.com/" rel="noopener" target="_blank"><b>Friendly</b>Captcha ⇗</a>

How to fixIncrease the touch target size of the interactive element to at least 24x24px to make it easier for users to activate by touch.

Affected pages/contact /checkout /payment-methods

ComponentRef QS8R5C

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/payment-methods

Elementdiv > nav > div > ol > li:nth-of-type(1) > a

Accessible nameHome

Markup

<a href="https://www.racket-company.de/" class="no-underline" title="Zur Homepage">Home</a>

How to fixIncrease the touch target size of the 'Home' link to at least 24x24px to make it easier for users to tap on mobile devices. Consider adding padding or increasing the font size of the link text to achieve this.

Affected pages/faqs /payment-methods

ComponentRef 3QEDIY

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/faqs

Elementdiv:nth-of-type(4) > div > div:nth-of-type(2) > p:nth-of-type(23) > span > a

Accessible nameHier

Markup

<a href="http://www.dhl.de/de/paket/pakete-empfangen/packstation/faq.html" title="Packstation Maße" target="_blank">Hier</a>

How to fixTo fix this issue, increase the size of the touch target to at least 24x24px. This can be achieved by adding padding or increasing the font size of the interactive element.

ComponentRef 6PHAMX

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/

Elementdiv > section > div > section > div > a

Accessible nameClicken, um das Karussell zu überspringen

Markup

<a href="#-slider-end" class="action skip sr-only focus:not-sr-only focus:absolute focus:z-30 focus:bg-white">
                Clicken, um das Karussell zu überspringen            </a>

How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch. Consider adding padding or increasing the font size of the interactive element.

ComponentRef W9ZUO2

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/contact

Elementdiv > div > div > ul > li:nth-of-type(1) > a

Accessible name+49 (0) 69 590255

Markup

<a class="inline" href="tel:+49069590255">
            +49 (0) 69 590255        </a>

How to fixTo fix this issue, consider increasing the size of the touch target to at least 24x24 pixels. This can be achieved by adding padding to the element or increasing its font size.

ComponentRef 9WWK5P

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/

Elementdiv:nth-of-type(1) > div > div:nth-of-type(1) > form > div:nth-of-type(2) > button

Accessible nameZur Wunschliste hinzufügen VICTOR Thruster K 66 Super Light AJ Badmintonschläger superleicht kopflastig medium limitiert

Markup

<button x-data="initWishlist()" x-defer="intersect" @click.prevent="addToWishlist(81374)" aria-label="Zur Wunschliste hinzufügen VICTOR Thruster K 66 Super Light AJ Badmintonschläger superleicht kopflastig medium limitiert" type="button" class="rounded-full w-5 h-5 p-0 border-0 inline-flex shrink-0 items-center justify-center text-primary hover:text-red-600 group" data-addto="wishlist" x-ignore="">
    <svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke-width="2" stroke="currentColor" class="group-hover:fill-current" width="20" height="20" aria-hidden="true">
  <path…

How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch.

ComponentRef 16Q6GF

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/faqs

Elementdiv > div:nth-of-type(2) > p:nth-of-type(3) > span > strong > a

Accessible nameWie lange dauert es, bis ich meine Ware erhalte?

Markup

<a href="#Lieferzeit">Wie lange dauert es, bis ich meine Ware erhalte?</a>

How to fixTo make this element easier to use on mobile devices, consider increasing its size to at least 24x24 pixels or ensuring that it has a larger touch target. You can do this by adding padding to the element or wrapping it in a larger container.

ComponentRef NDJBPI

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/checkout/cart/

Elementdiv:nth-of-type(4) > div > div:nth-of-type(1) > div > p:nth-of-type(2) > a

Accessible namehier

Markup

<a href="https://www.racket-company.de/">hier</a>

How to fixIncrease the size of the touch target to at least 24x24px to make it easier for users to activate by touch.

ComponentRef WOH8YY

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/payment-methods

Elementtable > tbody > tr:nth-of-type(6) > td:nth-of-type(2) > p:nth-of-type(1) > a

Accessible namehier

Markup

<a href="https://www.racket-company.de/directions">hier</a>

How to fixIncrease the size of the touch target to at least 24x24px to make it easier for users to activate by touch.

ComponentRef 791LVS

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://www.racket-company.de/faqs

Elementdiv:nth-of-type(2) > p:nth-of-type(8) > span > strong > strong > a

Accessible nameWie erhalte ich die Rechnung für meine Bestellung?

Markup

<a href="#Rechnung">Wie erhalte ich die Rechnung für meine Bestellung?</a>

How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch.

Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)12 instances5 affected pages

ComponentRef N94EAI

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://www.racket-company.de/

Element#CybotCookiebotDialogBodyContentText

Accessible nameWe use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services.

Markup

<div id="CybotCookiebotDialogBodyContentText" lang="en">

How to fixIncrease the contrast between the text color and the background color to meet the minimum contrast ratio of 4.5:1 for normal text and 7:1 for larger text (18pt or 14pt bold). Consider using a color contrast analyzer tool to determine the optimal colors.

Affected pages/ /faqs /contact /checkout /payment-methods

ComponentRef 4NU4J8

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Affected pagehttps://www.racket-company.de/payment-methods

Element._1abw4e6

Accessible name(11,3k)

Markup

<span data-testid="compact-rating-count" class="_1abw4e6">(11,3k)</span>

How to fixTo improve the accessibility of this element, increase the contrast between the text color and the background color. You can do this by changing the CSS styles for the span element with the class '_1abw4e6' to use a color that has sufficient contrast with the background.

Affected pages/faqs /contact /checkout /payment-methods

Medium

Keyboard focus may be trapped

WCAG 2.1.2 (A)2 instances2 affected pages

ComponentRef 2FGV9R

Repeated Tab presses did not move focus through the page as expected — focus appears to cycle within a small set of elements, which can strand keyboard users. Requires manual confirmation.

Affected pagehttps://www.racket-company.de/payment-methods

Elementbutton#CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll

Accessible nameAllow all

Markup

<button></button>

How to fixTo address this issue, ensure that the keyboard focus can move through all interactive elements on the page in a logical order. Review the page's focus management and modify the code to prevent focus from being trapped within a small set of elements. Consider implementing a robust focus management system that allows keyboard users to navigate through the page seamlessly.

Affected pages/checkout /payment-methods

Medium

Content overflows horizontally on narrow viewports

WCAG 1.4.10 (AA)1 instance1 affected page

ComponentRef 1STVXK

The page scrolls horizontally at a mobile width, indicating content that does not reflow.

Affected pagehttps://www.racket-company.de/payment-methods

Elementhtml

Accessible nameZahlungsarten window.YIREO_GOOGLETAGMANAGER2_ENABLED = true; (function (events) { const initYireoGoogleTagManager2 = function () { events.forEach(function (eventType) { window.removeEventListener(eventType, initYireoGoogleTagManager2); }); (function (w, d, s, l, i) { w[l] = w[l] || []; w[l].push({'gtm.start': new Date().getTime(), event: 'gtm.js'}); var f = d.getElementsByTagName(s)[0], j = d.createElement(s), dl = l != 'dataLayer' ? '&l=' + l : ''; j.async = true; j.src = 'https://www.googletagmanager.com' + '/gtm.js?id=' + i + dl; f.parentNode.insertBefore(j, f); })(window, document, 'script', 'dataLayer', 'GTM-PFRRF2QC'); }; events.forEach(function (eventType) { window.addEventListener(eventType, initYireoGoogleTagManager2, {once: true, passive: true}) }); })(['load', 'keydown', 'mouseover', 'scroll', 'touchstart', 'wheel']); var BASE_URL = 'https://www.racket-company.de/'; var THEME_PATH = 'https://www.racket-company.de/static/version1787120031/frontend/racket-company/theme/de_DE'; var COOKIE_CONFIG = { "expires": null, "path": "\u002F", "domain": ".www.racket\u002Dcompany.de", "secure": true, "lifetime": "3600", "cookie_restriction_enabled": false }; var CURRENT_STORE_CODE = 'de'; var CURRENT_WEBSITE_ID = '1'; window.hyva = window.hyva || {} window.cookie_consent_groups = window.cookie_consent_groups || {} window.cookie_consent_groups['necessary'] = true; window.cookie_consent_config = window.cookie_consent_config || {}; window.cookie_consent_config['necessary'] = [].concat( window.cookie_consent_config['necessary'] || [], [ 'user_allowed_save_cookie', 'form_key', 'mage-messages', 'private_content_version', 'mage-cache-sessid', 'last_visited_store', 'section_data_ids' ] ); //# sourceURL=hyva-variables.js (function( hyva, undefined ) { function lifetimeToExpires(options, defaults) { const lifetime = options.lifetime || defaults.lifetime; if (lifetime) { const date = new Date; date.setTime(date.getTime() + lifetime * 1000); return date; } return null; } function generateRandomString() { const allowedCharacters = '0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ', length = 16; let formKey = '', charactersLength = allowedCharacters.length; for (let i = 0; i < length; i++) { formKey += allowedCharacters[Math.round(Math.random() * (charactersLength - 1))] } return formKey; } const sessionCookieMarker = {noLifetime: true} const cookieTempStorage = {}; const internalCookie = { get(name) { const v = document.cookie.match('(^|;) ?' + name + '=([^;]*)(;|$)'); return v ? v[2] : null; }, set(name, value, days, skipSetDomain) { let expires, path, domain, secure, samesite; const defaultCookieConfig = { expires: null, path: '/', domain: null, secure: false, lifetime: null, samesite: 'lax' }; const cookieConfig = window.COOKIE_CONFIG || {}; expires = days && days !== sessionCookieMarker ? lifetimeToExpires({lifetime: 24 * 60 * 60 * days, expires: null}, defaultCookieConfig) : lifetimeToExpires(window.COOKIE_CONFIG, defaultCookieConfig) || defaultCookieConfig.expires; path = cookieConfig.path || defaultCookieConfig.path; domain = !skipSetDomain && (cookieConfig.domain || defaultCookieConfig.domain); secure = cookieConfig.secure || defaultCookieConfig.secure; samesite = cookieConfig.samesite || defaultCookieConfig.samesite; document.cookie = name + "=" + encodeURIComponent(value) + (expires && days !== sessionCookieMarker ? '; expires=' + expires.toGMTString() : '') + (path ? '; path=' + path : '') + (domain ? '; domain=' + domain : '') + (secure ? '; secure' : '') + (samesite ? '; samesite=' + samesite : 'lax'); }, isWebsiteAllowedToSaveCookie() { const allowedCookies = this.get('user_allowed_save_cookie'); if (allowedCookies) { const allowedWebsites = JSON.parse(unescape(allowedCookies)); return allowedWebsites[CURRENT_WEBSITE_ID] === 1; } return false; }, getGroupByCookieName(name) { const cookieConsentConfig = window.cookie_consent_config || {}; let group = null; for (let prop in cookieConsentConfig) { if (!cookieConsentConfig.hasOwnProperty(prop)) continue; if (cookieConsentConfig[prop].includes(name)) { group = prop; break; } } return group; }, isCookieAllowed(name) { const cookieGroup = this.getGroupByCookieName(name); return cookieGroup ? window.cookie_consent_groups[cookieGroup] : this.isWebsiteAllowedToSaveCookie(); }, saveTempStorageCookies() { for (const [name, data] of Object.entries(cookieTempStorage)) { if (this.isCookieAllowed(name)) { this.set(name, data['value'], data['days'], data['skipSetDomain']); delete cookieTempStorage[name]; } } } }; hyva.getCookie = (name) => { const cookieConfig = window.COOKIE_CONFIG || {}; if (cookieConfig.cookie_restriction_enabled && ! internalCookie.isCookieAllowed(name)) { return cookieTempStorage[name] ? cookieTempStorage[name]['value'] : null; } return internalCookie.get(name); } hyva.setCookie = (name, value, days, skipSetDomain) => { const cookieConfig = window.COOKIE_CONFIG || {}; if (cookieConfig.cookie_restriction_enabled && ! internalCookie.isCookieAllowed(name)) { cookieTempStorage[name] = {value, days, skipSetDomain}; return; } return internalCookie.set(name, value, days, skipSetDomain); } hyva.setSessionCookie = (name, value, skipSetDomain) => { return hyva.setCookie(name, value, sessionCookieMarker, skipSetDomain) } hyva.getBrowserStorage = () => { const browserStorage = window.localStorage || window.sessionStorage; if (!browserStorage) { console.warn('Browser Storage is unavailable'); return false; } try { browserStorage.setItem('storage_test', '1'); browserStorage.removeItem('storage_test'); } catch (error) { console.warn('Bro…[truncated by Evolize: exceeded D1 value limit]

Markup

<html lang="de" style="--page-header-height: 135px;"><head prefix="og: http://ogp.me/ns# cms: http://ogp.me/ns/cms#">
    <meta charset="utf-8">
<meta name="title" content="Zahlungsarten">
<meta name="robots" content="INDEX,FOLLOW">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Zahlungsarten</title>
<link rel="stylesheet" type="text/css" media="all" href="https://www.racket-company.de/static/version1787120031/frontend/racket-company/theme/de_DE/css/styles.css">
<link rel="stylesheet" type="text/css" media="all" href="https://www.racket-company.de/static/version178…

How to fixTo fix this issue, ensure that the content of the page is able to reflow and adapt to different viewport sizes, particularly on mobile devices. Consider using responsive design techniques, such as using relative units for sizing and positioning elements, and avoiding fixed widths that can cause content to overflow. Additionally, test the page on different devices and viewport sizes to ensure that the content is accessible and usable.

Low

Low-quality alternative text

WCAG 1.1.1 (A)99 instances5 affected pages

ComponentRef GF0IM9

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Affected pagehttps://www.racket-company.de/

Elementdiv#CybotCookiebotDialogDetailBodyContentCookieTabsNecessary > div > ul > li:nth-of-type(1) > a:nth-of-type(2) > img

Markup

<img class="CybotExternalLinkArrow" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAYAAABWzo5XAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAC6SURBVHgBpdTdCcMgEAdwT/vk04EOkBG6QifpHH3rCF2hk3SVvBaEuoDYu4IgRRMv/iEkD/Hn+QnOuatS6gEAqDoJIQC/vfe594+m576FjAZKL6XXkSDiYox5UQFLXZEoNZJzXg9B/0hK6SKGWkiMcRVBewjnNIuURdIzyFBFo0jZPnoGqaMbCEqRJkSNIiFPCfILj7F1GLkySfvuqnFlShDxWesF6D76zF4jPJ/GWvum7/NRjBCegtsXQuuTY/odOJIAAAAASUVORK5CYII=" alt="opens in a new window">

How to fixProvide descriptive alternative text for the image that indicates its purpose and content, rather than using a generic phrase like 'opens in a new window'. For example, 'External link to Cookiebot's privacy policy' would be more descriptive.

Affected pages/ /faqs /contact /checkout /payment-methods

05 · Pages inspected

/27 findings Critical
/faqs21 findings High
/payment-methods21 findings High
/checkout/cart/19 findings High
/contact17 findings High

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

Publicly accessible surfaces only — no credentials, private systems, or source-code access.
Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

MONITOR THIS WEBSITE SEE PRICING

Is information in this report inaccurate or outdated? Request a correction or removal.

Accessibility issues detected on racket-company.de

01 · Accessibility summary

02 · Priority findings

03 · WCAG criteria affected

A scan shows today's exposure. Monitoring shows what changes next.

04 · All detected findings

Links lack accessible text

Interactive controls are not keyboard-accessible

Hidden elements can still receive keyboard focus

Modal dialog does not trap keyboard focus

Elements must only use permitted ARIA attributes

ARIA hidden element must not be focusable or contain focusable elements

No skip link to main content

Touch targets are too small

Touch targets are too small on mobile

Text has insufficient colour contrast

Keyboard focus may be trapped

Content overflows horizontally on narrow viewports

Low-quality alternative text

05 · Pages inspected

06 · About this assessment

07 · Continuous monitoring

Other public accessibility assessments