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 4 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ 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

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

5 landmarks

REVIEW

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

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

Mobile-Readable Font Sizes

Action

73% of visible text renders at >= 12 CSS px (67 below threshold)

REVIEW

73% of visible text renders at >= 12 CSS px (67 below threshold)

67 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: <span> 9.0px ("Matchup champion"); <span> 10.0px ("Cumshot"); <span> 10.0px ("Big Tits"); <span> 10.0px ("All Sex"); <span> 10.0px ("Big Dick").

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 RateMyScene — Watch less blindly. Discover with taste. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 Watch less blindly.

1.18:1

#000000

#2B0E19

needs 3.0:1 (large text)

32px · mid-page

h2 Trending Now

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Most Popular Categories

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Everything after you press play.

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest Scenes

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trending Pornstars

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Editor's Choice

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Highest Rated

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Build a better watchlist, one honest rat…

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Big Dick Hunk Justice Gives To Brunette …

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 My Wife Threatened To Fuck Five Black Gu…

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Sexy Professor Reagan Foxx Will Grade Ri…

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Best Of Brazzers: Anal Extravaganza

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Prime

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Brandi Love Shows the Pool Cleaner How A…

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Rate & Review

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep a diary

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Discover Quality

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Follow performers

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Vanessa, Picked Up And Fucked

1.10:1

#000000

#1B0B14

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Watch less blindly.	1.18:1	3.0:1	#000000	#2B0E19	Fail
h2 Trending Now	1.10:1	3.0:1	#000000	#1B0B14	Fail
h2 Most Popular Categor…	1.10:1	3.0:1	#000000	#1B0B14	Fail
h2 Everything after you…	1.10:1	3.0:1	#000000	#1B0B14	Fail
h2 Latest Scenes	1.10:1	3.0:1	#000000	#1B0B14	Fail
h2 Trending Pornstars	1.10:1	3.0:1	#000000	#1B0B14	Fail
h2 Editor's Choice	1.10:1	3.0:1	#000000	#1B0B14	Fail
h2 Highest Rated	1.10:1	3.0:1	#000000	#1B0B14	Fail
h2 Build a better watch…	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Big Dick Hunk Justic…	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 My Wife Threatened T…	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Sexy Professor Reaga…	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Best Of Brazzers: An…	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Prime	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Brandi Love Shows th…	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Rate & Review	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Keep a diary	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Discover Quality	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Follow performers	1.10:1	3.0:1	#000000	#1B0B14	Fail
h3 Vanessa, Picked Up A…	1.10:1	3.0:1	#000000	#1B0B14	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

45 headings

PASS

45 headings

Single H1 present

H1 Watch less blindly.Discover with taste.
H2 Trending Now
H3 Big Dick Hunk Justice Gives To Brunette Jayden James All His Load!
H3 My Wife Threatened To Fuck Five Black Guys So I'd Stay Home And I Ended Up Giving Her What She Deserved
H3 Sexy Professor Reagan Foxx Will Grade Rion on How Well He Fucks!!!
H3 Best Of Brazzers: Anal Extravaganza
H3 Prime
H3 Brandi Love Shows the Pool Cleaner How Appreciative She Is for His Hard Work
H2 Most Popular Categories
H2 Everything after you press play.
H3 Rate & Review
H3 Keep a diary
H3 Discover Quality
H3 Follow performers
H2 Latest Scenes
H3 Vanessa, Picked Up And Fucked
H3 Franki & Shona: Ketchup, Curves, And Lesbian Sex
H3 Samantha Bond: Explosive, Oily Blonde, Horny In A Threesome
H3 Franky Knight: Curvy And Horny, Looking For A Stallion
H3 Alexis James
H3 Harley Haze
H2 Trending Pornstars
H3 AJ Applegate
H3 Reagan Foxx
H3 Alexis Fawx
H3 Kendra Lust
H3 Danielle Renae
H3 Aaliyah Ca Pelle
H2 Editor's Choice
H3 Day With A Pornstar - Luna & Sara
H3 JOI Boob Tease With Reagan Foxx
H3 Naught Nicole
H3 Monique Alexander a Muse Dream Cum True
H3 Aletta Ocean's Is The Perfect Secretary And Loves Anal Sex
H2 Highest Rated
H3 Sexy Professor Reagan Foxx Will Grade Rion on How Well He Fucks!!!
H3 Prime
H3 Reagan Foxx Is a MILF Masterpiece
H3 JOI Boob Tease With Reagan Foxx
H3 Best Of Brazzers: Anal Extravaganza
H3 Free-Use Sitter Fucker
H2 Build a better watchlist, one honest rating at a time.
H3 Explore
H3 Community
H3 About

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 40 images OK

PASS

All 40 images OK

1 decorative image(s) correctly marked

39 image(s) with good alt text

40 images 39 good alt text 1 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 name="q">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
q	input	(Search scenes, performers...)	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

72 links, 16 buttons — all OK

PASS

72 links, 16 buttons — all OK

72 link(s) with descriptive text

72 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

88 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 "q" should use type="search" (currently type="text")

Field name "q" 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+

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+

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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 23 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
Start your diary `div.max-w-3xl > div.mt-9 > a > button.inline-flex`
Create your free account `div.rounded-[2rem] > div.mt-8 > a > button.inline-flex`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.geist_a71539c9-module__T19VSG__variable > header.glass > div.mx-auto > a.flex `body.geist_a71539c9-module__T19VSG__variable > header.glass > div.mx-auto > a.flex`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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

●Document has a `<title>` element

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

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

●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

●Image elements do not have `[alt]` attributes that are redundant text.

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

○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

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