Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 5 REVIEW 7 FIX

Alt Text Quality

Action

13 of 13 images have issues

FIX

13 of 13 images have issues

13 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image-in-link without alt text

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

13 images 13 missing

Issue	Count
missing	13 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-tq4oqz

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://dedecms.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://dedecms.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

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

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

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

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

Heading Hierarchy

15 headings, 1 skip(s)

REVIEW

15 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H5 (empty)
H1 DedeCMS V5.7.118 正式版下载
H2 产品特性
H5 用户口碑 skipped
H5 模块组合
H5 模板引擎
H5 自定义模型
H5 动静态部署
H5 升级无忧
H5 强大的SEO
H5 安全可靠
H5 021-37788569
H5 技术支持
H5 服务支持
H5 关于我们

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Link & Button Quality

Action

3 issue(s) across 37 links and 2 buttons

REVIEW

3 issue(s) across 37 links and 2 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; /

6 link(s) open in new tab without warning

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

Got: /post/20211026.html; /post/20210930.html; tel:021-37788569; http://beian.miit.gov.cn/; https://www.beian.gov.cn/portal/registerSystemInfo?recordcode=31011802005130; https://www.landui.com/

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.navbar-toggler (#27 on page)

29 link(s) with descriptive text

37 links

2 empty

0 generic text

6 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/post/20211026.html	关于侵权网站清单及存…	new tab	Add '(opens in new tab)' to text
/post/20210930.html	致广大DedeCMS用户的一�…	new tab	Add '(opens in new tab)' to text
tel:021-37788569	021-37788569	new tab	Add '(opens in new tab)' to text
http://beian.miit.gov.cn/	沪ICP备17008595号	new tab	Add '(opens in new tab)' to text
https://www.beian.gov.cn/portal/register…	沪公网安备31011802005130�…	new tab	Add '(opens in new tab)' to text
https://www.landui.com/	蓝队云	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

30 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; /

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

/post/20211026.html; /post/20210930.html; tel:021-37788569; http://beian.miit.gov.cn/; https://www.beian.gov.cn/portal/registerSystemInfo?recordcode=31011802005130; https://www.landui.com/

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.navbar-toggler (#27 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 15 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 DedeCMS V5.7.118 正…	6.37:1	3.0:1	#000000	#50A000	Pass
h2 产品特性	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title 织梦 (DedeCMS) 官…	19.92:1	4.5:1	#000000	#F8F9FA	Pass
span 织梦 (DedeCMS) 官…	19.92:1	4.5:1	#000000	#F8F9FA	Pass
span 021-37788569	10.52:1	4.5:1	#000000	#94C664	Pass
a 首页	6.59:1	4.5:1	#000000	#51A300	Pass
a 产品下载	6.60:1	4.5:1	#000000	#52A300	Pass
a 开源协议	6.60:1	4.5:1	#000000	#52A300	Pass
a 授权查询	6.60:1	4.5:1	#000000	#52A300	Pass
a 正版授权	6.53:1	4.5:1	#000000	#52A201	Pass
a 网站定制	6.45:1	4.5:1	#000000	#51A101	Pass
a 增值服务	6.53:1	4.5:1	#000000	#52A201	Pass
a 套餐服务	6.45:1	4.5:1	#000000	#51A100	Pass
a 单项服务	6.45:1	4.5:1	#000000	#51A100	Pass
a 推荐主机	6.45:1	4.5:1	#000000	#51A100	Pass
a 帮助中心	6.45:1	4.5:1	#000000	#51A100	Pass
a 注册	6.45:1	4.5:1	#000000	#51A100	Pass
a 登录	6.45:1	4.5:1	#000000	#51A100	Pass
p Nginx/IIS/Apache PHP…	6.37:1	4.5:1	#000000	#50A000	Pass
p 更新于 2025-07-30	6.37:1	4.5:1	#000000	#50A000	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.

Lighthouse Accessibility Audits

Action

Score 75/100 — 6 failing, 15 passed

REVIEW

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.

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