Skip to content
https://fps.agency

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
4
REVIEW
9
PASS
11
INFO
0
Checks
24
11 PASS 9 REVIEW 4 FIX
D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
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" id="email-input">
Warning::
1 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.
Got: <input type="email" name="email" id="email-input">
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #1e88e5
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 ModePartial Dark Mode
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::
8 navigation landmark(s) detected
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 8 <nav> element(s)
Back to Top
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.
B
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
7 of 8 <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 "Main Navigation" MAIN CONTENTINFO footer

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

B
Heading Hierarchy
34 headings
REVIEW
34 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 We are FpS
  • H2 Digital Marketing & Social
  • H2 Content MKT & SEO
  • H2 Web Dev & Design
  • H2 Influencer Marketing
  • H2 Ufficio Stampa
  • H2 Performance MKT & Sales online
  • H2 Neuromarketing
  • H3 Un cliente soddisfatto è il miglior biglietto da visita
  • H2 Google
  • H2 Macrolibrarsi
  • H2 Centro Medico Santagostino
  • H2 Gi-Metal
  • H2 Master “Mass web e social”
  • H2 Sky Tg24
  • H2 Kelly Services
  • H2 eFanswer
  • H2 Entel
  • H2 Presidenza Consiglio Ministri
  • H2 CrowdFundMe
  • H2 Panorama d’Italia
  • H2 Anpal
  • H2 Focus Live
  • H2 Non Sprecare
  • H2 Acotel Net
  • H2 Best Practice
  • H2 Brand authority: cos’è e come aumentarla per il tuo successo
  • H2 Limiti dell’AI nel marketing: come usarla senza perdere autenticità
  • H2 Le 10 migliori agenzie SEO in Italia 2026
  • H2 Prompt marketing: guida all’uso dell’AI nel marketing
  • H2 Contenuti AI-friendly: come farsi citare da ChatGPT e AI
  • H2 Preventivo online
  • H2 (empty)
  • H2 Contattaci

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

C
Mobile-Readable Font Sizes
Action
70% of visible text renders at >= 12 CSS px (14 below threshold)
REVIEW
70% of visible text renders at >= 12 CSS px (14 below threshold)
Warning::
14 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: <button> 8.7px ("Personalizza"); <button> 8.7px ("Rifiuta"); <button> 8.7px ("Accetta"); <div> 8.7px ("Chi siamo"); <p> 8.7px ("Aiutiamo persone e imprese a trovare la ...").
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Pagina non trovata - FpS Agency – Agenzia di marketing e comunicazione Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: FpS
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name FpS 192×192 icon 512×512 icon Start URL Display Mode standalone
Name FpS Display Mode standalone Theme Color #1e88e5 Background Color #1e88e5 Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 9 fail WCAG AA
REVIEW

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

11 pass 9 fail WCAG AA
h2 are
1.46:1
#000000
on
#082954
needs 3.0:1 (large text)
24px · above the fold
title FpS Agency – Agenzia di marketing e co…
1.35:1
#000000
on
#06234C
needs 4.5:1 (normal text)
16px · top of page (header area)
div Hero Section
1.38:1
#000000
on
#07254E
needs 4.5:1 (normal text)
16px · top of page (header area)
p We are
1.41:1
#000000
on
#072651
needs 4.5:1 (normal text)
16px · top of page (header area)
p Welcome
1.43:1
#000000
on
#072852
needs 4.5:1 (normal text)
16px · top of page (header area)
div Chi siamo
1.44:1
#000000
on
#072853
needs 4.5:1 (normal text)
16px · above the fold
span FpS
1.40:1
#000000
on
#07264F
needs 4.5:1 (normal text)
16px · above the fold
p Aiutiamo persone e imprese a trovare la …
1.43:1
#000000
on
#072851
needs 4.5:1 (normal text)
16px · above the fold
p Creiamo strategie e relazioni in grado d…
1.49:1
#000000
on
#092B54
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 are1.46:13.0:1
#000000
#082954
Fail
h2 Contattaci21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Un cliente soddisfat…21.00:13.0:1
#000000
#FFFFFF
Pass
title FpS Agency – Agenz…1.35:14.5:1
#000000
#06234C
Fail
div Hero Section1.38:14.5:1
#000000
#07254E
Fail
p We are1.41:14.5:1
#000000
#072651
Fail
p Welcome1.43:14.5:1
#000000
#072852
Fail
div Chi siamo1.44:14.5:1
#000000
#072853
Fail
span FpS1.40:14.5:1
#000000
#07264F
Fail
p Aiutiamo persone e i…1.43:14.5:1
#000000
#072851
Fail
p Creiamo strategie e …1.49:14.5:1
#000000
#092B54
Fail
a Scopri di più21.00:14.5:1
#000000
#FFFFFF
Pass
div Servizi21.00:14.5:1
#000000
#FFFFFF
Pass
a Digital Marketing & …21.00:14.5:1
#000000
#FFFFFF
Pass
p Pianifichiamo e real…21.00:14.5:1
#000000
#FFFFFF
Pass
a Content MKT & SEO21.00:14.5:1
#000000
#FFFFFF
Pass
p Produciamo strategie…21.00:14.5:1
#000000
#FFFFFF
Pass
a Web Dev & Design21.00:14.5:1
#000000
#FFFFFF
Pass
p Creiamo e-commerce, …21.00:14.5:1
#000000
#FFFFFF
Pass
a Influencer Marketing21.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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 25 passed
REVIEW
82

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#page > header#masthead > nav#site-navigation > button#toggleButton div#page > header#masthead > nav#site-navigation > button#toggleButton

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.carousel > div#service-1 > div.service-excerpt > a.next div.carousel > div#service-1 > div.service-excerpt > a.next
div.carousel > div#service-2 > div.service-excerpt > a.next div.carousel > div#service-2 > div.service-excerpt > a.next
div.carousel > div#service-3 > div.service-excerpt > a.next div.carousel > div#service-3 > div.service-excerpt > a.next
div.carousel > div#service-4 > div.service-excerpt > a.next div.carousel > div#service-4 > div.service-excerpt > a.next
div.carousel > div#service-5 > div.service-excerpt > a.next div.carousel > div#service-5 > div.service-excerpt > a.next
div.carousel > div#service-6 > div.service-excerpt > a.next div.carousel > div#service-6 > div.service-excerpt > a.next
article#home > section#section-home-services > div.carousel-nav > a.current article#home > section#section-home-services > div.carousel-nav > a.current
article#home > section#section-home-services > div.carousel-nav > a article#home > section#section-home-services > div.carousel-nav > a
article#home > section#section-home-services > div.carousel-nav > a article#home > section#section-home-services > div.carousel-nav > a
article#home > section#section-home-services > div.carousel-nav > a article#home > section#section-home-services > div.carousel-nav > a
article#home > section#section-home-services > div.carousel-nav > a article#home > section#section-home-services > div.carousel-nav > a
article#home > section#section-home-services > div.carousel-nav > a article#home > section#section-home-services > div.carousel-nav > a
article#home > section#section-home-services > div.carousel-nav > a article#home > section#section-home-services > div.carousel-nav > a
div.clients-box > nav#client-logos-nav > nav.carousel-nav > a.current div.clients-box > nav#client-logos-nav > nav.carousel-nav > a.current
div.clients-box > nav#client-logos-nav > nav.carousel-nav > a div.clients-box > nav#client-logos-nav > nav.carousel-nav > a
div.clients-box > nav#client-logos-nav > nav.carousel-nav > a div.clients-box > nav#client-logos-nav > nav.carousel-nav > a
div.clients-box > nav#client-logos-nav > nav.carousel-nav > a div.clients-box > nav#client-logos-nav > nav.carousel-nav > 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.

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
scopri di più article#home > section#section-home-intro > p.more > a
scopri di più section#section-home-clients > div.clients-box > div.clients-cta > a

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Google Italia section#section-home-clients > div.clients-box > nav#client-logos-nav > ul.carousel

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Google Italia nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Accenture nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
TIM nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Università di Torino nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Sky Tg24 nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Irsap nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
RCS nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Centro Medico Santagostino nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Contents.com nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Marsilio Arte nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Randstad nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
Metalltech nav#client-logos-nav > ul.carousel > div#slide-1 > li.client-logo
IED nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Moveo by Telepass nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Verti nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
SkySport nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Felsa nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Transpobank nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Lilac nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Desom nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
AGI nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Cogenio nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Fondazione Maratona Alzheimer nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Trusters nav#client-logos-nav > ul.carousel > div#slide-2 > li.client-logo
Google Cloud nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Consiglio dei Ministri nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Leroy Merlin nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Simbiosi nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Gruppo Mondadori nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
NostroFiglio nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Macrolibrarsi nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Rete Dafne nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
L’albero della vita nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Università Cattolica nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Panorama d’Italia nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
eFanswer nav#client-logos-nav > ul.carousel > div#slide-3 > li.client-logo
Non Sprecare nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
Kelly Services nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
CrowdFundMe nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
Entel nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
Focus Live nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
Acotel Net nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
Anpal nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
La Repubblica nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
Università Bicocca nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
H-Farm nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
LA7 nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo
GQ nav#client-logos-nav > ul.carousel > div#slide-4 > li.client-logo

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Image elements have `[alt]` attributes
Input buttons have discernible text.
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.
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[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
All heading elements contain content.
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 type="image">` elements have `[alt]` text
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
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.
A+
Heading Text Quality
All 34 heading(s) have substantive, well-formed text
PASS
All 34 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 53 images OK
PASS
All 53 images OK
Info::
53 image(s) with good alt text
53 images 53 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 6 controls have issues
PASS
1 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
5 control(s) properly labeled
6 controls
5 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#name-inputtextNomefor/id
#email-inputemailEmailfor/id
#subject-inputtextOggettofor/id
#message-inputtextareaMessaggiofor/id
privacycheckboxnone
inputsubmit(none)none

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

<input type="submit">

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
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback