Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 5 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-iolwlz

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://siffredirocco.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://siffredirocco.com/manifest.json

Manifest contains invalid JSON.

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 ✗

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Mobile-Readable Font Sizes

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

REVIEW

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

2 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: <strong> 9.0px ("Rocco Siffredi"); <p> 9.0px ("- the official home of videos directed b...").

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)

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

title Rocco Siffredi - The Italian Stallion Ex…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

strong Rocco Siffredi

1.00:1

#000000

needs 3.0:1 (large text)

16px · top of page (header area)

p - the official home of videos directed b…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span ‹

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a All Videos

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

button 🔍

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

button ✕

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a 🔥 GOAT

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a 📈 Trending

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a ⭐ Top Models

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span ›

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span •

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Now

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

div Rocco and Kelly’s UK Adventure

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Kelly Stafford

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Tina Snows

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Rocco Siffredi

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span 252

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span •

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

div My Fantasy with Rocco #09

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Rocco Siffredi - The…	1.00:1	4.5:1	#000000	#000000	Fail
strong Rocco Siffredi	1.00:1	3.0:1	#000000	#000000	Fail
p - the official home …	1.00:1	4.5:1	#000000	#000000	Fail
span ‹	1.00:1	4.5:1	#000000	#000000	Fail
a All Videos	1.00:1	4.5:1	#000000	#000000	Fail
button 🔍	1.00:1	4.5:1	#000000	#000000	Fail
button ✕	1.00:1	4.5:1	#000000	#000000	Fail
a 🔥 GOAT	1.00:1	4.5:1	#000000	#000000	Fail
a 📈 Trending	1.00:1	4.5:1	#000000	#000000	Fail
a ⭐ Top Models	1.00:1	4.5:1	#000000	#000000	Fail
span ›	1.00:1	4.5:1	#000000	#000000	Fail
span •	1.00:1	4.5:1	#000000	#000000	Fail
span Now	1.00:1	4.5:1	#000000	#000000	Fail
div Rocco and Kelly’s …	1.00:1	4.5:1	#000000	#000000	Fail
a Kelly Stafford	1.00:1	4.5:1	#000000	#000000	Fail
a Tina Snows	1.00:1	4.5:1	#000000	#000000	Fail
a Rocco Siffredi	1.00:1	4.5:1	#000000	#000000	Fail
span 252	1.00:1	4.5:1	#000000	#000000	Fail
span •	1.00:1	4.5:1	#000000	#000000	Fail
div My Fantasy with Rocc…	1.00:1	4.5:1	#000000	#000000	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.

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 17 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
All Videos `div.category-header > div.series-nav-wrapper > div#seriesNav > a.series-item`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●Links have a discernible name

●Touch targets have sufficient size and spacing.

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

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

●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

○Deprecated ARIA roles were not used

○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

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

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

○Heading elements appear in a sequentially-descending order

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

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

○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

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

○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

No headings to evaluate -- check is N/A

PASS

No headings to evaluate -- check is N/A

A+

Alt Text Quality

All 74 images OK

PASS

All 74 images OK

24 decorative image(s) correctly marked

50 image(s) with good alt text

74 images 50 good alt text 24 decorative

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" name="s">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
s	text	(Search...)	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

A+

Link & Button Quality

282 links, 4 buttons — all OK

PASS

282 links, 4 buttons — all OK

282 link(s) with descriptive text

282 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

286 links and buttons have descriptive text

A+

Form Input Types

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

PASS

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

A+

Form Input Quality

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

PASS

1 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+

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

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+

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.