Skip to content
https://fattoasezze.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 12 -1-on-focusable
FIX
0 positive, 12 -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.)
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::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
B
Landmark Structure
25 landmarks
REVIEW
25 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
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 "Horizontal" MAIN 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

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

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pagina non trovata - Fatto a Sezze ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Navigazione articoli19.95:13.0:1
#000000
#F9F9F9
Pass
title Fatto a Sezze - La r…19.26:14.5:1
#000000
#F5F5F5
Pass
a Skip to the content18.93:14.5:1
#000000
#F3F3F3
Pass
span Fatto a Sezze18.93:14.5:1
#000000
#F3F3F3
Pass
a Fatto a Sezze18.93:14.5:1
#000000
#F3F3F3
Pass
span La rivista online di…18.93:14.5:1
#000000
#F3F3F3
Pass
a La redazione18.93:14.5:1
#000000
#F3F3F3
Pass
span Favourites6.17:14.5:1
#000000
#688CC8
Pass
a Le clarisse e “l…18.93:14.5:1
#000000
#F3F3F3
Pass
time 16 Febbraio 202618.93:14.5:1
#000000
#F3F3F3
Pass
a Luigi, un carabinier…18.93:14.5:1
#000000
#F3F3F3
Pass
time 13 Febbraio 202618.93:14.5:1
#000000
#F3F3F3
Pass
a La Meloni che vuole …18.93:14.5:1
#000000
#F3F3F3
Pass
time 31 Gennaio 202618.93:14.5:1
#000000
#F3F3F3
Pass
a La fiaccola olimpica…18.93:14.5:1
#000000
#F3F3F3
Pass
time 28 Dicembre 202518.93:14.5:1
#000000
#F3F3F3
Pass
a Auguri atei ma di ca…18.93:14.5:1
#000000
#F3F3F3
Pass
time 24 Dicembre 202518.93:14.5:1
#000000
#F3F3F3
Pass
a Lucio Planera raccon…18.93:14.5:1
#000000
#F3F3F3
Pass
time 6 Dicembre 202518.93:14.5:1
#000000
#F3F3F3
Pass

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

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 25 passed
REVIEW
84

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrapper > div.header-item > div.navbar-controls > button.navbar-control div.wrapper > div.header-item > div.navbar-controls > button.navbar-control
div.wrapper > div.header-item > div.navbar-controls > button.navbar-control div.wrapper > div.header-item > div.navbar-controls > button.navbar-control
div.column > div.theme-block-left > div.theme-heading-controls > button.slide-btn div.column > div.theme-block-left > div.theme-heading-controls > button.slide-btn
div.column > div.theme-block-left > div.theme-heading-controls > button.slide-btn div.column > div.theme-block-left > div.theme-heading-controls > button.slide-btn
div.header-searchbar-inner > div.wrapper > div.header-searchbar-panel > button#search-closer div.header-searchbar-inner > div.wrapper > div.header-searchbar-panel > button#search-closer

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.theme-slider-item > article.theme-news-article > div.data-bg > a.img-link div.theme-slider-item > article.theme-news-article > div.data-bg > a.img-link
div.theme-block-middle > article.theme-news-article > div.data-bg > a.img-link div.theme-block-middle > article.theme-news-article > div.data-bg > a.img-link
div.theme-block-right > article.theme-news-article > div.data-bg > a.img-link div.theme-block-right > article.theme-news-article > div.data-bg > a.img-link
div.theme-block-right > article.theme-news-article > div.data-bg > a.img-link div.theme-block-right > article.theme-news-article > div.data-bg > a.img-link
div.theme-block-right > article.theme-news-article > div.data-bg > a.img-link div.theme-block-right > article.theme-news-article > div.data-bg > a.img-link
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post div.post-content > header.entry-header > h2.entry-title > a.booster-favourite-post
div.wrapper > div.header-searchbar-panel > div.header-searchbar-area > a.skip-link-search-top div.wrapper > div.header-searchbar-panel > div.header-searchbar-area > a.skip-link-search-top
div#offcanvas-menu > div.offcanvas-wraper > div.close-offcanvas-menu > a.skip-link-off-canvas div#offcanvas-menu > div.offcanvas-wraper > div.close-offcanvas-menu > a.skip-link-off-canvas
div#page > div#offcanvas-menu > div.offcanvas-wraper > a.skip-link-offcanvas div#page > div#offcanvas-menu > div.offcanvas-wraper > a.skip-link-offcanvas

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.

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
ULTIMI ARTICOLI div.theme-panel-header > div.block-title-wrapper > h2.block-title > span

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●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
●Links are distinguishable without relying on color.
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 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.
○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.
○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
Heading Hierarchy
31 headings, 1 skip(s)
PASS
31 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Fatto a SezzeFatto a Sezze
  • H3 Le clarisse e “l’impiego” irraggiungibile skipped
  • H3 Luigi, un carabiniere a via Resistenza
  • H3 La Meloni che vuole copiare Franco Zocca , l’ angelo e San Isidoro
  • H3 La fiaccola olimpica che passa a Sermoneta e umilia Sezze
  • H3 Auguri atei ma di cattolico educato
  • H3 Lucio Planera racconta la cappella sistina del popolo: l’Eremo di Santa Lucia. Una bella storia e una lettera per me
  • H3 La demografia di Lucidi e la memoria di Memmo Guidi
  • H3 La demografia di Lucidi e il futuro
  • H3 Il Volo di Luca Velletri ricordando Pavarotti
  • H2 Ultimi articoli
  • H3 Le clarisse e “l’impiego” irraggiungibile
  • H3 Luigi, un carabiniere a via Resistenza
  • H3 La Meloni che vuole copiare Franco Zocca , l’ angelo e San Isidoro
  • H3 La fiaccola olimpica che passa a Sermoneta e umilia Sezze
  • H3 Auguri atei ma di cattolico educato
  • H3 Le clarisse e “l’impiego” irraggiungibile
  • H3 Luigi, un carabiniere a via Resistenza
  • H3 La Meloni che vuole copiare Franco Zocca , l’ angelo e San Isidoro
  • H3 La fiaccola olimpica che passa a Sermoneta e umilia Sezze
  • H2 Le clarisse e “l’impiego” irraggiungibile
  • H2 Luigi, un carabiniere a via Resistenza
  • H2 La Meloni che vuole copiare Franco Zocca , l’ angelo e San Isidoro
  • H2 La fiaccola olimpica che passa a Sermoneta e umilia Sezze
  • H2 Auguri atei ma di cattolico educato
  • H2 Lucio Planera racconta la cappella sistina del popolo: l’Eremo di Santa Lucia. Una bella storia e una lettera per me
  • H2 La demografia di Lucidi e la memoria di Memmo Guidi
  • H2 La demografia di Lucidi e il futuro
  • H2 Il Volo di Luca Velletri ricordando Pavarotti
  • H2 Dicono dei morti e il mio viaggio piccolo
  • H2 Navigazione articoli

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

A+
Heading Text Quality
All 31 heading(s) have substantive, well-formed text
PASS
All 31 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
1 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
2 images 1 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 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: <input type="submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
ssearchRicerca per:none
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

A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
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+
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 91 visible text node(s) render at >= 12 CSS pixels
PASS
All 91 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