Skip to content
https://pornhub.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
7
REVIEW
8
PASS
9
INFO
0
Checks
24
9 PASS 8 REVIEW 7 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
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 header MAIN (missing!) ASIDE 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

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

F
Alt Text Quality
Action
5 of 153 images have issues
FIX
5 of 153 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
5 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
146 image(s) with good alt text
153 images 146 good alt text 1 decorative 5 missing
IssueCount
missing5 image(s)
too long1 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
Mobile-Readable Font Sizes
Action
69% of visible text renders at >= 12 CSS px (8 below threshold)
FIX
69% of visible text renders at >= 12 CSS px (8 below threshold)
Warning::
8 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: <a> 11.0px ("Spicevids"); <a> 11.0px ("Fancentro"); <a> 11.0px ("Sexual wellness"); <a> 11.0px ("Insights"); <span> 11.0px ("sites").
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::
Hamburger menu detected (responsive design)
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
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.
C
Heading Hierarchy
Action
20 headings, 1 skip(s)
REVIEW
20 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
4 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 (empty)
  • H3 This is an adult website
  • H5 A text message with your code has been sent to: skipped
  • H5 An email with the verification code has been sent to:
  • H5 Use the 6 digit code sent to your two-factor authentication app
  • H5 (empty)
  • H5 (empty)
  • H3 Orientation
  • H3 Most popular
  • H3 Popular Searches
  • H2 Free 7 day premium access
  • H2 Watch this exclusive video only on pornhub premium.
  • H2 You will never see ads again!
  • H2 Watch this 1080p video only on pornhub premium.
  • H2 By upgrading today, you get one week free access
  • H2 By signing up today, you get one week free access
  • H1 Hot Porn Videos
  • H2 (empty)
  • H3 This website is only intended for users over the age of 18.
  • H2 Payment Method

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
Form Accessibility
2 of 7 controls have issues
REVIEW
2 of 7 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="email" id="usernameModal">; <input type="password" name="password" id="passwordModal">
Info::
5 control(s) properly labeled
7 controls
5 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#enterVerificationCodenumberEnter the codefor/id
#recommendSwitchcheckboxOnOfffor/id
#searchInputtextnone
#languageMenuselectEnglishnone
#locationMenuselectUnited Statesnone
#passwordModalpassword(Password)placeholder only
#usernameModaltext(Email)placeholder only

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

<input type="text" name="email" id="usernameModal">; <input type="password" name="password" id="passwordModal">

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

B
Form Input Quality
2 input-semantic issue(s) across 7 form control(s)
REVIEW
2 input-semantic issue(s) across 7 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="password">.
Info::
1 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="email">.
C
Mobile Keyboard & Autofill
Action
2/3 eligible field(s) missing autocomplete or inputmode
REVIEW
2/3 eligible field(s) missing autocomplete or inputmode
Warning::
2 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, current-password.
Got: <input type="text" name="email" id="usernameModal">, <input type="password" name="password" id="passwordModal">
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
100 icon(s) detected
REVIEW
100 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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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
h1 Hot Porn Videos
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Free 7 day
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 premium
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 access
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Watch this exclusive
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 video only on
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 pornhub premium.
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 You will never
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 see ads again!
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Watch this 1080p
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 video only on
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 pornhub premium.
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By upgrading today,
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 you get one week
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 free access
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By signing up today,
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 you get one week
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 free access
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Payment Method
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 This is an adult website
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Hot Porn Videos1.00:13.0:1
#000000
#000000
Fail
h2 Free 7 day1.00:13.0:1
#000000
#000000
Fail
h2 premium1.00:13.0:1
#000000
#000000
Fail
h2 access1.00:13.0:1
#000000
#000000
Fail
h2 Watch this exclusive1.00:13.0:1
#000000
#000000
Fail
h2 video only on1.00:13.0:1
#000000
#000000
Fail
h2 pornhub premium.1.00:13.0:1
#000000
#000000
Fail
h2 You will never1.00:13.0:1
#000000
#000000
Fail
h2 see ads again!1.00:13.0:1
#000000
#000000
Fail
h2 Watch this 1080p1.00:13.0:1
#000000
#000000
Fail
h2 video only on1.00:13.0:1
#000000
#000000
Fail
h2 pornhub premium.1.00:13.0:1
#000000
#000000
Fail
h2 By upgrading today,1.00:13.0:1
#000000
#000000
Fail
h2 you get one week1.00:13.0:1
#000000
#000000
Fail
h2 free access1.00:13.0:1
#000000
#000000
Fail
h2 By signing up today,1.00:13.0:1
#000000
#000000
Fail
h2 you get one week1.00:13.0:1
#000000
#000000
Fail
h2 free access1.00:13.0:1
#000000
#000000
Fail
h2 Payment Method1.00:13.0:1
#000000
#000000
Fail
h3 This is an adult web…1.00:13.0:1
#000000
#000000
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 25 passed
REVIEW
78

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.globalCookieBanner > div.globalCookieBanner__wrapper > div.globalCookieBanner__content > button.globalCookieBanner__close div.globalCookieBanner > div.globalCookieBanner__wrapper > div.globalCookieBanner__content > button.globalCookieBanner__close
ul.videoList > div#shortiesListSection > div#expandableSectionBtn > button.js-shorties-expand-btn ul.videoList > div#shortiesListSection > div#expandableSectionBtn > button.js-shorties-expand-btn

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
body.logged-out > div#mobileContainer > div.r69xkycaamkqowg4aa > iframe body.logged-out > div#mobileContainer > div.r69xkycaamkqowg4aa > iframe
li.r69xkycaamkqowg4 > div.positionRelative > div > iframe li.r69xkycaamkqowg4 > div.positionRelative > div > iframe
div#singleFeedSection > ul.videoList > div.r69xkycaamkqowg4aa > iframe div#singleFeedSection > ul.videoList > div.r69xkycaamkqowg4aa > iframe
li.r69xkycaamkqowg4 > div.positionRelative > div > iframe li.r69xkycaamkqowg4 > div.positionRelative > div > iframe
div#mobileContainer > div#singleFeedSection > div.r69xkycaamkqowg4aa > iframe div#mobileContainer > div#singleFeedSection > div.r69xkycaamkqowg4aa > iframe

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
parental controls page div.contentMTubes > p.bottomText > p > a

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
7:58 AthenaSexy18 77.5K He Fucked Me While I Was Brushing My Teeth! ES 17:36 … body.logged-out > div#mobileContainer > div#singleFeedSection > ul.videoList
ES 11:56 Luchibbok 233K TBT DOS PETITES NINFOMANAS ft cofla24 / bootywhite 25… body.logged-out > div#mobileContainer > div#singleFeedSection > ul.videoList

These are opportunities to improve the experience of reading tabular or list data using 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.

Internationalization and localization

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.linkGroup > li > div.footerInfoContent > a.infoAnchor ul.linkGroup > li > div.footerInfoContent > a.infoAnchor
ul.linkGroup > li > div.footerInfoContent > a.infoAnchor ul.linkGroup > li > div.footerInfoContent > a.infoAnchor

These are opportunities to improve the interpretation of your content by users in different locales.

○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
●Image elements have `[alt]` attributes
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●ARIA input fields have accessible names
●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 have a discernible name
●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
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○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.
A+
Heading Text Quality
All 20 heading(s) have substantive, well-formed text
PASS
All 20 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
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 "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "search" should use type="search" (currently type="text")
Field name "search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
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
86 explicit tabindex attribute(s) checked, no anti-patterns
PASS
86 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Pornhub
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Pornhub ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa_app ✓Display Mode standalone ✓
Name Pornhub Display Mode standalone Theme Color #FF9900 Background Color #000000 Icons 98 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
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