Skip to content
https://porn-stars.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
7
REVIEW
2
PASS
15
INFO
0
Checks
24
15 PASS 2 REVIEW 7 FIX
D
Mobile-Readable Font Sizes
Action
33% of visible text renders at >= 12 CSS px (97 below threshold)
FIX
33% of visible text renders at >= 12 CSS px (97 below threshold)
Warning::
97 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> 10.2px ("PORN-STARS.COM · ADULT PORN STARS & PERF..."); <a> 10.2px ("XVIDEOS"); <a> 10.2px ("XNXX"); <a> 10.2px ("BANGBROS"); <span> 10.2px ("PORN STARS · ADULT PERFORMERS · HOT WOME...").
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
Info::
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
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: #11141a
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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 "Featured adult destinations" MAIN (missing!) ASIDE CONTENTINFO footer

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

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 .COM
1.19:1
#000000
on
#151823
needs 3.0:1 (large text)
32px · above the fold
h2 Find porn stars, adult performers, hot w…
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Free Adult Video Tubes
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Adult Studio & Specialist Options
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Compare porn-star searches, performer ca…
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 XVideos
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 XNXX
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 BangBros
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AnalVids
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 XVideos Red
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 XNXX Gold
1.13:1
#000000
on
#0F131B
needs 3.0:1 (large text)
19px · bottom of viewport
title Porn-Stars.com | Adult Porn Stars & Perf…
3.24:1
#000000
on
#735662
needs 4.5:1 (normal text)
16px · top of page (header area)
span PORN-STARS.COM · ADULT PORN STARS & PER…
1.09:1
#000000
on
#0C0E15
needs 4.5:1 (normal text)
16px · top of page (header area)
a XVIDEOS
1.11:1
#000000
on
#0E1017
needs 4.5:1 (normal text)
16px · top of page (header area)
a XNXX
1.11:1
#000000
on
#0E1119
needs 4.5:1 (normal text)
16px · top of page (header area)
a BANGBROS
1.11:1
#000000
on
#0E1119
needs 4.5:1 (normal text)
16px · above the fold
span PORN STARS · ADULT PERFORMERS · HOT WO…
1.12:1
#000000
on
#0F121B
needs 4.5:1 (normal text)
16px · above the fold
span PORN-STARS.COM · ADULT PORN STARS & PER…
1.14:1
#000000
on
#11141E
needs 4.5:1 (normal text)
16px · above the fold
a XVIDEOS
1.15:1
#000000
on
#12141F
needs 4.5:1 (normal text)
16px · above the fold
a XNXX
1.17:1
#000000
on
#141622
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 .COM1.19:13.0:1
#000000
#151823
Fail
h2 Find porn stars, adu…1.13:13.0:1
#000000
#0F131B
Fail
h2 Free Adult Video Tub…1.13:13.0:1
#000000
#0F131B
Fail
h2 Adult Studio & Speci…1.13:13.0:1
#000000
#0F131B
Fail
h3 Compare porn-star se…1.13:13.0:1
#000000
#0F131B
Fail
h3 XVideos1.13:13.0:1
#000000
#0F131B
Fail
h3 XNXX1.13:13.0:1
#000000
#0F131B
Fail
h3 BangBros1.13:13.0:1
#000000
#0F131B
Fail
h3 AnalVids1.13:13.0:1
#000000
#0F131B
Fail
h3 XVideos Red1.13:13.0:1
#000000
#0F131B
Fail
h3 XNXX Gold1.13:13.0:1
#000000
#0F131B
Fail
title Porn-Stars.com | Adu…3.24:14.5:1
#000000
#735662
Fail
span PORN-STARS.COM · AD…1.09:14.5:1
#000000
#0C0E15
Fail
a XVIDEOS1.11:14.5:1
#000000
#0E1017
Fail
a XNXX1.11:14.5:1
#000000
#0E1119
Fail
a BANGBROS1.11:14.5:1
#000000
#0E1119
Fail
span PORN STARS · ADULT …1.12:14.5:1
#000000
#0F121B
Fail
span PORN-STARS.COM · AD…1.14:14.5:1
#000000
#11141E
Fail
a XVIDEOS1.15:14.5:1
#000000
#12141F
Fail
a XNXX1.17:14.5:1
#000000
#141622
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
11 headings
PASS
11 headings
Info::
Single H1 present
  • H1 PORN-STARS.COM
  • H2 Find porn stars, adult performers, hot women and mature women.
  • H3 Compare porn-star searches, performer categories, mature women and premium adult catalogs.
  • H2 Free Adult Video Tubes
  • H3 XVideos
  • H3 XNXX
  • H2 Adult Studio & Specialist Options
  • H3 BangBros
  • H3 AnalVids
  • H3 XVideos Red
  • H3 XNXX Gold
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 2 all-caps heading(s)
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
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 98/100 — 1 failing, 16 passed
PASS
98

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.

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
●`[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 are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[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
○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
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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
○`<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.
○Identical links have the same purpose.
○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