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 5 REVIEW 4 FIX

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

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

3 landmarks

REVIEW

3 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

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.

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, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h1 Digital Marketing Agency Roma

1.46:1

#000000

#2A2A2A

needs 3.0:1 (large text)

32px · bottom of viewport

title Digital Marketing Agency a Roma - Web So…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

p Utilizziamo i cookie per migliorare la t…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

p Utilizziamo i cookie per aiutarti a navi…

1.09:1

#000000

#0E0E0E

needs 4.5:1 (normal text)

16px · above the fold

button Mostra di più

1.09:1

#000000

#0E0E0E

needs 4.5:1 (normal text)

16px · above the fold

span Sempre attivi

1.01:1

#000000

#020202

needs 4.5:1 (normal text)

16px · above the fold

p I cookie necessari sono fondamentali per…

1.01:1

#000000

#020202

needs 4.5:1 (normal text)

16px · above the fold

p Nessun cookie da visualizzare.

1.01:1

#000000

#020202

needs 4.5:1 (normal text)

16px · above the fold

p I cookie funzionali aiutano a svolgere d…

1.46:1

#000000

#2A2A2A

needs 4.5:1 (normal text)

16px · mid-page

p Nessun cookie da visualizzare.

1.46:1

#000000

#2A2A2A

needs 4.5:1 (normal text)

16px · mid-page

p I cookie analitici vengono utilizzati pe…

1.46:1

#000000

#2A2A2A

needs 4.5:1 (normal text)

16px · mid-page

div Cookie

1.46:1

#000000

#2A2A2A

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Digital Marketing Ag…	1.46:1	3.0:1	#000000	#2A2A2A	Fail
title Digital Marketing Ag…	1.00:1	4.5:1	#000000	#000000	Fail
p Diamo valore alla tu…	13.62:1	4.5:1	#D0D0D0	#000000	Pass
p Utilizziamo i cookie…	3.66:1	4.5:1	#000000	#666666	Fail
button Personalizza	12.52:1	4.5:1	#D0D0D0	#0E0E0E	Pass
button Rifiuta tutto	12.52:1	4.5:1	#D0D0D0	#0E0E0E	Pass
button Accettare tutto	12.52:1	4.5:1	#D0D0D0	#0E0E0E	Pass
span Personalizza le pref…	12.52:1	4.5:1	#D0D0D0	#0E0E0E	Pass
p Utilizziamo i cookie…	1.09:1	4.5:1	#000000	#0E0E0E	Fail
button Mostra di più	1.09:1	4.5:1	#000000	#0E0E0E	Fail
button Necessaria	12.52:1	4.5:1	#D0D0D0	#0E0E0E	Pass
span Sempre attivi	1.01:1	4.5:1	#000000	#020202	Fail
p I cookie necessari s…	1.01:1	4.5:1	#000000	#020202	Fail
p Nessun cookie da vis…	1.01:1	4.5:1	#000000	#020202	Fail
button Funzionale	13.37:1	4.5:1	#D0D0D0	#030303	Pass
p I cookie funzionali …	1.46:1	4.5:1	#000000	#2A2A2A	Fail
p Nessun cookie da vis…	1.46:1	4.5:1	#000000	#2A2A2A	Fail
button Analitica	9.31:1	4.5:1	#D0D0D0	#2A2A2A	Pass
p I cookie analitici v…	1.46:1	4.5:1	#000000	#2A2A2A	Fail
div Cookie	1.46:1	4.5:1	#000000	#2A2A2A	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 87/100 — 4 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.

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
Accettare tutto `div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn`
Chi siamo `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button`
- DIGITAL MARKETING AGENCY - `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > h5`
© 2026 WEB SOLUTIONS ROMA® \| TUTTI I DIRITTI SONO RISERVATI \| PRIVACY & COOKI… `footer#main-footer > div#footer-bottom > div.container > div#footer-info`
PRIVACY & COOKIE POLICY \| P. IVA IT16984651006 - R.E.A. RM 1688589 `div#footer-bottom > div.container > div#footer-info > a`

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
- DIGITAL MARKETING AGENCY - `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > h5`

These are opportunities to improve keyboard navigation in your application.

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.js `html.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-*]` 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 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.

●Deprecated ARIA roles were not used

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

●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

○Links are distinguishable without relying on color.

○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

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

Heading Hierarchy

2 headings, 1 skip(s)

PASS

2 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H5 (missing H2)

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

H1 Digital Marketing Agency Roma
H5 - DIGITAL MARKETING AGENCY - skipped

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

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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 6 images OK

PASS

All 6 images OK

1 decorative image(s) correctly marked

5 image(s) with good alt text

6 images 5 good alt text 1 decorative

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
#ckySwitchanalytics	checkbox	Abilitare Analitica	aria-label

Link & Button Quality

39 links, 23 buttons — all OK

PASS

39 links, 23 buttons — all OK

7 link(s) open in new tab without warning

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

Got: https://www.cookieyes.com/product/cookie-consent; https://www.facebook.com/websolutionsroma; https://www.instagram.com/websolutions_roma/; https://www.linkedin.com/company/web-solutions-roma/; https://www.tiktok.com/@websolutionsroma; https://www.youtube.com/channel/UC4c1wCBaL-7FKJo8o5lFkmg;

32 link(s) with descriptive text

39 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cookieyes.com/product/cookie…	Cookieyes logo	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/websolutionsrom…	Segui	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/websolutions_r…	Segui	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/web-sol…	Segui	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@websolutionsroma	Segui	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UC4c1wCB…	Segui	new tab	Add '(opens in new tab)' to text
	PRIVACY & COOKIE POLICY \| P. I…	new tab	Add '(opens in new tab)' to text

55 links and buttons have descriptive text

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

https://www.cookieyes.com/product/cookie-consent; https://www.facebook.com/websolutionsroma; https://www.instagram.com/websolutions_roma/; https://www.linkedin.com/company/web-solutions-roma/; https://www.tiktok.com/@websolutionsroma; https://www.youtube.com/channel/UC4c1wCBaL-7FKJo8o5lFkmg;

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

PASS

Lang attribute set to "it-IT"

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

Got: it-IT

A+

Tabindex Anti-Patterns

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

PASS

20 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+

Mobile-Readable Font Sizes

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

PASS

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