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 2 REVIEW 6 FIX

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

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

No <nav> landmark 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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h2 Backstage

1.16:1

#000000

#20130D

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h2 VERIFY

1.70:1

#000000

#363434

needs 3.0:1 (large text)

24px · bottom of viewport

h2 VERIFY

1.67:1

#000000

#343333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 VERIFY

1.67:1

#000000

#343333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 VERIFY

1.67:1

#000000

#343333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 VERIFY

1.67:1

#000000

#343333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 VERIFY

1.67:1

#000000

#343333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 VERIFY

1.67:1

#000000

#343333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 VERIFY

1.67:1

#000000

#343333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 VERIFY

1.67:1

#000000

#343333

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Performers

1.67:1

#000000

#343333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Vlog Videos

1.67:1

#000000

#343333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Download

1.67:1

#000000

#343333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Streaming

1.67:1

#000000

#343333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Exclusive

1.67:1

#000000

#343333

needs 3.0:1 (large text)

19px · bottom of viewport

title Vlog - Verify you are an adult to remove…

1.22:1

#000000

#1B1B1B

needs 4.5:1 (normal text)

16px · top of page (header area)

p This site uses cookies that are necessar…

1.22:1

#000000

#1B1B1B

needs 4.5:1 (normal text)

16px · top of page (header area)

a Privacy policy

1.22:1

#000000

#1B1B1B

needs 4.5:1 (normal text)

16px · top of page (header area)

p to learn more.

1.16:1

#000000

#161616

needs 4.5:1 (normal text)

16px · top of page (header area)

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 The Scenes Footage	6.62:1	3.0:1	#000000	#AA8983	Pass
h2 Backstage	1.16:1	3.0:1	#000000	#20130D	Fail
h2 VERIFY	1.70:1	3.0:1	#000000	#363434	Fail
h2 VERIFY	1.67:1	3.0:1	#000000	#343333	Fail
h2 VERIFY	1.67:1	3.0:1	#000000	#343333	Fail
h2 VERIFY	1.67:1	3.0:1	#000000	#343333	Fail
h2 VERIFY	1.67:1	3.0:1	#000000	#343333	Fail
h2 VERIFY	1.67:1	3.0:1	#000000	#343333	Fail
h2 VERIFY	1.67:1	3.0:1	#000000	#343333	Fail
h2 VERIFY	1.67:1	3.0:1	#000000	#343333	Fail
h2 VERIFY	1.67:1	3.0:1	#000000	#343333	Fail
h3 Performers	1.67:1	3.0:1	#000000	#343333	Fail
h3 Vlog Videos	1.67:1	3.0:1	#000000	#343333	Fail
h3 Download	1.67:1	3.0:1	#000000	#343333	Fail
h3 Streaming	1.67:1	3.0:1	#000000	#343333	Fail
h3 Exclusive	1.67:1	3.0:1	#000000	#343333	Fail
title Vlog - Verify you ar…	1.22:1	4.5:1	#000000	#1B1B1B	Fail
p This site uses cooki…	1.22:1	4.5:1	#000000	#1B1B1B	Fail
a Privacy policy	1.22:1	4.5:1	#000000	#1B1B1B	Fail
p to learn more.	1.16:1	4.5:1	#000000	#161616	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

16 headings

PASS

16 headings

Single H1 present

H1 Behind The Scenes Footage
H2 Backstage
H2 VERIFY
H2 VERIFY
H2 VERIFY
H2 VERIFY
H2 VERIFY
H2 VERIFY
H3 Trending Performers
H3 Top BTS Vlog Videos
H2 VERIFY
H2 VERIFY
H2 VERIFY
H3 Download
H3 Streaming
H3 Exclusive

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

9 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: 9 all-caps heading(s)

A+

Alt Text Quality

All 41 images OK

PASS

All 41 images OK

41 image(s) with good alt text

41 images 41 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

82 links, 2 buttons — all OK

PASS

82 links, 2 buttons — all OK

11 link(s) open in new tab without warning

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

Got: /includes/privacy.php; /includes/privacy.php; https://www.vlogxxx.com/pages.php?id=dmca; https://www.vlogxxx.com/pages.php?id=legal-notices; https://support.spizoo.com/contentremoval/form.php?site=vlogxxx; https://www.vlogxxx.com/pages.php?id=privacy-policy; https://www.vlogxxx.com/pages.php?id=custodian-of-records; https://support.spizoo.com/; https://join.vlogxxx.com/signup/cancelplus.php; https://cs.segpay.com/ (+1 more)

71 link(s) with descriptive text

82 links

0 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/includes/privacy.php	Privacy policy	new tab	Add '(opens in new tab)' to text
/includes/privacy.php	Privacy policy	new tab	Add '(opens in new tab)' to text
https://www.vlogxxx.com/pages.php?id=dmc…	DMCA	new tab	Add '(opens in new tab)' to text
https://www.vlogxxx.com/pages.php?id=leg…	Terms And Conditions	new tab	Add '(opens in new tab)' to text
https://support.spizoo.com/contentremova…	Content Removal	new tab	Add '(opens in new tab)' to text
https://www.vlogxxx.com/pages.php?id=pri…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.vlogxxx.com/pages.php?id=cus…	USC 2257 Record Keeping Requir…	new tab	Add '(opens in new tab)' to text
https://support.spizoo.com/	SUPPORT	new tab	Add '(opens in new tab)' to text
https://join.vlogxxx.com/signup/cancelpl…	RocketGate	new tab	Add '(opens in new tab)' to text
https://cs.segpay.com/	SegPay	new tab	Add '(opens in new tab)' to text
https://support.spizoo.com/	Contact Us	new tab	Add '(opens in new tab)' to text

73 links and buttons have descriptive text

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

/includes/privacy.php; /includes/privacy.php; https://www.vlogxxx.com/pages.php?id=dmca; https://www.vlogxxx.com/pages.php?id=legal-notices; https://support.spizoo.com/contentremoval/form.php?site=vlogxxx; https://www.vlogxxx.com/pages.php?id=privacy-policy; https://www.vlogxxx.com/pages.php?id=custodian-of-records; https://support.spizoo.com/; https://join.vlogxxx.com/signup/cancelplus.php; https://cs.segpay.com/ (+1 more)

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

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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 95 visible text node(s) render at >= 12 CSS pixels

PASS

All 95 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

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.

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 17 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
Accept Cookies `body > div#cookie-popup > div.cookie-btns > button#accept-cookies`
WATCH NOW ALL BTS VLOG VIDEOS `section#presentation > div.gallery-section > div.container > a.link-full-width`
WATCH NOW ALL BTS VLOG VIDEOS `body > div.container > section.acclaimed-series > a.link-full-width`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BTS VLOG `div.big-banner > div.content-part > div.info-banner > a.get-access`
WATCH NOW ALL BTS VLOG VIDEOS `section#presentation > div.gallery-section > div.container > a.link-full-width`
Savannah Bond `section.pornstars > div.pornstars-pics > div > a.model-img`
Kylie Rocket `section.pornstars > div.pornstars-pics > div > a.model-img`
Kali Roses `section.pornstars > div.pornstars-pics > div > a.model-img`
Kayley Gunner `section.pornstars > div.pornstars-pics > div > a.model-img`
Emma Rosie `section.pornstars > div.pornstars-pics > div > a.model-img`
Jennifer White `section.pornstars > div.pornstars-pics > div > a.model-img`
Lumi Ray `section.pornstars > div.pornstars-pics > div > a.model-img`
Xxlayna Marie `section.pornstars > div.pornstars-pics > div > a.model-img`
WATCH NOW ALL BTS VLOG VIDEOS `body > div.container > section.acclaimed-series > a.link-full-width`
PRIVACY POLICY `div.footer-content > div.footer-middle > p > a`

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

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

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

●Buttons have an accessible name

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

●ARIA attributes are used as specified for the element's role

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

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

○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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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