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

Mobile Keyboard & Autofill

Action

7/7 eligible field(s) missing autocomplete or inputmode

FIX

7/7 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email">

6 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email, url, tel, numeric.

Got: <input type="email" name="email">, <input type="url" name="sito">, <input type="email" name="email_agenzia">, <input type="tel" name="telefono">, <input type="number" name="anno">

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 clouds_shape ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

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

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) 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

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

Form Accessibility

2 of 61 controls have issues

REVIEW

2 of 61 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">

59 control(s) properly labeled

61 controls

59 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
nome	text	Tuo nome e ruolo *	none
email	email	Email *	none
azienda	text	Azienda *	none
settore	select	Settore *	none
tipo_agenzia[]	checkbox		none
tipo_agenzia[]	checkbox		none
tipo_agenzia[]	checkbox		none
tipo_agenzia[]	checkbox		none
tipo_agenzia[]	checkbox		none
tipo_agenzia[]	checkbox		none
citta	text	Città o zona di preferenza	none
budget	select	Budget indicativo *	none
tempistica	select	Quando ti serve? *	none
descrizione	textarea	Raccontaci il progetto *	none
privacy	checkbox		none
nome_agenzia	text	Nome dell'agenzia *	none
sito	url	Sito web *	none
email_agenzia	email	Email di contatto pubblica dell'agenzia *	none
telefono	tel	Telefono dell'agenzia	none
citta	text	Città principale (sede operativa) *	none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
servizi[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
settori[]	checkbox		none
anno	number	Anno di fondazione *	none
team	select	Dimensione team *	none
lingue[]	checkbox		none
lingue[]	checkbox		none
lingue[]	checkbox		none
lingue[]	checkbox		none
lingue[]	checkbox		none
nome_proponente	text	Il tuo nome *	none
email_proponente	email	La tua email *	none
relazione	radio		none
relazione	radio		none
relazione	radio		none
relazione	radio		none
note	textarea	Note per la redazione	none
privacy	checkbox		none
input	submit	(none)	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

Mobile-Readable Font Sizes

92% of visible text renders at >= 12 CSS px (9 below threshold)

REVIEW

92% of visible text renders at >= 12 CSS px (9 below threshold)

9 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: <p> 11.0px ("EVENTI"); <p> 11.0px ("EVENTI"); <p> 11.0px ("EMAIL MARKETING"); <p> 11.0px ("COMUNICAZIONE"); <p> 11.0px ("GOOGLE ADS").

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

title La guida indipendente alle agenzie | mig…

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · top of page (header area)

a Servizi

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · top of page (header area)

a Metodologia

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · top of page (header area)

a Trova un'agenzia

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · top of page (header area)

span →

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · above the fold

a Proponi la tua agenzia

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · above the fold

span →

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · above the fold

a Branding

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · above the fold

a Comunicazione

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · above the fold

a Digital PR

1.21:1

#000000

#1B1A17

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Cura editoriale dell…	6.02:1	3.0:1	#000000	#E85D24	Pass
h2 Raccontaci cosa cerc…	6.02:1	3.0:1	#000000	#E85D24	Pass
h2 Proponi un'agenzia	6.02:1	3.0:1	#000000	#E85D24	Pass
h2 Le agenzie del momen…	6.02:1	3.0:1	#000000	#E85D24	Pass
h2 Leggere prima di sce…	6.02:1	3.0:1	#000000	#E85D24	Pass
h2 Conosci un’agenzia…	6.02:1	3.0:1	#000000	#E85D24	Pass
h3 Metodo trasparente	6.02:1	3.0:1	#000000	#E85D24	Pass
h3 Curatela italiana	6.02:1	3.0:1	#000000	#E85D24	Pass
h3 Indipendenza editori…	6.02:1	3.0:1	#000000	#E85D24	Pass
h3 Doppio servizio	6.02:1	3.0:1	#000000	#E85D24	Pass
title La guida indipendent…	1.21:1	4.5:1	#000000	#1B1A17	Fail
a Servizi	1.21:1	4.5:1	#000000	#1B1A17	Fail
a Metodologia	1.21:1	4.5:1	#000000	#1B1A17	Fail
a Trova un'agenzia	1.21:1	4.5:1	#000000	#1B1A17	Fail
span →	1.21:1	4.5:1	#000000	#1B1A17	Fail
a Proponi la tua agenz…	1.21:1	4.5:1	#000000	#1B1A17	Fail
span →	1.21:1	4.5:1	#000000	#1B1A17	Fail
a Branding	1.21:1	4.5:1	#000000	#1B1A17	Fail
a Comunicazione	1.21:1	4.5:1	#000000	#1B1A17	Fail
a Digital PR	1.21:1	4.5:1	#000000	#1B1A17	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 Hierarchy

19 headings

PASS

19 headings

Single H1 present

H2 Raccontaci cosa cerchi
H2 Proponi un'agenzia
H1 Cura editoriale delle agenzie italiane di SEO, web, marketing, comunicazione, pubblicità ed eventi.
H2 Le agenzie del momento, scelte per te.
H3 Metodo trasparente
H3 Curatela italiana
H3 Indipendenza editoriale
H3 Doppio servizio
H2 Leggere prima di scegliere.
H3 Quanto costa un evento aziendale con un’agenzia
H3 Come scegliere un’agenzia di eventi aziendali
H3 Agenzia email marketing e inbound: come scegliere
H3 Le migliori agenzie di comunicazione a Milano
H3 Quanto costa un’agenzia di marketing in Italia
H3 Come scegliere un’agenzia di marketing
H3 Agenzia lead generation: cos’è, come si sceglie
H3 Le migliori web agency a Milano
H3 Quanto costa un’agenzia SEO in Italia
H2 Conosci un’agenzia da segnalare?

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

12 image(s) with good alt text

12 images 12 good alt text

All images have appropriate alt text.

Link & Button Quality

124 links, 9 buttons — all OK

PASS

124 links, 9 buttons — all OK

2 link(s) open in new tab without warning

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

Got: /privacy/; /privacy/

122 link(s) with descriptive text

124 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/privacy/	privacy policy	new tab	Add '(opens in new tab)' to text
/privacy/	privacy policy	new tab	Add '(opens in new tab)' to text

131 links and buttons have descriptive text

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

/privacy/; /privacy/

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

61 form control(s) checked, no type mismatches

PASS

61 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

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

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

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

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.

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 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
CERCA PER COMPETENZA `main.main-content > section#cerca-competenza > div.container > p.mg-section-label`
441 RISULTATI `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-count`
ESPLORA → `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-cta`
428 RISULTATI `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-count`
ESPLORA → `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-cta`
402 RISULTATI `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-count`
ESPLORA → `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-cta`
359 RISULTATI `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-count`
ESPLORA → `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-cta`
350 RISULTATI `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-count`
ESPLORA → `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-cta`
303 RISULTATI `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-count`
ESPLORA → `ul.mg-competenze-list > li.mg-competenze-item > a.mg-competenze-link > span.mg-competenze-cta`
RICERCA AVANZATA → `section#cerca-competenza > div.container > div.text-center > a.mg-competenze-advanced`
01 `div.col-lg-8 > div.row > div.col-md-6 > span.mg-promessa-num`
02 `div.col-lg-8 > div.row > div.col-md-6 > span.mg-promessa-num`
03 `div.col-lg-8 > div.row > div.col-md-6 > span.mg-promessa-num`
04 `div.col-lg-8 > div.row > div.col-md-6 > span.mg-promessa-num`
Proponi una scheda alla redazione. Nessuna fee, nessuna posizione acquistabile,… `main.main-content > section#proponi > div.container > p.mg-cta-text`
PROPONI UN'AGENZIA → `main.main-content > section#proponi > div.container > a.mg-cta-btn`

These are opportunities to improve the legibility of your content.

Best practices

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

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●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

●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

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

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

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