Skip to content
https://toplista.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
F
Heading Hierarchy
Action
32 headings, 3 skip(s)
FIX
32 headings, 3 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 I Migliori Siti di Pronostici di Calcio 2026 – Classifica
  • H5 Classifica dei Migliori Siti di Scommesse e bookmaker con i Bonus più Alti in Italia 2026 skipped
  • H5 Migliori friggitrici ad aria: Top 10 del 2026
  • H5 I Migliori Calciatori di sempre: la Top 10 secondo uno studio matematico
  • H5 Migliori Affiliazioni Trading 2025: i 10 programmi che fanno guadagnare fino a 50.000€ al mese
  • H2 Le classifiche più lette
  • H5 I Migliori Calciatori di sempre: la Top 10 secondo uno studio matematico skipped
  • H5 Migliori Affiliazioni Trading 2025: i 10 programmi che fanno guadagnare fino a 50.000€ al mese
  • H5 I Migliori Vini Siciliani: Top10 Classifica definitiva del 2025
  • H6 Le nostre Classifiche Migliori
  • H2 Migliori siti Trading Online 2025
  • H4 I Migliori Calciatori di sempre: la Top 10 secondo uno studio matematico skipped
  • H4 Migliori Affiliazioni Trading 2025: i 10 programmi che fanno guadagnare fino a 50.000€ al mese
  • H4 I Migliori Vini Siciliani: Top10 Classifica definitiva del 2025
  • H4 I Migliori Materassi in Commercio: la top 10 aggiornata al 2025
  • H4 Le Migliori Rock Band di Sempre: Classifica Definitiva delle Leggende del Rock
  • H4 Migliori servizi per denunciare online in Italia: la classifica Completa
  • H4 Classifica dei Migliori Conti Correnti Gratuiti e Senza Spese per Sempre
  • H4 I Migliori Conti Deposito di Novembre 2026: Classifica Completa
  • H4 Iscriviti alla Newsletter
  • H5 I Migliori Siti di Pronostici di Calcio 2026 – Classifica
  • H5 Classifica dei Migliori Siti di Scommesse e bookmaker con i Bonus più Alti in Italia 2026
  • H5 Migliori friggitrici ad aria: Top 10 del 2026
  • H6 I Migliori Siti di Pronostici di Calcio 2026 – Classifica
  • H6 Classifica dei Migliori Siti di Scommesse e bookmaker con i Bonus più Alti in Italia 2026
  • H6 Migliori friggitrici ad aria: Top 10 del 2026
  • H5 Classifica dei Migliori Siti di Scommesse e bookmaker con i Bonus più Alti in Italia 2026
  • H5 Migliori friggitrici ad aria: Top 10 del 2026
  • H5 I Migliori Calciatori di sempre: la Top 10 secondo uno studio matematico
  • H3 Toplista Tech
  • H2 Iscriviti alla newsletter
  • H2 Tutte le Classifiche che hai sempre cercato GRATIS!

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

D
Tabindex Anti-Patterns
Action
0 positive, 29 -1-on-focusable
FIX
0 positive, 29 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
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::
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.
C
Form Accessibility
Action
3 of 4 controls have issues
REVIEW
3 of 4 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="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="kb_field_2" id="kb_field_10734_74ff65-d6_2">; <input type="email" name="kb_field_0" id="kb_field_10734_d31233-a5_0">
Info::
1 control(s) properly labeled
4 controls
1 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
ssearchRicerca per:none
#kb_field_10734_d31233-a5_0email(Email)placeholder only
#kb_field_10734_74ff65-d6_2email(Lascia la tua mail...)placeholder only
inputsubmit(none)none

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

<input type="submit">

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="email" name="kb_field_2" id="kb_field_10734_74ff65-d6_2">; <input type="email" name="kb_field_0" id="kb_field_10734_d31233-a5_0">

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
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h2 Le classifiche più lette
1.05:1
#000000
on
#08012A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Migliori siti Trading Online 2025
1.05:1
#000000
on
#08012A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Iscriviti alla newsletter
1.05:1
#000000
on
#08012A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tutte le Classifiche che hai sempre cerc…
1.05:1
#000000
on
#08012A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Toplista Tech
1.05:1
#000000
on
#08012A
needs 3.0:1 (large text)
19px · bottom of viewport
span Cinema
1.08:1
#000000
on
#09003D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Animazione
1.08:1
#000000
on
#09003C
needs 4.5:1 (normal text)
16px · above the fold
a Horror
1.07:1
#000000
on
#09003A
needs 4.5:1 (normal text)
16px · above the fold
a Serie Tv
1.07:1
#000000
on
#090038
needs 4.5:1 (normal text)
16px · above the fold
a Musica
1.07:1
#000000
on
#080037
needs 4.5:1 (normal text)
16px · above the fold
span Tech
1.07:1
#000000
on
#090038
needs 4.5:1 (normal text)
16px · above the fold
a Giochi
1.07:1
#000000
on
#090038
needs 4.5:1 (normal text)
16px · above the fold
a Fotografia
1.07:1
#000000
on
#080137
needs 4.5:1 (normal text)
16px · above the fold
a Internet
1.06:1
#000000
on
#050135
needs 4.5:1 (normal text)
16px · above the fold
a Sicurezza
1.06:1
#000000
on
#050135
needs 4.5:1 (normal text)
16px · above the fold
a Smartphone
1.06:1
#000000
on
#050231
needs 4.5:1 (normal text)
16px · mid-page
a Telefonia
1.06:1
#000000
on
#050230
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Le classifiche più …1.05:13.0:1
#000000
#08012A
Fail
h2 Migliori siti Tradin…1.05:13.0:1
#000000
#08012A
Fail
h2 Iscriviti alla newsl…1.05:13.0:1
#000000
#08012A
Fail
h2 Tutte le Classifiche…1.05:13.0:1
#000000
#08012A
Fail
h3 Toplista Tech1.05:13.0:1
#000000
#08012A
Fail
title Toplista: Le Miglior…21.00:14.5:1
#000000
#FFFFFF
Pass
a Salta al contenuto21.00:14.5:1
#000000
#FFFFFF
Pass
p Le Migliori Liste e …7.61:14.5:1
#000000
#9C99B2
Pass
span Cinema1.08:14.5:1
#000000
#09003D
Fail
a Animazione1.08:14.5:1
#000000
#09003C
Fail
a Horror1.07:14.5:1
#000000
#09003A
Fail
a Serie Tv1.07:14.5:1
#000000
#090038
Fail
a Musica1.07:14.5:1
#000000
#080037
Fail
span Tech1.07:14.5:1
#000000
#090038
Fail
a Giochi1.07:14.5:1
#000000
#090038
Fail
a Fotografia1.07:14.5:1
#000000
#080137
Fail
a Internet1.06:14.5:1
#000000
#050135
Fail
a Sicurezza1.06:14.5:1
#000000
#050135
Fail
a Smartphone1.06:14.5:1
#000000
#050231
Fail
a Telefonia1.06:14.5:1
#000000
#050230
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
56 landmarks
PASS
56 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Navigazione Principale" 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 Text Quality
All 32 heading(s) have substantive, well-formed text
PASS
All 32 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 32 images OK
PASS
All 32 images OK
Info::
4 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
32 images 28 good alt text 4 decorative
All images have appropriate alt text.
A+
Form Input Types
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 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+
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+
Mobile-Readable Font Sizes
All 121 visible text node(s) render at >= 12 CSS pixels
PASS
All 121 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
Lighthouse Accessibility Audits
Score 91/100 — 4 failing, 24 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
div.wp-block-kadence-form > form.kb-form > div.kadence-blocks-form-field > input#kb_field_10734_74ff65-d6_2 div.wp-block-kadence-form > form.kb-form > div.kadence-blocks-form-field > input#kb_field_10734_74ff65-d6_2

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
Classifica Dei Migliori Siti Di Scommesse E Bookmaker Con I Bonus Più Alti In I… article.entry > div.entry-content-wrap > header.entry-header > h5.entry-title
I Migliori Calciatori Di Sempre: La Top 10 Secondo Uno Studio Matematico article.entry > div.entry-content-wrap > header.entry-header > h5.entry-title
I Migliori Calciatori Di Sempre: La Top 10 Secondo Uno Studio Matematico article.entry > div.entry-content-wrap > header.entry-header > h4.entry-title

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.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay
div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay
div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay
div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay
div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay
div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay
div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay
div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay div.kb-row-layout-wrap > div.kt-row-column-wrap > div.wp-block-kadence-column > a.kb-section-link-overlay

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.

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
Toplista Tech Le Migliori Classifiche Tech del momento Entra div.wp-block-kadence-column > div.kt-inside-inner-col > div.wp-block-kadence-infobox > a.kt-blocks-info-box-link-wrap
○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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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 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
○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.
○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.
○`<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.
○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