Skip to content
https://thepornator.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
4
REVIEW
8
PASS
12
INFO
0
Checks
24
12 PASS 8 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
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.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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

C
Form Accessibility
Action
5 of 6 controls have issues
REVIEW
5 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="query">; <textarea id="rp-details">; <input type="text" id="rp-name">; <input type="email" id="rp-email">
Info::
1 control(s) properly labeled
6 controls
1 labeled
4 placeholder only
1 unlabeled
ControlTypeLabelMethod
#categoryselectCategoryaria-label
querytext(What are you looking for?)placeholder only
#rp-detailstextarea(Please describe the issue in detail…)placeholder only
#rp-nametext(Your name (optional))placeholder only
#rp-emailemail(Your email (optional))placeholder only
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="query">; <textarea id="rp-details">; <input type="text" id="rp-name">; <input type="email" id="rp-email">

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

C
Mobile Keyboard & Autofill
Action
1/2 eligible field(s) missing autocomplete or inputmode
REVIEW
1/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" id="rp-email">
B
Mobile-Readable Font Sizes
94% of visible text renders at >= 12 CSS px (9 below threshold)
REVIEW
94% of visible text renders at >= 12 CSS px (9 below threshold)
Info::
9 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: <a> 0.0px ("Start survey"); <span> 11.5px ("08-15-2026"); <span> 11.5px ("Vxxx"); <span> 11.5px ("08-15-2026"); <span> 11.5px ("Vxxx").
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Unknown page ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
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 Find your perfect porn site in 3 minutes…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 The Pornator is your ultimate porn hub. …
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Newest porn sites
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most recent AI porn pics
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most recent AI porn videos
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most recent porn lexicon terms
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Models of the day
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most recent porn videos
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most recent blog porn articles
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Clavicular and the rise of masculinism: …
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How Lemoncams balances entertainment and…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most recent sex stories
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Girl next door invites two to wreck her
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The baller's initiation
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most recent sex scripts
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Top 10 des APPARITIONS des STARS DU X da…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Memoirs of a Former Adult Talent Agent-C…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pornator is different than others porn s…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Share the Pornator
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently asked questions
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Find your perfect po…1.00:13.0:1
#000000
#000000
Fail
h2 The Pornator is your…1.00:13.0:1
#000000
#000000
Fail
h2 Newest porn sites1.00:13.0:1
#000000
#000000
Fail
h2 Most recent AI porn …1.00:13.0:1
#000000
#000000
Fail
h2 Most recent AI porn …1.00:13.0:1
#000000
#000000
Fail
h2 Most recent porn lex…1.00:13.0:1
#000000
#000000
Fail
h2 Models of the day1.00:13.0:1
#000000
#000000
Fail
h2 Most recent porn vid…1.00:13.0:1
#000000
#000000
Fail
h2 Most recent blog por…1.00:13.0:1
#000000
#000000
Fail
h2 Clavicular and the r…1.00:13.0:1
#000000
#000000
Fail
h2 How Lemoncams balanc…1.00:13.0:1
#000000
#000000
Fail
h2 Most recent sex stor…1.00:13.0:1
#000000
#000000
Fail
h2 Girl next door invit…1.00:13.0:1
#000000
#000000
Fail
h2 The baller's initiat…1.00:13.0:1
#000000
#000000
Fail
h2 Most recent sex scri…1.00:13.0:1
#000000
#000000
Fail
h2 Top 10 des APPARITIO…1.00:13.0:1
#000000
#000000
Fail
h2 Memoirs of a Former …1.00:13.0:1
#000000
#000000
Fail
h2 Pornator is differen…1.00:13.0:1
#000000
#000000
Fail
h2 Share the Pornator1.00:13.0:1
#000000
#000000
Fail
h2 Frequently asked que…1.00:13.0: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.

A+
Heading Hierarchy
40 headings
PASS
40 headings
Info::
Single H1 present
  • H1 Find your perfect porn site in 3 minutes with Pornator!
  • H2 The Pornator is your ultimate porn hub. Browse sites, videos, AI pictures, models, a glossary, and scripts!
  • H2 Newest porn sites
  • H3 AI Undress CC (11)
  • H3 GTkWhruQyLfrBFKzDO
  • H3 Kinky Florida Amateurs
  • H3 Kinky Florida Amateurs
  • H2 Most recent AI porn pics
  • H2 Most recent AI porn videos
  • H2 Most recent porn lexicon terms
  • H3 Pussypic
  • H3 Knismolagnia
  • H3 Humbler
  • H3 Nyctophilia
  • H2 Models of the day
  • H2 Most recent porn videos
  • H3 Astonishing Xxx Clip Big Dick
  • H3 Hottest Porn Movie Milf Just For You
  • H3 Exotic Porn Video Big Dick Newest Unique
  • H3 Crazy Sex Movie Big Tits Fantastic Uncut
  • H2 Most recent blog porn articles
  • H2 Clavicular and the rise of masculinism: Analyzing a viral counterculture
  • H2 How Lemoncams balances entertainment and user privacy
  • H2 Most recent sex stories
  • H2 Girl next door invites two to wreck her
  • H2 The baller's initiation
  • H2 Most recent sex scripts
  • H2 Top 10 des APPARITIONS des STARS DU X dans les films et à la télé
  • H2 Memoirs of a Former Adult Talent Agent-Chris
  • H2 Pornator is different than others porn sites list
  • H3 Knowledge of porn sites
  • H3 Smart matching
  • H3 Evolutionary learning
  • H2 Share the Pornator
  • H2 Frequently asked questions
  • H3 anna 🐱
  • H2 Report a problem
  • H2 Report a problem —
  • H2 Report sent
  • H3 Thank you for your report!
A+
Heading Text Quality
All 40 heading(s) have substantive, well-formed text
PASS
All 40 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 128 images OK
PASS
All 128 images OK
Info::
128 image(s) with good alt text
128 images 128 good alt text
All images have appropriate alt 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
Info::
Input "query" should use type="search" (currently type="text")
Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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 93/100 — 2 failing, 27 passed
PASS
93

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Rating of this product is 4.1875 out of 5. div.d-block > div.lh-content > h3 > div.Stars

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Undress Her 🔥 div.d-block > div.lh-content > address > span

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
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●ARIA `progressbar` elements have accessible names
●Document has a `<title>` element
●`<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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` 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 type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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.

Send Feedback