Accessibility

F

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

Web Manifest

Action

Not found

FIX

Not found

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

Theme color only

FIX

Theme color only

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: #0d0d0d

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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

2 navigation landmark(s) detected

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 2 <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

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

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.)

tabindex="-1" on naturally-focusable <button>

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.)

tabindex="-1" on naturally-focusable <button>

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.)

tabindex="-1" on naturally-focusable <button>

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.)

B

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (4 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (4 below threshold)

4 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: <p> 11.0px ("奇想爽剧，禁忌乱伦\nAI懂你的每一帧“色”"); <p> 11.0px ("梦幻国漫，脑洞大开\n多元内容自由切换"); <p> 11.0px ("梦幻国漫，脑洞大开\n多元内容自由切换"); <p> 11.0px ("经典翻新，脑洞爆改\n剧情不走寻常路").

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h2 剧场类型

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 沉浸式体验

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 许愿榜

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 创作者计划

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 黄果短剧常见问题

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 手机扫码下载

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 投诉举报

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 AI短剧

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI换脸

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI漫剧

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI魔改

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 一滑即播

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 猜你喜欢

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 多元题材

1.27:1

#000000

on

#1F1F1F

needs 3.0:1 (large text)

19px · bottom of viewport

title 黄果短剧｜AI成人短剧｜AI漫剧…

1.02:1

#000000

on

#010406

needs 4.5:1 (normal text)

16px · top of page (header area)

a 跳至主要内容

1.03:1

#000000

on

#010509

needs 4.5:1 (normal text)

16px · top of page (header area)

a 首页

1.05:1

#000000

on

#030A0F

needs 4.5:1 (normal text)

16px · top of page (header area)

a 剧场类型

1.07:1

#000000

on

#040D15

needs 4.5:1 (normal text)

16px · top of page (header area)

a 许愿榜

1.13:1

#000000

on

#05141F

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 黄果短剧	4.84:1	3.0:1	#000000	#A46C51	Pass
h2 剧场类型	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h2 沉浸式体验	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h2 许愿榜	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h2 创作者计划	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h2 黄果短剧常见�…	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h2 手机扫码下载	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h2 投诉举报	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h3 AI短剧	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h3 AI换脸	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h3 AI漫剧	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h3 AI魔改	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h3 一滑即播	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h3 猜你喜欢	1.27:1	3.0:1	#000000	#1F1F1F	Fail
h3 多元题材	1.27:1	3.0:1	#000000	#1F1F1F	Fail
title 黄果短剧｜AI成…	1.02:1	4.5:1	#000000	#010406	Fail
a 跳至主要内容	1.03:1	4.5:1	#000000	#010509	Fail
a 首页	1.05:1	4.5:1	#000000	#030A0F	Fail
a 剧场类型	1.07:1	4.5:1	#000000	#040D15	Fail
a 许愿榜	1.13:1	4.5:1	#000000	#05141F	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

Landmark Structure

14 landmarks

PASS

14 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

15 headings

PASS

15 headings

Single H1 present

H1 黄果短剧
H2 剧场类型
H3 AI短剧
H3 AI换脸
H3 AI漫剧
H3 AI魔改
H2 沉浸式体验
H3 一滑即播
H3 猜你喜欢
H3 多元题材
H2 许愿榜
H2 创作者计划
H2 黄果短剧常见问题
H2 手机扫码下载
H2 投诉举报

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

14 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: 14 all-caps heading(s)

A+

Alt Text Quality

All 39 images OK

PASS

All 39 images OK

21 decorative image(s) correctly marked

18 image(s) with good alt text

39 images 18 good alt text 21 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
type	select	问题类型	none
content	textarea	问题描述	none
contract	input	联系方式（选填）	none

A

Link & Button Quality

29 links, 9 buttons — all OK

PASS

29 links, 9 buttons — all OK

6 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://t.me/huangguofans; https://cf2d4.ee51vc9g.cc?aff_code=ad3vu&tpl=B; https://x.com/huangguoai; https://t.me/huangguofans; https://qu16cnk5.4dy3t-t1t1.icu?channel=YD001; https://cf2d4.ee51vc9g.cc?aff_code=ad3vu&tpl=B

23 link(s) with descriptive text

29 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/www/api/v1/download/entry?aff_code=ad3v…	下载APP	img no alt	Add alt attribute to the image
/www/api/v1/download/entry?aff_code=ad3v…	下载黄果短剧	img no alt	Add alt attribute to the image
https://t.me/huangguofans	官方社群	new tab	Add '(opens in new tab)' to text
https://cf2d4.ee51vc9g.cc?aff_code=ad3vu…	打开网页版	new tab	Add '(opens in new tab)' to text
https://x.com/huangguoai	访问 Twitter 主页	new tab	Add '(opens in new tab)' to text
https://t.me/huangguofans	加入 Telegram 频道	new tab	Add '(opens in new tab)' to text
https://qu16cnk5.4dy3t-t1t1.icu?channel=…	商务合作	new tab	Add '(opens in new tab)' to text
https://cf2d4.ee51vc9g.cc?aff_code=ad3vu…	打开网页版	new tab	Add '(opens in new tab)' to text

32 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://t.me/huangguofans; https://cf2d4.ee51vc9g.cc?aff_code=ad3vu&tpl=B; https://x.com/huangguoai; https://t.me/huangguofans; https://qu16cnk5.4dy3t-t1t1.icu?channel=YD001; https://cf2d4.ee51vc9g.cc?aff_code=ad3vu&tpl=B

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "zh-CN"

PASS

Lang attribute set to "zh-CN"

<html lang="zh-CN"> is set and valid

Got: zh-CN

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

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.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 24 passed

PASS

96

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
打开黄果短剧，遇见更多精彩故事 `footer#about > div.footer-primary > div.footer-brand > p`
© 黄果短剧 All Rights Reserved. `body.brand-site > footer#about > p.footer-copyright`

These are opportunities to improve the legibility of your content.

○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

●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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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 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.

○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.

○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.

○Identical links have the same purpose.

○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.