Skip to content
https://truffa.net

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
7
REVIEW
3
PASS
14
INFO
0
Checks
24
14 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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 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

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
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: #29292a
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Mobile-Readable Font Sizes
94% of visible text renders at >= 12 CSS px (15 below threshold)
REVIEW
94% of visible text renders at >= 12 CSS px (15 below threshold)
Info::
15 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 ("ADM"); <span> 0.0px ("Gioco Responsabile"); <span> 0.0px ("Global Gambling Guidance Group"); <a> 0.0px ("X.com"); <a> 0.0px ("Instagram").
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 ✗
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 il sito d’informazione su gioco e inve…
1.90:1
#000000
on
#313F3B
needs 3.0:1 (large text)
32px · above the fold
title Truffa.net - i tuoi siti di gioco e di i…
1.44:1
#000000
on
#29292A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Truffa.net -
2.08:1
#000000
on
#244A23
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Navigate al sicuro
1.67:1
#000000
on
#2A3633
needs 4.5:1 (normal text)
16px · top of page (header area)
a Casinò Online Sicuri
1.70:1
#000000
on
#2B3734
needs 4.5:1 (normal text)
16px · top of page (header area)
a Siti Scommesse
1.72:1
#000000
on
#2C3835
needs 4.5:1 (normal text)
16px · above the fold
a Poker Online
1.75:1
#000000
on
#2C3936
needs 4.5:1 (normal text)
16px · above the fold
a Truffe Online
1.77:1
#000000
on
#2D3A37
needs 4.5:1 (normal text)
16px · above the fold
a Gioco d'Azzardo Online
1.80:1
#000000
on
#2E3B38
needs 4.5:1 (normal text)
16px · above the fold
a Broker Online
1.83:1
#000000
on
#2F3C39
needs 4.5:1 (normal text)
16px · above the fold
span Truffa.net:
1.85:1
#000000
on
#303D39
needs 4.5:1 (normal text)
16px · above the fold
p Benvenuti su Truffa.net, un portale che …
1.93:1
#000000
on
#32403C
needs 4.5:1 (normal text)
16px · above the fold
a Le truffe online più diffuse
1.96:1
#000000
on
#33413D
needs 4.5:1 (normal text)
16px · mid-page
p Tutte le informazioni sui raggiri e le t…
1.99:1
#000000
on
#33423E
needs 4.5:1 (normal text)
16px · mid-page
a Lista di casinò online sicuri
2.02:1
#000000
on
#34433E
needs 4.5:1 (normal text)
16px · mid-page
p L’elenco dei siti per giocare online i…
2.05:1
#000000
on
#35443F
needs 4.5:1 (normal text)
16px · mid-page
a I migliori siti di poker online
2.08:1
#000000
on
#364540
needs 4.5:1 (normal text)
16px · mid-page
p Le informazioni sui portali più affidab…
2.11:1
#000000
on
#364641
needs 4.5:1 (normal text)
16px · mid-page
a Top siti scommesse sicuri
2.14:1
#000000
on
#374742
needs 4.5:1 (normal text)
16px · mid-page
p La classifica dei migliori siti legali p…
2.18:1
#000000
on
#384843
needs 4.5:1 (normal text)
16px · mid-page

1 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
h1 il sito d’informaz…1.90:13.0:1
#000000
#313F3B
Fail
title Truffa.net - i tuoi …1.44:14.5:1
#000000
#29292A
Fail
a Truffa.net -2.08:14.5:1
#000000
#244A23
Fail
span Navigate al sicuro1.67:14.5:1
#000000
#2A3633
Fail
a Casinò Online Sicur…1.70:14.5:1
#000000
#2B3734
Fail
a Siti Scommesse1.72:14.5:1
#000000
#2C3835
Fail
a Poker Online1.75:14.5:1
#000000
#2C3936
Fail
a Truffe Online1.77:14.5:1
#000000
#2D3A37
Fail
a Gioco d'Azzardo Onli…1.80:14.5:1
#000000
#2E3B38
Fail
a Broker Online1.83:14.5:1
#000000
#2F3C39
Fail
span Truffa.net:1.85:14.5:1
#000000
#303D39
Fail
p Benvenuti su Truffa.…1.93:14.5:1
#000000
#32403C
Fail
a Le truffe online pi…1.96:14.5:1
#000000
#33413D
Fail
p Tutte le informazion…1.99:14.5:1
#000000
#33423E
Fail
a Lista di casinò onl…2.02:14.5:1
#000000
#34433E
Fail
p L’elenco dei siti …2.05:14.5:1
#000000
#35443F
Fail
a I migliori siti di p…2.08:14.5:1
#000000
#364540
Fail
p Le informazioni sui …2.11:14.5:1
#000000
#364641
Fail
a Top siti scommesse s…2.14:14.5:1
#000000
#374742
Fail
p La classifica dei mi…2.18:14.5:1
#000000
#384843
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+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 Truffa.net: il sito d’informazione su gioco e investimenti sicuri online
  • H2 La nostra missione
  • H3 La nostra redazione
  • H2 La vostra fonte contro le truffe online
  • H3 La nostra sezione news
  • H2 Le ultime news sul gioco online, investimenti e truffe
  • H2 Perché fidarsi delle nostre recensioni
  • H3 Guide e recensioni dei siti di gioco online
  • H3 I migliori giochi e i portali sicuri di gambling in Italia
  • H3 Il gioco sicuro diventa sempre più accessibile e rapido
  • H3 Siti per scommettere sullo sport
  • H2 Il nostro impegno contro le truffe online
A+
Heading Text Quality
All 12 heading(s) have substantive, well-formed text
PASS
All 12 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
1 of 16 images have issues
PASS
1 of 16 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
15 image(s) with good alt text
16 images 15 good alt text 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 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">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Scegli il tuo Paese)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 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"
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+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 25 passed
PASS
95

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
div.container > div.row > div.ft-links > div.ft-title div.container > div.row > div.ft-links > div.ft-title
div.row > div.ft-text > div > p div.row > div.ft-text > div > p
div.row > div.ft-text > div > p div.row > div.ft-text > div > p
body.template-homepage > footer.footer > div.container > div.rights body.template-homepage > footer.footer > div.container > div.rights

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.loaded html.loaded

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
3 div.Container-sc-fc289e8f-2 > div.Block-sc-666647aa-0 > div.Counters__Container-sc-7e553217-3 > a.Link__A-sc-fbeb463-0
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback