Skip to content
https://fetish4all.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 500, custom page
FIX
HTTP 500, custom page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 500 ✗Page Title Database Error ✓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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ 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
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Form Accessibility
Action
3 of 9 controls have issues
REVIEW
3 of 9 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="s" id="s">; <input type="submit" id="searchsubmit">; <input type="text" name="wpst_user_login">
Info::
6 control(s) properly labeled
9 controls
6 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
age_gate[remember]checkboxnone
#wpst_user_passpasswordPasswordfor/id
#wpst_user_or_emailtextUsername or E-mailfor/id
#moove_gdpr_strict_cookiescheckboxEnable or Disable Cookiesnone
#moove_gdpr_performance_cookiescheckboxEnable or Disable Cookiesnone
#moove_gdpr_advanced_cookiescheckboxEnable or Disable Cookiesnone
wpst_user_logintext(none)none
#searchsubmitsubmit(none)none
#stext(none)none

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

<input type="text" name="s" id="s">; <input type="submit" id="searchsubmit">; <input type="text" name="wpst_user_login">

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
Form Input Quality
2 input-semantic issue(s) across 9 form control(s)
REVIEW
2 input-semantic issue(s) across 9 form control(s)
Info::
1 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="wpst_user_pass">.
Info::
2 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text" name="wpst_user_login">, <input type="text" name="wpst_user_or_email">.
B
Iframe Accessibility
3/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://cdn.creativesumo.com/html/c/8/c83162daf2754a01e3fc482819db0ec3.html")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://atwmcd.com/natlf/lf/ch/?c=object_container&site=fetishfix&cobrandId=&ps…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
h1 Fetish Adult Porn | We Feed your Fetish!
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Newest
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Login to Fetish4All.com
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Reset Password
1.29:1
#000000
on
#202020
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Fetish Adult Porn | …1.29:13.0:1
#000000
#202020
Fail
h2 Newest1.29:13.0:1
#000000
#202020
Fail
h3 Channels21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Login to Fetish4All.…1.29:13.0:1
#000000
#202020
Fail
h3 Reset Password1.29:13.0:1
#000000
#202020
Fail
title Fetish4All.com - Fet…19.26:14.5:1
#000000
#F5F5F5
Pass
a Skip to content19.26:14.5:1
#000000
#F5F5F5
Pass
p Feed your Fetish!17.62:14.5:1
#000000
#EBEBEB
Pass
a Home15.46:14.5:1
#000000
#DDDDDD
Pass
a LegalPorno Daily Upd…15.46:14.5:1
#000000
#DDDDDD
Pass
a PissVids15.46:14.5:1
#000000
#DDDDDD
Pass
a AnalVids15.46:14.5:1
#000000
#DDDDDD
Pass
a Live FetishCam21.00:14.5:1
#000000
#FFFFFF
Pass
a Hankey’s Toys21.00:14.5:1
#000000
#FFFFFF
Pass
a Gay21.00:14.5:1
#000000
#FFFFFF
Pass
a Channels21.00:14.5:1
#000000
#FFFFFF
Pass
a Tags21.00:14.5:1
#000000
#FFFFFF
Pass
a Newest21.00:14.5:1
#000000
#FFFFFF
Pass
a Best21.00:14.5:1
#000000
#FFFFFF
Pass
a Most viewed21.00:14.5: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.

B
Lighthouse Accessibility Audits
Score 81/100 — 5 failing, 22 passed
REVIEW
81

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
This is an adult website Are you over 18 years of age? No Yes Remember me Th… body.home > div.age-gate__wrapper > div.age-gate

These are opportunities to improve the usage of ARIA in your application which 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
The best Adult Fetish porn videos are right here at Fetisk4All.com. Click here … div#primary > main#main > div.archive-content > p.homepage-description

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#page > div.happy-header-mobile > a > iframe.lazyloaded div#page > div.happy-header-mobile > a > iframe.lazyloaded
body.home > iframe.chatHeadFrame--U2eof body.home > iframe.chatHeadFrame--U2eof

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
body.home > div#page > div.happy-header-mobile > a body.home > div#page > div.happy-header-mobile > 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.

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

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>`
●`[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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●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
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○`<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
○Links are distinguishable without relying on color.
○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.
○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
Landmark Structure
55 landmarks
PASS
55 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE "GDPR Cookie Banner" CONTENTINFO footer

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.

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
6 headings
PASS
6 headings
Info::
Single H1 present
  • H3 Channels
  • H1 Fetish Adult Porn | We Feed your Fetish!
  • H2 Newest
  • H2 This is an adult website
  • H3 Login to Fetish4All.com
  • H3 Reset Password
A+
Heading Text Quality
All 6 heading(s) have substantive, well-formed text
PASS
All 6 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
All 58 images OK
PASS
All 58 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
55 image(s) with good alt text
58 images 55 good alt text
IssueCount
too long3 image(s)
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 "wpst_user_or_email" should use type="email" (currently type="text")
Field name "wpst_user_or_email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
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 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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 156 visible text node(s) render at >= 12 CSS pixels
PASS
All 156 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback