Skip to content
https://sportradar.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Heading Hierarchy
Action
78 headings, 5 skip(s)
FIX
78 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Choose your region
  • H6 Products skipped
  • H6 Trading & Risk Management
  • H6 Marketing Services
  • H6 Platforms
  • H6 Prediction Services
  • H6 Data & Content
  • H6 Audiovisual Services
  • H6 Marketing Services
  • H6 Marketplace
  • H6 Audiovisual Services
  • H6 Marketing Services
  • H6 Synergy Coaching & Scouting
  • H6 Integrity Services
  • H6 Regulatory Services
  • H5 Let us know what you want to achieve
  • H4 Content Hub
  • H4 News
  • H6 Latest Case Study skipped
  • H6 Latest Guide
  • H4 Who we are
  • H4 INVESTORS
  • H4 APIs
  • H4 FUTURES HUB
  • H4 How we help
  • H4 How we help
  • H5 Betting, Gaming, & Prediction Markets
  • H5 Products
  • H5 Trading & Risk Management
  • H5 Marketing Services
  • H5 Platforms
  • H5 Prediction Services
  • H5 Media & Tech Companies
  • H5 Data & Content
  • H5 Audiovisual Services
  • H5 Marketing Services
  • H5 Marketplace
  • H5 Teams, Leagues & Federations
  • H5 Audiovisual Services
  • H5 Marketing Services
  • H5 Synergy Coaching & Scouting
  • H5 Integrity & Regulatory Services
  • H5 Integrity Services
  • H5 Regulatory Services
  • H4 Let us know what you want to achieve
  • H4 Content & News
  • H4 Content & News
  • H4 Content Hub
  • H4 News
  • H6 Latest Case Study skipped
  • H6 Latest Guide
  • H4 About Us
  • H4 About Us
  • H5 INVESTORS
  • H5 APIs
  • H5 FUTURES HUB
  • H4 Careers
  • H4 Contact Us
  • H1 THE SPORTSTECHNOLOGY COMPANY
  • H4 Reimagining immersive experiences for sports fans and bettors skipped
  • H2 OUR PARTNERS & CLIENTS
  • H2 LATEST NEWS
  • H5 The Window for World Cup Audience Growth Is Open and It Won’t Be for Long skipped
  • H5 The month that separates the serious from the scrambling
  • H5 From Pre-Match to In-Play: How Data is Transforming Golf Betting
  • H5 Sportradar to Power Future of Brazil’s Top Basketball League LNB
  • H5 How Does Sports Moments Marketing Work? The Tech Behind Real-Time Fan Engagement
  • H5 Sportradar Expands Partnership with Hard Rock Bet, Adding Official Data from the PGA TOUR and Ultimate Fighting Championship
  • H5 How to make this IPL season work for you
  • H5 Sportradar launches iGaming brand Playradar, combining sports data expertise with casino content for global operators
  • H5 Sportradar and BSN strengthen partnership to elevate basketball in Puerto Rico
  • H2 HOW WE HELP
  • H3 BETTING & GAMING OPERATORS
  • H3 MEDIA & TECH COMPANIES
  • H3 TEAM, LEAGUES & FEDERATIONS
  • H3 INTEGRITY & REGULATORY SERVICES
  • H4 GET IN TOUCH WITH OUR TEAM
  • H4 GET IN TOUCH WITH OUR TEAM

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-5f1t3o
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://sportradar.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://sportradar.com/manifest.json

Manifest contains invalid JSON.

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::
2 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 2 <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
Favicon & Branding
4 icon(s) detected
REVIEW
4 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, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h2 LATEST NEWS
1.01:1
#FFFFFF
on
#FEFEFE
needs 3.0:1 (large text)
24px · bottom of viewport
h3 BETTING & GAMING OPERATORS
1.01:1
#FFFFFF
on
#FEFEFE
needs 3.0:1 (large text)
19px · bottom of viewport
h3 MEDIA & TECH COMPANIES
1.01:1
#FFFFFF
on
#FEFEFE
needs 3.0:1 (large text)
19px · bottom of viewport
h3 TEAM, LEAGUES & FEDERATIONS
1.01:1
#FFFFFF
on
#FEFEFE
needs 3.0:1 (large text)
19px · bottom of viewport
h3 INTEGRITY & REGULATORY SERVICES
1.01:1
#FFFFFF
on
#FEFEFE
needs 3.0:1 (large text)
19px · bottom of viewport
title Sportradar - The Sports Technology Compa…
1.08:1
#000000
on
#050536
needs 4.5:1 (normal text)
16px · top of page (header area)
button Regions
1.11:1
#000000
on
#0A0A35
needs 4.5:1 (normal text)
16px · top of page (header area)
h4 Choose your region
1.12:1
#000000
on
#0A0B3B
needs 3.0:1 (large text)
16px · top of page (header area)
a North America
1.14:1
#000000
on
#0B0C3E
needs 4.5:1 (normal text)
16px · top of page (header area)
button South America
1.24:1
#000000
on
#1E173B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Spanish
1.67:1
#000000
on
#3B2F41
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Brazilian Portuguese
2.29:1
#000000
on
#50388C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a English
1.51:1
#000000
on
#2F2160
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Europe
2.70:1
#000000
on
#3948AC
needs 4.5:1 (normal text)
16px · above the fold
a Africa
2.02:1
#000000
on
#483B50
needs 4.5:1 (normal text)
16px · above the fold
a Middle East
3.20:1
#000000
on
#64577D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Asia Pacific
2.61:1
#000000
on
#3C45A8
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a English
2.51:1
#000000
on
#3B43A2
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

7 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
h2 OUR PARTNERS & CLIEN…19.55:13.0:1
#00003C
#FEFEFE
Pass
h2 LATEST NEWS1.01:13.0:1
#FFFFFF
#FEFEFE
Fail
h2 HOW WE HELP19.55:13.0:1
#00003C
#FEFEFE
Pass
h3 BETTING & GAMING OPE…1.01:13.0:1
#FFFFFF
#FEFEFE
Fail
h3 MEDIA & TECH COMPANI…1.01:13.0:1
#FFFFFF
#FEFEFE
Fail
h3 TEAM, LEAGUES & FEDE…1.01:13.0:1
#FFFFFF
#FEFEFE
Fail
h3 INTEGRITY & REGULATO…1.01:13.0:1
#FFFFFF
#FEFEFE
Fail
title Sportradar - The Spo…1.08:14.5:1
#000000
#050536
Fail
button Regions1.11:14.5:1
#000000
#0A0A35
Fail
h4 Choose your region1.12:13.0:1
#000000
#0A0B3B
Fail
a North America1.14:14.5:1
#000000
#0B0C3E
Fail
button South America1.24:14.5:1
#000000
#1E173B
Fail
a Spanish1.67:14.5:1
#000000
#3B2F41
Fail
a Brazilian Portuguese2.29:14.5:1
#000000
#50388C
Fail
a English1.51:14.5:1
#000000
#2F2160
Fail
a Europe2.70:14.5:1
#000000
#3948AC
Fail
a Africa2.02:14.5:1
#000000
#483B50
Fail
a Middle East3.20:14.5:1
#000000
#64577D
Fail
button Asia Pacific2.61:14.5:1
#000000
#3C45A8
Fail
a English2.51:14.5:1
#000000
#3B43A2
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.

C
Lighthouse Accessibility Audits
Action
Score 74/100 — 5 failing, 15 passed
REVIEW
74

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
body.home > header.header > div.header__mbl > button.header__mbl__region body.home > header.header > div.header__mbl > button.header__mbl__region

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NTgzOjE3Nw==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NjMwOjE3OQ==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NjcxOjE3OQ==-1
div.how-mbl__dropdowns > div.how-mbl__dropdowns__item > button.how-mbl__dropdowns__item__head > img#NzA0OjE3OQ==-1

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
body.home > header.header > a.header__logo body.home > header.header > a.header__logo
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item div.header__mbl__nav > div > div.header__mbl__nav__foot > a.header__mbl__nav__foot__item
body.home > section#sr_section_1 > div.container > a#scroll-button body.home > section#sr_section_1 > div.container > a#scroll-button
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > a
div.footer__top--socialLink > ul.d__flex > li > a div.footer__top--socialLink > ul.d__flex > li > 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest Case Study div.hub__featured > div.hub__featured__list > a.hub__featured__list__item > h6
Reimagining immersive experiences for sports fans and bettors section#sr_section_1 > div.container > div.homeBanner__heading > h4.main__subtitle
The Window for World Cup Audience Growth Is Open and It Won’t Be for Long a.text-decoration-none > div.newsCard__bottom > div.newsCard__bottom--newstitle > h5.color__black

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Imprint footer.footer > div.footer__bottom > div.container > a
Privacy Notice footer.footer > div.footer__bottom > div.container > a
Cookie Notice footer.footer > div.footer__bottom > div.container > a
Report a Security Vulnerability footer.footer > div.footer__bottom > div.container > a
Ethics Hotline footer.footer > div.footer__bottom > div.container > a
Sitemap footer.footer > div.footer__bottom > div.container > a

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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 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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○Elements with visible text labels have matching accessible names.
○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
Alt Text Quality
4 of 89 images have issues
PASS
4 of 89 images have issues
Warning::
4 image(s) with generic alt text
Info::
64 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
89 images 21 good alt text 64 decorative 4 generic
IssueCount
generic4 image(s)
A+
Form Accessibility
All 15 controls labeled
PASS
All 15 controls labeled
Info::
15 control(s) properly labeled
15 controls
15 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#input_59_37textLinkedInfor/id
#input_59_10_3textYour first namefor/id
#input_59_10_6textYour last namefor/id
#input_59_3emailYour work email*for/id
#input_59_33telYour phone number*for/id
#input_59_4textWhat's the name of your company?*for/id
#input_59_11selectWhich of the following applies to you*for/id
#input_59_13selectAs a betting and gaming operator, which bit below are you most interested in?*for/id
#input_59_14selectAs a media and tech company, which bit below are you most interested in?*for/id
#input_59_17selectAs a rightsholder, which bit below are you most interested in?*for/id
#input_59_19selectAs an integrity and regulatory authority, which bit below are you most interested in?*for/id
#input_59_5selectWhere’s the main market you’ll be using this?*for/id
#input_59_7textareaWhat challenges or problems should our products solve for you?*for/id
#choice_59_36_1checkboxBy clicking this checkbox, you consent to having your email address processed by the Sportradar Group to send you marketing communications about our products, services and events. You can opt-out at any time by clicking the "unsubscribe" link at the end of each communication received. For more information, please see our privacy notice.for/id
#choice_59_36_2checkboxBy clicking this checkbox, you consent to having your phone number processed by the Sportradar Group to contact you in the future regarding our products and services. You can opt-out verbally at any time. For more information, please see our privacy notice.for/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback