Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 5 REVIEW 8 FIX

Landmark Structure

Action

16 landmarks

FIX

16 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <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

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

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

Form Accessibility

Action

4 of 6 controls have issues

FIX

4 of 6 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">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="s">; <input type="text" name="s" id="search">

2 control(s) properly labeled

6 controls

2 labeled

2 placeholder only

2 unlabeled

Control	Type	Label	Method
#ckySwitchfunctional	checkbox	Enable Funzionali	aria-label
#ckySwitchanalytics	checkbox	Enable Analytics	aria-label
s	search	(Cerca …)	placeholder only
#search	text	(Enter your search text...)	placeholder only
input	submit	(none)	none
#g-recaptcha-response-100000	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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

12 issue(s) across 77 links and 13 buttons

FIX

12 issue(s) across 77 links and 13 buttons

10 link(s) with no accessible text

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

Got: #mm-2; #mm-3; #mobile-nav; https://www.facebook.com/francescomargherita; https://twitter.com/francescomarghe; https://www.youtube.com/user/francescomargherita; https://www.linkedin.com/in/francescomargherita; https://www.instagram.com/francescomargherita/; #; https://www.facebook.com/groups/fattidiseo/

2 button(s) with no accessible text

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

Got: button.btn (#109 on page); input[type="submit"].sb-search-submit (#402 on page)

67 link(s) with descriptive text

77 links

10 empty

0 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
#mm-2	(empty)	empty	Add link text or aria-label
#mm-3	(empty)	empty	Add link text or aria-label
#mobile-nav	(empty)	empty	Add link text or aria-label
https://www.facebook.com/francescomarghe…	(empty)	empty	Add link text or aria-label
https://twitter.com/francescomarghe	(empty)	empty	Add link text or aria-label
https://www.youtube.com/user/francescoma…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/in/francescomar…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/francescomargh…	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.facebook.com/groups/fattidis…	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<input>	(empty)	empty	Add button text or aria-label

78 links and buttons have descriptive text

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

#mm-2; #mm-3; #mobile-nav; https://www.facebook.com/francescomargherita; https://twitter.com/francescomarghe; https://www.youtube.com/user/francescomargherita; https://www.linkedin.com/in/francescomargherita; https://www.instagram.com/francescomargherita/; #; https://www.facebook.com/groups/fattidiseo/

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

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

button.btn (#109 on page); input[type="submit"].sb-search-submit (#402 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

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

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

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.

Mobile-Readable Font Sizes

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

REVIEW

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

6 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.6px ("Content Marketing"); <a> 10.7px ("SEO E-Commerce"); <a> 10.0px ("Ottimizzazione SEO"); <a> 10.0px ("Ottimizzazione SEO"); <a> 10.0px ("Posizionamento nei motori di ricerca").

404 Error Page

Action

Could not test

REVIEW

Could not test

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.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA 11 pass AA only

button Accetta tutti

1.10:1

#FFFFFF

#F4F4F4

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Qui è dove parliamo…	6.59:1	3.0:1	#000000	#6D9E31	Pass
h3 e scopri se faccio a…	6.59:1	3.0:1	#000000	#6D9E31	Pass
h3 Seogarden srl	6.59:1	3.0:1	#000000	#6D9E31	Pass
title Homepage \| SeoGarden…	18.97:1	4.5:1	#000000	#F0F5EB	Pass
a Consulente SEO	18.97:1	4.5:1	#000000	#F0F5EB	Pass
a Francesco Margherita	12.71:1	4.5:1	#000000	#B9D1A3	Pass
a Consulente SEO per e…	6.25:1	4.5:1	#000000	#679A36	Pass
a Motori di ricerca	6.25:1	4.5:1	#000000	#679A35	Pass
a Corso SEO Online 202…	6.25:1	4.5:1	#000000	#679A35	Pass
a Costi SEO 2026	6.31:1	4.5:1	#000000	#679B34	Pass
a Preventivo SEO	6.31:1	4.5:1	#000000	#679B34	Pass
a Contattami per una c…	6.32:1	4.5:1	#000000	#689B33	Pass
span Ricerca per:	6.32:1	4.5:1	#000000	#689B33	Pass
p Usiamo i cookie	4.85:1	4.5:1	#212121	#689B32	Pass
p Utilizziamo cookie t…	6.32:1	4.5:1	#000000	#689B32	Pass
button Personalizza	6.39:1	4.5:1	#000000	#689C31	Pass
button Rifiuta tutti	6.39:1	4.5:1	#000000	#689C30	Pass
button Accetta tutti	1.10:1	4.5:1	#FFFFFF	#F4F4F4	Fail
span Personalizza prefere…	14.64:1	4.5:1	#212121	#F4F4F4	Pass
div Usiamo solo cookie t…	14.64:1	4.5:1	#212121	#F4F4F4	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.

Lighthouse Accessibility Audits

Score 80/100 — 7 failing, 23 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.