Skip to content
https://west.cn

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 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

D
Form Accessibility
Action
5 of 29 controls have issues
FIX
5 of 29 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="searchedDomainName" id="J_domainNames">; <input type="submit">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="u_name" id="J_u_name">; <input type="password" name="u_password" id="J_u_password">; <input type="text" name="searchedDomainName" id="J_domName">
Info::
24 control(s) properly labeled
29 controls
24 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
#chkAutoLogincheckboxnone
#label_for_0_0checkboxnone
#label_for_0_1checkboxnone
#label_for_0_2checkboxnone
#label_for_0_3checkboxnone
#label_for_0_4checkboxnone
#label_for_0_5checkboxnone
#label_for_0_6checkboxnone
#label_for_0_7checkboxnone
#label_for_0_8checkboxnone
#label_for_0_9checkboxnone
#label_for_0_10checkboxnone
#label_for_0_11checkboxnone
#label_for_0_12checkboxnone
#label_for_0_13checkboxnone
#label_for_0_14checkboxnone
#label_for_0_15checkboxnone
#label_for_0_16checkboxnone
#label_for_0_17checkboxnone
#label_for_0_18checkboxnone
#label_for_0_19checkboxnone
#label_for_0_20checkboxnone
#label_for_0_21checkboxnone
#label_for_0_22checkboxnone
#J_domNametext(注册域名先查询，请输入域名，如west， 也可以输入west.cn直接查询)placeholder only
#J_u_passwordpassword(请输入您的用户密码)placeholder only
#J_u_nametext(请输入您的用户名/手机/邮箱)placeholder only
inputsubmit(none)none
#J_domainNamestextarea(none)none

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

<textarea name="searchedDomainName" id="J_domainNames">; <input type="submit">

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" name="u_name" id="J_u_name">; <input type="password" name="u_password" id="J_u_password">; <input type="text" name="searchedDomainName" id="J_domName">

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

F
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'>.
✓ favicon.ico Present
✓ 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 52/100 — 7 failing, 10 passed
FIX
52

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
查域名 section.domain_reg > form#J_domainForm > p.domain_serach > a.large-btn
更多域名>> section.domain_reg > div#J_domainList > label > a.moredomain
云服务器 section > ul#J_serverTab > li.active > a.nav_text_nav
西南枢纽 div.list_box > span.list_text > p > span.list_suffix
¥115/月 div.list_content_div > div.list_box > span.list_sell > p
¥115 div.list_box > span.list_sell > p > span.list_sell_price
立即购买 div.list_content_div > div.list_box > span.list_sell > a.btn
西南枢纽 div.list_box > span.list_text > p > span.list_suffix
¥153/月 div.list_content_div > div.list_box > span.list_sell > p
¥153 div.list_box > span.list_sell > p > span.list_sell_price
立即购买 div.list_content_div > div.list_box > span.list_sell > a.btn
西南枢纽 div.list_box > span.list_text > p > span.list_suffix
¥261/月 div.list_content_div > div.list_box > span.list_sell > p
¥261 div.list_box > span.list_sell > p > span.list_sell_price
立即购买 div.list_content_div > div.list_box > span.list_sell > a.btn
最新公告 section.module-f > ul#J_newsTab > li.active > a.nav_text_nav

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
网站地图 footer#g_footer > div.copyright > p > a.blue-link

These are opportunities to improve the legibility of your content.

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.list_content_div > div.list_box > span.list_imgbox > img div.list_content_div > div.list_box > span.list_imgbox > img
div.list_content_div > div.list_box > span.list_imgbox > img div.list_content_div > div.list_box > span.list_imgbox > img
div.list_content_div > div.list_box > span.list_imgbox > img div.list_content_div > div.list_box > span.list_imgbox > img

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#globalWrapper > header.header-nav > div.head_btn > a div#globalWrapper > header.header-nav > div.head_btn > a

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#J_banner > div.slide-wrapper > div.tempWrap > ul

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-hidden="true"]` is not present on the document `<body>`
●Form elements have associated labels
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●The page contains a heading, skip link, or landmark region
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○`<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
○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
○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
Heading Hierarchy
Action
42 headings, 2 skip(s)
REVIEW
42 headings, 2 skip(s)
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 我的购物车
  • H3 快速链接
  • H3 新用户
  • H3 用户登录
  • H3 新用户
  • H3 新人专享优惠
  • H3 您好，
  • H3 .com域名
  • H3 .cn域名
  • H3 云服务器 Hot
  • H3 云虚拟主机
  • H1 西部数码云服务器
  • H2 西部数码-20年老牌云服务器提供商。域名注册保有量全国第2，网站备案接入量全国第3。
  • H2 热门抢注
  • H2 热门竞价
  • H2 推荐一口价
  • H3 WEB HOST
  • H3 国内虚拟主机
  • H3 WEB HOST
  • H3 外贸虚拟主机
  • H3 CLOUD HOST
  • H3 云服务器
  • H3 EMALL
  • H3 企业邮箱
  • H3 LATEST OFFERS
  • H3 最新优惠
  • H6 体验型150M skipped
  • H6 云峰A 1G
  • H6 独享基础型
  • H6 香港体验型 200M
  • H6 香港入门型 1G
  • H6 美国入门型 600M
  • H6 入门型云服务器
  • H6 标准型云服务器
  • H6 商务型云服务器
  • H1 西部数码最新活动 duplicate H1
  • H1 建站流程说明 duplicate H1
  • H1 为什么选择西部数码？ duplicate H1
  • H2 西部数码是成立于2002年的老牌互联网基础服务提供商，域名注册保有量全国第2，网站备案接入量全国第3。24年来，累计超过50万个网站在西部数码平台�
  • H6 客服热线 skipped
  • H3 400-028-5800
  • H3 24小时客服热线

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

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
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ҳ��δ�ҵ�����������,ȫ��3ǿ���й����ȵ��������������������á�����ע�������̣� ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
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 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 西部数码云服…3.79:13.0:1
#000000
#096ABB
Pass
h1 西部数码最新…3.79:13.0:1
#000000
#096ABB
Pass
h1 建站流程说明3.79:13.0:1
#000000
#096ABB
Pass
h1 为什么选择西…3.79:13.0:1
#000000
#096ABB
Pass
h2 西部数码-20年…3.79:13.0:1
#000000
#096ABB
Pass
h2 西部数码是成…3.79:13.0:1
#000000
#096ABB
Pass
h2 在西部数码，…3.79:13.0:1
#000000
#096ABB
Pass
h3 快速链接3.79:13.0:1
#000000
#096ABB
Pass
h3 新用户3.79:13.0:1
#000000
#096ABB
Pass
h3 用户登录3.79:13.0:1
#000000
#096ABB
Pass
h3 新用户3.79:13.0:1
#000000
#096ABB
Pass
h3 新人专享优惠3.79:13.0:1
#000000
#096ABB
Pass
h3 您好，3.79:13.0:1
#000000
#096ABB
Pass
h3 .com域名3.79:13.0:1
#000000
#096ABB
Pass
h3 .cn域名3.79:13.0:1
#000000
#096ABB
Pass
h3 云服务器3.79:13.0:1
#000000
#096ABB
Pass
h3 云虚拟主机3.79:13.0:1
#000000
#096ABB
Pass
h3 WEB HOST3.79:13.0:1
#000000
#096ABB
Pass
h3 WEB HOST3.79:13.0:1
#000000
#096ABB
Pass
h3 CLOUD HOST3.79:13.0:1
#000000
#096ABB
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.

A
Alt Text Quality
1 of 55 images have issues
PASS
1 of 55 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
54 image(s) with good alt text
55 images 54 good alt text 1 missing
IssueCount
missing1 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

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

Send Feedback