Skip to content
https://zblogcn.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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::
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.
B
Heading Hierarchy
4 headings
REVIEW
4 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 为什么选择Z-Blog？
  • H3 Z-Blog让建站更简单
  • H4 海量的优质建站模板
  • H4 智能化的后台管理

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
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
h3 为什么选择Z-Blog？
1.15:1
#000000
on
#15141E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Z-Blog让建站更简单
1.15:1
#000000
on
#15141E
needs 3.0:1 (large text)
19px · bottom of viewport
title ZBlog、Z-Blog官方网站，开源免…
1.13:1
#000000
on
#13121C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Z-Blog主页
1.13:1
#000000
on
#13121B
needs 4.5:1 (normal text)
16px · top of page (header area)
a 文档
1.13:1
#000000
on
#13121B
needs 4.5:1 (normal text)
16px · top of page (header area)
a 论坛
1.13:1
#000000
on
#14121C
needs 4.5:1 (normal text)
16px · top of page (header area)
a 应用
1.14:1
#000000
on
#15121C
needs 4.5:1 (normal text)
16px · above the fold
a 菠萝阁
1.08:1
#000000
on
#0A0C19
needs 4.5:1 (normal text)
16px · above the fold
a Z5加密
1.08:1
#000000
on
#070C19
needs 4.5:1 (normal text)
16px · above the fold
div Z-Blog
1.07:1
#000000
on
#050B17
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span 用户中心
1.08:1
#000000
on
#070C19
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p 一个账号即可畅玩Z-Blog全部平…
1.19:1
#000000
on
#1F1621
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a 注册账号
1.63:1
#000000
on
#3B2E36
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
li 统一Z-Blog网站所有账号系统
1.95:1
#000000
on
#573435
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
li 支持GitHub和QQ登录
1.90:1
#000000
on
#4A373C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
li 支持手机绑定
2.18:1
#000000
on
#4B424A
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
li 开放了两步验证和单次Token系…
1.60:1
#000000
on
#332F38
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
div Z-Blog
1.62:1
#000000
on
#352F39
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span PHP
1.87:1
#000000
on
#413844
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
div 1.7.5
1.62:1
#000000
on
#362F39
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

11 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
h3 为什么选择Z-Blo…1.15:13.0:1
#000000
#15141E
Fail
h3 Z-Blog让建站更…1.15:13.0:1
#000000
#15141E
Fail
title ZBlog、Z-Blog官方…1.13:14.5:1
#000000
#13121C
Fail
a Z-Blog主页1.13:14.5:1
#000000
#13121B
Fail
a 文档1.13:14.5:1
#000000
#13121B
Fail
a 论坛1.13:14.5:1
#000000
#14121C
Fail
a 应用1.14:14.5:1
#000000
#15121C
Fail
a 菠萝阁1.08:14.5:1
#000000
#0A0C19
Fail
a Z5加密1.08:14.5:1
#000000
#070C19
Fail
div Z-Blog1.07:14.5:1
#000000
#050B17
Fail
span 用户中心1.08:14.5:1
#000000
#070C19
Fail
p 一个账号即可…1.19:14.5:1
#000000
#1F1621
Fail
a 注册账号1.63:14.5:1
#000000
#3B2E36
Fail
li 统一Z-Blog网站…1.95:14.5:1
#000000
#573435
Fail
li 支持GitHub和QQ登…1.90:14.5:1
#000000
#4A373C
Fail
li 支持手机绑定2.18:14.5:1
#000000
#4B424A
Fail
li 开放了两步验…1.60:14.5:1
#000000
#332F38
Fail
div Z-Blog1.62:14.5:1
#000000
#352F39
Fail
span PHP1.87:14.5:1
#000000
#413844
Fail
div 1.7.51.62:14.5:1
#000000
#362F39
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+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
5 image(s) with good alt text
5 images 5 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Lighthouse Accessibility Audits
Score 93/100 — 1 failing, 14 passed
PASS
93

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
简单易用，体积小速度快，操作方便，更适合国人的设计 ul > li > a > p
程序多年打磨，具有极高的安全性，系统底层稳定且坚固 ul > li > a > p
丰富的插件接口，轻松应对各种拓展需求，具有可定制性 ul > li > a > p
自带应用中心客户端，实现主题、插件在线安装，一键更新 ul > li > a > p
© 2026 ZBLOGCN.COM 版权所有. 鄂ICP备19031813号-6 div.footer > div.copyright > div.wrap > p
鄂ICP备19031813号-6 div.copyright > div.wrap > p > a
由提供CDN及云存储服务   本站由Toyean拓源网设计 div.footer > div.copyright > div.wrap > p
Toyean拓源网 div.copyright > div.wrap > p > a
严禁使用Z-BLOG从事任何非法活动，禁止违法网站使用Z-BLOG及相关程序 | 违法和不良信息举报中心 div.footer > div.copyright > div.wrap > p
违法和不良信息举报中心 div.copyright > div.wrap > p > a

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-hidden="true"]` is not present on the document `<body>`
●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.
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback