Skip to content
https://mediasetitalia.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
D
Heading Hierarchy
Action
115 headings, 1 skip(s)
FIX
115 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 AVANTI UN ALTRO
  • H2 (empty)
  • H2 ZELIG ON
  • H2 SUPER KARAOKE
  • H2 QUARTO GRADO
  • H2 AVANTI UN ALTRO
  • H2 (empty)
  • H6 SOLE A CATINELLE skipped
  • H6 C'ERA UNA VOLTA IL MUSICARELLO -- C'ERA UNA VOLTA IL ?MUSICARELLO FEGATELLO 6
  • H6 TIRA & MOLLA
  • H6 SPORT MEDIASET
  • H6 STUDIO APERTO MAG -- 23/05/2026
  • H6 DIARIO DEL GIORNO
  • H6 4 DI SERA NEWS
  • H6 PILLOLE DEL TG4 MEDICINA
  • H6 FORUM
  • H6 LO SPORTELLO DI FORUM
  • H6 PILLOLE DEL TG4 CASH - MEDIASET ITALIA -- , 19
  • H6 BEAUTIFUL -- 8408
  • H6 TRADIMENTO -- 220
  • H6 AVANTI UN ALTRO '25 - '26 STORY -- AVANTI UN ALTRO STORY, 97
  • H6 TG5
  • H6 SPORT MEDIASET
  • H6 SPORT MEDIASET EXTRA
  • H6 MORNING NEWS
  • H6 C'ERA UNA VOLTA IL MUSICARELLO -- C'ERA UNA VOLTA IL ?MUSICARELLO FEGATELLO 6
  • H6 CARABINIERI -- LA MIGLIORE TERAPIA
  • H6 COSE DI QUESTO MONDO -- COREA DEL NORD
  • H6 STUDIO APERTO MAG -- 23/05/2026
  • H6 SE SON ROSE
  • H6 TG5 PRIMA PAGINA
  • H6 TG5
  • H6 TRE SORELLE
  • H6 CROCIERA VIANELLO
  • H6 SPORT MEDIASET
  • H6 SPORT MEDIASET EXTRA
  • H6 4 DI SERA NEWS
  • H6 AVANTI UN ALTRO '25 - '26 STORY -- AVANTI UN ALTRO STORY, 98
  • H6 SOLE A CATINELLE
  • H6 C'ERA UNA VOLTA IL MUSICARELLO -- C'ERA UNA VOLTA IL ?MUSICARELLO FEGATELLO 6
  • H6 TIRA & MOLLA
  • H6 SPORT MEDIASET
  • H6 STUDIO APERTO MAG -- 23/05/2026
  • H6 DIARIO DEL GIORNO
  • H6 TIRA & MOLLA
  • H6 NANA' SUPER GIRL -- DOPPIO RAPIMENTO
  • H6 SPORT MEDIASET
  • H6 DIARIO DEL GIORNO
  • H6 4 DI SERA NEWS
  • H6 PILLOLE DEL TG4 MEDICINA
  • H6 FORUM
  • H6 LO SPORTELLO DI FORUM
  • H6 PILLOLE DEL TG4 CASH - MEDIASET ITALIA -- , 19
  • H6 BEAUTIFUL -- 8408
  • H6 TRADIMENTO -- 220
  • H6 AVANTI UN ALTRO '25 - '26 STORY -- AVANTI UN ALTRO STORY, 97
  • H6 TG5
  • H6 SPORT MEDIASET
  • H6 SPORT MEDIASET EXTRA
  • H6 MORNING NEWS
  • H6 C'ERA UNA VOLTA IL MUSICARELLO -- C'ERA UNA VOLTA IL ?MUSICARELLO FEGATELLO 6
  • H6 CARABINIERI -- LA MIGLIORE TERAPIA
  • H6 COSE DI QUESTO MONDO -- COREA DEL NORD
  • H6 STUDIO APERTO MAG -- 23/05/2026
  • H6 SE SON ROSE
  • H6 TG5 PRIMA PAGINA
  • H6 TG5
  • H6 TRE SORELLE
  • H6 CROCIERA VIANELLO
  • H6 SPORT MEDIASET
  • H6 SPORT MEDIASET EXTRA
  • H6 4 DI SERA NEWS
  • H6 AVANTI UN ALTRO '25 - '26 STORY -- AVANTI UN ALTRO STORY, 98
  • H6 SOLE A CATINELLE
  • H6 C'ERA UNA VOLTA IL MUSICARELLO -- C'ERA UNA VOLTA IL ?MUSICARELLO FEGATELLO 6
  • H6 TIRA & MOLLA
  • H6 NANA' SUPER GIRL -- DOPPIO RAPIMENTO
  • H6 SPORT MEDIASET
  • H6 DIARIO DEL GIORNO
  • H6 4 DI SERA NEWS
  • H6 PILLOLE DEL TG4 MEDICINA
  • H6 SPORT MEDIASET
  • H6 STUDIO APERTO MAG -- 23/05/2026
  • H6 DIARIO DEL GIORNO
  • H6 4 DI SERA NEWS
  • H6 FORUM
  • H6 LO SPORTELLO DI FORUM
  • H6 BEAUTIFUL -- 8407
  • H6 TRADIMENTO -- 219
  • H6 AVANTI UN ALTRO '25 - '26 STORY -- AVANTI UN ALTRO STORY, 96
  • H6 TG5
  • H6 SPORT MEDIASET
  • H6 SPORT MEDIASET EXTRA
  • H6 MORNING NEWS
  • H6 CARABINIERI -- SALTO NEL VUOTO
  • H6 COSE DI QUESTO MONDO -- CERCANDO SODOMA
  • H6 STUDIO APERTO MAG
  • H6 BUONA GIORNATA
  • H6 TG5 PRIMA PAGINA
  • H6 TG5
  • H6 TEMPTATION ISLAND
  • H6 ZONA BIANCA
  • H6 SPORT MEDIASET
  • H6 SPORT MEDIASET EXTRA
  • H6 4 DI SERA NEWS
  • H6 DIETRO LE QUINTE DI "ROSY ABATE"
  • H6 TIRA & MOLLA
  • H6 SPORT MEDIASET
  • H6 STUDIO APERTO MAG -- 23/05/2026
  • H6 DIARIO DEL GIORNO
  • H6 4 DI SERA NEWS
  • H6 FORUM
  • H6 LO SPORTELLO DI FORUM
  • H3 In Vetrina
  • H3 Tgcom24 news

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search_bar" id="search_bar">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search_bartext(Cerca...)placeholder only
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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="text" name="search_bar" id="search_bar">

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

B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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
h2 AVANTI UN ALTRO
1.05:1
#000000
on
#090707
needs 3.0:1 (large text)
24px · above the fold
h2 ZELIG ON
1.06:1
#000000
on
#0B0A0D
needs 3.0:1 (large text)
24px · above the fold
h2 SUPER KARAOKE
1.07:1
#000000
on
#0C0B0E
needs 3.0:1 (large text)
24px · mid-page
h2 QUARTO GRADO
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · mid-page
h2 AVANTI UN ALTRO
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · mid-page
h3 In Vetrina
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tgcom24 news
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
19px · bottom of viewport
title Mediaset Italia
1.20:1
#000000
on
#19191E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.20:1
#000000
on
#19191E
needs 4.5:1 (normal text)
16px · top of page (header area)
a GUARDA IN STREAMING SU PC, TABLET E SMAR…
1.20:1
#000000
on
#19191E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.20:1
#000000
on
#19191E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Guida tv
1.13:1
#000000
on
#161210
needs 4.5:1 (normal text)
16px · above the fold
a FAQ
1.01:1
#000000
on
#010203
needs 4.5:1 (normal text)
16px · above the fold
a Digita il titolo di un programma tv...
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Home
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Guida tv
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a FAQ
1.06:1
#000000
on
#0C0909
needs 4.5:1 (normal text)
16px · above the fold
p Paolo Bonolis, con Luca Laurenti, torna …
1.06:1
#000000
on
#09090B
needs 4.5:1 (normal text)
16px · above the fold
p Nuove voci della comicità tra pezzi ine…
1.07:1
#000000
on
#0B0B0D
needs 4.5:1 (normal text)
16px · mid-page
p Torna lo storico show in una veste tutta…
1.14:1
#000000
on
#141414
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 AVANTI UN ALTRO1.05:13.0:1
#000000
#090707
Fail
h2 ZELIG ON1.06:13.0:1
#000000
#0B0A0D
Fail
h2 SUPER KARAOKE1.07:13.0:1
#000000
#0C0B0E
Fail
h2 QUARTO GRADO1.14:13.0:1
#000000
#141414
Fail
h2 AVANTI UN ALTRO1.14:13.0:1
#000000
#141414
Fail
h3 In Vetrina1.14:13.0:1
#000000
#141414
Fail
h3 Tgcom24 news1.14:13.0:1
#000000
#141414
Fail
title Mediaset Italia1.20:14.5:1
#000000
#19191E
Fail
a Skip to content1.20:14.5:1
#000000
#19191E
Fail
a GUARDA IN STREAMING …1.20:14.5:1
#000000
#19191E
Fail
a Home1.20:14.5:1
#000000
#19191E
Fail
a Guida tv1.13:14.5:1
#000000
#161210
Fail
a FAQ1.01:14.5:1
#000000
#010203
Fail
a Digita il titolo di …1.00:14.5:1
#000000
#000000
Fail
a Home1.00:14.5:1
#000000
#000000
Fail
a Guida tv1.00:14.5:1
#000000
#000000
Fail
a FAQ1.06:14.5:1
#000000
#0C0909
Fail
p Paolo Bonolis, con L…1.06:14.5:1
#000000
#09090B
Fail
p Nuove voci della com…1.07:14.5:1
#000000
#0B0B0D
Fail
p Torna lo storico sho…1.14:14.5:1
#000000
#141414
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 20 passed
REVIEW
88

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
ROME (CET/CEST) div.section-inner-container > a > div.ls-banner > span.time-location
AUSTRALIA (AEST/AEDT) div.section-inner-container > a > div.ls-banner > span.time-location

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
C'ERA UNA VOLTA IL MUSICARELLO -- C'ERA UNA VOLTA IL ?MUSICARELLO FEGATELLO 6 a > div.live-schedule-item > div.top-info > h6.program-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content body.home > div#page > a.skip-link

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contatti div.menu-container > div.row > div.col-12 > a
Privacy & Cookie div.menu-container > div.row > div.col-12 > a

These items highlight common accessibility best practices.

○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 use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #primary
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
105 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: 105 all-caps heading(s)
A+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
2 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
23 images 21 good alt text 2 decorative
All images have appropriate alt text.
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 "search_bar" should use type="search" (currently type="text")
Field name "search_bar" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
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+
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
8 explicit tabindex attribute(s) checked, no anti-patterns
PASS
8 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Mobile-Readable Font Sizes
All 224 visible text node(s) render at >= 12 CSS pixels
PASS
All 224 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback