Skip to content
https://huangguoac.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
D
Mobile-Readable Font Sizes
Action
33% of visible text renders at >= 12 CSS px (163 below threshold)
FIX
33% of visible text renders at >= 12 CSS px (163 below threshold)
Warning::
163 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 ("更新至1集"); <a> 10.0px ("现代"); <a> 10.0px ("都市"); <a> 10.0px ("乱伦"); <span> 11.0px ("更新至10集").
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::
3 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 3 <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
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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

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

C
Mobile Keyboard & Autofill
Action
1/3 eligible field(s) missing autocomplete or inputmode
REVIEW
1/3 eligible field(s) missing autocomplete or inputmode
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: search.
Got: <input type="search" name="keyword">
C
Tap Target Adequacy
Action
6 tap target(s) too small or too close together
REVIEW
6 tap target(s) too small or too close together
Warning::
6 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
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 黄果漫剧 – AI漫剧、里番动漫…
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
32px · bottom of viewport
h2 精选推荐
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 AI漫剧
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 里番动漫
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 成人短剧
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 成人日漫
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 成人韩漫
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 专题推荐
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h3 东郊到家
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 选修课
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 人妻第一次破防
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 小龙女的心动
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 绝世仙宗
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 系统带我攻略弟弟（漫剧版）
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 美丽新世界（漫剧版）
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 目标是奴可梦训练大师
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 夫妻游戏第二季
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 师姐双修能不能带上我们
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 サキュバステードライフ THE AN…
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 英才狂育 [中文字幕]
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 黄果漫剧 – AI…1.05:13.0:1
#000000
#080808
Fail
h2 精选推荐1.05:13.0:1
#000000
#080808
Fail
h2 AI漫剧1.05:13.0:1
#000000
#080808
Fail
h2 里番动漫1.05:13.0:1
#000000
#080808
Fail
h2 成人短剧1.05:13.0:1
#000000
#080808
Fail
h2 成人日漫1.05:13.0:1
#000000
#080808
Fail
h2 成人韩漫1.05:13.0:1
#000000
#080808
Fail
h2 专题推荐1.05:13.0:1
#000000
#080808
Fail
h3 东郊到家1.05:13.0:1
#000000
#080808
Fail
h3 选修课1.05:13.0:1
#000000
#080808
Fail
h3 人妻第一次破…1.05:13.0:1
#000000
#080808
Fail
h3 小龙女的心动1.05:13.0:1
#000000
#080808
Fail
h3 绝世仙宗1.05:13.0:1
#000000
#080808
Fail
h3 系统带我攻略…1.05:13.0:1
#000000
#080808
Fail
h3 美丽新世界（…1.05:13.0:1
#000000
#080808
Fail
h3 目标是奴可梦…1.05:13.0:1
#000000
#080808
Fail
h3 夫妻游戏第二…1.05:13.0:1
#000000
#080808
Fail
h3 师姐双修能不…1.05:13.0:1
#000000
#080808
Fail
h3 サキュバステ…1.05:13.0:1
#000000
#080808
Fail
h3 英才狂育 [中文…1.05:13.0:1
#000000
#080808
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 86/100 — 3 failing, 22 passed
REVIEW
86

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
更多推荐 section.hg-section > div.hg-section-header > a.hg-see-more > span
更多推荐 section.hg-section > div.hg-section-header > a.hg-see-more > span
更多推荐 section.hg-section > div.hg-section-header > a.hg-see-more > span
更多推荐 section.hg-section > div.hg-section-header > a.hg-see-more > span
更多推荐 section.hg-section > div.hg-section-header > a.hg-see-more > span
更多推荐 section.hg-section > div.hg-section-header > a.hg-see-more > span
全部专题 section.hg-section > div.hg-section-header > a.hg-see-more > span
© 黄果漫剧 · ALL RIGHTS RESERVED footer#app-footer > div.hg-footer__inner > div.hg-footer__brand > p.hg-footer__copy
黄果漫剧 div.hg-footer__inner > div.hg-footer__brand > p.hg-footer__copy > a
常见问题 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
联系我们 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
隐私政策 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
使用协议 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
dmca div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a
2257 div.hg-footer__inner > div.hg-footer__cols > div.hg-footer__col > a

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
切换轮播 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot
切换轮播 section.hg-hero > div.hg-hero__controls > div.hg-hero__dots > button.hg-hero__dot

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-*]` 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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 are distinguishable without relying on color.
●Links have a discernible name
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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 Hierarchy
50 headings
PASS
50 headings
Info::
Single H1 present
  • H1 黄果漫剧 – AI漫剧、里番动漫、成人日漫与成人韩漫在线观看
  • H2 精选推荐
  • H3 东郊到家
  • H3 选修课
  • H3 人妻第一次破防
  • H3 小龙女的心动
  • H3 东郊到家
  • H3 选修课
  • H3 人妻第一次破防
  • H3 小龙女的心动
  • H2 AI漫剧
  • H3 绝世仙宗
  • H3 系统带我攻略弟弟（漫剧版）
  • H3 美丽新世界（漫剧版）
  • H3 目标是奴可梦训练大师
  • H3 夫妻游戏第二季
  • H3 师姐双修能不能带上我们
  • H2 里番动漫
  • H3 サキュバステードライフ THE ANIMATION [中文字幕]
  • H3 英才狂育 [中文字幕]
  • H3 春恋*乙女 [中文字幕]
  • H3 死妹人形 第一章「蘇生」 [中文字幕]
  • H3 下級生2 ～季花詞集〔Anthology〕～ [中文字幕]
  • H3 解放区 痴漢ハーレム [中文字幕]
  • H2 成人短剧
  • H3 被潜规则的女孩
  • H3 诱色游戏：和女神的七天游戏
  • H3 时停手表
  • H3 道之触
  • H3 暮色心囚
  • H3 失踪的飞机杯
  • H2 成人日漫
  • H3 滞纳ビッチ返済计画 (COMIC 失楽天 2026年8月号)
  • H3 チョロいくノ一に绞られる话 (NARUTO - ナルト-)
  • H3 ダブル魔女の挟爱 (ニュイ・ソシエール)
  • H3 エロとツッコミ ～メスガキ理解らせ编～
  • H3 俺の妻はカーテン越しにほぐされる。
  • H3 欲望のままに 後編 (COMIC ペンギンクラブ 2024年2月3月合併号) [中国翻訳] [DL版]
  • H2 成人韩漫
  • H3 公主抢孕大作战
  • H3 馆长是大野狼
  • H3 黑道X上班族
  • H3 梦幻家教
  • H3 秘书的难言之隐
  • H3 魔法刺青店
  • H2 专题推荐
  • H3 精品高分AI成人漫剧
  • H3 深夜里番动漫精选
  • H3 人气必看日本成人漫画
  • H3 热门爆款韩国成人漫画
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
46 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: 46 all-caps heading(s)
A+
Alt Text Quality
All 92 images OK
PASS
All 92 images OK
Info::
22 decorative image(s) correctly marked
Info::
70 image(s) with good alt text
92 images 70 good alt text 22 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
keywordsearchnone
usernametext账号none
passwordpassword密码none
confirm_passwordpassword确认密码none
A+
Form Input Types
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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 页面未找到 · 黄果漫剧 ✓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
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback