Skip to content
https://blissagency.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
37 landmarks
FIX
37 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
12 <nav> landmark(s) found
Warning::
6 of 12 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Page Structure — as a screen reader sees it
BANNER header NAV "Menu" MAIN (missing!) CONTENTINFO footer

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

D
Tabindex Anti-Patterns
Action
0 positive, 26 -1-on-focusable
FIX
0 positive, 26 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
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 ✗
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::
12 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 12 <nav> element(s)
Back to Top
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.
B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 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.
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) 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::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
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
h2 Il nostro Framework
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 L'advisory è il sistema che orienta le …
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 La Governance è il sistema che mantiene…
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Portiamo la strategia sui mercati con es…
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Agenzia Certificata
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 CONTATTI
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FAQ - Methodology & Vision
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Blog & Trends 2026
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Presenza mediatica
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Approfondisici il nostro approccio e le …
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Marketing roma e Milano
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Agenzia di Marketing e Comunicazione
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 problema
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 soluzione
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 valore
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 azione
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Storie di successo
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 pubblica amministrazione
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Certificazioni
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Completa il Form
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Il nostro Framework1.46:13.0:1
#000000
#2A2A2A
Fail
h2 L'advisory è il sis…1.46:13.0:1
#000000
#2A2A2A
Fail
h2 La Governance è il …1.46:13.0:1
#000000
#2A2A2A
Fail
h2 Portiamo la strategi…1.46:13.0:1
#000000
#2A2A2A
Fail
h2 Agenzia Certificata1.46:13.0:1
#000000
#2A2A2A
Fail
h2 CONTATTI1.46:13.0:1
#000000
#2A2A2A
Fail
h2 FAQ - Methodology & …1.46:13.0:1
#000000
#2A2A2A
Fail
h2 Blog & Trends 20261.46:13.0:1
#000000
#2A2A2A
Fail
h2 Presenza mediatica1.46:13.0:1
#000000
#2A2A2A
Fail
h2 Approfondisici il no…1.46:13.0:1
#000000
#2A2A2A
Fail
h2 Marketing roma e Mil…1.46:13.0:1
#000000
#2A2A2A
Fail
h2 Agenzia di Marketing…1.46:13.0:1
#000000
#2A2A2A
Fail
h3 problema1.46:13.0:1
#000000
#2A2A2A
Fail
h3 soluzione1.46:13.0:1
#000000
#2A2A2A
Fail
h3 valore1.46:13.0:1
#000000
#2A2A2A
Fail
h3 azione1.46:13.0:1
#000000
#2A2A2A
Fail
h3 Storie di successo1.46:13.0:1
#000000
#2A2A2A
Fail
h3 pubblica amministraz…1.46:13.0:1
#000000
#2A2A2A
Fail
h3 Certificazioni1.46:13.0:1
#000000
#2A2A2A
Fail
h3 Completa il Form1.46:13.0: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.

B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 29 passed
REVIEW
87

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Decreto Dignità e scommesse: vietare la cura non ha cancellato la malattia Lugl… div.e-con-inner > div.elementor-element > div.elementor-element > div.swiper

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
PROFVMVM div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
MIELE div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
WURTH div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
DORECA div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
CHARLES PHILIP MILANO div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
HONDA div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
WE DEFINE IT summary.e-n-accordion-item-title > span.e-n-accordion-item-title-header > div.e-n-accordion-item-title-text > span.testo-accordion
WE GOVERN IT summary.e-n-accordion-item-title > span.e-n-accordion-item-title-header > div.e-n-accordion-item-title-text > span.testo-accordion
WE MAKE IT REAL summary.e-n-accordion-item-title > span.e-n-accordion-item-title-header > div.e-n-accordion-item-title-text > span.testo-accordion
AOSTA div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
SAN MARINO div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
COURMAYEUR div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
REGIONE PUGLIA div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
ICE AGENZIA div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
REG. PIEMONTE div.elementor-element > div.elementor-element > h4.elementor-heading-title > a
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-name form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-name
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_617b735 form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_617b735
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_0d176e8 form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_0d176e8
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_fc9a5b3 form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_fc9a5b3
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-email > input#form-field-email form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-email > input#form-field-email
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-number > input#form-field-message form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-number > input#form-field-message
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-textarea > textarea#form-field-field_dbfc74a form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-textarea > textarea#form-field-field_dbfc74a
Seleziona CMO / Marketing Director Brand Manager Marketing Manager Sales Direct… div.elementor-form-fields-wrapper > div.elementor-field-type-select > div.elementor-field > select#form-field-field_c53d2ca
• Sì, sono decisore finale • Sì, partecipo alla decisione • No, raccolgo inform… div.elementor-form-fields-wrapper > div.elementor-field-type-select > div.elementor-field > select#form-field-field_feed94c

These are opportunities to improve the legibility of your content.

Names and labels

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.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-element > div.elementor-element > div.elementor-element > a div.elementor-element > div.elementor-element > div.elementor-element > a
div.elementor-element > div.elementor-element > div.elementor-element > a div.elementor-element > div.elementor-element > div.elementor-element > a
div.elementor-element > div.e-con-inner > div.elementor-element > a div.elementor-element > div.e-con-inner > div.elementor-element > a
div.elementor-element > div.e-con-inner > div.elementor-element > a div.elementor-element > div.e-con-inner > div.elementor-element > a
div.elementor-element > div.e-con-inner > div.elementor-element > a div.elementor-element > div.e-con-inner > div.elementor-element > a
div.elementor-element > div.e-con-inner > div.elementor-element > a div.elementor-element > div.e-con-inner > div.elementor-element > 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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ISO 9001:2015 div.elementor > b > div.elementor-element > a.elementor-element
ISO 45001:2018 div.elementor > b > div.elementor-element > a.elementor-element
ISO 14001:2015 div.elementor > b > div.elementor-element > a.elementor-element

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]`s are contained by their required parent element
●`[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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●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.
●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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●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 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
A+
Heading Hierarchy
108 headings
PASS
108 headings
Info::
Single H1 present
  • H1 Agenzia di Marketing
  • H2 Il nostro Framework
  • H3 problema
  • H3 soluzione
  • H3 valore
  • H3 azione
  • H2 casi studio
  • H3 Storie di successo
  • H4 miele
  • H4 profumum
  • H4 cocacola hbc
  • H4 wurth
  • H4 charles philip milano
  • H4 doreca
  • H4 Paramount
  • H4 pandora
  • H4 Honda
  • H4 parmigiano
  • H4 Rustichella
  • H4 laura biagiotti
  • H4 COCA-COLA HBC
  • H4 PROFVMVM
  • H4 MIELE
  • H4 wurth
  • H4 DORECA
  • H4 charles philip milano
  • H4 Honda
  • H2 L'advisory è il sistema che orienta le decisioni strategiche. Definiamo direzione, priorità e criteri.
  • H2 La Governance è il sistema che mantiene il brand fedele a se stesso, mentre l'organizzazione cresce, i mercati cambiano, le persone si rinnovano.
  • H2 Portiamo la strategia sui mercati con esecuzione concreta e misurabile. Cinque aree operative integrate che lavorano all'interno dei framework definiti dalla Governance.
  • H3 pubblica amministrazione
  • H4 San Marino
  • H4 courmayeur
  • H4 regione puglia
  • H4 regione piemonte
  • H4 aosta
  • H4 ice agenzia
  • H4 AOSTA
  • H4 SAN MARINO
  • H4 COURMAYEUR
  • H4 REGIONE PUGLIA
  • H4 ICE AGENZIA
  • H4 REG. PIEMONTE
  • H2 Agenzia Certificata
  • H3 Certificazioni
  • H4 ISO/IEC
  • H5 27001:2017
  • H5 9001:2015
  • H5 45001:2018
  • H5 14001:2015
  • H4 UNI PDR
  • H5 125:2022
  • H2 CONTATTI
  • H3 Completa il Form
  • H2 FAQ - Methodology & Vision
  • H3 Quando un’azienda dovrebbe rivedere il proprio posizionamento strategico?
  • H3 Come capire se il problema è strutturale e non operativo?
  • H3 Perché stiamo investendo molto ma non abbiamo ancora il controllo reale della nostra crescita?
  • H3 Perché la nostra azienda non è ancora percepita come leader, nonostante i risultati?
  • H3 Perché il nostro business cresce, ma la struttura interna diventa sempre più complessa e difficile da governare?
  • H3 Perché una strategia di branding solida spesso non basta a garantire la coerenza nel tempo?
  • H3 Come si elimina l'incoerenza comunicativa tra Headquarter e mercati locali?
  • H3 In che modo la governance del brand influisce sul valore patrimoniale dell'azienda?
  • H3 Come garantire che l'esecuzione operativa sia sempre allineata alla direzione strategica?
  • H3 Quali sono i segnali concreti che indicano la necessità di un sistema strutturato di Brand Governance?
  • H2 Blog & Trends 2026
  • H3 I Nostri Insight
  • H4 AI e brand: cosa succede quando a prendere la parola è l’algoritmo
  • H4 Decreto Dignità e scommesse: vietare la cura non ha cancellato la malattia
  • H4 NPS: significato, formula, benchmark e come usarlo per crescere davvero
  • H4 MANGOS immaturi: quando il mercato paga quello che spera e non quello che sa
  • H4 D&AD: Guida Completa al Premio del Craft e del Design Internazionale
  • H4 Digital Transformation: significato, esempi e tutto quello che un’impresa dovrebbe sapere
  • H4 AI e brand: cosa succede quando a prendere la parola è l’algoritmo
  • H4 Decreto Dignità e scommesse: vietare la cura non ha cancellato la malattia
  • H4 NPS: significato, formula, benchmark e come usarlo per crescere davvero
  • H4 MANGOS immaturi: quando il mercato paga quello che spera e non quello che sa
  • H2 Presenza mediatica
  • H3 Brand Advisory
  • H4 ll Messaggero
  • H3 Visual Direction
  • H4 La Repubblica®
  • H3 Positioning
  • H4 La Stampa®
  • H3 Brand strategy
  • H4 Milano Finanza®
  • H2 Approfondisici il nostro approccio e le aree di competenza
  • H3 Brand Advisory
  • H4 AUDIT
  • H5 Posizionamento
  • H4 CONSULTING
  • H5 Direzione
  • H4 ADVISORY
  • H5 Controllo
  • H4 GROWTH
  • H5 Consolidamento
  • H3 Le cinque aree operative
  • H4 Visual Production
  • H4 Brand Design
  • H4 Web Architecture
  • H4 Performance Marketing
  • H4 GEO & AIO
  • H2 Marketing roma e Milano
  • H2 Agenzia di Marketing e Comunicazione
  • H3 Cosa fa un'agenzia di marketing e comunicazione come Bliss Agency
  • H3 La differenza tra un'agenzia di marketing e un partner strategico
  • H3 Settori in cui operiamo come agenzia di marketing e comunicazione
  • H3 Inizia con un'agenzia di marketing e comunicazione che parte dalla strategia
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
2 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 145 chars - H2: 169 chars
Got: 2 >120-char heading(s)
Info::
18 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: 18 all-caps heading(s)
A
Alt Text Quality
All 135 images OK
PASS
All 135 images OK
Info::
23 image(s) with alt text over 125 characters
Info::
31 decorative image(s) correctly marked
Info::
81 image(s) with good alt text
135 images 81 good alt text 31 decorative
IssueCount
too long23 image(s)
A+
Form Accessibility
All 14 controls labeled
PASS
All 14 controls labeled
Info::
14 control(s) properly labeled
14 controls
14 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ckySwitchanalyticscheckboxAbilitare Analiticaaria-label
#ckySwitchadvertisementcheckboxAbilitare Pubblicitariaria-label
#ckySwitchothercheckboxAbilitare Non categorizzatoaria-label
#form-field-nametextReferentefor/id
#form-field-field_617b735textCompanyfor/id
#form-field-field_0d176e8textSito Webfor/id
#form-field-field_fc9a5b3textP. IVAfor/id
#form-field-emailemailEmailfor/id
#form-field-messagenumberTelefonofor/id
#form-field-field_dbfc74atextareaInformazioni Aggiuntivefor/id
#form-field-field_c53d2caselectRuolo in aziendafor/id
#form-field-field_feed94cselectsei coinvolto nella decisione?for/id
#form-field-field_a963abacheckboxHo letto l'informativa sulla privacy e acconsento alla memorizzazione dei miei dati, secondo quanto stabilito dal regolamento europeo per la protezione dei dati personali n. 679/2016 (GDPR), per avere informazioni sui servizi di blissagency.itfor/id
full-name-maspik-hptextLeave this field emptyaria-label
A+
Form Input Types
14 form control(s) checked, no type mismatches
PASS
14 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
14 form control(s) checked, no input-semantic issues
PASS
14 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
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Mobile-Readable Font Sizes
All 78 visible text node(s) render at >= 12 CSS pixels
PASS
All 78 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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