Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 2 REVIEW 5 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 404 - Oops! This page seems to have disappeared | Rocco Siffredi ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

FIX

4 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

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

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

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 ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 #18181b ✓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 Rocco Siffredi

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The Rocco Experience: How To Be A Great …

1.27:1

#000000

#211E22

needs 3.0:1 (large text)

24px · above the fold

h2 The Rocco Experience: How To Be A Great …

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · mid-page

h2 Latest

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Upcoming

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Rocco Siffredi

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Serie : Rocco's Sex Clinic

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Serie : Rocco's Perverted Secretaries

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Serie : Introspection

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Teen

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Anal

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why Become a Member?

1.19:1

#000000

#18181B

needs 3.0:1 (large text)

24px · bottom of viewport

title Rocco Siffredi Porn Videos & Films | Roc…

1.14:1

#000000

#141415

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.10:1

#000000

#120F0D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.34:1

#000000

#292220

needs 4.5:1 (normal text)

16px · top of page (header area)

a Latest

1.61:1

#000000

#372F2F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Top Rated

1.71:1

#000000

#3E3231

needs 4.5:1 (normal text)

16px · above the fold

a Actors

1.29:1

#000000

#291D1C

needs 4.5:1 (normal text)

16px · above the fold

a Categories

1.25:1

#000000

#241C17

needs 4.5:1 (normal text)

16px · above the fold

a About

1.40:1

#000000

#2D2520

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Rocco Siffredi	1.19:1	3.0:1	#000000	#18181B	Fail
h2 The Rocco Experience…	1.27:1	3.0:1	#000000	#211E22	Fail
h2 The Rocco Experience…	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Latest	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Upcoming	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Rocco Siffredi	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Serie : Rocco's Sex …	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Serie : Rocco's Perv…	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Serie : Introspectio…	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Teen	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Anal	1.19:1	3.0:1	#000000	#18181B	Fail
h2 Why Become a Member?	1.19:1	3.0:1	#000000	#18181B	Fail
title Rocco Siffredi Porn …	1.14:1	4.5:1	#000000	#141415	Fail
a Skip to main content	1.10:1	4.5:1	#000000	#120F0D	Fail
a Home	1.34:1	4.5:1	#000000	#292220	Fail
a Latest	1.61:1	4.5:1	#000000	#372F2F	Fail
a Top Rated	1.71:1	4.5:1	#000000	#3E3231	Fail
a Actors	1.29:1	4.5:1	#000000	#291D1C	Fail
a Categories	1.25:1	4.5:1	#000000	#241C17	Fail
a About	1.40:1	4.5:1	#000000	#2D2520	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

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

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

13 headings

PASS

13 headings

Single H1 present

H2 The Rocco Experience: How To Be A Great Pornstar - Vampire Contamination
H2 The Rocco Experience: How To Be A Great Pornstar - Vampire Contamination
H1 Rocco Siffredi
H2 LatestSee All
H2 UpcomingSee All
H2 Rocco SiffrediSee All
H2 Serie : Rocco's Sex ClinicSee All
H2 Serie : Rocco's Perverted SecretariesSee All
H2 Serie : IntrospectionSee All
H2 TeenSee All
H2 AnalSee All
H2 Who is Rocco Siffredi?
H2 Why Become a Member?

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 53 images OK

PASS

All 53 images OK

53 image(s) with good alt text

53 images 53 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	Language	aria-label

A+

Link & Button Quality

78 links, 26 buttons — all OK

PASS

78 links, 26 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://www.famesupport.com

77 link(s) with descriptive text

78 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.famesupport.com	Support	new tab	Add '(opens in new tab)' to text

103 links and buttons have descriptive text

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

https://www.famesupport.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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

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+

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

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

PASS

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

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

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

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 23 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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

●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

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

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

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

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