Skip to content
https://pornordo.com

Accessibility

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

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
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
50 headings
REVIEW
50 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 HALL OF FAME
  • H3 AI PORN
  • H3 CAM SITES
  • H3 VR PORN
  • H3 PORN NETWORK
  • H3 TABOO PORN
  • H3 GAMBLING SITES
  • H3 SHEMALE PORN
  • H3 24/7 VOYEUR CAMS
  • H3 AMATEUR PORN
  • H3 ASIAN PORN
  • H3 HENTAI / COMICS
  • H3 LESBIAN PORN
  • H3 GAY PORN
  • H3 EUROPEAN PORN
  • H3 LATINA PORN
  • H3 CREATOR PLATFORM
  • H3 MATURE PORN
  • H3 DATING
  • H3 SEX SHOPS
  • H3 HER PORN
  • H3 BLACK & MIX
  • H3 FETISH PORN
  • H3 BBW PORN
  • H3 ANAL PORN
  • H3 BJ/HJ & MASSAGE
  • H3 AWESOME TOOLS
  • H3 PORN GAMES
  • H3 PORN FORUM
  • H3 FREE PORN VIDEOS
  • H3 DIRECTORIES
  • H3 PORNSTARS
  • H3 ARAB PORN
  • H3 INDIAN PORN
  • H3 EROTIC BLOGS
  • H3 SEX STORIES
  • H3 AGGREGATORS
  • H3 CELEBRITY PORN
  • H3 XXX PHOTOS
  • H3 Welcome to Pornordo.com 🔞
  • H4 The joint’s your ultimate guide to the finest porn sites the web has to offer. We’re not just throwing random names in the air, hoping one sticks. Every site you see here has been handpicked, thor
  • H4 We’ve scoured the internet so you don’t have to. The result is a curated list of the most reliable, high-quality porn sites out there. From premium porn sites mentioned in the site’s Hall Of Fam
  • H4 At pornordo.com, we don’t half-ass it. Our experienced team invests time into exploring the wild world of porn, wading through all the junk to bring you the cream of the crop.
  • H4 Whether you’re after high-quality sites that’ve been dishing out premium content for years or some fresh new hottie that’s blowing up the scene, we’ve got you covered. If a site starts sucking
  • H4 Everything here is about you, the user. pornordo.com knows navigating through a sea of porn can be boring, so it keeps it simple. This porn directory is easy to navigate. It’s cut out the garbage so
  • H4 It’s not blowing smoke when we say that pornordo.com is the best destination for those searching for top-tier porn site listings. We’ve seen it all and know exactly what to look for in a site. Our
  • H4 Honest Listings: We keep it real. If a site doesn’t measure up, you won’t find it here.
  • H4 Constant Updates: The porn game changes fast, but we’re always on top of it.
  • H4 Expert Insight: We’re no amateurs. Our team knows the adult industry inside and out, curating only the top listings for you.
  • H4 If you’re on the hunt for the best porn sites on the web, pornordo.com is your go-to directory. Start exploring our curated picks today!

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

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 Page not found – Pornordo Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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 Missing
Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 18 passed
REVIEW
88

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contact div.textwidget > div.footer-content > p > a
Honorable Mention div.textwidget > div.footer-content > p > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Honorable Mention div.textwidget > div.footer-content > p > a

These are opportunities to improve the legibility of your content.

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-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
Buttons have an accessible name
Image elements have `[alt]` attributes
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.
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Deprecated ARIA roles were not used
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
`[accesskey]` values are unique
`[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-hidden="true"]` elements do not contain focusable descendents
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
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
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H4: 196 chars - H4: 194 chars - H4: 175 chars
Got: 3 >120-char heading(s)
Info::
39 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: 39 all-caps heading(s)
A+
Alt Text Quality
All 1082 images OK
PASS
All 1082 images OK
Info::
1082 image(s) with good alt text
1082 images 1082 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="search-input">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-inputtext(Search sites...)placeholder only

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

<input type="text" id="search-input">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
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 "search-input" should use type="search" (currently type="text")
Field name "search-input" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
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
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+
Mobile-Readable Font Sizes
All 262 visible text node(s) render at >= 12 CSS pixels
PASS
All 262 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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.
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
h3 HALL OF FAME14.88:13.0:1
#000000
#D9D9D9
Pass
h3 AI PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 CAM SITES14.88:13.0:1
#000000
#D9D9D9
Pass
h3 VR PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 PORN NETWORK14.88:13.0:1
#000000
#D9D9D9
Pass
h3 TABOO PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 GAMBLING SITES14.88:13.0:1
#000000
#D9D9D9
Pass
h3 SHEMALE PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 24/7 VOYEUR CAMS14.88:13.0:1
#000000
#D9D9D9
Pass
h3 AMATEUR PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 ASIAN PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 HENTAI / COMICS14.88:13.0:1
#000000
#D9D9D9
Pass
h3 LESBIAN PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 GAY PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 EUROPEAN PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 LATINA PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 CREATOR PLATFORM14.88:13.0:1
#000000
#D9D9D9
Pass
h3 MATURE PORN14.88:13.0:1
#000000
#D9D9D9
Pass
h3 DATING14.88:13.0:1
#000000
#D9D9D9
Pass
h3 SEX SHOPS14.88:13.0:1
#000000
#D9D9D9
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