Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 3 REVIEW 3 FIX

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #ffffff

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

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

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Pagina non trovata – Osteria del Pane ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

20 icon(s) detected

REVIEW

20 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

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 Prenota

1.29:1

#000000

#410B19

needs 3.0:1 (large text)

24px · above the fold

h2 Telefonaci

1.47:1

#000000

#352728

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h2 Il menu

1.41:1

#000000

#2A2722

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h2 Carta dei vini

1.32:1

#000000

#2B2019

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h2 Orari

1.27:1

#000000

#1D1F21

needs 3.0:1 (large text)

24px · mid-page

h2 Scrivici

2.65:1

#000000

#575048

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Raggiungici

2.65:1

#000000

#575048

needs 3.0:1 (large text)

24px · bottom of viewport

h2 INFORMATIVA PRIVACY AI SENSI DEGLI ARTT.…

2.65:1

#000000

#575048

needs 3.0:1 (large text)

24px · bottom of viewport

h2 TERMINI DI SERVIZIO

2.65:1

#000000

#575048

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Prova 2

2.65:1

#000000

#575048

needs 3.0:1 (large text)

24px · bottom of viewport

title Osteria del Pane

3.61:1

#000000

#666563

needs 4.5:1 (normal text)

16px · top of page (header area)

a Salta al contenuto principale

3.59:1

#000000

#656563

needs 4.5:1 (normal text)

16px · top of page (header area)

a 0522 59.56.39

3.54:1

#000000

#646463

needs 4.5:1 (normal text)

16px · top of page (header area)

a Prenota

3.54:1

#000000

#646463

needs 4.5:1 (normal text)

16px · top of page (header area)

a Telefonaci

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

a Menu di Pasqua

2.76:1

#000000

#535453

needs 4.5:1 (normal text)

16px · above the fold

a RrrrMenu

3.18:1

#000000

#5C5D5E

needs 4.5:1 (normal text)

16px · above the fold

a La carta dei vini

3.39:1

#000000

#606164

needs 4.5:1 (normal text)

16px · above the fold

a Scrivici

3.41:1

#000000

#5E6265

needs 4.5:1 (normal text)

16px · above the fold

a Raggiungici

1.55:1

#000000

#4C202D

needs 4.5:1 (normal text)

16px · above the fold

3 contrast failures on background images/gradients

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

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Prenota	1.29:1	3.0:1	#000000	#410B19	Fail
h2 Telefonaci	1.47:1	3.0:1	#000000	#352728	Fail
h2 Il menu	1.41:1	3.0:1	#000000	#2A2722	Fail
h2 Carta dei vini	1.32:1	3.0:1	#000000	#2B2019	Fail
h2 Orari	1.27:1	3.0:1	#000000	#1D1F21	Fail
h2 Scrivici	2.65:1	3.0:1	#000000	#575048	Fail
h2 Raggiungici	2.65:1	3.0:1	#000000	#575048	Fail
h2 INFORMATIVA PRIVACY …	2.65:1	3.0:1	#000000	#575048	Fail
h2 TERMINI DI SERVIZIO	2.65:1	3.0:1	#000000	#575048	Fail
h2 Prova 2	2.65:1	3.0:1	#000000	#575048	Fail
title Osteria del Pane	3.61:1	4.5:1	#000000	#666563	Fail
a Salta al contenuto p…	3.59:1	4.5:1	#000000	#656563	Fail
a 0522 59.56.39	3.54:1	4.5:1	#000000	#646463	Fail
a Prenota	3.54:1	4.5:1	#000000	#646463	Fail
a Telefonaci	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Menu di Pasqua	2.76:1	4.5:1	#000000	#535453	Fail
a RrrrMenu	3.18:1	4.5:1	#000000	#5C5D5E	Fail
a La carta dei vini	3.39:1	4.5:1	#000000	#606164	Fail
a Scrivici	3.41:1	4.5:1	#000000	#5E6265	Fail
a Raggiungici	1.55:1	4.5:1	#000000	#4C202D	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H2 Prenota
H2 Telefonaci
H2 Il menu
H2 Carta dei vini
H2 Orari
H2 Scrivici
H2 Raggiungici
H2 INFORMATIVA PRIVACY AI SENSI DEGLI ARTT. 13-14 DEL REGOLAMENTO EUROPEO "PRIVACY" (GDPR)
H2 TERMINI DI SERVIZIO
H2 Prova 2

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 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: 2 all-caps heading(s)

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.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

25 links, 13 buttons — all OK

PASS

25 links, 13 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://www.google.com/maps?ll=44.813621,10.841101&z=19&t=h&hl=it&gl=US&mapcl…; https://www.google.com/maps?ll=44.813621,10.841101&z=19&t=h&hl=it&gl=US&mapcl…

23 link(s) with descriptive text

25 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.google.com/maps?ll=44.813621…	Raggiungici	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps?ll=44.813621…	Apri la mappa con la posizione…	new tab	Add '(opens in new tab)' to text

36 links and buttons have descriptive text

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

https://www.google.com/maps?ll=44.813621,10.841101&z=19&t=h&hl=it&gl=US&mapcl…; https://www.google.com/maps?ll=44.813621,10.841101&z=19&t=h&hl=it&gl=US&mapcl…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "it"

PASS

Lang attribute set to "it"

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

Got: it

A+

Tabindex Anti-Patterns

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

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

All text uses legible mobile font sizes (>= 12 CSS px)

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Osteria del Pane

192x192 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Osteria del Pane ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓

Name Osteria del Pane Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 6 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

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

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 26 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
Tutti i giorni pranzo dalle 12 alle 14, cena dalle 19.30 alle 22. `main#main > div.right2left > div > div.text-center`
.30 `div.right2left > div > div.text-center > sup`
La cucina chiude alle 14 ed alle 23. `main#main > div.right2left > div > div.text-center`
Privacy Policy `div.link_utils > ul > li > a.privacy_policy`
Informativa sull'utilizzo dei cookie `div.link_utils > ul > li > a.cookie_policy`
Termini di servizio `div.link_utils > ul > li > a.terms_of_service`
MAVA di Marchi e Vanzolini Snc – via Budrione Migliarina P. Ovest, 94 – 41012 C… `body > footer.footer > div.font_thin`

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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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