Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 3 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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

No dark mode signals

FIX

No dark mode signals

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

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

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

7 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 7 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit" name="go" id="searchButton">; <input type="submit" name="fulltext" id="mw-searchButton">

1 control(s) properly labeled

3 controls

1 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#searchInput	search	Search Wikiporno	aria-label
#searchButton	submit	(none)	none
#mw-searchButton	submit	(none)	none

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

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

Link & Button Quality

3 issue(s) across 236 links and 2 buttons

REVIEW

3 issue(s) across 236 links and 2 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#top; /

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: #p-cactions ("More")

233 link(s) with descriptive text

236 links

2 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
#p-cactions	More	generic text	Replace with descriptive text
Before: More Suggested: #P Cactions
/	(empty)	empty	Add link text or aria-label

235 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#top; /

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

#p-cactions ("More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Mobile-Readable Font Sizes

Action

73% of visible text renders at >= 12 CSS px (63 below threshold)

REVIEW

73% of visible text renders at >= 12 CSS px (63 below threshold)

63 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: <p> 9.0px ("So far we have"); <a> 9.0px ("135,089"); <p> 9.0px ("articles. Enjoy!\nWikiporno.org does not..."); <h3> 11.0px ("Page actions"); <a> 11.5px ("Main Page").

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

7 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Skip link target(s) don't exist on page: #column-one, #searchInput

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.

Search landmark present

Page Structure — as a screen reader sees it

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 Hierarchy

29 headings

PASS

29 headings

Single H1 present

H1 Free Porn Directory
H2 Porn Stars
H2 Porn Sites
H2 Free Porn Videos
H2 Free Porn Pictures & Galleries
H2 Webcams & Live Chat
H2 Porn Reviews
H2 Porn Lists
H2 AI Porn
H2 Sex Toys
H2 Porn Movies
H2 Porn Studios
H2 Popular Articles
H2 Adult Blogs
H2 Adult Dating
H2 VOD
H2 Porn Games
H2 Sex Education
H2 Community
H2 Porn Webmasters
H2 Navigation menu
H3 Page actions
H3 Page actions
H3 Personal tools
H3 Navigation
H3 Search
H3 Categories
H3 Tools
H3 In other languages

A+

Heading Text Quality

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

PASS

All 29 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.

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 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+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

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)

Element	Ratio	Required	FG	BG	Result
h2 Navigation menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Page actions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Page actions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Personal tools	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Navigation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Categories	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Tools	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 In other languages	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Wikiporno - Free Por…	19.26:1	4.5:1	#000000	#F5F5F5	Pass
span Free Porn Directory	19.26:1	4.5:1	#000000	#F5F5F5	Pass
div From Wikiporno	17.46:1	4.5:1	#000000	#EAEAEA	Pass
a Jump to navigation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Jump to search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
b Welcome to	21.00:1	3.0:1	#000000	#FFFFFF	Pass
a Wikiporno	21.00:1	4.5:1	#000000	#FFFFFF	Pass
b – the	21.00:1	3.0:1	#000000	#FFFFFF	Pass
a free porn directory	21.00:1	4.5:1	#000000	#FFFFFF	Pass
b that anyone can	21.00:1	3.0:1	#000000	#FFFFFF	Pass
a edit	21.00:1	4.5:1	#000000	#FFFFFF	Pass
b Wikiporno	21.00:1	3.0:1	#000000	#FFFFFF	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.

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 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.

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
Porn Stars `div.mainpage-column-div > h2.mainpage-h2 > span#Porn_Stars > a`
Porn Sites `div.mainpage-column-div > h2.mainpage-h2 > span#Porn_Sites > a`
Free Porn Videos `div.mainpage-column-div > h2.mainpage-h2 > span#Free_Porn_Videos > a`
Free Porn Pictures & Galleries `div.mainpage-column-div > h2.mainpage-h2 > span#Free_Porn_Pictures_&_Galleries > a`
Webcams & Live Chat `div.mainpage-column-div > h2.mainpage-h2 > span#Webcams_&_Live_Chat > a`
Porn Reviews `div.mainpage-column-div > h2.mainpage-h2 > span#Porn_Reviews > a`
Porn Lists `div.mainpage-column-div > h2.mainpage-h2 > span#Porn_Lists > a`
AI Porn `div.mainpage-column-div > h2.mainpage-h2 > span#AI_Porn > a`
Sex Toys `div.mainpage-column-div > h2.mainpage-h2 > span#Sex_Toys > a`
Porn Movies `div.mainpage-column-div > h2.mainpage-h2 > span#Porn_Movies > a`
Porn Studios `div.mainpage-column-div > h2.mainpage-h2 > span#Porn_Studios > a`

These are opportunities to improve the legibility of your content.

Names and labels

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
header.header-container > div.minerva-header > nav.navigation-drawer > input#main-menu-input `header.header-container > div.minerva-header > nav.navigation-drawer > input#main-menu-input`

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.

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○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

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

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

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

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