Skip to content
https://xvideos.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
F
Alt Text Quality
Action
44 of 46 images have issues
FIX
44 of 46 images have issues
Critical::
44 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
44 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 image(s) with good alt text
46 images 2 good alt text 44 missing
IssueCount
missing44 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #000000
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 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.

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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
D
Lighthouse Accessibility Audits
Action
Score 68/100 — 4 failing, 12 passed
FIX
68

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.head__top > header.head__top__container > div#header-mobile-right > button.head__btn div.head__top > header.head__top__container > div#header-mobile-right > button.head__btn

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.thumb-inside > div.thumb > a > img#pic_89723530 div.thumb-inside > div.thumb > a > img#pic_89723530
div.thumb-inside > div.thumb > a > img#pic_89888959 div.thumb-inside > div.thumb > a > img#pic_89888959
div.thumb-inside > div.thumb > a > img#pic_89927329 div.thumb-inside > div.thumb > a > img#pic_89927329
div.thumb-inside > div.thumb > a > img#pic_89877430 div.thumb-inside > div.thumb > a > img#pic_89877430
div.thumb-inside > div.thumb > a > img#pic_88747639 div.thumb-inside > div.thumb > a > img#pic_88747639
div.thumb-inside > div.thumb > a > img#pic_89899999 div.thumb-inside > div.thumb > a > img#pic_89899999
div.thumb-inside > div.thumb > a > img#pic_89719411 div.thumb-inside > div.thumb > a > img#pic_89719411
div.thumb-inside > div.thumb > a > img#pic_89913931 div.thumb-inside > div.thumb > a > img#pic_89913931
div.thumb-inside > div.thumb > a > img#pic_89905438 div.thumb-inside > div.thumb > a > img#pic_89905438
div.thumb-inside > div.thumb > a > img#pic_89902486 div.thumb-inside > div.thumb > a > img#pic_89902486
div.thumb-inside > div.thumb > a > img#pic_34681429 div.thumb-inside > div.thumb > a > img#pic_34681429
div.thumb-inside > div.thumb > a > img#pic_89710573 div.thumb-inside > div.thumb > a > img#pic_89710573
div.thumb-inside > div.thumb > a > img#pic_89734840 div.thumb-inside > div.thumb > a > img#pic_89734840
div.thumb-inside > div.thumb > a > img#pic_89841415 div.thumb-inside > div.thumb > a > img#pic_89841415
div.thumb-inside > div.thumb > a > img#pic_89884345 div.thumb-inside > div.thumb > a > img#pic_89884345
div.thumb-inside > div.thumb > a > img#pic_89909995 div.thumb-inside > div.thumb > a > img#pic_89909995
div.thumb-inside > div.thumb > a > img#pic_89762488 div.thumb-inside > div.thumb > a > img#pic_89762488
div.thumb-inside > div.thumb > a > img#pic_85994615 div.thumb-inside > div.thumb > a > img#pic_85994615
div.thumb-inside > div.thumb > a > img#pic_71318283 div.thumb-inside > div.thumb > a > img#pic_71318283
div.thumb-inside > div.thumb > a > img#pic_65828569 div.thumb-inside > div.thumb > a > img#pic_65828569
div.thumb-inside > div.thumb > a > img#pic_86729461 div.thumb-inside > div.thumb > a > img#pic_86729461
div.thumb-inside > div.thumb > a > img#pic_89636146 div.thumb-inside > div.thumb > a > img#pic_89636146
div.thumb-inside > div.thumb > a > img#pic_89828437 div.thumb-inside > div.thumb > a > img#pic_89828437
div.thumb-inside > div.thumb > a > img#pic_89888059 div.thumb-inside > div.thumb > a > img#pic_89888059
div.thumb-inside > div.thumb > a > img#pic_68868263 div.thumb-inside > div.thumb > a > img#pic_68868263
div.thumb-inside > div.thumb > a > img#pic_89918002 div.thumb-inside > div.thumb > a > img#pic_89918002
div.thumb-inside > div.thumb > a > img#pic_42383611 div.thumb-inside > div.thumb > a > img#pic_42383611
div.thumb-inside > div.thumb > a > img#pic_56165727 div.thumb-inside > div.thumb > a > img#pic_56165727
div.thumb-inside > div.thumb > a > img#pic_36047417 div.thumb-inside > div.thumb > a > img#pic_36047417
div.thumb-inside > div.thumb > a > img#pic_35463861 div.thumb-inside > div.thumb > a > img#pic_35463861
div.thumb-inside > div.thumb > a > img#pic_76852073 div.thumb-inside > div.thumb > a > img#pic_76852073
div.thumb-inside > div.thumb > a > img#pic_89911264 div.thumb-inside > div.thumb > a > img#pic_89911264
div.thumb-inside > div.thumb > a > img#pic_78399597 div.thumb-inside > div.thumb > a > img#pic_78399597
div.thumb-inside > div.thumb > a > img#pic_89876938 div.thumb-inside > div.thumb > a > img#pic_89876938
div.thumb-inside > div.thumb > a > img#pic_89931214 div.thumb-inside > div.thumb > a > img#pic_89931214
div.thumb-inside > div.thumb > a > img#pic_82584883 div.thumb-inside > div.thumb > a > img#pic_82584883
div.thumb-inside > div.thumb > a > img#pic_48298474 div.thumb-inside > div.thumb > a > img#pic_48298474
div.thumb-inside > div.thumb > a > img#pic_79884839 div.thumb-inside > div.thumb > a > img#pic_79884839
div.thumb-inside > div.thumb > a > img#pic_89620849 div.thumb-inside > div.thumb > a > img#pic_89620849
div.thumb-inside > div.thumb > a > img#pic_89756929 div.thumb-inside > div.thumb > a > img#pic_89756929
div.thumb-inside > div.thumb > a > img#pic_74053689 div.thumb-inside > div.thumb > a > img#pic_74053689
div.thumb-inside > div.thumb > a > img#pic_89907190 div.thumb-inside > div.thumb > a > img#pic_89907190
div.thumb-inside > div.thumb > a > img#pic_89237749 div.thumb-inside > div.thumb > a > img#pic_89237749
div.thumb-inside > div.thumb > a > img#pic_28897277 div.thumb-inside > div.thumb > a > img#pic_28897277

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
div#video_hbleffdf6e7 > div.thumb-inside > div.thumb > a div#video_hbleffdf6e7 > div.thumb-inside > div.thumb > a
div.pagination > ul > li > a.no-page div.pagination > ul > li > a.no-page

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-hidden="true"]` is not present on the document `<body>`
Form elements have associated labels
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.
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.
Document has a main landmark.
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
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
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
Heading elements appear in a sequentially-descending order
`<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
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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 header NAV "primary" MAIN (missing!) 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

B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="k">; <input type="text" name="k">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
ktext(Search X videos)placeholder only
ktext(Search X videos)placeholder only

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

<input type="text" name="k">; <input type="text" name="k">

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

C
Mobile-Readable Font Sizes
Action
82% of visible text renders at >= 12 CSS px (46 below threshold)
REVIEW
82% of visible text renders at >= 12 CSS px (46 below threshold)
Warning::
46 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: <button> 0.0px ("Language:"); <span> 10.8px ("14 min"); <span> 10.8px ("9 min"); <span> 10.8px ("10 min"); <span> 10.8px ("8 min").
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 Not found - XVIDEOS.COM Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 12 pass AA only
span adults only
2.61:1
#DE2600
on
#BFBFBF
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title Free Porn Videos - X…11.42:14.5:1
#000000
#BFBFBF
Pass
span WARNING this site is…11.42:14.5:1
#000000
#BFBFBF
Pass
span adults only2.61:14.5:1
#DE2600
#BFBFBF
Fail
p By entering this web…11.42:14.5:1
#000000
#BFBFBF
Pass
a here11.42:14.5:1
#000000
#BFBFBF
Pass
span Straight11.42:14.5:1
#000000
#BFBFBF
Pass
span Gay9.04:14.5:1
#000000
#AAAAAA
Pass
span Trans6.25:14.5:1
#000000
#8C8C8C
Pass
span Enter6.25:14.5:1
#000000
#8C8C8C
Pass
span I am 18 years old or…6.25:14.5:1
#000000
#8C8C8C
Pass
span Parents read this to…6.25:14.5:1
#000000
#8C8C8C
Pass
button Language:6.25:14.5:1
#000000
#8C8C8C
Pass
span Your location6.25:14.5:1
#000000
#8C8C8C
Pass
span Spain6.25:14.5:1
#000000
#8C8C8C
Pass
span Straight6.25:14.5:1
#000000
#8C8C8C
Pass
span Login6.25:14.5:1
#000000
#8C8C8C
Pass
span Join for FREE6.25:14.5:1
#000000
#8C8C8C
Pass
span Premium6.25:14.5:1
#000000
#8C8C8C
Pass
span Best Videos6.58:14.5:1
#000000
#909090
Pass
span Categories10.82:14.5:1
#000000
#BABABA
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.

A+
Heading Text Quality
No headings to evaluate -- check is N/A
PASS
No headings to evaluate -- check is N/A
Info::
No headings to evaluate -- check is N/A
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "k" should use type="search" (currently type="text")
Field name "k" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "k" should use type="search" (currently type="text")
Field name "k" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
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
Favicon & Branding
7 icon(s) detected
PASS
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Present
Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: XVideos
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name XVideos 192×192 icon 512×512 icon Start URL https://www.xvideos.com Display Mode standalone
Name XVideos Display Mode standalone Theme Color #000000 Background Color #000000 Icons 2 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
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.
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback