Skip to content
https://titanicporn.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
7
REVIEW
6
PASS
11
INFO
0
Checks
24
11 PASS 6 REVIEW 7 FIX
D
Alt Text Quality
Action
2 of 34 images have issues
FIX
2 of 34 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
34 images 30 good alt text 2 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Mobile-Readable Font Sizes
Action
66% of visible text renders at >= 12 CSS px (90 below threshold)
FIX
66% of visible text renders at >= 12 CSS px (90 below threshold)
Warning::
90 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> 11.0px ("HD"); <span> 11.0px ("36"); <span> 11.0px ("16:16"); <span> 11.0px ("HD"); <span> 11.0px ("38").
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Missing
✗ Multiple Sizes Missing
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
No dark mode signals
FIX
No dark mode signals
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 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.

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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
6 headings
REVIEW
6 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Free Porn Sites
  • H2 Latest videos
  • H3 Recommeded Porn Sites
  • H3 Join
  • H3 Login to
  • H3 Reset Password

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Form Accessibility
Action
6 of 9 controls have issues
REVIEW
6 of 9 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="checkBtn">; <input type="text" name="s" id="s">; <input type="submit" id="searchsubmit">; <input type="text" name="wpst_user_login">; <input type="password" name="wpst_user_pass">; <input type="text" name="wpst_user_login">
Info::
3 control(s) properly labeled
9 controls
3 labeled
0 placeholder only
6 unlabeled
ControlTypeLabelMethod
#wpst_user_emailemailEmailfor/id
#wpst_user_passpasswordPasswordfor/id
#wpst_user_or_emailtextUsername or E-mailfor/id
wpst_user_logintext(none)none
#checkBtncheckbox(none)none
wpst_user_passpassword(none)none
wpst_user_logintext(none)none
#stext(none)none
#searchsubmitsubmit(none)none

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

<input type="checkbox" id="checkBtn">; <input type="text" name="s" id="s">; <input type="submit" id="searchsubmit">; <input type="text" name="wpst_user_login">; <input type="password" name="wpst_user_pass">; <input type="text" name="wpst_user_login">

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

C
Iframe Accessibility
Action
4/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
4/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="javascript:false")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://titanicporn.com/wp-content/uploads/ad-banners/mypervyfamily_300-250.html")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.picthumbs.com/wp-content/uploads/ad-banners/evilangel-sheena-shaw_3…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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
h2 Latest videos
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Free Porn Sites
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
19px · above the fold
h3 Recommeded Porn Sites
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Join
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Login to
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Reset Password
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
19px · bottom of viewport
title Welcome To Titanic Porn! Only FREE HQ hi…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Categories
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Tags
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Actors
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · above the fold
a Paysites
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · above the fold
a The Porn Dude
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · above the fold
a Porn Sites
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · above the fold
a Pink World
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · above the fold
a Sexy Nude Pics
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · above the fold
a TeensYoung.com
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · above the fold
a Family-Sex.me
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · mid-page
a The Best Fetish Sites
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Latest videos1.29:13.0:1
#000000
#202020
Fail
h3 Free Porn Sites1.29:13.0:1
#000000
#202020
Fail
h3 Recommeded Porn Site…1.29:13.0:1
#000000
#202020
Fail
h3 Join1.29:13.0:1
#000000
#202020
Fail
h3 Login to1.29:13.0:1
#000000
#202020
Fail
h3 Reset Password1.29:13.0:1
#000000
#202020
Fail
title Welcome To Titanic P…1.00:14.5:1
#000000
#000000
Fail
a Skip to content1.00:14.5:1
#000000
#000000
Fail
a Home1.00:14.5:1
#000000
#000000
Fail
a Categories1.00:14.5:1
#000000
#000000
Fail
a Tags1.13:14.5:1
#000000
#131313
Fail
a Actors1.29:14.5:1
#000000
#202020
Fail
a Paysites1.29:14.5:1
#000000
#202020
Fail
a The Porn Dude1.29:14.5:1
#000000
#202020
Fail
a Porn Sites1.29:14.5:1
#000000
#202020
Fail
a Pink World1.29:14.5:1
#000000
#202020
Fail
a Sexy Nude Pics1.29:14.5:1
#000000
#202020
Fail
a TeensYoung.com1.29:14.5:1
#000000
#202020
Fail
a Family-Sex.me1.29:14.5:1
#000000
#202020
Fail
a The Best Fetish Site…1.29:14.5:1
#000000
#202020
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 3 failing, 18 passed
REVIEW
82

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-offer > div.footer-offer-1 > a > iframe div.footer-offer > div.footer-offer-1 > a > iframe

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
header#masthead > div.site-branding > div.logo > a header#masthead > div.site-branding > div.logo > a
div.row > div.footer-offer > div.footer-offer-1 > a div.row > div.footer-offer > div.footer-offer-1 > a
div#page > footer#colophon > div.logo-footer > a div#page > footer#colophon > div.logo-footer > a

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●Image elements have `[alt]` attributes
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●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
●Skip links are focusable.
●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
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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 use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○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.
○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.
A
Landmark Structure
35 landmarks
PASS
35 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+
Heading Text Quality
All 6 heading(s) have substantive, well-formed text
PASS
All 6 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
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 "wpst_user_or_email" should use type="email" (currently type="text")
Field name "wpst_user_or_email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A
Form Input Quality
1 input-semantic issue(s) across 9 form control(s)
PASS
1 input-semantic issue(s) across 9 form control(s)
Info::
2 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="wpst_user_pass">, <input type="password" name="wpst_user_pass">.
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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::
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.

Send Feedback