Skip to content
https://www.gambling.com/be

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
3
REVIEW
10
PASS
11
INFO
0
Checks
24
11 PASS 10 REVIEW 3 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
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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
15 landmarks
REVIEW
15 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <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 ASIDE 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
Form Accessibility
Action
4 of 6 controls have issues
REVIEW
4 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="footer_cookie_checkbox">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="signup-name" id="signup-name">; <input type="email" name="email" id="signup-email">; <input type="password" name="password" id="signup-password">
Info::
2 control(s) properly labeled
6 controls
2 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputsearchSearcharia-label
inputsearchSearcharia-label
#signup-passwordpassword(Vul je wachtwoord in)placeholder only
#signup-nametext(John Doe)placeholder only
#signup-emailemail(you@example.com)placeholder only
#footer_cookie_checkboxcheckbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="footer_cookie_checkbox">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="signup-name" id="signup-name">; <input type="email" name="email" id="signup-email">; <input type="password" name="password" id="signup-password">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Mobile Keyboard & Autofill
Action
3/5 eligible field(s) missing autocomplete or inputmode
REVIEW
3/5 eligible field(s) missing autocomplete or inputmode
Warning::
3 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email, search.
Got: <input type="email" name="email" id="signup-email">, <input type="search">, <input type="search">
B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Tap Target Adequacy
Action
8 tap target(s) too small or too close together
REVIEW
8 tap target(s) too small or too close together
Warning::
8 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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 Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 86/100 — 6 failing, 30 passed
REVIEW
86

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Dean Ryan Experiência Estratégia de Cassino, Casino Product Development, Horse … section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Alejandra Chipatecua Experiência Cassino online, Cassino ao vivo Experiência E… section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Carolina Morales Experiência Apostas esportivas Experiência Apaixonada por apo… section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Leidy Plaza Experiência Caça-níqueis online, Cassino ao vivo Experiência Espec… section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Carolina Morales Experiência Apostas esportivas Experiência Apaixonada por apo… section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Leidy Plaza Experiência Caça-níqueis online, Cassino ao vivo Experiência Espec… section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Dean Ryan Experiência Estratégia de Cassino, Casino Product Development, Horse … section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Alejandra Chipatecua Experiência Cassino online, Cassino ao vivo Experiência E… section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Carolina Morales Experiência Apostas esportivas Experiência Apaixonada por apo… section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide
Leidy Plaza Experiência Caça-níqueis online, Cassino ao vivo Experiência Espec… section.carousel > div.carousel__viewport > ol.carousel__track > li.carousel__slide

These are opportunities to improve the usage of ARIA in your application which 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
+18 Ministério da Fazenda adverte: Aposta não é investimento. Requerimento SIGA… ul.qp__track > li.qp__card > div.qp__tcs > div.qp__tcs-body
+18 Ministério da Fazenda adverte: Aposta não é investimento. Requerimento SIGA… ul.qp__track > li.qp__card > div.qp__tcs > div.qp__tcs-body
Alex Pereira busca revanche contra Magomed Ankalaev e promete agitar o UFC 320. a.global-home-news__card > div.global-home-news__body > div.global-home-news__text > p.global-home-news__excerpt
há 1 mês div.global-home-news__track > a.global-home-news__card > div.global-home-news__body > p.global-home-news__date
Análise das semifinais do Paulistão 2026 com odds atualizados, palpites e dicas… a.global-home-news__card > div.global-home-news__body > div.global-home-news__text > p.global-home-news__excerpt
há 1 mês div.global-home-news__track > a.global-home-news__card > div.global-home-news__body > p.global-home-news__date
Confira de maneira simples e direta as novas mudanças propostas para o setor de… a.global-home-news__card > div.global-home-news__body > div.global-home-news__text > p.global-home-news__excerpt
há 1 mês div.global-home-news__track > a.global-home-news__card > div.global-home-news__body > p.global-home-news__date
Evolution lança Ice Fishing, jogo ao vivo com multiplicador de até 5.000x a.global-home-news__card > div.global-home-news__body > div.global-home-news__text > p.global-home-news__excerpt
há 1 mês div.global-home-news__track > a.global-home-news__card > div.global-home-news__body > p.global-home-news__date
Em março, a BetMGM Brasil oferece 10% de cashback nas perdas líquidas no Aviato… a.global-home-news__card > div.global-home-news__body > div.global-home-news__text > p.global-home-news__excerpt
há 1 mês div.global-home-news__track > a.global-home-news__card > div.global-home-news__body > p.global-home-news__date
Crie uma conta GRATUITA div.flex > div.break-words > div.px-3 > span.font-bold
ISENÇÃO DE RESPONSABILIDADE: As apostas online são ilegais em algumas jurisdiçõ… div#footer-container > div#disclamier-social-media-container > div#disclamier-container > p
Termos e Condições div#disclamier-social-media-container > div#disclamier-container > p > a.text-[#999999]
POLÍTICA DE PRIVACIDADE E COOKIES div#disclamier-social-media-container > div#disclamier-container > p > a.text-[#999999]

These are opportunities to improve the legibility of your content.

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
Onde você quer jogar? div.qp > div.lg:flex > aside.qp__filters > h3.text-[22px]
Autoexclusão nacional ul.cc-list-with-thumbnail > li.items-center > div.text > h4.text-center

These are opportunities to improve keyboard navigation in your application.

Names and labels

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#column-links-container > div.container > div.column-container > a.block div#column-links-container > div.container > div.column-container > a.block

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.

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
Search icon div.relative > div.ais-InstantSearch > div.ais-SearchBox > button.ais-SearchBox-submit
Go to page 1 div.[&_.js-carousel-dots]:lg:hidden > div#content-card-113cc60d-8099-441c-9260-53d37b6547b7 > div.js-carousel-dots > button.js-carousel-dot
Go to page 2 div.[&_.js-carousel-dots]:lg:hidden > div#content-card-113cc60d-8099-441c-9260-53d37b6547b7 > div.js-carousel-dots > button.js-carousel-dot
Go to page 3 div.[&_.js-carousel-dots]:lg:hidden > div#content-card-113cc60d-8099-441c-9260-53d37b6547b7 > div.js-carousel-dots > button.js-carousel-dot
Go to page 4 div.[&_.js-carousel-dots]:lg:hidden > div#content-card-113cc60d-8099-441c-9260-53d37b6547b7 > div.js-carousel-dots > button.js-carousel-dot
Go to page 5 div.[&_.js-carousel-dots]:lg:hidden > div#content-card-113cc60d-8099-441c-9260-53d37b6547b7 > div.js-carousel-dots > button.js-carousel-dot
Go to page 6 div.[&_.js-carousel-dots]:lg:hidden > div#content-card-113cc60d-8099-441c-9260-53d37b6547b7 > div.js-carousel-dots > button.js-carousel-dot
div#column-links-container > div.container > div.column-container > a.block div#column-links-container > div.container > div.column-container > a.block

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.android html.android

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-*]` attributes match their 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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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 use only permitted ARIA attributes
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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
A
Heading Hierarchy
24 headings, 1 skip(s)
PASS
24 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 VERSTANDIGER GOKKEN HIER BEGINT HET.
  • H3 Waar wil je spelen? skipped
  • H2 Free play. Real rewards.
  • H3 Free Play Slots
  • H3 BetBuilderAI
  • H2 Gambling NEWS
  • H3 Ballon d'Or 2026, de favorieten en hun odds
  • H3 Voorbeschouwing en Odds WK Finale 2026 Spanje vs Argentinië
  • H3 Vuelta 2026 Parcours & Etappes: het volledige schema van de Ronde van Spanje
  • H3 UFC 330: Makhachev vs Machado Garry, onze tips en voorspelling
  • H3 Vuelta 2026 Favorieten & Odds: wie wint de Ronde van Spanje?
  • H3 Een korte samenvatting van waar wij naar kijken:
  • H3 Tijdlijn hoe het legale online casino in België tot stand kwam.
  • H2 Waarom spelen bij legale Belgische casino's?
  • H2 Referenties
  • H2 Veelgestelde vragen
  • H3 Vanaf welke leeftijd mag ik online casino spelen in België?
  • H3 Vanaf wanneer is online gokken legaal in België?
  • H3 Wat zijn de risico's van illegale online casino's?
  • H3 Is Gambling.com betrouwbaar?
  • H3 Maak kennis met het team
  • H2 Populair
  • H2 Snelle links
  • H2 Bedrijf

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 192 images OK
PASS
All 192 images OK
Info::
30 decorative image(s) correctly marked
Info::
162 image(s) with good alt text
192 images 162 good alt text 30 decorative
All images have appropriate alt text.
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "nl-BE"
PASS
Lang attribute set to "nl-BE"
Info::
<html lang="nl-BE"> is set and valid
Got: nl-BE
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input id="super_secret_username">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
Mobile-Readable Font Sizes
All 5 visible text node(s) render at >= 12 CSS pixels
PASS
All 5 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Gambling19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Waarom spelen bij le…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Veelgestelde vragen19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Populair19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Snelle links19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Bedrijf19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Waar wil je spelen?19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Free Play Slots19.09:13.0:1
#000000
#F4F4F4
Pass
h3 BetBuilderAI19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Ballon d'Or 2026, de…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Voorbeschouwing en O…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Vuelta 2026 Parcours…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 UFC 330: Makhachev v…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Vuelta 2026 Favoriet…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Een korte samenvatti…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Tijdlijn hoe het leg…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Vanaf welke leeftijd…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Vanaf wanneer is onl…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Wat zijn de risico's…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Is Gambling.com betr…19.09:13.0:1
#000000
#F4F4F4
Pass

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback