Skip to content
https://sitiscommesse.org

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title clouds_shape ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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.
C
Mobile-Readable Font Sizes
Action
83% of visible text renders at >= 12 CSS px (33 below threshold)
REVIEW
83% of visible text renders at >= 12 CSS px (33 below threshold)
Warning::
33 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.8px ("Siti Scommesse Svizzera"); <span> 10.8px ("Siti Scommesse Streaming"); <span> 10.8px ("App Scommesse"); <span> 10.8px ("Siti Scommesse con Deposito Minimo"); <span> 10.8px ("Siti Scommesse UK e Bookmakers Inglesi").
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Siti Scommesse 24: Scommetti da esperto
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Il nostro TOP bookmaker
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Lista bookmakers
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recensioni sui migliori siti scommesse
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
24px · bottom of viewport
h2 TOP articoli del 2026
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recensione bookmakers 2026
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
24px · bottom of viewport
h3 BetLabel scommesse
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Betonic scommesse
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Betrebels scommesse
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 MrXbet scommesse
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 22Bet scommesse
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Notizie scommesse sportive
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Guide scommesse sportive
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bonus bookmaker 2026
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Siti Scommesse 24
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 TOP 5 Bookies
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cashout 24 Ore
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ultime News
1.02:1
#000000
on
#040404
needs 3.0:1 (large text)
19px · bottom of viewport
title Siti Scommesse: Migliori Bookmakers Stra…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Home
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Siti Scommesse 24: S…1.02:13.0:1
#000000
#040404
Fail
h2 Il nostro TOP bookma…1.02:13.0:1
#000000
#040404
Fail
h2 Lista bookmakers1.02:13.0:1
#000000
#040404
Fail
h2 Recensioni sui migli…1.02:13.0:1
#000000
#040404
Fail
h2 TOP articoli del 202…1.02:13.0:1
#000000
#040404
Fail
h2 Recensione bookmaker…1.02:13.0:1
#000000
#040404
Fail
h3 BetLabel scommesse1.02:13.0:1
#000000
#040404
Fail
h3 Betonic scommesse1.02:13.0:1
#000000
#040404
Fail
h3 Betrebels scommesse1.02:13.0:1
#000000
#040404
Fail
h3 MrXbet scommesse1.02:13.0:1
#000000
#040404
Fail
h3 22Bet scommesse1.02:13.0:1
#000000
#040404
Fail
h3 Notizie scommesse sp…1.02:13.0:1
#000000
#040404
Fail
h3 Guide scommesse spor…1.02:13.0:1
#000000
#040404
Fail
h3 Bonus bookmaker 20261.02:13.0:1
#000000
#040404
Fail
h3 Siti Scommesse 241.02:13.0:1
#000000
#040404
Fail
h3 TOP 5 Bookies1.02:13.0:1
#000000
#040404
Fail
h3 Cashout 24 Ore1.02:13.0:1
#000000
#040404
Fail
h3 Ultime News1.02:13.0:1
#000000
#040404
Fail
title Siti Scommesse: Migl…1.00:14.5:1
#000000
#000000
Fail
span Home1.00:14.5:1
#000000
#000000
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.

A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
21 headings
PASS
21 headings
Info::
Single H1 present
  • H2 Il nostro TOP bookmaker
  • H3 BetLabel scommesse
  • H2 Lista bookmakers
  • H1 Siti Scommesse 24: Scommetti da esperto
  • H2 Recensioni sui migliori siti scommesse
  • H2 TOP articoli del 2026
  • H2 Recensione bookmakers 2026
  • H3 Betonic scommesse
  • H3 Betrebels scommesse
  • H3 MrXbet scommesse
  • H3 22Bet scommesse
  • H3 Notizie scommesse sportive
  • H4 Le regole per scommettere sulle gare di nuoto
  • H4 Come scommettere sulla UFC
  • H4 Come scommettere sulla Boxe
  • H3 Guide scommesse sportive
  • H3 Bonus bookmaker 2026
  • H3 Siti Scommesse 24
  • H3 TOP 5 Bookies
  • H3 Cashout 24 Ore
  • H3 Ultime News
A+
Heading Text Quality
All 21 heading(s) have substantive, well-formed text
PASS
All 21 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 39 images OK
PASS
All 39 images OK
Info::
39 image(s) with good alt text
39 images 39 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="selectnav1">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#selectnav1select(none)none

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

<select id="selectnav1">

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

A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "it-IT"
PASS
Lang attribute set to "it-IT"
Info::
<html lang="it-IT"> is set and valid
Got: it-IT
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
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
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 27 passed
PASS
91

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.

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
TUTTE LE NEWS div#main > div.articlesection > div.articlesect > a.rmore
TUTTE LE GUIDE div#main > div.articlesection > div.articlesect > a.rmore
BOOKMAKERS DEL 2026 div#main > div.articlesection > div.articlesect > a.rmore
SITI SCOMMESSE 24 div.topfooter > div.widgetarea > section.footerwidget > h3
TOP 5 BOOKIES div.topfooter > div.widgetarea > section.footerwidget > h3
CASHOUT 24 ORE div.topfooter > div.widgetarea > section.footerwidget > h3
ULTIME NEWS div.topfooter > div.widgetarea > section.footerwidget > h3

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select page... Home Bookmakers Stranieri - Siti Scommesse Svizzera - Siti Scomm… header.main-header > nav#navigation > div.selectarea > select#selectnav1

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BOOKMAKER BONUS RECENSIONEVISITA 100% FINO A 250€ SI APPLICANO T&C | SOLO 18+ … div#outerwrap > div#main > div.contenthome > table.midsites
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●Elements use only permitted ARIA attributes
●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.
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
●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
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○`[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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback