Skip to content
https://www.alessandrorosina.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
4
REVIEW
10
PASS
10
INFO
0
Checks
24
10 PASS 10 REVIEW 4 FIX
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: #121212
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::
3 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 3 <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.
B
Landmark Structure
19 landmarks
REVIEW
19 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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 ASIDE CONTENTINFO footer

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

B
Heading Hierarchy
12 headings, 1 skip(s)
REVIEW
12 headings, 1 skip(s)
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Alessandro Rosina
  • H2 articoli
  • H1 Italia, generazione zero figli: il peso delle incertezze e dei cambiamenti culturali duplicate H1
  • H1 Le giovani generazioni, il basso peso elettorale e le priorità politiche duplicate H1
  • H2 agenda
  • H2 Mediateca
  • H2 commenti e riflessioni
  • H1 Quello che i demografi anticipano... duplicate H1
  • H1 Degiovanimento duplicate H1
  • H4 La scomparsa dei giovani skipped
  • H4 Argomenti
  • H2 Informativa

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

B
Alt Text Quality
3 of 6 images have issues
REVIEW
3 of 6 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
6 images 2 good alt text 1 decorative 3 missing
IssueCount
missing3 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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="searchsubmit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
1 control(s) properly labeled
3 controls
1 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#stextCerca:for/id
#searchsubmitsubmit(none)none
#g-recaptcha-response-100000textarea(none)none

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

<input type="submit" id="searchsubmit">; <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

B
Iframe Accessibility
2/14 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/14 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.
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.
C
Mobile-Readable Font Sizes
Action
88% of visible text renders at >= 12 CSS px (11 below threshold)
REVIEW
88% of visible text renders at >= 12 CSS px (11 below threshold)
Warning::
11 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> 11.2px ("07/11/2026"); <span> 11.2px ("12:00 - 13:00"); <span> 11.2px ("Padova, Centro Altinate"); <span> 11.2px ("06/11/2026"); <span> 11.2px ("9.30").
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h1 Alessandro Rosina
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · above the fold
title Alessandro Rosina
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Alessandro Rosina
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a chi sono
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a agenda pubblica
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a articoli
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a materiali e proposte
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a commenti e riflessioni
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a libri
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a sulla stampa
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a link
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a contatti
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
label Navigation
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Home
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a chi sono
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a agenda pubblica
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a articoli
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Alessandro Rosina1.00:13.0:1
#000000
#000000
Fail
h2 Mediateca18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Informativa18.10:13.0:1
#000000
#EEEEEE
Pass
title Alessandro Rosina1.00:14.5:1
#000000
#000000
Fail
a Alessandro Rosina1.00:14.5:1
#000000
#000000
Fail
a Home1.00:14.5:1
#000000
#000000
Fail
a chi sono1.00:14.5:1
#000000
#000000
Fail
a agenda pubblica1.00:14.5:1
#000000
#000000
Fail
a articoli1.00:14.5:1
#000000
#000000
Fail
a materiali e proposte1.00:14.5:1
#000000
#000000
Fail
a commenti e riflessio…1.00:14.5:1
#000000
#000000
Fail
a libri1.00:14.5:1
#000000
#000000
Fail
a sulla stampa1.00:14.5:1
#000000
#000000
Fail
a link1.00:14.5:1
#000000
#000000
Fail
a contatti1.00:14.5:1
#000000
#000000
Fail
label Navigation1.00:14.5:1
#000000
#000000
Fail
a Home1.00:14.5:1
#000000
#000000
Fail
a chi sono1.00:14.5:1
#000000
#000000
Fail
a agenda pubblica1.00:14.5:1
#000000
#000000
Fail
a articoli1.00:14.5:1
#000000
#000000
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 27 passed
REVIEW
83

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
Alessandro Rosina div.contain-to-grid > nav.tab-bar > section.middle > h1.title
A.Rosina div#inner-content > div#main > div#minime > span#minime-auth
Italia, generazione zero figli: il peso delle incertezze e dei cambiamenti cult… article#post- > header.home-articolo-header > h1.entry-title > a
di Alessandro Rosina - 28 Luglio 2026 - in giovani, popolazione, risorse e svil… article#post- > header.home-articolo-header > div.byline-data > div.byline-home
giovani header.home-articolo-header > div.byline-data > div.byline-home > a
popolazione, risorse e sviluppo header.home-articolo-header > div.byline-data > div.byline-home > a
vai all'articolo article#post- > section.home-articolo-content > span.vai-a > a
Le giovani generazioni, il basso peso elettorale e le priorità politiche article#post- > header.home-articolo-header > h1.entry-title > a
di Alessandro Rosina - 17 Luglio 2026 - in giovani, popolazione, risorse e svil… article#post- > header.home-articolo-header > div.byline-data > div.byline-home
giovani header.home-articolo-header > div.byline-data > div.byline-home > a
popolazione, risorse e sviluppo header.home-articolo-header > div.byline-data > div.byline-home > a
vai all'articolo article#post- > section.home-articolo-content > span.vai-a > a
07/11/2026 tbody > tr > td > span
12:00 - 13:00 tbody > tr > td > span
Padova, Centro Altinate tbody > tr > td > span
CICAP FEST - “SALTO. IL FUTURO È QUI” div#home-agenda > div.home-evento > span > a
sito div#home-agenda > div.home-evento > span.home-evento-info > a
06/11/2026 tbody > tr > td > span
9.30 tbody > tr > td > span
Bologna, Sala Filla (auditorium), Parco della Montagnola in via Irnerio, 2/6 – … tbody > tr > td > span
III Giornata seminariale di Alleanza per l'Infanzia div#home-agenda > div.home-evento > span > a
05/11/2026 tbody > tr > td > span
14.30 tbody > tr > td > span
Milano - Fondazione Feltrinelli tbody > tr > td > span
HR INNOVATION CIRCLE div#home-agenda > div.home-evento > span > a
sito div#home-agenda > div.home-evento > span.home-evento-info > a
Quello che i demografi anticipano... article#post- > header.home-articolo-header > h1.entry-title > a
di Alessandro Rosina - 9 Agosto 2022 - in article#post- > header.home-articolo-header > div.byline-data > p.byline
Degiovanimento article#post- > header.home-articolo-header > h1.entry-title > a
di Alessandro Rosina - 3 Ottobre 2021 - in article#post- > header.home-articolo-header > div.byline-data > p.byline
ISBN: 9788832967159 div#widget_sp_image-2 > div.widget_sp_image-description > p > a
div#sidebar1 > div#search-2 > form#searchform > input#searchsubmit div#sidebar1 > div#search-2 > form#searchform > input#searchsubmit
giovani div#categories-3 > ul > li.cat-item > a
degiovanimento li.cat-item > ul.children > li.cat-item > a
millennials li.cat-item > ul.children > li.cat-item > a
longevità e invecchiamento attivo div#categories-3 > ul > li.cat-item > a
popolazione, risorse e sviluppo div#categories-3 > ul > li.cat-item > a
talenti in movimento div#categories-3 > ul > li.cat-item > a
ulteriori temi demografici div#categories-3 > ul > li.cat-item > a
welfare e innovazione sociale div#categories-3 > ul > li.cat-item > a
Tweets by @AleRosina68 div#sidebar1 > div#text-3 > div.textwidget > a.twitter-timeline
© 2026 Alessandro Rosina - contenuti a cura di Alessia Marsigalia div#inner-footer > div.large-12 > div.large-8 > p.source-org
contenuti a cura di Alessia Marsigalia div.large-12 > div.large-8 > p.source-org > span

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
giovani header.home-articolo-header > div.byline-data > div.byline-home > a
popolazione, risorse e sviluppo header.home-articolo-header > div.byline-data > div.byline-home > a
giovani header.home-articolo-header > div.byline-data > div.byline-home > a
popolazione, risorse e sviluppo header.home-articolo-header > div.byline-data > div.byline-home > a

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
La scomparsa dei giovani div#inner-content > div#sidebar1 > div#widget_sp_image-2 > h4.widgettitle

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#logo-wrapper > div#logo-1 > span.show-for-small-only > img div#logo-wrapper > div#logo-1 > span.show-for-small-only > img
div#inner-header > div#logo-wrapper > div#logo-2 > img div#inner-header > div#logo-wrapper > div#logo-2 > img

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.contain-to-grid > nav.tab-bar > section.left-small > a.left-off-canvas-toggle div.contain-to-grid > nav.tab-bar > section.left-small > a.left-off-canvas-toggle

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NAVIGATION Home chi sono agenda pubblica articoli materiali e proposte commenti… header.header > div#inner-header > aside.left-off-canvas-menu > ul.off-canvas-list

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Input buttons have discernible text.
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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 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.
○`<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.
○Elements with visible text labels have matching accessible names.
○`<td>` elements in a large `<table>` have one or more table headers.
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+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 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
4 explicit tabindex attribute(s) checked, no anti-patterns
PASS
4 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pagina non trovata - Alessandro Rosina ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback