Skip to content
https://webmarketingagency.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 50/100 — 7 failing, 8 passed
FIX
50

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
Più del 95% delle sessioni di navigazione iniziano con una ricerca su Google. S… div.row > div.four > div.column-service-wrapper > div.column-service-caption
La pubblicità è l'anima del commercio. Anche sui internet e sui motori di ricer… div.row > div.four > div.column-service-wrapper > div.column-service-caption
Facebook, Twitter, Linkedin, e da ultimi Pinterest e Google+ hanno cambiato il … div.row > div.four > div.column-service-wrapper > div.column-service-caption
  Facebook Advertising rappresenta una grande opportunità per i markettari. Neg… div.row > div.three > div.blog-content-wrapper > div.blog-content
I brand che hanno bisogno di catturare l’interesse di lettori devono sicurament… div.row > div.three > div.blog-content-wrapper > div.blog-content
Stiamo attraversando una nuova fase all’interno della storia del web-marketing:… div.row > div.three > div.blog-content-wrapper > div.blog-content
Il titolo sicuramente suona strano: i farmers, ovvero agricoltori ed allevatori… div.row > div.three > div.blog-content-wrapper > div.blog-content
Non c'è altro al di fuori del primo posto. Se vuoi ottenere maggior traffico, a… div.six > ul.gdl-accordion > li.active > div.accordion-content
Lavora con noi div.gdl-tab > ul.gdl-tab-title > li > a
La nostra web marketing agency (siamo a Roma e Milano) può supportare la tua az… div.gdl-tab > ul.gdl-tab-content > li.active > p
web marketing agency ul.gdl-tab-content > li.active > p > strong
Roma ul.gdl-tab-content > li.active > p > a
Milano ul.gdl-tab-content > li.active > p > a
Grazie ad un team di professionisti nell'ambito del posizionamento sui motori d… div.gdl-tab > ul.gdl-tab-content > li.active > p
posizionamento sui motori di ricerca ul.gdl-tab-content > li.active > p > a
pubblicità display ul.gdl-tab-content > li.active > p > a
promozione sui social network ul.gdl-tab-content > li.active > p > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Roma ul.gdl-tab-content > li.active > p > a
Milano ul.gdl-tab-content > li.active > p > a
posizionamento sui motori di ricerca ul.gdl-tab-content > li.active > p > a
pubblicità display ul.gdl-tab-content > li.active > p > a
promozione sui social network ul.gdl-tab-content > li.active > p > a
Info body.home > div#cookie-law-info-bar > span > a#CONSTANT_OPEN_URL

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.copyright-wrapper > div.copyright-left > a > img div.copyright-wrapper > div.copyright-left > a > img

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
— Main Menu — SEO Social Media Marketing SEM Chi siamo Contatti div.header-outer-wrapper > div.header-wrapper > div.responsive-menu-wrapper > select#menu-menu-1

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.three > div.blog-content-wrapper > div.blog-media-wrapper > a div.three > div.blog-content-wrapper > div.blog-media-wrapper > a
div.three > div.blog-content-wrapper > div.blog-media-wrapper > a div.three > div.blog-content-wrapper > div.blog-media-wrapper > a
div.three > div.blog-content-wrapper > div.blog-media-wrapper > a div.three > div.blog-content-wrapper > div.blog-media-wrapper > a
div.three > div.blog-content-wrapper > div.blog-media-wrapper > a div.three > div.blog-content-wrapper > div.blog-media-wrapper > a
div.container > div.copyright-wrapper > div.copyright-left > a div.container > div.copyright-wrapper > div.copyright-left > 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

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

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.no-js html.no-js

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-hidden="true"]` is not present on the document `<body>`
●Document has a `<title>` element
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` 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 use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<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
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○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.
B
Alt Text Quality
1 of 7 images have issues
REVIEW
1 of 7 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
4 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
7 images 2 good alt text 4 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

B
Mobile-Readable Font Sizes
90% of visible text renders at >= 12 CSS px (5 below threshold)
REVIEW
90% of visible text renders at >= 12 CSS px (5 below threshold)
Info::
5 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: <a> 11.0px ("Agenzia di web marketing"); <div> 11.0px ("è un'idea"); <a> 11.0px ("Via Tomacelli, 103, 00186 Roma, Lazio, I..."); <div> 11.0px ("P.IVA 04416440750"); <div> 11.0px ("Tel: +39 345 23 68 445 - mail: info[@]we...").
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Fatti vedere sul web…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Search Engine Optimi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AdWords e display ad…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Social Media Marketi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Posizionamento nei m…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SEM e display21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Social Media Marketi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Servizi di web marke…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Chi siamo21.00:13.0:1
#000000
#FFFFFF
Pass
title Web Marketing Agency…6.03:14.5:1
#000000
#FD450D
Pass
a SEO21.00:14.5:1
#000000
#FFFFFF
Pass
a Social Media Marketi…21.00:14.5:1
#000000
#FFFFFF
Pass
a SEM21.00:14.5:1
#000000
#FFFFFF
Pass
a Chi siamo21.00:14.5:1
#000000
#FFFFFF
Pass
a Contatti21.00:14.5:1
#000000
#FFFFFF
Pass
option — Main Menu —21.00:14.5:1
#000000
#FFFFFF
Pass
option SEO21.00:14.5:1
#000000
#FFFFFF
Pass
option Social Media Marketi…21.00:14.5:1
#000000
#FFFFFF
Pass
option SEM21.00:14.5:1
#000000
#FFFFFF
Pass
option Chi siamo21.00:14.5:1
#000000
#FFFFFF
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.

A
Heading Hierarchy
14 headings
PASS
14 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 Search Engine Optimization
  • H2 AdWords e display adv
  • H2 Social Media Marketing
  • H1 Fatti vedere sul web. duplicate H1
  • H2 I sette errori da evitare in una campagna Facebook Ads
  • H2 Perché è importante inserire i contenuti “data-driven” nella propria strategia di marketing
  • H2 La rivoluzione dei ChatBot: un nuovo canale di marketing
  • H2 Come l’uso dei social da parte dei farmers può migliorare il nostro business
  • H3 Servizi di web marketing
  • H2 Posizionamento nei motori di ricerca
  • H2 SEM e display
  • H2 Social Media Marketing
  • H3 Chi siamo

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

A+
Heading Text Quality
All 14 heading(s) have substantive, well-formed text
PASS
All 14 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="menu-menu-1">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#menu-menu-1select(none)none

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

<select id="menu-menu-1">

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
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
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
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="it-IT"> is set and valid
Got: it-IT
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.

Send Feedback