Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 38 -1-on-focusable

FIX

0 positive, 38 -1-on-focusable

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

D

Mobile-Readable Font Sizes

Action

59% of visible text renders at >= 12 CSS px (127 below threshold)

FIX

59% of visible text renders at >= 12 CSS px (127 below threshold)

127 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> 9.0px ("AI"); <span> 11.5px ("新剧"); <span> 11.5px ("新剧"); <span> 11.5px ("新剧"); <span> 11.5px ("新剧").

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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: #07080d

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

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

Form Accessibility

4 of 4 controls have issues

REVIEW

4 of 4 controls have issues

4 control(s) rely on placeholder only

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

Got: <input id="auUser">; <input type="password" id="auPass">; <input type="password" id="auConfirm">; <input id="aiInput">

4 controls

0 labeled

4 placeholder only

0 unlabeled

Control	Type	Label	Method
#auUser	input	(用户名)	placeholder only
#auPass	password	(密码)	placeholder only
#auConfirm	password	(确认密码)	placeholder only
#aiInput	input	(例如：高分反转悬疑…)	placeholder only

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

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

Tap Target Adequacy

3 tap target(s) too small or too close together

REVIEW

3 tap target(s) too small or too close together

3 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 成人短剧 · 漫剧 · 真人剧

1.04:1

#000000

on

#06070C

needs 3.0:1 (large text)

32px · mid-page

h2 官方推荐

1.04:1

#000000

on

#07070C

needs 3.0:1 (large text)

24px · mid-page

h2 🔥 热播榜

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

24px · bottom of viewport

h2 成人短剧

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

24px · bottom of viewport

h2 成人漫剧

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

24px · bottom of viewport

h2 真人剧

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

24px · bottom of viewport

h2 成人视频

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

24px · bottom of viewport

h3 黄码宝贝

1.07:1

#000000

on

#0B0A17

needs 3.0:1 (large text)

19px · bottom of viewport

h3 瘾梦

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 恶魔契约

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 尤物讨妖队

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 合同深处

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 赤裸的心跳

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 木乃伊：以身为祭

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 爱情公寓

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 黄码宝贝

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 冥婚厉鬼-冥婚血怨

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 我把兄弟变母狗

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 时停手表

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

h3 隔壁空姐的诱惑

1.05:1

#000000

on

#080811

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 成人短剧 · 漫�…	1.04:1	3.0:1	#000000	#06070C	Fail
h2 官方推荐	1.04:1	3.0:1	#000000	#07070C	Fail
h2 🔥 热播榜	1.05:1	3.0:1	#000000	#080811	Fail
h2 成人短剧	1.05:1	3.0:1	#000000	#080811	Fail
h2 成人漫剧	1.05:1	3.0:1	#000000	#080811	Fail
h2 真人剧	1.05:1	3.0:1	#000000	#080811	Fail
h2 成人视频	1.05:1	3.0:1	#000000	#080811	Fail
h3 黄码宝贝	1.07:1	3.0:1	#000000	#0B0A17	Fail
h3 瘾梦	1.05:1	3.0:1	#000000	#080811	Fail
h3 恶魔契约	1.05:1	3.0:1	#000000	#080811	Fail
h3 尤物讨妖队	1.05:1	3.0:1	#000000	#080811	Fail
h3 合同深处	1.05:1	3.0:1	#000000	#080811	Fail
h3 赤裸的心跳	1.05:1	3.0:1	#000000	#080811	Fail
h3 木乃伊：以身�…	1.05:1	3.0:1	#000000	#080811	Fail
h3 爱情公寓	1.05:1	3.0:1	#000000	#080811	Fail
h3 黄码宝贝	1.05:1	3.0:1	#000000	#080811	Fail
h3 冥婚厉鬼-冥婚�…	1.05:1	3.0:1	#000000	#080811	Fail
h3 我把兄弟变母�…	1.05:1	3.0:1	#000000	#080811	Fail
h3 时停手表	1.05:1	3.0:1	#000000	#080811	Fail
h3 隔壁空姐的诱�…	1.05:1	3.0:1	#000000	#080811	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 88/100 — 4 failing, 21 passed

REVIEW

88

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
成人短剧 · 40297万热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 3120万热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 2120万热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 2120万热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 1122万热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 4732热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 2万热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 2万热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 1万热度 `a.card > div.card-info > div.meta > span`
成人短剧 · 2171热度 `a.card > div.card-info > div.meta > span`
成人漫剧 · 30万热度 `a.card > div.card-info > div.meta > span`
成人漫剧 · 28万热度 `a.card > div.card-info > div.meta > span`
成人漫剧 · 19万热度 `a.card > div.card-info > div.meta > span`
成人漫剧 · 18万热度 `a.card > div.card-info > div.meta > span`
成人漫剧 · 18万热度 `a.card > div.card-info > div.meta > span`
成人漫剧 · 17万热度 `a.card > div.card-info > div.meta > span`
真人剧 · 8万热度 `a.card > div.card-info > div.meta > span`
真人剧 · 8万热度 `a.card > div.card-info > div.meta > span`
真人剧 · 8万热度 `a.card > div.card-info > div.meta > span`
真人剧 · 8万热度 `a.card > div.card-info > div.meta > span`
真人剧 · 8万热度 `a.card > div.card-info > div.meta > span`
真人剧 · 8万热度 `a.card > div.card-info > div.meta > span`
成人视频 · 4万热度 `a.card > div.card-info > div.meta > span`
成人视频 · 4万热度 `a.card > div.card-info > div.meta > span`
成人视频 · 4万热度 `a.card > div.card-info > div.meta > span`
成人视频 · 4万热度 `a.card > div.card-info > div.meta > span`
成人视频 · 4万热度 `a.card > div.card-info > div.meta > span`
成人视频 · 4万热度 `a.card > div.card-info > div.meta > span`
© 2026 91成人短剧版权所有 · All Rights Reserved `footer > div.wrap > div.foot-bottom > div`

These are opportunities to improve the legibility of your content.

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
div > div > div > a `div > div > div > 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

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
0d7e.ak29x31k.cc `div.foot-col > div.foot-addr > div.addr-row > a`
91crdjai.pages.dev `div.foot-col > div.foot-addr > div.addr-row > a`
91crdjai.com `div.foot-col > div.foot-addr > div.addr-row > a`

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
iOS · Android 下载 APP `div.foot-grid > div.foot-col > div.foot-brand > a.foot-app`

○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

●Form elements have associated labels

●`[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

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

●Heading elements appear in a sequentially-descending order

●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

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

○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

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

7 landmarks

PASS

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

43 headings

PASS

43 headings

Single H1 present

H1 成人短剧 · 漫剧 · 真人剧免费在线观看
H2 官方推荐
H3 黄码宝贝
H3 瘾梦
H3 恶魔契约
H3 尤物讨妖队
H3 合同深处
H3 赤裸的心跳
H3 木乃伊：以身为祭
H3 爱情公寓
H2 🔥 热播榜
H3 黄码宝贝
H3 冥婚厉鬼-冥婚血怨
H3 我把兄弟变母狗
H3 时停手表
H3 隔壁空姐的诱惑
H2 成人短剧
H3 演艺圈生存法则
H3 偶像歌手的秘密
H3 女陪玩毛毛米：横扫电竞圈
H3 催眠眼镜
H3 嫂子把植物人弟弟玩醒了
H2 成人漫剧
H3 恶鬼新娘
H3 黑暗圣经第一季
H3 黑暗白雪之全员恶人无童话
H3 系统带我攻略弟弟
H3 反派：我的母亲是大帝
H3 赠物得长生：老头修仙记
H2 真人剧
H3 每月三万，我啃了四年馒头
H3 别对我摇尾
H3 归途的光
H3 夺风华
H3 旷野之夏：许我夏至
H3 以爱为家第四季
H2 成人视频
H3 青年权臣的宫廷传奇人生
H3 搓澡大爷上班的一天困境中的同行让彼此关系发生变化
H3 灯熄灭之后黑暗中的秘密逐渐浮现
H3 流金岁月四位都市女性的职场与情感故事
H3 情感反诈模拟器神秘互动背后的骗局真相
H3 青春毕业季离别之前留下最后约定

A

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "瘾梦"

Got: 1 ≤2-char heading(s)

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

A+

Alt Text Quality

All 47 images OK

PASS

All 47 images OK

8 decorative image(s) correctly marked

39 image(s) with good alt text

47 images 39 good alt text 8 decorative

All images have appropriate alt text.

A

Link & Button Quality

117 links, 23 buttons — all OK

PASS

117 links, 23 buttons — all OK

12 link(s) open in new tab without warning

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

Got: https://theporndude.com/zh; https://91crdj.app/; https://0d7e.ak29x31k.cc; https://91crdjai.pages.dev; https://91crdjai.com; https://x.com/91crdjai; https://t.me/hubiaorenshipin/4202; https://91aicrdj.github.io/; https://www.tiktok.com/@91crdj; https://www.instagram.com/91crdj_/ (+2 more)

105 link(s) with descriptive text

117 links

0 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://theporndude.com/zh	ThePornDude	new tab	Add '(opens in new tab)' to text
https://91crdj.app/	下载APP	new tab	Add '(opens in new tab)' to text
https://0d7e.ak29x31k.cc	0d7e.ak29x31k.cc	new tab	Add '(opens in new tab)' to text
https://91crdjai.pages.dev	91crdjai.pages.dev	new tab	Add '(opens in new tab)' to text
https://91crdjai.com	91crdjai.com	new tab	Add '(opens in new tab)' to text
https://x.com/91crdjai	X / Twitter	new tab	Add '(opens in new tab)' to text
https://t.me/hubiaorenshipin/4202	Telegram	new tab	Add '(opens in new tab)' to text
https://91aicrdj.github.io/	GitHub	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@91crdj	TikTok	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/91crdj_/	Instagram	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://91crdj.app/	📲APP下载	new tab	Add '(opens in new tab)' to text

128 links and buttons have descriptive text

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

https://theporndude.com/zh; https://91crdj.app/; https://0d7e.ak29x31k.cc; https://91crdjai.pages.dev; https://91crdjai.com; https://x.com/91crdjai; https://t.me/hubiaorenshipin/4202; https://91aicrdj.github.io/; https://www.tiktok.com/@91crdj; https://www.instagram.com/91crdj_/ (+2 more)

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

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

All 2 eligible field(s) carry autocomplete/inputmode

PASS

All 2 eligible field(s) carry autocomplete/inputmode

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 页面未找到 · 91成人短剧 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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