Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 5 REVIEW 6 FIX

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Visitor anti-robot validation ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Heading Hierarchy

Action

25 headings, 2 skip(s)

REVIEW

25 headings, 2 skip(s)

Single H1 present

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.

1 empty heading(s)

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

H1 AGENZIA DI PERFORMANCE MARKETING
H2 La nostra mission è quella di aiutarti a migliorare il marketing e le performance della tua azienda/attività, aumentando clienti e fatturato.
H2 I nostri servizi
H2 Casi di Successo
H4 Caso Studio ecommerce di abbigliamento: La Boutique Del Centro skipped
H4 Marepanino: il panino gourmet a base di pesce – ecommerce caso di studio
H4 Progemec srl: dallo sviluppo del sito all’ottimizzazione seo – caso studio
H4 Salus lab Frosinone: dal sito web alla strategia social – caso studio
H4 Prestige parrucchieri: dal rebrand al funnel marketing – caso studio
H4 Caso di studio Local Marketing: Buona Pizza e le Facebook Ads
H4 Carinci Group S.p.A: affermarsi con una strategia omnicanale – caso di studio
H4 Falc Ceramiche: Facebook Ads & Rebranding
H4 Acqua Filette e Frosinone Calcio: progettazione grafica
H2 Creatività social realizzate per alcuni clienti
H2 Ci hanno scelto
H2 Leggi il Blog sul Digital Marketing
H4 Video Social: 5 consigli per creare video che vendono skipped
H4 Facebook Ads di Natale: 7 consigli per realizzare campagne perfette
H4 Marketing per centro estetico: come generare contatti profilati
H4 Corsi di formazione in Digital Marketing rivolto ad aziende e professionisti
H4 Fondi per digitalizzazione 2022: fai crescere la tua azienda con gli incentivi
H4 Come scrivere una landing page che converte
H2 Dicono di noi
H2 (empty)
H2 Informativa

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Why this matters

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

Source: WCAG 2.4.6

Link & Button Quality

Action

1 issue(s) across 91 links and 10 buttons

REVIEW

1 issue(s) across 91 links and 10 buttons

1 link(s) with no accessible text

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

Got: https://propagandagroup.it/wp-content/uploads/2019/11/pdipropaganda.png

6 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://propagandagroup.it/wp-content/uploads/2021/01/carinci.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/centro-medico-life.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/marepanino1.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/sisal.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/prestige.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/salus-frosinone.jpg"]

6 link(s) open in new tab without warning

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

Got: https://www.iubenda.com/privacy-policy/71387446/legal; https://www.iubenda.com/privacy-policy/71387446/cookie-policy; https://www.linkedin.com/company/propaganda-design/; https://www.facebook.com/propagandawebmarketing; https://www.instagram.com/propaganda.group/; https://www.iubenda.com/privacy-policy/71387446/cookie-policy?an=no&s_ck=fals…

78 link(s) with descriptive text

91 links

1 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://propagandagroup.it/wp-content/up…	carinci	img no alt	Add alt attribute to the image
https://propagandagroup.it/wp-content/up…	centro-medico-life	img no alt	Add alt attribute to the image
https://propagandagroup.it/wp-content/up…	marepanino1	img no alt	Add alt attribute to the image
https://propagandagroup.it/wp-content/up…	sisal	img no alt	Add alt attribute to the image
https://propagandagroup.it/wp-content/up…	prestige	img no alt	Add alt attribute to the image
https://propagandagroup.it/wp-content/up…	salus-frosinone	img no alt	Add alt attribute to the image
https://propagandagroup.it/wp-content/up…	(empty)	empty	Add link text or aria-label
https://www.iubenda.com/privacy-policy/7…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/7…	Cookie Policy	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/propaga…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/propagandawebma…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/propaganda.gro…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/7…	cookie policy	new tab	Add '(opens in new tab)' to text

88 links and buttons have descriptive text

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

https://propagandagroup.it/wp-content/uploads/2019/11/pdipropaganda.png

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://propagandagroup.it/wp-content/uploads/2021/01/carinci.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/centro-medico-life.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/marepanino1.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/sisal.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/prestige.jpg"]; a[href="https://propagandagroup.it/wp-content/uploads/2021/01/salus-frosinone.jpg"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://www.iubenda.com/privacy-policy/71387446/legal; https://www.iubenda.com/privacy-policy/71387446/cookie-policy; https://www.linkedin.com/company/propaganda-design/; https://www.facebook.com/propagandawebmarketing; https://www.instagram.com/propaganda.group/; https://www.iubenda.com/privacy-policy/71387446/cookie-policy?an=no&s_ck=fals…

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

Tap Target Adequacy

Action

4 tap target(s) too small or too close together

REVIEW

4 tap target(s) too small or too close together

4 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Informativa

1.59:1

#000000

#1F304E

needs 3.0:1 (large text)

24px · bottom of viewport

title Propaganda Group - Agenzia di Performanc…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Salta al contenuto

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Cerca per:

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span HOME

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span SERVIZI

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Online Advertising

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Digital Strategy

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Seo & Posizionamento

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Comunicazione & Design

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span CHI SIAMO

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span CASI STUDIO

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span FORMAZIONE

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span BLOG

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span CONTATTACI

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span HOME

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span SERVIZI

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span Online Advertising

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span Digital Strategy

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span Seo & Posizionamento

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Informativa	1.59:1	3.0:1	#000000	#1F304E	Fail
title Propaganda Group - A…	1.00:1	4.5:1	#000000	#000000	Fail
a Salta al contenuto	1.00:1	4.5:1	#000000	#000000	Fail
span Cerca per:	1.00:1	4.5:1	#000000	#000000	Fail
span HOME	1.00:1	4.5:1	#000000	#000000	Fail
span SERVIZI	1.00:1	4.5:1	#000000	#000000	Fail
span Online Advertising	1.00:1	4.5:1	#000000	#000000	Fail
span Digital Strategy	1.00:1	4.5:1	#000000	#000000	Fail
span Seo & Posizionamento	1.00:1	4.5:1	#000000	#000000	Fail
span Comunicazione & Desi…	1.00:1	4.5:1	#000000	#000000	Fail
span CHI SIAMO	1.00:1	4.5:1	#000000	#000000	Fail
span CASI STUDIO	1.00:1	4.5:1	#000000	#000000	Fail
span FORMAZIONE	1.00:1	4.5:1	#000000	#000000	Fail
span BLOG	1.00:1	4.5:1	#000000	#000000	Fail
span CONTATTACI	1.00:1	4.5:1	#000000	#000000	Fail
span HOME	1.00:1	4.5:1	#000000	#000000	Fail
span SERVIZI	1.00:1	4.5:1	#000000	#000000	Fail
span Online Advertising	1.00:1	4.5:1	#000000	#000000	Fail
span Digital Strategy	1.00:1	4.5:1	#000000	#000000	Fail
span Seo & Posizionamento	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.

Lighthouse Accessibility Audits

Score 89/100 — 4 failing, 28 passed

REVIEW

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CONTATTACI `div.fusion-column-wrapper > div > a.fusion-button > span.fusion-button-text`

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
Caso Studio ecommerce di abbigliamento: La Boutique Del Centro `div.fusion-image-wrapper > div.fusion-rollover > div.fusion-rollover-content > h4.fusion-rollover-title`
Video Social: 5 consigli per creare video che vendono `section.fusion-columns > article.post > div.recent-posts-content > h4.entry-title`

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.fusion-columns > div.fusion-column > section#media_image-3 > a `div.fusion-columns > div.fusion-column > section#media_image-3 > 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.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Testimonial Pagination `div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a.activeSlide`
Testimonial Pagination `div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a`
Testimonial Pagination `div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a`
Testimonial Pagination `div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

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

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

●`[lang]` attributes have a valid value

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○Tables have different content in the summary attribute and `<caption>`.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 141 chars

Got: 1 >120-char heading(s)

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

A+

Alt Text Quality

All 52 images OK

PASS

All 52 images OK

18 decorative image(s) correctly marked

34 image(s) with good alt text

52 images 34 good alt text 18 decorative

All images have appropriate alt text.

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: <input type="submit">

9 control(s) properly labeled

10 controls

9 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
s	search	Cerca per:	none
input	submit	Cerca	aria-label
your-name	text	Il tuo nome e cognome (*)	none
your-email	email	La tua email (*)	none
tel-187	tel	Il tuo telefono (*)	none
text-245	text	Tipologia di Business (Il settore in cui operi) (*)	none
textarea-361	textarea	La tua presenza online (Se hai un sito web, pagina facebook, Budget che intendi investire)	none
your-message	textarea	I tuoi obiettivi e cosa desideri migliorare (Chiedici di cosa hai bisogno)	none
acceptance-727	checkbox		none
input	submit	(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

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

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

tabindex="-1" on naturally-focusable <a>

Iframe Accessibility

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

PASS

1/1 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+

Mobile-Readable Font Sizes

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

PASS

All 85 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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.