Skip to content
https://csdn.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
36
GRADE
F
FIX
9
REVIEW
4
PASS
0
INFO
0
Checks
13
4 REVIEW 9 FIX
F
Alt Text Quality
Action
29 of 229 images have issues
FIX
29 of 229 images have issues
Critical::
29 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
19 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
197 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
229 images 3 good alt text 197 decorative 29 missing
IssueCount
missing29 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
HTTP 521, bare page
FIX
HTTP 521, bare page
Warning::
Unexpected status code: HTTP 521
Expected HTTP 404 but received 521. This may confuse search engine crawlers.
Got: HTTP 521
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 521 Custom Styling Navigation Homepage Link Search Form
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) 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::
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'>.
favicon.ico Missing
PNG Icons Present
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.
D
Lighthouse Accessibility Audits
Action
Score 68/100 — 7 failing, 15 passed
FIX
68

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.van-dropdown > div.van-dropdown-menu > div.van-dropdown-menu__bar > div.van-dropdown-menu__item div.van-dropdown > div.van-dropdown-menu > div.van-dropdown-menu__bar > div.van-dropdown-menu__item

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.

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
关注 div#floor-content_885 > div.floor-blog-content > div.blog-cont-type > p
资讯 div#floor-content_885 > div.floor-blog-content > div.blog-cont-type > p
热榜 div#floor-content_885 > div.floor-blog-content > div.blog-cont-type > p
动态 div#floor-content_885 > div.floor-blog-content > div.blog-cont-type > p
有红包 div#floor-content_885 > div.floor-blog-content > div.blog-cont-type > p
601阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
381阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
207阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
66阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
77阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
601阅读 · 20评论 div.blog-recom-item > div.recom-content > dl > dd.desc
701阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
108阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
234阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
393阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
439阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
77阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
339阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
201阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
205阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
10阅读 · 3回答 div.blog-recom-item > div.recom-content > dl > dd.desc
1530阅读 · 59评论 div.blog-recom-item > div.recom-content > dl > dd.desc
312阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc
191阅读 · 0评论 div.blog-recom-item > div.recom-content > dl > dd.desc

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
实测文心大模型X1与文心大模型4.5,我们发现了这些惊喜 3月16日,百度文心大模型4.5如约正式上线,还惊喜发布了另一款新模型——文心大模型X1。 div.hot-item > div.hot-content > a.top > dl
华为PC全面转鸿蒙 开发者称Cursor拒绝帮写代码| 极客头条 div.hot-item > div.hot-content > a.top > dl

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

Names and labels

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.csdn-toolbar-box > div.mToolbarL > a.logo > img.logo div.csdn-toolbar-box > div.mToolbarL > a.logo > img.logo
div.csdn-toolbar-box > div.rightmenu > div.toolbarBack > img#mToolbarHome div.csdn-toolbar-box > div.rightmenu > div.toolbarBack > img#mToolbarHome

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.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image
div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image
div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image
div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image
div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image
div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image
div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image
div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image div.blog-cont-cont > div.blog-recom-item > div.recom-content > a.image

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

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-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
Form elements have associated labels
`[aria-hidden="true"]` elements do not contain focusable descendents
Definition list items are wrapped in `<dl>` elements
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.
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
ARIA attributes are used as specified for the element's role
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 use only permitted 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
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
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.
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.
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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 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 ASIDE 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
8 headings
REVIEW
8 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 社区推荐
  • H3 直播
  • H3 【企业对话专场】xLLM大模型推理优化之路
  • H3 CANNBot TileLang
  • H3 CANNBot PyPTO 算子开发实操
  • H3 CANNBot PyPTO开发
  • 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

B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="password">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="toolbar-search-input">
Info::
3 control(s) properly labeled
5 controls
3 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#tab0radio下载 APPfor/id
#tab1radio公众号for/id
#tab2radio视频号for/id
#toolbar-search-inputtext(搜CSDN)placeholder only
inputpassword(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="password">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" id="toolbar-search-input">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 2 pass AA only
a 新客开通会员
3.00:1
#000000
on
#633ACB
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span 立减60
2.25:1
#000000
on
#4A3F73
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 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 社区推荐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 CANNBot TileLang21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CANNBot PyPTO 算子…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CANNBot PyPTO开发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
title CSDN_专业开发者…20.08:14.5:1
#000000
#F9FAFA
Pass
span 搜索20.31:14.5:1
#000000
#FBFBFC
Pass
span AI 搜索21.00:14.5:1
#000000
#FFFFFF
Pass
a 登录19.44:14.5:1
#000000
#F0F7FE
Pass
div 登录后您可以…10.15:14.5:1
#000000
#82B7FE
Pass
li 复制代码和一…8.58:14.5:1
#000000
#79A5FA
Pass
li 与博主大V深度…21.00:14.5:1
#000000
#FFFFFF
Pass
li 解锁海量精选…21.00:14.5:1
#000000
#FFFFFF
Pass
li 获取前沿技术…6.29:14.5:1
#000000
#9976F7
Pass
a 立即登录5.34:14.5:1
#000000
#8F66F1
Pass
a 新客开通会员3.00:14.5:1
#000000
#633ACB
Fail
span 立减602.25:14.5:1
#000000
#4A3F73
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.

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

Send Feedback