Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 7 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 ✗

Form Accessibility

2 of 4 controls have issues

REVIEW

2 of 4 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" name="submit" id="searchsubmit">; <input type="submit" name="submit" id="searchsubmit">

2 control(s) properly labeled

4 controls

2 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#s	text	Search	for/id
#s	text	Search	for/id
#searchsubmit	submit	(none)	none
#searchsubmit	submit	(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

Link & Button Quality

Action

1 issue(s) across 78 links and 2 buttons

REVIEW

1 issue(s) across 78 links and 2 buttons

1 link(s) with no accessible text

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

Got: #masthead

5 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.miglioreroma.com/aziende-di-noleggio-arredi-per-eventi/"]; a[href="https://www.miglioreroma.com/fornitori-di-torte-nuziali/"]; a[href="https://www.miglioreroma.com/auto-depoca-per-matrimoni/"]; a[href="https://www.miglioreroma.com/scuole-cucina/"]; a[href="https://www.miglioreroma.com/servizi-di-protocollo-per-eventi/"]

1 link(s) open in new tab without warning

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

Got: https://catchthemes.com

71 link(s) with descriptive text

78 links

1 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.miglioreroma.com/aziende-di-…	Permalink to Le 10 migliori az…	img no alt	Add alt attribute to the image
https://www.miglioreroma.com/fornitori-d…	Permalink to I 10 migliori for…	img no alt	Add alt attribute to the image
https://www.miglioreroma.com/auto-depoca…	Permalink to Le 10 migliori au…	img no alt	Add alt attribute to the image
https://www.miglioreroma.com/scuole-cuci…	Permalink to Le 10 migliori sc…	img no alt	Add alt attribute to the image
https://www.miglioreroma.com/servizi-di-…	Permalink to I 10 migliori ser…	img no alt	Add alt attribute to the image
https://catchthemes.com	Catch Themes	new tab	Add '(opens in new tab)' to text
#masthead	(empty)	empty	Add link text or aria-label

73 links and buttons have descriptive text

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

#masthead

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.miglioreroma.com/aziende-di-noleggio-arredi-per-eventi/"]; a[href="https://www.miglioreroma.com/fornitori-di-torte-nuziali/"]; a[href="https://www.miglioreroma.com/auto-depoca-per-matrimoni/"]; a[href="https://www.miglioreroma.com/scuole-cucina/"]; a[href="https://www.miglioreroma.com/servizi-di-protocollo-per-eventi/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://catchthemes.com

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

Tap Target Adequacy

Action

7 tap target(s) too small or too close together

REVIEW

7 tap target(s) too small or too close together

7 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

98% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (1 below threshold)

1 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: <p> 11.0px ("Le migliori aziende a Roma").

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)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 1 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Primary Menu	6.19:1	3.0:1	#000000	#628EC5	Pass
h3 Post navigation	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Post navigation	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 Post popolari	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h3 In evidenza	19.95:1	3.0:1	#000000	#F9F9F9	Pass
title Migliore Roma - Le m…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Migliore Roma	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Le migliori aziende …	5.35:1	4.5:1	#000000	#5383BD	Pass
a Skip to content	12.47:1	4.5:1	#000000	#BAC9DB	Pass
a Inizio	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Aziende	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Alimentazione	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Bellezza	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Educazione	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Salute	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Servizi	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Chi siamo	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Pubblica la tua atti…	19.95:1	4.5:1	#000000	#F9F9F9	Pass
label Search	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Inizio	19.95:1	4.5:1	#000000	#F9F9F9	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 84/100 — 4 failing, 21 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
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
Continua a leggere → `div.entry-container > div.entry-summary > p > a.more-link`
← Post più vecchi `div#content > nav#nav-below > div.nav-previous > a`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Politica sulla riservatezza `div#site-generator > div.site-info > div.copyright > a.privacy-policy-link`

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#hgroup-wrap > div#header-right > div#header-mobile-menu > a.mobile-nav `div#hgroup-wrap > div#header-right > div#header-mobile-menu > a.mobile-nav`

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
Le 10 migliori università private di Roma `ul > li > span.tptn_after_thumb > a.tptn_link`
Le 10 migliori scuole di calcio di Roma `ul > li > span.tptn_after_thumb > a.tptn_link`
Le 10 migliori scuole private di Roma `ul > li > span.tptn_after_thumb > a.tptn_link`
Le 10 migliori scuole di tennis a Roma `ul > li > span.tptn_after_thumb > a.tptn_link`
Le 10 migliori scuole di cinema di Roma `ul > li > span.tptn_after_thumb > a.tptn_link`
I 10 migliori negozi di elettrodomestici a Roma `ul > li > span.tptn_after_thumb > a.tptn_link`
I 10 migliori centri per l’osteoporosi a Roma `ul > li > span.tptn_after_thumb > a.tptn_link`

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

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

●ARIA attributes are used as specified for the element's role

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○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

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Landmark Structure

32 landmarks

PASS

32 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

16 headings

PASS

16 headings

Single H1 present

H1 Migliore Roma
H2 Primary Menu
H3 Post navigation
H2 Le 10 migliori aziende di noleggio arredi per eventi a Roma
H2 I 10 migliori fornitori di torte nuziali a Roma
H2 Le 10 migliori auto d’epoca per matrimoni a Roma
H2 Le 10 migliori scuole di cucina di Roma
H2 I 10 migliori servizi di protocollo per eventi a Roma
H2 I 10 migliori ospedali odontoiatrici di Roma
H2 I 10 migliori truccatori professionisti di Roma
H2 Le 10 migliori caffetterie di Roma
H2 Le 10 migliori tenute con alloggio per matrimoni a Roma
H2 I 10 migliori cori per cerimonie a Roma
H3 Post navigation
H3 Post popolari
H3 In evidenza

A+

Heading Text Quality

All 16 heading(s) have substantive, well-formed text

PASS

All 16 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

1 image(s) with alt text over 125 characters

6 decorative image(s) correctly marked

15 image(s) with good alt text

22 images 15 good alt text 6 decorative

Issue	Count
too long	1 image(s)

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "s" should use type="search" (currently type="text")

Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "s" should use type="search" (currently type="text")

Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

4 form control(s) checked, no input-semantic issues

PASS

4 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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Página no encontrada - Migliore Roma ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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.