Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - goldbett.org ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

h1 Benvenuto al Casinò GoldBet in Italia

1.13:1

#000000

#011520

needs 3.0:1 (large text)

32px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Benvenuto al Casinò…	1.13:1	3.0:1	#000000	#011520	Fail
h2 Perché i Giocatori …	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Bonus e Offerte Spec…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Selezione di Giochi …	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Compatibilità Mobil…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Come Iniziare su Gol…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Si Possono Ottenere …	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Opzioni di Pagamento…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Prelievi su GoldBet …	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Licenze e Garanzie d…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Assistenza e Support…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Paesi in Cui È Poss…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Slot	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Giochi da Tavolo	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Giochi con Croupier …	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Giochi Speciali	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Scommesse Sportive	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Limiti di Prelievo	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Tempi di Elaborazion…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Garanzia di Gioco Eq…	18.76:1	3.0:1	#000000	#F2F2F2	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.

A+

Heading Hierarchy

21 headings

PASS

21 headings

Single H1 present

H1 Benvenuto al Casinò GoldBet in Italia
H2 Perché i Giocatori in Italia Dovrebbero Scegliere GoldBet?
H3 Paesi in Cui È Possibile Accedere al Casinò GoldBet
H2 Bonus e Offerte Speciali per i Giocatori di GoldBet Italia
H2 Selezione di Giochi GoldBet Italia
H3 Slot
H3 Giochi da Tavolo
H3 Giochi con Croupier dal Vivo / Casinò Live
H3 Giochi Speciali
H3 Scommesse Sportive
H2 Compatibilità Mobile
H2 Come Iniziare su GoldBet
H2 Si Possono Ottenere Vincite Reali su GoldBet Casino?
H2 Opzioni di Pagamento GoldBet Disponibili in Italia
H2 Prelievi su GoldBet Casino
H3 Limiti di Prelievo
H3 Tempi di Elaborazione
H2 Licenze e Garanzie di Sicurezza su GoldBet
H3 Garanzia di Gioco Equo su GoldBet
H2 Assistenza e Supporto Clienti
H3 Promozione del Gioco Responsabile per i Clienti in Italia

A+

Alt Text Quality

All 39 images OK

PASS

All 39 images OK

35 decorative image(s) correctly marked

4 image(s) with good alt text

39 images 4 good alt text 35 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

47 links, 0 buttons — all OK

PASS

47 links, 0 buttons — all OK

47 link(s) with descriptive text

47 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

47 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 98/100 — 2 failing, 21 passed

PASS

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.

Best practices

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 `html`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Gioca ora `div.w-center > div.w-section > div.w-btn > a.c-btn`
Gioca ora `div.w-center > div.w-section > div.w-btn > a.c-btn`
goldbett.org `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
App `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Bonus `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Accesso `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Bonus senza deposito `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Codice promozionale `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Supporto `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Informativa sulla privacy `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Gioco responsabile `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`

○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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●`[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

●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

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[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

○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

○Buttons have an accessible name

○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

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<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.

○`<td>` elements in a large `<table>` have one or more table headers.

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