Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title Pagina non trovata — I Classici Vivi ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

2 landmarks

REVIEW

2 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

No banner (header) landmark

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

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

h1 I Promessi Sposi.

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

32px · mid-page

h2 Accesso al Kit

1.07:1

#000000

#0B0B0B

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Perché I Promessi Sposi

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 sembrano impossibili da studiare

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Non un riassunto.

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Un'esperienza.

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tutto quello che ti serve,

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 in un unico kit

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Parla con loro.

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Non leggi di loro.

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Quello che credi di sapere

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 sui Promessi Sposi è sbagliato.

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Un prezzo unico.

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tutto incluso.

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hai dubbi?

1.11:1

#000000

#0D1117

needs 3.0:1 (large text)

24px · bottom of viewport

title I Classici Vivi — I Promessi Sposi. Fi…

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

div ⸻ ✦ ⸻

1.11:1

#000000

#12110E

needs 4.5:1 (normal text)

16px · top of page (header area)

p Inserisci il codice ricevuto via email d…

1.06:1

#000000

#0B0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

span Entra nel kit

1.07:1

#000000

#0B0B0B

needs 4.5:1 (normal text)

16px · above the fold

p Non hai ancora il kit?

1.07:1

#000000

#0B0B0B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 I Promessi Sposi.	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Accesso al Kit	1.07:1	3.0:1	#000000	#0B0B0B	Fail
h2 Perché I Promessi S…	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 sembrano impossibili…	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Non un riassunto.	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Un'esperienza.	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Tutto quello che ti …	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 in un unico kit	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Parla con loro.	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Non leggi di loro.	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Quello che credi di …	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 sui Promessi Sposi �…	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Un prezzo unico.	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Tutto incluso.	1.11:1	3.0:1	#000000	#0D1117	Fail
h2 Hai dubbi?	1.11:1	3.0:1	#000000	#0D1117	Fail
title I Classici Vivi — …	1.06:1	4.5:1	#000000	#0A0A0A	Fail
div ⸻ ✦ ⸻	1.11:1	4.5:1	#000000	#12110E	Fail
p Inserisci il codice …	1.06:1	4.5:1	#000000	#0B0A0A	Fail
span Entra nel kit	1.07:1	4.5:1	#000000	#0B0B0B	Fail
p Non hai ancora il ki…	1.07:1	4.5:1	#000000	#0B0B0B	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.

A+

Heading Hierarchy

9 headings

PASS

9 headings

Single H1 present

H2 Accesso al Kit
H1 I Promessi Sposi. Finalmente vivi.
H2 Perché I Promessi Sposisembrano impossibili da studiare
H2 Non un riassunto.Un'esperienza.
H2 Tutto quello che ti serve,in un unico kit
H2 Parla con loro.Non leggi di loro.
H2 Quello che credi di saperesui Promessi Sposi è sbagliato.
H2 Un prezzo unico.Tutto incluso.
H2 Hai dubbi?

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text" id="access-code-input">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#access-code-input	text	(ICV-XXXX-XXXX)	placeholder only

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

12 links, 6 buttons — all OK

PASS

12 links, 6 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://payhip.com/b/J0paf; /cookie.html; /privacy.html; https://payhip.com/b/J0paf

8 link(s) with descriptive text

12 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://payhip.com/b/J0paf	Acquistalo qui →	new tab	Add '(opens in new tab)' to text
/cookie.html	Cookie Policy	new tab	Add '(opens in new tab)' to text
/privacy.html	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://payhip.com/b/J0paf	OTTIENI IL KIT ORA — 9,90 �…	new tab	Add '(opens in new tab)' to text

14 links and buttons have descriptive text

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

https://payhip.com/b/J0paf; /cookie.html; /privacy.html; https://payhip.com/b/J0paf

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

Lighthouse Accessibility Audits

Score 93/100 — 1 failing, 12 passed

PASS

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
RIFIUTA `body > div#cookie-banner > div.cookie-btn-wrap > button.cookie-btn`
PERSONALIZZA `body > div#cookie-banner > div.cookie-btn-wrap > button.cookie-btn`
01 — PRIMO PASSO `section#componenti > div.components-grid > div.component-card > div.component-num`
02 — IMMERSIONE `section#componenti > div.components-grid > div.component-card > div.component-num`
03 — DIALOGO `section#componenti > div.components-grid > div.component-card > div.component-num`
04 — STUDIO `section#componenti > div.components-grid > div.component-card > div.component-num`
05 — VERIFICA `section#componenti > div.components-grid > div.component-card > div.component-num`
06 — ECCELLENZA `section#componenti > div.components-grid > div.component-card > div.component-num`
07 — GIOCO `section#componenti > div.components-grid > div.component-card > div.component-num`
08 — GUIDA `section#componenti > div.components-grid > div.component-card > div.component-num`
09 — TESTO `section#componenti > div.components-grid > div.component-card > div.component-num`
Z02 `section#flashcard-preview > div.flashcard-deck > div.fcard > div.fcard-num`
FLASHCARD ZERO `section#flashcard-preview > div.flashcard-deck > div.fcard > div.fcard-label`
© 2026 I Classici Vivi · classici `body > div#page-wrapper > footer > div`

These are opportunities to improve the legibility of your content.

○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-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

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

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

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

○Identical links have the same purpose.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.