Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 31 -1-on-focusable

FIX

0 positive, 31 -1-on-focusable

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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.)

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

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

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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

8 navigation landmark(s) detected

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 8 <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.

C

Landmark Structure

Action

19 landmarks

REVIEW

19 landmarks

<main> landmark present

8 <nav> landmark(s) found

4 of 8 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

No contentinfo (footer) landmark

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

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

14 headings

REVIEW

14 headings

No H1 heading found

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

H3 info@casaliniecosrl.it
H3 051 6199688
H3 Via dell'Intagliatore, 1, 40138 (BO)
H3 DIVISONE IMPERMEABILE
H3 DIVISIONE EDILE
H2 Leggi le News
H3 Casalini & co oltre al profitto, per scelta
H3 Casalini & CO Srl certificata ISO 27001:2022
H3 Casalini & CO Srl certificata ISO 50001: 2018
H2 La nostra evoluzione
H2 Per saperne di più
H2 Lavorazioni
H2 I nostri interventi negli ultimi 2 anni
H2 Clienti

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

C

Link & Button Quality

Action

14 issue(s) across 96 links and 0 buttons

REVIEW

14 issue(s) across 96 links and 0 buttons

14 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: mailto:info@casaliniecosrl.it; tel:+390516199673; https://www.google.it/maps/place/Via+dell'Intagliatore,+1,+40138+Bologna+BO/@…; mailto:info@casaliniecosrl.it; tel:+390516199673; https://www.google.com/maps/place/Via+dell'Intagliatore,+1,+40138+Bologna+BO/…; https://www.casaliniecosrl.it/casalini-co-srl-certificata-iso-270012022/; https://www.casaliniecosrl.it/casalini-co-srl-certificata-iso-50001-2018/; https://www.casaliniecosrl.it/wp-content/uploads/2023/03/Ospedale-Montecchio-…; https://www.casaliniecosrl.it/wp-content/uploads/2023/03/Unicoop-Lastra-a-Sig… (+4 more)

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.casaliniecosrl.it/casalini-co/; https://www.casaliniecosrl.it/casalini-co/; https://www.casaliniecosrl.it/casalini-co-srl-certificata-iso-270012022/; https://www.casaliniecosrl.it/casalini-co-srl-certificata-iso-50001-2018/; https://www.casaliniecosrl.it/wp-content/uploads/2025/07/BROCHURE-DIV.-EDILE-…; https://www.casaliniecosrl.it/wp-content/uploads/2025/06/BROCHURE-DIV.-IMPERM…; https://accesso.acconsento.click/informative/page/5790/it

75 link(s) with descriptive text

96 links

14 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
mailto:info@casaliniecosrl.it	(empty)	empty	Add link text or aria-label
tel:+390516199673	(empty)	empty	Add link text or aria-label
https://www.google.it/maps/place/Via+del…	(empty)	empty	Add link text or aria-label
mailto:info@casaliniecosrl.it	(empty)	empty	Add link text or aria-label
tel:+390516199673	(empty)	empty	Add link text or aria-label
https://www.google.com/maps/place/Via+de…	(empty)	empty	Add link text or aria-label
https://www.casaliniecosrl.it/casalini-c…	logo casalini società benefit	new tab	Add '(opens in new tab)' to text
https://www.casaliniecosrl.it/casalini-c…	Read more about Casalini & co …	new tab	Add '(opens in new tab)' to text
https://www.casaliniecosrl.it/casalini-c…	(empty)	empty	Add link text or aria-label
https://www.casaliniecosrl.it/casalini-c…	Read more about Casalini & CO …	new tab	Add '(opens in new tab)' to text
https://www.casaliniecosrl.it/casalini-c…	(empty)	empty	Add link text or aria-label
https://www.casaliniecosrl.it/casalini-c…	Read more about Casalini & CO …	new tab	Add '(opens in new tab)' to text
https://www.casaliniecosrl.it/wp-content…	BROCHURE DIV. EDILE	new tab	Add '(opens in new tab)' to text
https://www.casaliniecosrl.it/wp-content…	BROCHURE DIV. IMPERMEABILE	new tab	Add '(opens in new tab)' to text
https://www.casaliniecosrl.it/wp-content…	(empty)	empty	Add link text or aria-label
https://www.casaliniecosrl.it/wp-content…	(empty)	empty	Add link text or aria-label
https://www.casaliniecosrl.it/wp-content…	(empty)	empty	Add link text or aria-label
https://www.casaliniecosrl.it/wp-content…	(empty)	empty	Add link text or aria-label
https://www.casaliniecosrl.it/wp-content…	(empty)	empty	Add link text or aria-label
https://www.casaliniecosrl.it/wp-content…	(empty)	empty	Add link text or aria-label
https://accesso.acconsento.click/informa…	Privacy Policy	new tab	Add '(opens in new tab)' to text

75 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

mailto:info@casaliniecosrl.it; tel:+390516199673; https://www.google.it/maps/place/Via+dell'Intagliatore,+1,+40138+Bologna+BO/@…; mailto:info@casaliniecosrl.it; tel:+390516199673; https://www.google.com/maps/place/Via+dell'Intagliatore,+1,+40138+Bologna+BO/…; https://www.casaliniecosrl.it/casalini-co-srl-certificata-iso-270012022/; https://www.casaliniecosrl.it/casalini-co-srl-certificata-iso-50001-2018/; https://www.casaliniecosrl.it/wp-content/uploads/2023/03/Ospedale-Montecchio-…; https://www.casaliniecosrl.it/wp-content/uploads/2023/03/Unicoop-Lastra-a-Sig… (+4 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.casaliniecosrl.it/casalini-co/; https://www.casaliniecosrl.it/casalini-co/; https://www.casaliniecosrl.it/casalini-co-srl-certificata-iso-270012022/; https://www.casaliniecosrl.it/casalini-co-srl-certificata-iso-50001-2018/; https://www.casaliniecosrl.it/wp-content/uploads/2025/07/BROCHURE-DIV.-EDILE-…; https://www.casaliniecosrl.it/wp-content/uploads/2025/06/BROCHURE-DIV.-IMPERM…; https://accesso.acconsento.click/informative/page/5790/it

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

C

404 Error Page

Action

Could not test

REVIEW

Could not test

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.

B

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA

a La nostra evoluzione

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a La sede

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Lavorazioni

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a I nostri interventi

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a La flotta

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Certificazioni

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

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Leggi le News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 La nostra evoluzione	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Per saperne di più	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Lavorazioni	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 I nostri interventi …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Clienti	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 DIVISONE IMPERMEABIL…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 DIVISIONE EDILE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home - Casalini - Ca…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Vai al contenuto	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a info@casaliniecosrl.…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 051 6199688	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Via dell'Intagliator…	7.37:1	4.5:1	#000000	#999999	Pass
a La nostra evoluzione	1.00:1	4.5:1	#000000	#000000	Fail
a La sede	1.00:1	4.5:1	#000000	#000000	Fail
a Lavorazioni	1.00:1	4.5:1	#000000	#000000	Fail
a I nostri interventi	1.00:1	4.5:1	#000000	#000000	Fail
a La flotta	1.00:1	4.5:1	#000000	#000000	Fail
a Certificazioni	1.00:1	4.5:1	#000000	#000000	Fail
a Contatti	1.00:1	4.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.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 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: 2 all-caps heading(s)

A

Alt Text Quality

9 of 54 images have issues

PASS

9 of 54 images have issues

9 image(s) with generic alt text

8 decorative image(s) correctly marked

37 image(s) with good alt text

54 images 37 good alt text 8 decorative 9 generic

Issue	Count
generic	9 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "it-IT"

PASS

Lang attribute set to "it-IT"

<html lang="it-IT"> is set and valid

Got: it-IT

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 80 visible text node(s) render at >= 12 CSS pixels

PASS

All 80 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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 93/100 — 3 failing, 26 passed

PASS

93

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
Marzo 17, 2026 `article.elementor-post > div.elementor-post__card > div.elementor-post__meta-data > span.elementor-post-date`

These are opportunities to improve the legibility of your content.

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.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon`
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon`
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon`
div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link `div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link`
div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link `div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link`
div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item `div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item`
div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item `div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item`
div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item `div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item`
div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item `div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item`
div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item `div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item`
div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item `div.elementor-element > div.elementor-widget-container > div.elementor-gallery__container > a.e-gallery-item`

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
LEGGI TUTTO » `article.elementor-post > div.elementor-post__card > div.elementor-post__text > a.elementor-post__read-more`
LEGGI TUTTO » `article.elementor-post > div.elementor-post__card > div.elementor-post__text > a.elementor-post__read-more`
LEGGI TUTTO » `article.elementor-post > div.elementor-post__card > div.elementor-post__text > a.elementor-post__read-more`

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●`[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

●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

○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

○Buttons have an accessible name

○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

○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.

○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.