Skip to content
https://brazzers.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="email" id="email">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="email" id="email">
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
5 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 5 <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.
B
Heading Hierarchy
3 headings
REVIEW
3 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 LATEST BRAZZERS VIDEOS
  • H2 TRENDING VIDEOS
  • H2 MOST POPULAR BRAZZERS VIDEOS

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Mobile-Readable Font Sizes
Action
88% of visible text renders at >= 12 CSS px (27 below threshold)
REVIEW
88% of visible text renders at >= 12 CSS px (27 below threshold)
Warning::
27 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: <div> 8.0px ("Credit Card"); <div> 8.0px ("PayPal"); <div> 8.0px ("Gift cards"); <div> 8.0px ("Crypto Currency"); <div> 10.0px ("Billed in one payment of $121.99").
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 Page Not Found | Brazzers ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
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
h2 LATEST BRAZZERS VIDEOS
1.23:1
#000000
on
#211B18
needs 3.0:1 (large text)
24px · above the fold
h2 TRENDING VIDEOS
1.25:1
#000000
on
#221C1A
needs 3.0:1 (large text)
24px · mid-page
h2 MOST POPULAR BRAZZERS VIDEOS
1.77:1
#000000
on
#383737
needs 3.0:1 (large text)
24px · bottom of viewport
title Brazzers.com | Hot and Sexy Exclusive Po…
1.25:1
#000000
on
#1F1E11
needs 4.5:1 (normal text)
16px · top of page (header area)
label Hamburger menu open
1.25:1
#000000
on
#1F1E12
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a LOGIN
1.26:1
#000000
on
#201E12
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a JOIN NOW
1.26:1
#000000
on
#201E13
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span PORN VIDEOS
1.26:1
#000000
on
#211E15
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span PORNSTARS
1.26:1
#000000
on
#211E16
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span CATEGORIES
1.28:1
#000000
on
#221F18
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span EXTRAS
1.28:1
#000000
on
#221F19
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a CHANNELS
1.27:1
#000000
on
#221E19
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span SEARCH
1.27:1
#000000
on
#221E19
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a LOGIN
1.26:1
#000000
on
#221D19
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a JOIN NOW
1.24:1
#000000
on
#211C19
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a View all
1.23:1
#000000
on
#211B18
needs 4.5:1 (normal text)
16px · mid-page
a View all
1.28:1
#000000
on
#251E1C
needs 4.5:1 (normal text)
16px · mid-page
div Choose Your Membership Type
1.33:1
#000000
on
#28211F
needs 4.5:1 (normal text)
16px · mid-page
div Use your unused gift card
1.38:1
#000000
on
#2B2423
needs 4.5:1 (normal text)
16px · mid-page
div Where applicable, sales tax may be added…
1.45:1
#000000
on
#2E2827
needs 4.5:1 (normal text)
16px · mid-page

11 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)
ElementRatioRequiredFGBGResult
h2 LATEST BRAZZERS VIDE…1.23:13.0:1
#000000
#211B18
Fail
h2 TRENDING VIDEOS1.25:13.0:1
#000000
#221C1A
Fail
h2 MOST POPULAR BRAZZER…1.77:13.0:1
#000000
#383737
Fail
title Brazzers.com | Hot a…1.25:14.5:1
#000000
#1F1E11
Fail
label Hamburger menu open1.25:14.5:1
#000000
#1F1E12
Fail
a LOGIN1.26:14.5:1
#000000
#201E12
Fail
a JOIN NOW1.26:14.5:1
#000000
#201E13
Fail
span PORN VIDEOS1.26:14.5:1
#000000
#211E15
Fail
span PORNSTARS1.26:14.5:1
#000000
#211E16
Fail
span CATEGORIES1.28:14.5:1
#000000
#221F18
Fail
span EXTRAS1.28:14.5:1
#000000
#221F19
Fail
a CHANNELS1.27:14.5:1
#000000
#221E19
Fail
span SEARCH1.27:14.5:1
#000000
#221E19
Fail
a LOGIN1.26:14.5:1
#000000
#221D19
Fail
a JOIN NOW1.24:14.5:1
#000000
#211C19
Fail
a View all1.23:14.5:1
#000000
#211B18
Fail
a View all1.28:14.5:1
#000000
#251E1C
Fail
div Choose Your Membersh…1.33:14.5:1
#000000
#28211F
Fail
div Use your unused gift…1.38:14.5:1
#000000
#2B2423
Fail
div Where applicable, sa…1.45:14.5:1
#000000
#2E2827
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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 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: 3 all-caps heading(s)
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
11 image(s) with good alt text
11 images 11 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#emailemailEmailfor/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
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+
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
7 explicit tabindex attribute(s) checked, no anti-patterns
PASS
7 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
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.
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+
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.
A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 25 passed
PASS
91

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

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
This is an advertisement banner for Brazzers div.flickity-viewport > div.flickity-slider > div.sc-v5iir1-0 > 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.

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
PRIVACY NOTICE nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
SUPPORT nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
TERMS AND CONDITIONS nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
CANCELLATION POLICY nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
ACCESSIBILITY nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
ANTI-TRAFFICKING STATEMENT nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
AFFILIATE nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
PRIVACY NOTICE nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
SUPPORT nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
TERMS AND CONDITIONS nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
ACCESSIBILITY nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
ANTI-TRAFFICKING STATEMENT nav.sc-13v34sz-0 > ul.sc-13v34sz-1 > li.sc-13v34sz-2 > a.sc-13v34sz-3
here div.sc-c12nx1-0 > div.sc-qq931q-0 > p.sc-hq7nt5-0 > a
Vendo div.sc-c12nx1-0 > div.sc-qq931q-0 > p.sc-hq7nt5-0 > a
LOGIN div.sc-y3rqay-0 > div.sc-1dhvf0w-0 > div.sc-1dhvf0w-1 > a.sc-3byr16-0
TERMS AND CONDITIONS div.sc-y3rqay-1 > div.sc-1eyb95j-0 > p.sc-1eyb95j-1 > a
Exit div.sc-y3rqay-0 > div.sc-y3rqay-1 > div.sc-rkkkdv-0 > a.sc-3byr16-0
○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
●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
●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
●No element has a `[tabindex]` value greater than 0
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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.
○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.
○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.
○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.

Send Feedback