Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 4 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #cecece

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

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

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 LegalPorno.net 274994 Adult Porn Movies

1.00:1

#000000

needs 3.0:1 (large text)

32px · above the fold

title LegalPorno.net

1.23:1

#000000

#1B1C20

needs 4.5:1 (normal text)

16px · top of page (header area)

a LegalPorno.net

1.23:1

#000000

#1B1C20

needs 4.5:1 (normal text)

16px · top of page (header area)

a MODELS

1.11:1

#000000

#101113

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a GENRES

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

b JOIN NOW

1.00:1

#000000

needs 3.0:1 (large text)

16px · above the fold

button Search

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

p Legalporno.net 274994 exclusive porn vid…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span ⇐

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span ...

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a 11459

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a ⇒

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

video Your browser does not support the video …

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

div Full HD

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

div Invited a Porn Actor for Dinner and Deep…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Maxgen

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span 00:13:25

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

span 2026-07-11

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

video Your browser does not support the video …

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

div Full HD

1.00:1

#000000

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)

Element	Ratio	Required	FG	BG	Result
h1 LegalPorno.net 27499…	1.00:1	3.0:1	#000000	#000000	Fail
title LegalPorno.net	1.23:1	4.5:1	#000000	#1B1C20	Fail
a LegalPorno.net	1.23:1	4.5:1	#000000	#1B1C20	Fail
a MODELS	1.11:1	4.5:1	#000000	#101113	Fail
a GENRES	1.00:1	4.5:1	#000000	#000000	Fail
b JOIN NOW	1.00:1	3.0:1	#000000	#000000	Fail
button Search	1.00:1	4.5:1	#000000	#000000	Fail
p Legalporno.net 27499…	1.00:1	4.5:1	#000000	#000000	Fail
span ⇐	1.00:1	4.5:1	#000000	#000000	Fail
span ...	1.00:1	4.5:1	#000000	#000000	Fail
a 11459	1.00:1	4.5:1	#000000	#000000	Fail
a ⇒	1.00:1	4.5:1	#000000	#000000	Fail
video Your browser does no…	1.00:1	4.5:1	#000000	#000000	Fail
div Full HD	1.00:1	4.5:1	#000000	#000000	Fail
div Invited a Porn Actor…	1.00:1	4.5:1	#000000	#000000	Fail
a Maxgen	1.00:1	4.5:1	#000000	#000000	Fail
span 00:13:25	1.00:1	4.5:1	#000000	#000000	Fail
span 2026-07-11	1.00:1	4.5:1	#000000	#000000	Fail
video Your browser does no…	1.00:1	4.5:1	#000000	#000000	Fail
div Full HD	1.00:1	4.5:1	#000000	#000000	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 LegalPorno.net 274994 Adult Porn Movies

A+

Heading Text Quality

All 1 heading(s) have substantive, well-formed text

PASS

All 1 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text" name="story" id="story">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#story	text	(Search from 274994 LegalPorno.net scenes...)	placeholder only

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

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

Link & Button Quality

84 links, 1 buttons — all OK

PASS

84 links, 1 buttons — all OK

5 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://pornbox.com/landing/analvids?aff=YNKEXKKNRK_legalpornonet_slide1_; https://pornbox.com/landing/analvids?aff=YNKEXKKNRK_legalpornonet_footerbaner1_; https://twitter.com/evilutionplex; https://xxxpornbox.com; https://pornbox.com/application/docs/notice2257?aff=YNKEXKKNRK~legalporno~2257

79 link(s) with descriptive text

84 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://pornbox.com/landing/analvids?aff…	Join to LegalPorno.com	new tab	Add '(opens in new tab)' to text
https://pornbox.com/landing/analvids?aff…	Get instant access to LegalPor…	new tab	Add '(opens in new tab)' to text
https://twitter.com/evilutionplex	Twitter	new tab	Add '(opens in new tab)' to text
https://xxxpornbox.com	XXXPornBox.com	new tab	Add '(opens in new tab)' to text
https://pornbox.com/application/docs/not…	18 U.S.C. 2257 Record Keeping …	new tab	Add '(opens in new tab)' to text

80 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://pornbox.com/landing/analvids?aff=YNKEXKKNRK_legalpornonet_slide1_; https://pornbox.com/landing/analvids?aff=YNKEXKKNRK_legalpornonet_footerbaner1_; https://twitter.com/evilutionplex; https://xxxpornbox.com; https://pornbox.com/application/docs/notice2257?aff=YNKEXKKNRK~legalporno~2257

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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

Input "story" should use type="search" (currently type="text")

Field name "story" 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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 163 visible text node(s) render at >= 12 CSS pixels

PASS

All 163 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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 97/100 — 1 failing, 14 passed

PASS

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.svg `html.svg`

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>`

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[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-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

○`[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

○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.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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

○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.