Skip to content
https://sitiscommesse.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
7
REVIEW
2
PASS
15
INFO
0
Checks
24
15 PASS 2 REVIEW 7 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!) ASIDE 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

D
Mobile Keyboard & Autofill
Action
1/1 eligible field(s) missing autocomplete or inputmode
FIX
1/1 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="text" name="email" id="email">
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #0d8360
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 ModePartial Dark Mode
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.
C
Mobile-Readable Font Sizes
Action
85% of visible text renders at >= 12 CSS px (41 below threshold)
REVIEW
85% of visible text renders at >= 12 CSS px (41 below threshold)
Warning::
41 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> 0.0px ("Show Navigation"); <span> 0.0px ("Agenzia Dogane Monopoli"); <span> 0.0px ("ADM"); <span> 0.0px ("gioco responsabile"); <span> 0.0px ("Crittografia").
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pagina non trovata ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Heading Hierarchy
53 headings
PASS
53 headings
Info::
Single H1 present
  • H1 Migliori siti scommesse online: guida ai top bookmaker d’Italia
  • H2 I migliori siti scommesse in Italia del momento
  • H3 Planetwin365
  • H3 Eurobet
  • H3 GoldBet
  • H3 Betsson
  • H3 Sportium
  • H3 Netwin
  • H3 bwin
  • H3 Sisal
  • H3 BetFlag
  • H3 SNAI
  • H2 Le classifiche dei siti per scommesse sportive
  • H3 Siti di scommesse AAMS top del 2026
  • H3 Migliori quote siti scommesse
  • H3 Top bookmaker online per il calcio
  • H3 Siti scommesse sportive italiani
  • H3 Bookmaker stranieri top
  • H2 Come valutare i siti scommesse sicuri in Italia
  • H3 La varietà dell’offerta scommesse dei bookmaker AAMS/ADM
  • H3 Le quote sui bookies italiani
  • H3 Il palinsesto scommesse live
  • H3 La qualità delle applicazioni mobile dei bookmaker
  • H3 I bonus proposti dai siti scommesse
  • H3 Migliori siti scommesse online e modalità di pagamento
  • H3 Fate attenzione a particolari e dettagli
  • H3 I sistemi di sicurezza usati dai bookmaker
  • H3 Il miglior sito scommesse lo si vede anche dal servizio clienti
  • H3 Punti bonus
  • H2 Come abbiamo testato i siti di scommesse
  • H3 Il calcolo del payout medio
  • H3 L’effettiva incidenza di payout diversi
  • H3 Le tipologie di contatto del servizio clienti
  • H3 I metodi di pagamento disponibili sui bookmaker
  • H3 La grafica della piattaforma online
  • H3 Gli altri fattori che abbiamo considerato
  • H2 Scommesse online e in agenzia: pro e contro
  • H2 Conto gioco online: come aprirne uno
  • H2 Il betting exchange e il cash out
  • H3 Betting exchange: una breve panoramica
  • H3 L’opzione scommesse cash out
  • H4 I migliori siti per scommesse con cash out
  • H2 Licenza AAMS/ADM e norme per i bookmaker online
  • H3 La regolamentazione italiana sulle scommesse online
  • H3 La lista degli operatori illegali
  • H2 Conclusione: il miglior sito scommesse del momento
  • H2 Domande frequenti
  • H3 🔝Quali sono oggi i migliori siti di scommesse?
  • H3 🔒 Quali sono i siti scommesse online più sicuri?
  • H3 ⚙️ Come si scelgono i migliori siti scommesse online?
  • H3 ⚖️ Scommettere online in Italia è legale?
  • H3 ❓ Come posso incassare le vincite dai siti scommesse?
  • H3 💻 Come giocare una schedina online?
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 30 images OK
PASS
All 30 images OK
Info::
30 image(s) with good alt text
30 images 30 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#emailtextIndirizzo emailfor/id
inputtext(Seleziona lingua)placeholder only

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

<input type="text">

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

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "it"
PASS
Lang attribute set to "it"
Info::
<html lang="it"> is set and valid
Got: 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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
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
h1 Migliori siti scomme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I migliori siti scom…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Le classifiche dei21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Come valutare i siti…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Come abbiamo testato…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Scommesse online e i…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Conto gioco online: …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Il betting exchange …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Licenza AAMS/ADM e n…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Conclusione: il migl…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Domande frequenti21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Siti di scommesse AA…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Migliori quote siti …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Top bookmaker online…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Siti scommesse sport…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bookmaker stranieri …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 La varietà dell’o…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Le quote sui bookies…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Il palinsesto scomme…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 La qualità delle ap…21.00:13.0:1
#000000
#FFFFFF
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
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 18 passed
PASS
92

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
Scritto da: Denis Michelotti div.container > div.latest-info-box > div.author-info > div.content-box
Aggiornato il: 06.08.2026 div.container > div.latest-info-box > div.update-date > span
Planetwin365 div.list > ol.has-bullets > li > a
Eurobet div.list > ol.has-bullets > li > a
GoldBet div.list > ol.has-bullets > li > a
Betsson div.list > ol.has-bullets > li > a
Sportium div.list > ol.has-bullets > li > a
Netwin div.list > ol.has-bullets > li > a
bwin div.list > ol.has-bullets > li > a
Sisal div.list > ol.has-bullets > li > a
BetFlag div.list > ol.has-bullets > li > a
SNAI div.list > ol.has-bullets > li > a
div.accordion-simple > div.accordion-section > div.accordion-head > h3 div.accordion-simple > div.accordion-section > div.accordion-head > h3
div.accordion-simple > div.accordion-section > div.accordion-head > h3 div.accordion-simple > div.accordion-section > div.accordion-head > h3
div.accordion-simple > div.accordion-section > div.accordion-head > h3 div.accordion-simple > div.accordion-section > div.accordion-head > h3
div.accordion-simple > div.accordion-section > div.accordion-head > h3 div.accordion-simple > div.accordion-section > div.accordion-head > h3
i criteri e la metodologia div.container > div.container > p.emphasis > a
div.news-thumbs > ul.news-thumbs-list > li > span.news-author div.news-thumbs > ul.news-thumbs-list > li > span.news-author
div.news-thumbs > ul.news-thumbs-list > li > span.news-author div.news-thumbs > ul.news-thumbs-list > li > span.news-author
guida al fantacalcio div.container > div.container > p > a
scommesse sui motori div.container > div.container > p > a
div.container > div.author-quote-box > div.author-quote-name > a div.container > div.author-quote-box > div.author-quote-name > a
comparatore quote scommesse div.container > div.container > p > a
div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-title div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-title
div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-matchup-date div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-matchup-date
div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-title div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-title
div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-matchup-date div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-matchup-date
div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-title div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-title
div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-matchup-date div.odds-internal-group > div.odds-internal > div.odds-head > div.odds-matchup-date
migliori app scommesse div.container > div.container > p > a
bonus scommesse div.container > div.container > p > a
bonus casinò div.container > div.container > p > a
div.container > div.author-quote-box > div.author-quote-name > a div.container > div.author-quote-box > div.author-quote-name > a
bookies con SPID div.container > div.container > p > a
siti scommesse con deposito minimo 5 euro div.container > div.container > p > a
nuovi siti scommesse div.container > div.container > p > a
licenza rilasciata dall’ADM div.container > div.container > p > a
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a tbody > tr > td > a
siti scommesse con prelievo immediato div.container > div.container > p > a
401 del 1989, all’articolo 4, comma 1 div.container > div.container > p > a
tassa sulla fortuna div.container > div.container > p > a
sito web dell’Agenzia Dogane e Monopoli div.container > div.container > p > a
div.container > div.author-quote-box > div.author-quote-name > a div.container > div.author-quote-box > div.author-quote-name > a
div.area-illegal > div.area-pad > p.p-wico > a div.area-illegal > div.area-pad > p.p-wico > a
div.container > div.area-illegal > p > a div.container > div.area-illegal > p > a
siti roulette online div.container > div.container > p > a
info@sitiscommesse.com div.container > div.container > p > a

These are opportunities to improve the legibility of your content.

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.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.calc-halves > div.half1 > div.basic-table > table div.calc-halves > div.half1 > div.basic-table > table
div.calc-halves > div.half2 > div.basic-table > table div.calc-halves > div.half2 > div.basic-table > table
○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>`
●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.
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●`<td>` elements in a large `<table>` have one or more table headers.
○`[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
○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
○Elements use only permitted ARIA attributes
○`[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
○`[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
○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.
○`[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
○Elements with visible text labels have matching accessible names.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback