Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 3 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #0f1214

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 ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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

1 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

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Mobile-Readable Font Sizes

91% of visible text renders at >= 12 CSS px (8 below threshold)

REVIEW

91% of visible text renders at >= 12 CSS px (8 below threshold)

8 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.9px ("Agenzia SEO · Latina"); <span> 11.8px ("Agenzia SEO Latina"); <small> 10.0px ("Foto:"); <a> 10.0px ("Lory.captures / Lorenzo Messina / Pexels"); <span> 11.5px ("SEO · Latina").

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

h1 Migrazioni e recupero a Latina, con un m…

1.00:1

#000000

needs 3.0:1 (large text)

32px · mid-page

h2 Le pagine che sostengono il posizionamen…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Migrazioni e recupero: il taglio specifi…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Prima di lavorare su migrazioni e recupe…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Vuoi capire se il tuo sito può posizion…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Un esempio dichiaratamente ipotetico

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Quali materiali servono per iniziare?

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Come vengono definiti tempi e priorità?

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Come capiamo se il lavoro sta producendo…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Avete una sede a Latina?

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Quando ha senso lavorare su migrazioni e…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title Agenzia SEO Latina: migrazioni SEO

1.11:1

#000000

#0E1213

needs 4.5:1 (normal text)

16px · top of page (header area)

a Contattaci

1.11:1

#000000

#0E1213

needs 4.5:1 (normal text)

16px · top of page (header area)

a WhatsApp

1.12:1

#000000

#0F1214

needs 4.5:1 (normal text)

16px · top of page (header area)

span Consulenza gratuita

1.12:1

#000000

#0F1214

needs 4.5:1 (normal text)

16px · top of page (header area)

strong Prenota ora

1.12:1

#000000

#0F1214

needs 3.0:1 (large text)

16px · above the fold

span Agenzia SEO · Latina

1.12:1

#000000

#0F1214

needs 4.5:1 (normal text)

16px · above the fold

label Menu

1.12:1

#000000

#0F1214

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.12:1

#000000

#0F1214

needs 4.5:1 (normal text)

16px · above the fold

a Servizi SEO

1.12:1

#000000

#0F1214

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Migrazioni e recuper…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Le pagine che sosten…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Migrazioni e recuper…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Prima di lavorare su…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Vuoi capire se il tu…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Un esempio dichiarat…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Quali materiali serv…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Come vengono definit…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Come capiamo se il l…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Avete una sede a Lat…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Quando ha senso lavo…	1.00:1	3.0:1	#000000	#000000	Fail
title Agenzia SEO Latina: …	1.11:1	4.5:1	#000000	#0E1213	Fail
a Contattaci	1.11:1	4.5:1	#000000	#0E1213	Fail
a WhatsApp	1.12:1	4.5:1	#000000	#0F1214	Fail
span Consulenza gratuita	1.12:1	4.5:1	#000000	#0F1214	Fail
strong Prenota ora	1.12:1	3.0:1	#000000	#0F1214	Fail
span Agenzia SEO · Latin…	1.12:1	4.5:1	#000000	#0F1214	Fail
label Menu	1.12:1	4.5:1	#000000	#0F1214	Fail
a Home	1.12:1	4.5:1	#000000	#0F1214	Fail
a Servizi SEO	1.12:1	4.5:1	#000000	#0F1214	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.

Heading Hierarchy

13 headings, 1 skip(s)

PASS

13 headings, 1 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.

H1 Migrazioni e recupero a Latina, con un metodo verificabile
H2 Le pagine che sostengono il posizionamento
H3 Un esempio dichiaratamente ipotetico
H2 Migrazioni e recupero: il taglio specifico di questa pagina
H2 Prima di lavorare su migrazioni e recupero
H3 Quali materiali servono per iniziare?
H3 Come vengono definiti tempi e priorità?
H3 Come capiamo se il lavoro sta producendo valore?
H3 Avete una sede a Latina?
H3 Quando ha senso lavorare su migrazioni e recupero?
H2 Vuoi capire se il tuo sito può posizionarsi meglio a Latina?
H4 Servizi skipped
H4 Contatti e informazioni

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Heading Text Quality

All 13 heading(s) have substantive, well-formed text

PASS

All 13 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#mt	checkbox	Menu	for/id

Link & Button Quality

36 links, 5 buttons — all OK

PASS

36 links, 5 buttons — all OK

8 link(s) open in new tab without warning

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

Got: https://wa.me/393925922221?text=Buongiorno%2C%20vorrei%20maggiori%20informazi…; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://www.pexels.com/it-it/foto/citta-paesaggio-natura-skyline-27427296/; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://www.iubenda.com/privacy-policy/46067085/cookie-policy?an=no&s_ck=fals…

28 link(s) with descriptive text

36 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/393925922221?text=Buongior…	Scrivici su WhatsApp al numero…	new tab	Add '(opens in new tab)' to text
https://calendar.app.google/oc4ZmwKbvMXX…	Prenota una consulenza gratuit…	new tab	Add '(opens in new tab)' to text
https://calendar.app.google/oc4ZmwKbvMXX…	Prenota l’audit gratuito	new tab	Add '(opens in new tab)' to text
https://calendar.app.google/oc4ZmwKbvMXX…	Prenota una valutazione gratui…	new tab	Add '(opens in new tab)' to text
https://www.pexels.com/it-it/foto/citta-…	Lory.captures / Lorenzo Messin…	new tab	Add '(opens in new tab)' to text
https://calendar.app.google/oc4ZmwKbvMXX…	Prenota una valutazione gratui…	new tab	Add '(opens in new tab)' to text
https://calendar.app.google/oc4ZmwKbvMXX…	Prenota una consulenza gratuit…	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/4…	cookie policy	new tab	Add '(opens in new tab)' to text

33 links and buttons have descriptive text

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

https://wa.me/393925922221?text=Buongiorno%2C%20vorrei%20maggiori%20informazi…; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://www.pexels.com/it-it/foto/citta-paesaggio-natura-skyline-27427296/; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://calendar.app.google/oc4ZmwKbvMXXPimH8; https://www.iubenda.com/privacy-policy/46067085/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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

PASS

Lang attribute set to "it"

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

Got: it

A+

Tabindex Anti-Patterns

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Lighthouse Accessibility Audits

Score 92/100 — 4 failing, 19 passed

PASS

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
WhatsApp `body > div.global-cta-group > a.global-whatsapp-cta`
CONSULENZA GRATUITA `body > div.global-cta-group > a.global-consultation-cta > span`
Prenota ora `body > div.global-cta-group > a.global-consultation-cta > strong`

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
SERVIZI `footer.foot > div.wrap > div > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

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
CONSULENZA GRATUITA Prenota ora `body > div.global-cta-group > a.global-consultation-cta`

○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

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

●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 have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

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

○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 buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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

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

○Identical links have the same purpose.

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

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