https://rocoarighi-test-alpha.netlify.app

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 6 REVIEW 3 FIX

Favicon & Branding

Action

4 icon(s) detected

FIX

4 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 Present

✗ Multiple Sizes Missing

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

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

4 landmarks

REVIEW

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

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

Link & Button Quality

1 issue(s) across 26 links and 4 buttons

REVIEW

1 issue(s) across 26 links and 4 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /privacy ("Learn more")

5 link(s) open in new tab without warning

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

Got: https://www.instagram.com/rocoarighi/; https://www.youtube.com/@rocoarighi; https://www.youtube.com/playlist?list=PLGm1wDDBAhBq4FPUJTFtMUoR8HuiFF5vt; https://www.youtube.com/playlist?list=PLGm1wDDBAhBr5PIR5vzg8lbfL9uGfj7za; https://www.youtube.com/@rocoarighi

20 link(s) with descriptive text

26 links

0 empty

1 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/rocoarighi/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@rocoarighi	YouTube	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/playlist?list=PL…	Groove SyndicateTrio arrangeme…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/playlist?list=PL…	Songs and coversSolo and colla…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@rocoarighi	Full channel@rocoarighi, live …	new tab	Add '(opens in new tab)' to text
/privacy	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Privacy

24 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/privacy ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.instagram.com/rocoarighi/; https://www.youtube.com/@rocoarighi; https://www.youtube.com/playlist?list=PLGm1wDDBAhBq4FPUJTFtMUoR8HuiFF5vt; https://www.youtube.com/playlist?list=PLGm1wDDBAhBr5PIR5vzg8lbfL9uGfj7za; https://www.youtube.com/@rocoarighi

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Andrea Roco

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name Andrea Roco ✓192×192 icon ✗512×512 icon ✗Start URL / ✓Display Mode standalone ✓

Name Andrea Roco Display Mode standalone Theme Color #d0bcff Background Color #0b1326 Icons 1 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

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

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 Andrea Roco

1.21:1

#000000

#131A2A

needs 3.0:1 (large text)

32px · above the fold

h2 Hear my playing

1.26:1

#000000

#181E2E

needs 3.0:1 (large text)

24px · mid-page

h2 Areas of work

1.13:1

#000000

#0A1225

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Next dates

1.13:1

#000000

#0A1225

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Groove Syndicate

1.24:1

#000000

#161C2C

needs 3.0:1 (large text)

19px · mid-page

h3 Songs and covers

1.13:1

#000000

#0A1325

needs 3.0:1 (large text)

19px · mid-page

h3 Full channel

1.13:1

#000000

#0A1225

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Live

1.13:1

#000000

#0A1225

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Studio

1.13:1

#000000

#0A1225

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Projects

1.13:1

#000000

#0A1225

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Private events

1.13:1

#000000

#0A1225

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Currently available for bookings

1.13:1

#000000

#0A1225

needs 3.0:1 (large text)

19px · bottom of viewport

title Andrea Roco · Pianist · Producer · Mu…

1.24:1

#000000

#151C2E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Andrea Roco

1.17:1

#000000

#0F1628

needs 4.5:1 (normal text)

16px · top of page (header area)

a About

1.23:1

#000000

#151B2D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Media

1.28:1

#000000

#181F31

needs 4.5:1 (normal text)

16px · top of page (header area)

a Timeline

1.21:1

#000000

#131A2C

needs 4.5:1 (normal text)

16px · above the fold

a Press

1.25:1

#000000

#161D2E

needs 4.5:1 (normal text)

16px · above the fold

a Contact

1.19:1

#000000

#121829

needs 4.5:1 (normal text)

16px · above the fold

p Jazz pianist and session player · Milan

1.13:1

#000000

#0C1324

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Andrea Roco	1.21:1	3.0:1	#000000	#131A2A	Fail
h2 Hear my playing	1.26:1	3.0:1	#000000	#181E2E	Fail
h2 Areas of work	1.13:1	3.0:1	#000000	#0A1225	Fail
h2 Next dates	1.13:1	3.0:1	#000000	#0A1225	Fail
h3 Groove Syndicate	1.24:1	3.0:1	#000000	#161C2C	Fail
h3 Songs and covers	1.13:1	3.0:1	#000000	#0A1325	Fail
h3 Full channel	1.13:1	3.0:1	#000000	#0A1225	Fail
h3 Live	1.13:1	3.0:1	#000000	#0A1225	Fail
h3 Studio	1.13:1	3.0:1	#000000	#0A1225	Fail
h3 Projects	1.13:1	3.0:1	#000000	#0A1225	Fail
h3 Private events	1.13:1	3.0:1	#000000	#0A1225	Fail
h3 Currently available …	1.13:1	3.0:1	#000000	#0A1225	Fail
title Andrea Roco · Piani…	1.24:1	4.5:1	#000000	#151C2E	Fail
a Andrea Roco	1.17:1	4.5:1	#000000	#0F1628	Fail
a About	1.23:1	4.5:1	#000000	#151B2D	Fail
a Media	1.28:1	4.5:1	#000000	#181F31	Fail
a Timeline	1.21:1	4.5:1	#000000	#131A2C	Fail
a Press	1.25:1	4.5:1	#000000	#161D2E	Fail
a Contact	1.19:1	4.5:1	#000000	#121829	Fail
p Jazz pianist and ses…	1.13:1	4.5:1	#000000	#0C1324	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

12 headings

PASS

12 headings

Single H1 present

H1 Andrea Roco
H2 Hear my playing
H3 Groove Syndicate
H3 Songs and covers
H3 Full channel
H2 Areas of work
H3 Live
H3 Studio
H3 Projects
H3 Private events
H2 Next dates
H3 Currently available for bookings

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

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

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 "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

All 2 iframe(s) have descriptive titles

PASS

All 2 iframe(s) have descriptive titles

All 2 iframe(s) have title attributes

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 57 visible text node(s) render at >= 12 CSS pixels

PASS

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

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

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

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 25 passed

PASS

100

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.

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●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

○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

○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

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

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

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