Skip to content
https://bt.cn

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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
Theme color only
FIX
Theme color only
Info::
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: #111827
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 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
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::
2 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 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
Heading Hierarchy
26 headings, 1 skip(s)
REVIEW
26 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 添加客服微信
  • H3 SSL证书 安全防护 为您的网站保驾护航
  • H1 宝塔，安全高效的服务器运维面板
  • H3 域名注册服务 skipped
  • H3 SSL证书 安全防护 为您的网站保驾护航
  • H1 宝塔，安全高效的服务器运维面板 duplicate H1
  • H2 运维要高效，装宝塔
  • H2 搭配使用，更高效
  • H3 全球可信的SSL证书
  • H3 宝塔专业运维服务
  • H3 价格实惠的域名
  • H2 数据见证实力
  • H2 安全高效的服务器运维面板
  • H3 通过SSH连接您的服务器
  • H3 执行安装命令
  • H3 访问面板
  • H3 安装推荐套件
  • H4 添加客服微信
  • H3 提供服务
  • H3 常用文档
  • H3 快捷入口
  • H3 联系我们
  • H4 添加客服微信
  • H4 加入宝塔交流群
  • H4 添加客服微信
  • H3 OpenClaw 龙虾

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

B
Alt Text Quality
2 of 41 images have issues
REVIEW
2 of 41 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
41 images 37 good alt text 2 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - 页面不存在 | 宝塔面板 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 75/100 — 7 failing, 21 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
SSL证书 安全防护 为您的网站保驾护航 提供多品牌SSL证书服务，支持多种验证级别，为网站数据传输提供安全保护 查看SSL产品 立即咨询 main.body-main > story-carousel#story-carousel-a94vs43 > div.story-track > div.story-slide
宝塔， 安全高效 的服务器运维面板 全球超2000万台服务器安装宝塔，近300万注册用户使用宝塔，持续更新维护9年值得信赖 立即免费安装宝塔面板 运维服务 main.body-main > story-carousel#story-carousel-a94vs43 > div.story-track > div.story-slide

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.overflow-x-hidden > div#floating-actions > div.inline-block > button#floating-qr-service body.overflow-x-hidden > div#floating-actions > div.inline-block > button#floating-qr-service

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.flex > h1.xl:text-[56px] > img.ml-4 div.flex > div.flex > h1.xl:text-[56px] > img.ml-4

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.footer-container > div.footer-bottom > div.footer-bottom-links > a.footer-bottom-link div.footer-container > div.footer-bottom > div.footer-bottom-links > a.footer-bottom-link

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.

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
全球超2000万台服务器安装宝塔，近300万注册用户使用宝塔，持续更新维护9年值得信赖 div.home-banner-header > div.flex > div.flex > div.lg:text-[18px]
运维服务 div.home-banner-header > div.banner-btn-group > a#home-service-btn > div.mobile-title
简单高效的服务器运维面板，让服务器管理更轻松， 查看更多功能 »» main.body-main > div.pt-[40px] > div.gap-[10px] > div.md:text-[18px]
查看更多功能 »» div.pt-[40px] > div.gap-[10px] > div.md:text-[18px] > a.text-bt
多种不同品牌的(HTTPS)SSL证书快速接入，保障您网站安全，提升用户信任度 div.mx-auto > section.w-full > a.p-10 > p.mt-2
宝塔团队拥有10余年服务器运维行业经验，为您的业务保驾护航 div.mx-auto > section.w-full > a.p-10 > p.mt-2
提供价格实惠的域名注册服务，价格透明，无需隐藏费用，一键快速注册 div.mx-auto > section.w-full > a.p-10 > p.mt-2
万+ ul.w-full > li.flex > div.text-bt > span.ml-1
海量用户关注，信赖倍增 ul.w-full > li.flex > div.flex > span.text-[#787a79]
于中央大型政企广泛使用 ul.w-full > li.flex > div.flex > span.text-[#787a79]
万+ ul.w-full > li.flex > div.text-bt > span.ml-1
超过220万注册用户 ul.w-full > li.flex > div.flex > span.text-[#787a79]
支持一键 LAMP/LNMP/集群/监控/网站/FTP/数据库/JAVA 等 100+ 服务器管理能力 main.body-main > div.pt-[40px] > div.gap-[10px] > div.md:text-[18px]
使用堡塔 SSH 终端快速连接服务器，免去复杂密钥配置，保障连接安全与效率。 div.mx-auto > ol.flex > li.h-[330px] > p.mt-2
复制下方安装命令，在 SSH 终端中执行，快速开始安装面板。 div.mx-auto > ol.flex > li.h-[330px] > p.mt-2
安装完成后，按照提示访问链接并使用初始账号密码登录，开始管理服务器。 div.mx-auto > ol.flex > li.h-[330px] > p.mt-2
首次登录根据业务需要一键安装网站环境配置。 div.mx-auto > ol.flex > li.h-[330px] > p.mt-2
更多安装方式 div.pt-[40px] > div.mx-auto > section.flex > a.btn
立即安装 div#openclaw-notification > div.notification-card > div.relative > a.flex

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
查看更多功能 »» div.pt-[40px] > div.gap-[10px] > div.md:text-[18px] > a.text-bt

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
域名注册服务 div.story-track > div.story-slide > div.max-w-[1400px] > h3.mb-4

These are opportunities to improve keyboard navigation in your application.

○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
●`[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
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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 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
○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.
○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
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <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 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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 宝塔，21.00:13.0:1
#000000
#FFFFFF
Pass
h1 的服务器运维…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 宝塔，21.00:13.0:1
#000000
#FFFFFF
Pass
h1 的服务器运维…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 运维要21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ，装宝塔21.00:13.0:1
#000000
#FFFFFF
Pass
h2 搭配使用，更…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 数据见证实力21.00:13.0:1
#000000
#FFFFFF
Pass
h2 安全高效的服…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 安全防护 为您…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 域名注册服务21.00:13.0:1
#000000
#FFFFFF
Pass
h3 安全防护 为您…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 全球可信的SSL…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 宝塔专业运维…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 价格实惠的域…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 通过SSH连接您…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 执行安装命令21.00:13.0:1
#000000
#FFFFFF
Pass
h3 访问面板21.00:13.0:1
#000000
#FFFFFF
Pass
h3 安装推荐套件21.00:13.0:1
#000000
#FFFFFF
Pass
h3 提供服务21.00:13.0:1
#000000
#FFFFFF
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.

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

Send Feedback