Skip to content
https://socialmediapornstars.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
7
REVIEW
6
PASS
11
INFO
0
Checks
24
11 PASS 6 REVIEW 7 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 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 (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

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

F
Heading Hierarchy
Action
34 headings, 9 skip(s)
FIX
34 headings, 9 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Let's find your favorite Pornstars on social media!
  • H4 Browse our database and find all the social media accounts of the world's most sexy babes and pornstars. skipped
  • H3 Isabella Jules
  • H6 Find out if Isabella Jules is on Twitter, Snapchat, Instagram, Facebook or Camsoda... skipped
  • H3 Penelope Snaps
  • H6 Find out if Penelope Snaps is on Twitter, Snapchat, Instagram, Facebook or Camsoda... skipped
  • H3 Era Queen
  • H6 Find out if Era Queen is on Twitter, Snapchat, Instagram, Facebook or Camsoda... skipped
  • H3 Eva Nyx
  • H6 Find out if Eva Nyx is on Twitter, Snapchat, Instagram, Facebook or Camsoda... skipped
  • H3 Dolly Orchid
  • H6 Find out if Dolly Orchid is on Twitter, Snapchat, Instagram, Facebook or Camsoda... skipped
  • H3 Gia Ohmy
  • H6 Find out if Gia Ohmy is on Twitter, Snapchat, Instagram, Facebook or Camsoda... skipped
  • H3 Jennie Rose
  • H6 Find out if Jennie Rose is on Twitter, Snapchat, Instagram, Facebook or Camsoda... skipped
  • H6 SocialMediaPornstars.com
  • H6 Search Model
  • H6 Popular Babes
  • H6 Browse Database
  • H6 Pornstars of the Week
  • H6 Snap of the Month
  • H6 Latest Blog Posts
  • H6 Popular Blog Posts
  • H6 Weekly Porn Discount!
  • H6 Most Related Links
  • H6 Most Instagram Fans
  • H6 Follow Us Online
  • H2 Finding your favorite pornstars on social media has never been so easy...
  • H5 Navigation skipped
  • H5 DB Categories
  • H5 Our Friends
  • H5 Legal & Info
  • H3 (empty)

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
F
Lighthouse Accessibility Audits
Action
Score 41/100 — 11 failing, 11 passed
FIX
41

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#outerboxSearch > div#searchbarV2 > form#search > button.button-design-2 div#outerboxSearch > div#searchbarV2 > form#search > button.button-design-2

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.widget > div > a > img div.widget > div > a > img
aside.right-float > div.imgoverlay > a > img aside.right-float > div.imgoverlay > a > img
div#smallAds > div#bnrfootermob > a > img.lzy_img div#smallAds > div#bnrfootermob > a > img.lzy_img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#outerboxSearch > div#searchbarV2 > form#search > input#global-search div#outerboxSearch > div#searchbarV2 > form#search > input#global-search

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Pornstars Blog Posts div#outerboxSearch > div#searchbarV2 > div.boxs > select#dropdownSearch

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
div#page-content > div#menu-responsive > div#menu-responsive-inner > a.close-responsive-nav div#page-content > div#menu-responsive > div#menu-responsive-inner > a.close-responsive-nav
header#header > div.header-inner > div.menu > a.open-responsive-nav header#header > div.header-inner > div.menu > a.open-responsive-nav
div.whitebox > div.widget > p > a div.whitebox > div.widget > p > a
div.whitebox > div.widget > div > a div.whitebox > div.widget > div > a
aside.right-float > div.whitebox > div.widget > a aside.right-float > div.whitebox > div.widget > a
div.whitebox > div.widget > div.viddeal > a div.whitebox > div.widget > div.viddeal > a
div.section-inner > aside.right-float > div.imgoverlay > a div.section-inner > aside.right-float > div.imgoverlay > a
footer > div#smallAds > div#bnrfootermob > a footer > div#smallAds > div#bnrfootermob > a
div.page-body > footer > div.footerinner > a#backtotop div.page-body > footer > div.footerinner > a#backtotop
div.footerinner > h3 > strong > a div.footerinner > h3 > strong > a
div.footerinner > h3 > strong > a div.footerinner > h3 > strong > a
div.footerinner > h3 > strong > a div.footerinner > h3 > strong > 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.

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
FIND OUT IF ISABELLA JULES IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMS… div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
[Read More] div.blog-content > p.blog-intro > b > a
FIND OUT IF PENELOPE SNAPS IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMS… div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
[Read More] div.blog-content > p.blog-intro > b > a
FIND OUT IF ERA QUEEN IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSODA... div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
[Read More] div.blog-content > p.blog-intro > b > a
FIND OUT IF EVA NYX IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSODA... div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
[Read More] div.blog-content > p.blog-intro > b > a
FIND OUT IF DOLLY ORCHID IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSOD… div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
[Read More] div.blog-content > p.blog-intro > b > a
FIND OUT IF GIA OHMY IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSODA... div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
[Read More] div.blog-content > p.blog-intro > b > a
FIND OUT IF JENNIE ROSE IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSODA… div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
10 div.main-content > div#entries-pagination > center > a
127 div.main-content > div#entries-pagination > center > a
128 div.main-content > div#entries-pagination > center > a
NEXT PAGE div.main-content > div#entries-pagination > center > a.sr-button
blockchain div.widget > p > b > a
div#outerboxSearch > div#searchbarV2 > form#search > input#global-search div#outerboxSearch > div#searchbarV2 > form#search > input#global-search
Pornstars Blog Posts div#outerboxSearch > div#searchbarV2 > div.boxs > select#dropdownSearch
ELSA JEAN div.whitebox > div.widget > div.tag-list > a.design-2
VIKING BARBIE div.whitebox > div.widget > div.tag-list > a.design-2
MIA MALKOVA div.whitebox > div.widget > div.tag-list > a.design-2
ASA AKIRA div.whitebox > div.widget > div.tag-list > a.design-2
DANI DANIELS div.whitebox > div.widget > div.tag-list > a.design-2
ANA LORDE div.whitebox > div.widget > div.tag-list > a.design-2
BRANDI LOVE div.whitebox > div.widget > div.tag-list > a.design-2
RILEY REID div.whitebox > div.widget > div.tag-list > a.design-2
LEXI BELLE div.whitebox > div.widget > div.tag-list > a.design-2
KENDRA LUST div.whitebox > div.widget > div.tag-list > a.design-2
AJ APPLEGATE div.whitebox > div.widget > div.tag-list > a.design-2
LANA RHOADES div.whitebox > div.widget > div.tag-list > a.design-2
DANI LYNN div.whitebox > div.widget > div.tag-list > a.design-2
ANGELA WHITE div.whitebox > div.widget > div.tag-list > a.design-2
Claim Free Week! center > p > a > button.btndeal
AdultTime.com div.widget > p > b > a
Adriana Chechik div.whitebox > div.widget > a > b
Zoe Bloom div.whitebox > div.widget > a > b
Ayumi Anime div.whitebox > div.widget > a > b
Pornstar Mia Malkova div.whitebox > div.widget > a > b
Pornstar Database b > ul.price-options > li > a
Swipe Pornstars (Random) b > ul.price-options > li > a
Blog Posts b > ul.price-options > li > a
Snap Of The Month b > ul.price-options > li > a
Instagram Of The Month b > ul.price-options > li > a
Most Searched Babes b > ul.price-options > li > a
Asian Pornstars b > ul.price-options > li > a
Bubble Butt Pornstars b > ul.price-options > li > a
Busty Pornstars b > ul.price-options > li > a
Black (Ebony) Pornstars b > ul.price-options > li > a
MILF Pornstars b > ul.price-options > li > a
Petite Pornstars b > ul.price-options > li > a
Inked (Tattooed) Pornstars b > ul.price-options > li > a
Virtual Girlfriend b > ul.price-options > li > a
Free Cams b > ul.price-options > li > a
Best Amateur Porn b > ul.price-options > li > a
IndieGameMag b > ul.price-options > li > a
Indexxx b > ul.price-options > li > a
PornCrash b > ul.price-options > li > a
Porn Whitelist b > ul.price-options > li > a
The Porn Bin b > ul.price-options > li > a
Blockchain & API b > ul.price-options > li > a
Historical Data (Twitter) b > ul.price-options > li > a
Terms of Service b > ul.price-options > li > a
Privacy and Cookies Policy b > ul.price-options > li > a

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#outerboxSearch > div#searchbarV2 > form#search > input#global-search div#outerboxSearch > div#searchbarV2 > form#search > input#global-search

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Browse our database and find all the social media accounts of the world's most … section#blog > div.section-inner > div.section-title > h4.subtitle
FIND OUT IF ISABELLA JULES IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMS… div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
FIND OUT IF PENELOPE SNAPS IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMS… div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
FIND OUT IF ERA QUEEN IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSODA... div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
FIND OUT IF EVA NYX IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSODA... div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
FIND OUT IF DOLLY ORCHID IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSOD… div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
FIND OUT IF GIA OHMY IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSODA... div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
FIND OUT IF JENNIE ROSE IS ON TWITTER, SNAPCHAT, INSTAGRAM, FACEBOOK OR CAMSODA… div.blog-entry > div.blog-content > div.blog-headline > h6.post-meta
NAVIGATION div.column-section > div.column > div.pricing-table > h5.price-name

These are opportunities to improve keyboard navigation in your application.

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#outerboxSearch > div#searchbarV2 > form#search > button.button-design-2 div#outerboxSearch > div#searchbarV2 > form#search > button.button-design-2

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.js html.js

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>`
`[aria-hidden="true"]` elements do not contain focusable descendents
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.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
`<video>` elements contain a `<track>` element with `[kind="captions"]`
All heading elements contain content.
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
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
Elements use only permitted ARIA attributes
`[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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
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>`.
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.
B
Alt Text Quality
1 of 26 images have issues
REVIEW
1 of 26 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
25 image(s) with good alt text
26 images 25 good alt text 1 missing
IssueCount
missing1 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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="term" id="global-search">; <select id="dropdownSearch">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#global-searchtext(none)none
#dropdownSearchselect(none)none

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

<input type="text" name="term" id="global-search">; <select id="dropdownSearch">

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

B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Mobile-Readable Font Sizes
92% of visible text renders at >= 12 CSS px (16 below threshold)
REVIEW
92% of visible text renders at >= 12 CSS px (16 below threshold)
Info::
16 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> 10.0px ("Next page"); <a> 11.0px ("Elsa Jean"); <a> 11.0px ("Viking Barbie"); <a> 11.0px ("Mia Malkova"); <a> 11.0px ("Asa Akira").
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
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404 Error: Page Not Found - SocialMediaPornstars.com Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
A+
Heading Text Quality
All 34 heading(s) have substantive, well-formed text
PASS
All 34 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 "term" should use type="search" (currently type="text")
Field name "term" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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 positive, 0 -1-on-focusable
PASS
1 positive, 0 -1-on-focusable
Warning::
Positive tabindex on <input id="global-search">: tabindex=1
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Social Pornstars
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Social Pornstars 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name Social Pornstars Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
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+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Let's find your favo…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 on social media!20.12:13.0:1
#000000
#FAFAFA
Pass
title Search for your favo…20.12:14.5:1
#000000
#FAFAFA
Pass
a All Pornstars20.12:14.5:1
#000000
#FAFAFA
Pass
a Blog20.12:14.5:1
#000000
#FAFAFA
Pass
a Popular20.12:14.5:1
#000000
#FAFAFA
Pass
a Phoenix Marie20.12:14.5:1
#000000
#FAFAFA
Pass
a Tori Black20.12:14.5:1
#000000
#FAFAFA
Pass
a Mia Melano20.12:14.5:1
#000000
#FAFAFA
Pass
a Abella Danger20.12:14.5:1
#000000
#FAFAFA
Pass
a Asa Akira20.12:14.5:1
#000000
#FAFAFA
Pass
a Dani Daniels20.12:14.5:1
#000000
#FAFAFA
Pass
a Valentina Nappi20.12:14.5:1
#000000
#FAFAFA
Pass
a Most Searched Babes20.12:14.5:1
#000000
#FAFAFA
Pass
a Most Active Pornstar…20.12:14.5:1
#000000
#FAFAFA
Pass
a Top 100 Instagram20.12:14.5:1
#000000
#FAFAFA
Pass
a Lists20.12:14.5:1
#000000
#FAFAFA
Pass
a All Pornstars on Sna…20.12:14.5:1
#000000
#FAFAFA
Pass
a All Pornstars on Onl…20.12:14.5:1
#000000
#FAFAFA
Pass
a All Pornstars on Cha…20.12:14.5:1
#000000
#FAFAFA
Pass

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.

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

Send Feedback