Accessibility

F

Heading Hierarchy

Action

59 headings, 12 skip(s)

FIX

59 headings, 12 skip(s)

Single H1 present

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Strategie Digitali personalizzate
H1 Italiainweb, la tua Web Agency di Pescara
H2 italiainweb Pescara
H2 Trasformiamo le tue idee in realtà digitale, migliorando la tua visibilità e ottimizzando le tue strategie di marketing
H3 Soluzioni Personalizzate
H3 Tecnologie all'Avanguardia
H3 Supporto Continuo
H4 Alcuni dei nostri Clienti
H6 Realizziamo progetti customizzati che rispondono ai bisogni e alle necessità dei nostri clienti. skipped
H3 Tecnologie Avanzate per Storie di Successo - Servizi Completi di Marketing Digitale
H2 Lavori Recenti
H3 .portfolio
H2 .grafica
H2 .siti web
H2 .ecommerce
H2 Matec srl
H2 Royal Lube
H2 Italia Alveari
H2 Nodo Interni su misura
H2 3R Edilizia Ponteggi
H2 Liberprì – Progetto Casa
H3 Servizi
H4 Realizzazione siti web.
H2 Realizziamo il tuo Sito Web
H4 Sviluppo siti eCommerce. skipped
H2 Sviluppiamo il tuo Ecommerce
H4 Google Ads. skipped
H2 Miglioriamo la visibilità della tua Attività
H4 Social Media Marketing. skipped
H2 Facciamo conoscere la tua Attività con i Social
H6 . Intelligenza Artificiale skipped
H2 Sviluppiamo Chatbot Intelligenti
H6 . GRAFICA skipped
H2 Creiamo il Logo per la tua Attività
H6 . Social media Marketing skipped
H2 Sviluppiamo Piani Editoriali di Qualità
H3 News
H3 Enrico Piscione
H3 Orari migliori per pubblicare su TikTok nel 2026: guida strategica per aziende e creator
H3 Enrico Piscione
H3 Come Vendere su WordPress con Shopify: Guida Completa al plug in di Shopify
H3 Enrico Piscione
H3 Come sfruttare Instagram Stories per far crescere il tuo brand nel 2025
H3 Richiedi un preventivo
H2 Frequently Asked Questions
H3 Marketing Digital
H2 Come aumentare le vendite del 30% senza aumentare il lavoro
H2 Inviaci un messaggio.
H6 lavora con noi skipped
H6 Feedbacks
H3 DOVE SIAMO?
H5 Via Vittorio Veneto, 45 - 65123 Pescara (PE) skipped
H3 ORARI
H5 Lun - Ven 09:00 - 13:00 14:00 -19:00 skipped
H3 chiamaci
H5 085 471 5078 skipped
H3 hai bisogno di supporto?
H5 support@italiainweb.it skipped
H3 RESTIAMO IN CONTATTO

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

F

Link & Button Quality

Action

22 issue(s) across 136 links and 13 buttons

FIX

22 issue(s) across 136 links and 13 buttons

18 link(s) with no accessible text

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

Got: https://italiainweb.it/portfolio/matec-srl/; https://italiainweb.it/portfolio/royal-lube/; https://italiainweb.it/portfolio/italia-alveari/; https://italiainweb.it/portfolio/nodo-interni-su-misura/; https://italiainweb.it/portfolio/3r-edilizia-ponteggi/; https://italiainweb.it/portfolio/liberpri-progetto-casa/; https://italiainweb.it/siti-web; https://italiainweb.it/e-commerce/; https://italiainweb.it/google-ads/; https://italiainweb.it/social-media-marketing/ (+8 more)

4 link(s) open in new tab without warning

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

Got: https://cookiedatabase.org/tcf/purposes/; https://www.facebook.com/Italiainwebagency; https://www.instagram.com/webagencyitaliainweb/; https://www.linkedin.com/company/italiainweb/about/

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.cmplz-category-toggle (#141 on page); button.cmplz-category-toggle (#154 on page); button.cmplz-category-toggle (#167 on page); button.cmplz-category-toggle (#181 on page)

114 link(s) with descriptive text

136 links

18 empty

0 generic text

4 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://cookiedatabase.org/tcf/purposes/	Read more about TCF purposes o…	new tab	Add '(opens in new tab)' to text
https://italiainweb.it/portfolio/matec-s…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/portfolio/royal-l…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/portfolio/italia-…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/portfolio/nodo-in…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/portfolio/3r-edil…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/portfolio/liberpr…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/siti-web	(empty)	empty	Add link text or aria-label
https://italiainweb.it/e-commerce/	(empty)	empty	Add link text or aria-label
https://italiainweb.it/google-ads/	(empty)	empty	Add link text or aria-label
https://italiainweb.it/social-media-mark…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/orari-migliori-pe…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/come-vendere-su-w…	(empty)	empty	Add link text or aria-label
https://italiainweb.it/come-sfruttare-in…	(empty)	empty	Add link text or aria-label
https://g.co/kgs/ANvfj1K	(empty)	empty	Add link text or aria-label
mailto:info@italiainweb.it	(empty)	empty	Add link text or aria-label
https://www.facebook.com/Italiainwebagen…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/webagencyitali…	(empty)	empty	Add link text or aria-label
mailto:info@italiainweb.it	(empty)	empty	Add link text or aria-label
https://www.facebook.com/Italiainwebagen…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/webagencyitali…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/italiai…	Linkedin	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

123 links and buttons have descriptive text

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

https://italiainweb.it/portfolio/matec-srl/; https://italiainweb.it/portfolio/royal-lube/; https://italiainweb.it/portfolio/italia-alveari/; https://italiainweb.it/portfolio/nodo-interni-su-misura/; https://italiainweb.it/portfolio/3r-edilizia-ponteggi/; https://italiainweb.it/portfolio/liberpri-progetto-casa/; https://italiainweb.it/siti-web; https://italiainweb.it/e-commerce/; https://italiainweb.it/google-ads/; https://italiainweb.it/social-media-marketing/ (+8 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://cookiedatabase.org/tcf/purposes/; https://www.facebook.com/Italiainwebagency; https://www.instagram.com/webagencyitaliainweb/; https://www.linkedin.com/company/italiainweb/about/

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.cmplz-category-toggle (#141 on page); button.cmplz-category-toggle (#154 on page); button.cmplz-category-toggle (#167 on page); button.cmplz-category-toggle (#181 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

3 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 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

12 landmarks

REVIEW

12 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - Italiainweb ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

B

Lighthouse Accessibility Audits

Score 89/100 — 4 failing, 26 passed

REVIEW

89

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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-element > div.elementor-widget-container > div.elementor-image-carousel-wrapper > div.elementor-swiper-button `div.elementor-element > div.elementor-widget-container > div.elementor-image-carousel-wrapper > div.elementor-swiper-button`
div.elementor-element > div.elementor-widget-container > div.elementor-image-carousel-wrapper > div.elementor-swiper-button `div.elementor-element > div.elementor-widget-container > div.elementor-image-carousel-wrapper > div.elementor-swiper-button`

These are opportunities to improve the usage of ARIA in your application which 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
Gestisci servizi `div.cmplz-links > ul > li > a.cmplz-link`
ACCETTA `div#cmplz-cookiebanner-container > div#cmplz-cookiebanner-1-optin > div.cmplz-buttons > button.cmplz-btn`
Cookie Policy `div.cmplz-documents > ul > li > a.cmplz-link`
Dichiarazione sulla Privacy `div.cmplz-documents > ul > li > a.cmplz-link`

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
Realizziamo progetti customizzati che rispondono ai bisogni e alle necessità de… `div.elementor-element > div.elementor-widget-container > div#ld-fancy-heading-6ae9c7031bb68 > h6.ld-fh-element`
Sviluppo siti eCommerce. `div#accordion-6ae9c7033b99f > div.accordion-item > div#heading-2412 > h4.accordion-title`
. INTELLIGENZA ARTIFICIALE `div.elementor-element > div.elementor-widget-container > div#ld-fancy-heading-6ae9c70386af1 > h6.ld-fh-element`
. GRAFICA `div.elementor-element > div.elementor-widget-container > div#ld-fancy-heading-6ae9c7039019f > h6.ld-fh-element`
. SOCIAL MEDIA MARKETING `div.elementor-element > div.elementor-widget-container > div#ld-fancy-heading-6ae9c7039874d > h6.ld-fh-element`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.carousel-item-content > article#post-81150 > div.lqd-pf-item-inner > a.lqd-overlay `div.carousel-item-content > article#post-81150 > div.lqd-pf-item-inner > a.lqd-overlay`
div.carousel-item-content > article#post-81125 > div.lqd-pf-item-inner > a.lqd-overlay `div.carousel-item-content > article#post-81125 > div.lqd-pf-item-inner > a.lqd-overlay`
div.carousel-item-content > article#post-81098 > div.lqd-pf-item-inner > a.lqd-overlay `div.carousel-item-content > article#post-81098 > div.lqd-pf-item-inner > a.lqd-overlay`
div.carousel-item-content > article#post-81066 > div.lqd-pf-item-inner > a.lqd-overlay `div.carousel-item-content > article#post-81066 > div.lqd-pf-item-inner > a.lqd-overlay`
div.carousel-item-content > article#post-81033 > div.lqd-pf-item-inner > a.lqd-overlay `div.carousel-item-content > article#post-81033 > div.lqd-pf-item-inner > a.lqd-overlay`
div.carousel-item-content > article#post-81013 > div.lqd-pf-item-inner > a.lqd-overlay `div.carousel-item-content > article#post-81013 > div.lqd-pf-item-inner > a.lqd-overlay`
div.lqd-imggrp-single > div.lqd-imggrp-img-container > figure.w-100 > a.lqd-overlay `div.lqd-imggrp-single > div.lqd-imggrp-img-container > figure.w-100 > a.lqd-overlay`
div.lqd-lp-row > div.lqd-lp-column > article#post-54458 > a.lqd-lp-overlay-link `div.lqd-lp-row > div.lqd-lp-column > article#post-54458 > a.lqd-lp-overlay-link`
div.lqd-lp-row > div.lqd-lp-column > article#post-16722 > a.lqd-lp-overlay-link `div.lqd-lp-row > div.lqd-lp-column > article#post-16722 > a.lqd-lp-overlay-link`
div.lqd-lp-row > div.lqd-lp-column > article#post-16594 > a.lqd-lp-overlay-link `div.lqd-lp-row > div.lqd-lp-column > article#post-16594 > a.lqd-lp-overlay-link`
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a `div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a`
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a `div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a`
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a `div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a`
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a `div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a`
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a `div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a`

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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 39 images OK

PASS

All 39 images OK

22 decorative image(s) correctly marked

17 image(s) with good alt text

39 images 17 good alt text 22 decorative

All images have appropriate alt text.

A

Form Accessibility

1 of 10 controls have issues

PASS

1 of 10 controls have issues

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">

9 control(s) properly labeled

10 controls

9 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#cmplz-functional-optin	checkbox	Funzionale	for/id
#cmplz-preferences-optin	checkbox	Preferenze	for/id
#cmplz-statistics-optin	checkbox	Statistiche	for/id
#cmplz-marketing-optin	checkbox	Marketing	for/id
#form-field-name	text	Nome	for/id
#form-field-field_3a1b3c3	text	Cognome	for/id
#form-field-message	tel	Telefono	for/id
#form-field-email	email	Email	for/id
#joinchat_optin	checkbox	Autorizzazione al Trattamento dei Dati Personali Acconsento a ricevere messaggi da Italiainweb SRLS tramite WhatsApp o altri canali di comunicazione. Accetto che i miei dati di contatto vengano utilizzati esclusivamente per fornirmi informazioni, aggiornamenti, promozioni e altri contenuti rilevanti. L'azienda garantisce che i dati saranno trattati nel rispetto della normativa vigente sulla privacy (Regolamento UE 2016/679 - GDPR) e che non saranno ceduti a terzi senza il mio esplicito consenso.	for/id
#g-recaptcha-response	textarea	(none)	none

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

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

10 form control(s) checked, no type mismatches

PASS

10 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

10 form control(s) checked, no input-semantic issues

PASS

10 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

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

Got: it-IT

A+

Tabindex Anti-Patterns

17 explicit tabindex attribute(s) checked, no anti-patterns

PASS

17 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A

Iframe Accessibility

1/6 iframe(s) missing title; 0 placeholder(s)

PASS

1/6 iframe(s) missing title; 0 placeholder(s)

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+

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 63 visible text node(s) render at >= 12 CSS pixels

PASS

All 63 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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Italiainweb, la tua …	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Strategie Digitali p…	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 italiainweb Pescara	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Trasformiamo le tue	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 in realtà digitale,	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 le tue strategie di …	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Lavori Recenti	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 .grafica	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 .siti web	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 .ecommerce	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Matec srl	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Royal Lube	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Italia Alveari	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Nodo Interni su misu…	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 3R Edilizia Ponteggi	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Liberprì – Proget…	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Creiamo il Logo per …	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Frequently Asked Que…	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Come aumentare le ve…	14.88:1	3.0:1	#000000	#D9D9D9	Pass
h2 Inviaci un	14.88:1	3.0:1	#000000	#D9D9D9	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.