Skip to content
https://bilibili.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
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::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER (missing!) MAIN CONTENTINFO (missing!)

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

B
Heading Hierarchy
10 headings
REVIEW
10 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 律师的高情商VS低情商
  • H3 你被外星人抓了，想回地球需3个小时内，吃完其中一盘茶点。
  • H3 靠这台读书机器，我成了顶级学霸！
  • H3 无法遗忘 这里玫瑰的盛放
  • H3 鹭西法
  • H3 墨西哥街头柴火烤肉！
  • H3 【苏新皓｜8K直拍】ECHO！三机位直拍｜260412 浪漫主义演唱会
  • H3 我爸用极为离谱的一生，治愈了我的精神焦虑
  • H3 黑白色悬浮字，写《征明临兰亭》，我也来！
  • H3 😭真的好害怕啊啊啊

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 出错啦! - bilibili.com ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA 1 pass AA only
span 首页
2.63:1
#000000
on
#614B4F
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span 番剧
1.77:1
#000000
on
#423244
needs 4.5:1 (normal text)
16px · top of page (header area)
span 下载客户端
1.95:1
#000000
on
#28414A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span 登录
3.05:1
#000000
on
#5D595D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p 登录后你可以：
2.30:1
#000000
on
#464947
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span 免费看高清视频
1.35:1
#000000
on
#0C2636
needs 4.5:1 (normal text)
16px · above the fold
span 多端同步播放记录
1.43:1
#000000
on
#122B38
needs 4.5:1 (normal text)
16px · above the fold
span 发表弹幕/评论
1.40:1
#000000
on
#142936
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span 热门番剧影视看不停
1.46:1
#000000
on
#172C39
needs 4.5:1 (normal text)
16px · mid-page
div 立即登录
1.27:1
#000000
on
#0F2129
needs 4.5:1 (normal text)
16px · mid-page
div 首次使用？
1.21:1
#000000
on
#161B20
needs 4.5:1 (normal text)
16px · mid-page
span 点我注册
1.19:1
#000000
on
#15191C
needs 4.5:1 (normal text)
16px · mid-page
span 大会员
1.19:1
#000000
on
#15191C
needs 4.5:1 (normal text)
16px · mid-page

5 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
title 哔哩哔哩 (゜-…6.40:14.5:1
#000000
#A08B6C
Pass
span 首页2.63:14.5:1
#000000
#614B4F
Fail
span 番剧1.77:14.5:1
#000000
#423244
Fail
span 直播8.36:14.5:1
#000000
#AD9FAF
Pass
span 游戏中心15.26:14.5:1
#000000
#E4D8E6
Pass
span 会员购19.96:14.5:1
#000000
#F9F9FA
Pass
span 漫画20.43:14.5:1
#000000
#FBFCFC
Pass
span 赛事20.43:14.5:1
#000000
#FBFCFC
Pass
span 下载客户端1.95:14.5:1
#000000
#28414A
Fail
span 登录3.05:14.5:1
#000000
#5D595D
Fail
p 登录后你可以…2.30:14.5:1
#000000
#464947
Fail
span 免费看高清视…1.35:14.5:1
#000000
#0C2636
Fail
span 多端同步播放…1.43:14.5:1
#000000
#122B38
Fail
span 发表弹幕/评论1.40:14.5:1
#000000
#142936
Fail
span 热门番剧影视…1.46:14.5:1
#000000
#172C39
Fail
div 立即登录1.27:14.5:1
#000000
#0F2129
Fail
div 首次使用？1.21:14.5:1
#000000
#161B20
Fail
span 点我注册1.19:14.5:1
#000000
#15191C
Fail
span 大会员1.19:14.5:1
#000000
#15191C
Fail
span 消息8.29:14.5:1
#000000
#A1A3A4
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 5 failing, 13 passed
REVIEW
75

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
Download App div.m-navbar > div.right > m-open-app.m-open-app > div.open-app-img
Open in App m-open-app.m-open-app > button.v5-button > div.v5-button__content__wrap > span

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.suspension-box > div.m-navbar > div.right > a.search div.suspension-box > div.m-navbar > div.right > a.search

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.

Tables and lists

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
首页 番剧 国创 纪录片 电影 电视剧 影视 娱乐 音乐 舞蹈 动画 绘画 鬼畜 游戏 资讯 知识 人工智能 科技数码 汽车 时尚美妆 家装房产 户外潮流 健… div > div.v-switcher__header > div.v-switcher__header__tabs__wrap > ul.v-switcher__header__tabs__list

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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>`
●`[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 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
●Touch targets have sufficient size and spacing.
●The page contains a heading, skip link, or landmark region
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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
○`<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
○Heading elements appear in a sequentially-descending order
○`<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.
○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
○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.
A+
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
4 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
26 images 22 good alt text 4 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(2027届高考生彻底爽了)placeholder only

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

<input type="text">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback