Skip to content
https://porncgw.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
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 ✗
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.
C
Tap Target Adequacy
Action
8 tap target(s) too small or too close together
REVIEW
8 tap target(s) too small or too close together
Warning::
8 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Mobile-Readable Font Sizes
Action
73% of visible text renders at >= 12 CSS px (29 below threshold)
REVIEW
73% of visible text renders at >= 12 CSS px (29 below threshold)
Warning::
29 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: <span> 11.0px ("发现最新内容"); <span> 11.0px ("为你精选推荐"); <span> 11.0px ("今日最新爆料"); <span> 11.0px ("为你精选推荐"); <span> 11.0px ("登录后查看更多").
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 porn吃瓜网 - 明星网红吃瓜爆料…
1.06:1
#000000
on
#0A0A0B
needs 3.0:1 (large text)
32px · bottom of viewport
title porn吃瓜网 - 吃瓜爆料·国产原…
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · top of page (header area)
a 跳过导航
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · top of page (header area)
span 导航
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · top of page (header area)
span porn吃瓜网
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · top of page (header area)
div 搜索
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · above the fold
label 搜索吃瓜内容
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · above the fold
button 搜索
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · above the fold
strong 搜索历史
1.06:1
#000000
on
#0A0A0B
needs 3.0:1 (large text)
16px · above the fold
button 清空
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · above the fold
span 热门搜索
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · above the fold
span 素人真实
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · above the fold
span HOT
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · above the fold
span 抖音擦边
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · above the fold
span HOT
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · mid-page
span 高颜值美女
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · mid-page
span 眼镜妹
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · mid-page
span 巨乳美女
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · mid-page
div 热门标签
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · mid-page
a #素人真实
1.06:1
#000000
on
#0A0A0B
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 porn吃瓜网 - 明…1.06:13.0:1
#000000
#0A0A0B
Fail
title porn吃瓜网 - 吃…1.06:14.5:1
#000000
#0A0A0B
Fail
a 跳过导航1.06:14.5:1
#000000
#0A0A0B
Fail
span 导航1.06:14.5:1
#000000
#0A0A0B
Fail
span porn吃瓜网1.06:14.5:1
#000000
#0A0A0B
Fail
div 搜索1.06:14.5:1
#000000
#0A0A0B
Fail
label 搜索吃瓜内容1.06:14.5:1
#000000
#0A0A0B
Fail
button 搜索1.06:14.5:1
#000000
#0A0A0B
Fail
strong 搜索历史1.06:13.0:1
#000000
#0A0A0B
Fail
button 清空1.06:14.5:1
#000000
#0A0A0B
Fail
span 热门搜索1.06:14.5:1
#000000
#0A0A0B
Fail
span 素人真实1.06:14.5:1
#000000
#0A0A0B
Fail
span HOT1.06:14.5:1
#000000
#0A0A0B
Fail
span 抖音擦边1.06:14.5:1
#000000
#0A0A0B
Fail
span HOT1.06:14.5:1
#000000
#0A0A0B
Fail
span 高颜值美女1.06:14.5:1
#000000
#0A0A0B
Fail
span 眼镜妹1.06:14.5:1
#000000
#0A0A0B
Fail
span 巨乳美女1.06:14.5:1
#000000
#0A0A0B
Fail
div 热门标签1.06:14.5:1
#000000
#0A0A0B
Fail
a #素人真实1.06:14.5:1
#000000
#0A0A0B
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 5 failing, 21 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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
热门爆料 div.sidebar-inner > nav#sidebarNavList > div.v0-nav-group > div.v0-nav-parent-split
社会热点 div.sidebar-inner > nav#sidebarNavList > div.v0-nav-group > div.v0-nav-parent-split
热门短片 div.sidebar-inner > nav#sidebarNavList > div.v0-nav-group > div.v0-nav-parent-split
门事件 div.sidebar-inner > nav#sidebarNavList > div.v0-nav-group > div.v0-nav-parent-split
AI成人 div.sidebar-inner > nav#sidebarNavList > div.v0-nav-group > div.v0-nav-parent-split
长视频 div.sidebar-inner > nav#sidebarNavList > div.v0-nav-group > div.v0-nav-parent-split
吃瓜社区 div.sidebar-inner > nav#sidebarNavList > div.v0-nav-group > div.v0-nav-parent-split

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
首页 main#main-content > div.page-home > nav.mobile-top-nav > a.mobile-top-nav-item
深夜印刷厂 · 仅限成人 · 入夜后开启 footer#app-footer > div.app-footer-main > div.app-footer-brand > p
不可言说的真相 · 印刷于墨与火 footer#app-footer > div.app-footer-main > div.app-footer-brand > p

These are opportunities to improve the legibility of your content.

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
常见问题 div.app-footer-main > div.app-footer-links > nav.app-footer-col > a
内容移除 div.app-footer-main > div.app-footer-links > nav.app-footer-col > a
DMCA div.app-footer-main > div.app-footer-links > nav.app-footer-col > a
条款条件 div.app-footer-main > div.app-footer-links > nav.app-footer-col > a
隐私声明 div.app-footer-main > div.app-footer-links > nav.app-footer-col > a
2257 声明 div.app-footer-main > div.app-footer-links > nav.app-footer-col > a
回家方法 div.app-footer-main > div.app-footer-links > nav.app-footer-col > a
Telegram 频道 ↗ div.app-footer-main > div.app-footer-links > nav.app-footer-col > a.app-footer-tg

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
欧美女优重度中出女上位高潮尖叫勾人小妖精 3.4w播放·1天前 ul#videoGrid > li > article.card > a.card-link
至日庄园的罪孽 拉文内斯的隐秘渴望 2.8w播放·1天前 ul#videoGrid > li > article.card > a.card-link
航海王 曼麦亚军子宫事件引发全球震撼与热血追击 2.0w播放·1天前 ul#videoGrid > li > article.card > a.card-link
星铁黑天鹅深陷记忆漩涡 3.6w播放·1天前 ul#videoGrid > li > article.card > a.card-link
鸣潮长离龙本 2.9w播放·1天前 ul#videoGrid > li > article.card > a.card-link
恶魔高校姬岛朱乃莉雅丝吉蒙里与兵藤一诚的激情羁绊 7365播放·1天前 ul#videoGrid > li > article.card > a.card-link
夜场嗨吧厕所内男女集体厕所 真实经历分享 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
极品美女正妹自拍深喉偷拍现场高能刺激视觉盛宴 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
红唇酥胸细腰大长腿新马子 骑马秀大长腿现场画面火爆全网引爆热搜 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
黑渔网情趣内衣诱惑牛奶湿身水蛇腰 情趣诱惑激情瞬间爆发 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
极品美女正妹骑马视频 美女骑马时那股骚气冲天的诱惑模样 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
自拍偷拍 夫妻沙发激情被偷录的真实画面 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
韩国美女骑马视频 真实处女魅力让人心动不已 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
南航极品空姐刘佳妮制服asmr休息室甜蜜事件 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
情趣诱惑ktv夜店马来西亚小姐姐太放得开现场画面让人脸红心跳 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
马来西亚大学极品美女正妹###门事件视频意外流出引爆全网热议 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
大奶妹子女主播，粉色奶头好诱人，性感热舞清晰国语对白 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
极品可爱美女和男友大玩cosplay性爱啪啪啪 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
富二代的极品女友，极品身材，睡着了都被干醒 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
极品少妇自拍与男友啪啪足交自慰手交丝袜诱惑调教 热门播放·1天前 ul#videoGrid > li > article.card > a.card-link
○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>`
●`[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
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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.
○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.
A
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "主导航" MAIN ASIDE "分类导航" CONTENTINFO footer

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

A+
Heading Hierarchy
21 headings
PASS
21 headings
Info::
Single H1 present
  • H1 porn吃瓜网 - 明星网红吃瓜爆料视频在线看
  • H2 欧美女优重度中出女上位高潮尖叫勾人小妖精欧美女优重度中出女上位高潮尖叫勾人小妖精
  • H2 至日庄园的罪孽 拉文内斯的隐秘渴望至日庄园的罪孽 拉文内斯的隐秘渴望
  • H2 航海王 曼麦亚军子宫事件引发全球震撼与热血追击航海王 曼麦亚军子宫事件引发全球震撼与热血追击
  • H2 星铁黑天鹅深陷记忆漩涡星铁黑天鹅深陷记忆漩涡
  • H2 鸣潮长离龙本鸣潮长离龙本
  • H2 恶魔高校姬岛朱乃莉雅丝吉蒙里与兵藤一诚的激情羁绊恶魔高校姬岛朱乃莉雅丝吉蒙里与兵藤一诚的激情羁绊
  • H2 夜场嗨吧厕所内男女集体厕所 真实经历分享夜场嗨吧厕所内男女集体厕所 真实经历分享
  • H2 极品美女正妹自拍深喉偷拍现场高能刺激视觉盛宴极品美女正妹自拍深喉偷拍现场高能刺激视觉盛宴
  • H2 红唇酥胸细腰大长腿新马子 骑马秀大长腿现场画面火爆全网引爆热搜红唇酥胸细腰大长腿新马子 骑马秀大长腿现场画面火爆全网引爆热搜
  • H2 黑渔网情趣内衣诱惑牛奶湿身水蛇腰 情趣诱惑激情瞬间爆发黑渔网情趣内衣诱惑牛奶湿身水蛇腰 情趣诱惑激情瞬间爆发
  • H2 极品美女正妹骑马视频 美女骑马时那股骚气冲天的诱惑模样极品美女正妹骑马视频 美女骑马时那股骚气冲天的诱惑模样
  • H2 自拍偷拍 夫妻沙发激情被偷录的真实画面自拍偷拍 夫妻沙发激情被偷录的真实画面
  • H2 韩国美女骑马视频 真实处女魅力让人心动不已韩国美女骑马视频 真实处女魅力让人心动不已
  • H2 南航极品空姐刘佳妮制服asmr休息室甜蜜事件南航极品空姐刘佳妮制服asmr休息室甜蜜事件
  • H2 情趣诱惑ktv夜店马来西亚小姐姐太放得开现场画面让人脸红心跳情趣诱惑ktv夜店马来西亚小姐姐太放得开现场画面让人脸红心跳
  • H2 马来西亚大学极品美女正妹###门事件视频意外流出引爆全网热议马来西亚大学极品美女正妹###门事件视频意外流出引爆全网热议
  • H2 大奶妹子女主播，粉色奶头好诱人，性感热舞清晰国语对白大奶妹子女主播，粉色奶头好诱人，性感热舞清晰国语对白
  • H2 极品可爱美女和男友大玩cosplay性爱啪啪啪极品可爱美女和男友大玩cosplay性爱啪啪啪
  • H2 富二代的极品女友，极品身材，睡着了都被干醒富二代的极品女友，极品身材，睡着了都被干醒
  • H2 极品少妇自拍与男友啪啪足交自慰手交丝袜诱惑调教极品少妇自拍与男友啪啪足交自慰手交丝袜诱惑调教
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
17 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: 17 all-caps heading(s)
A+
Alt Text Quality
All 58 images OK
PASS
All 58 images OK
Info::
38 decorative image(s) correctly marked
Info::
20 image(s) with good alt text
58 images 20 good alt text 38 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchInputsearch搜索吃瓜内容for/id
#login-emailtext账号none
#login-passwordpassword密码none
#register-emailtext账号none
#register-passwordpassword密码none
#register-confirm-passwordpassword确认密码none
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 "login-email" should use type="email" (currently type="text")
Field name "login-email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "register-email" should use type="email" (currently type="text")
Field name "register-email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A
Form Input Quality
1 input-semantic issue(s) across 6 form control(s)
PASS
1 input-semantic issue(s) across 6 form control(s)
Info::
3 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" id="login-password">, <input type="password" id="register-password">, <input type="password" id="register-confirm-password">.
A+
Mobile Keyboard & Autofill
All 4 eligible field(s) carry autocomplete/inputmode
PASS
All 4 eligible field(s) carry autocomplete/inputmode
Info::
All 4 eligible field(s) carry autocomplete/inputmode
A+
Document Language
Lang attribute set to "zh-CN"
PASS
Lang attribute set to "zh-CN"
Info::
<html lang="zh-CN"> is set and valid
Got: zh-CN
A+
Tabindex Anti-Patterns
20 explicit tabindex attribute(s) checked, no anti-patterns
PASS
20 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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 页面未找到 · porn吃瓜网 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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