Skip to content
https://xinnet.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
36
GRADE
F
FIX
11
REVIEW
2
PASS
0
INFO
0
Checks
13
2 REVIEW 11 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
Heading Hierarchy
Action
36 headings, 2 skip(s)
FIX
36 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 全部产品
  • H5 热门产品 skipped
  • H5 域名
  • H5 企业服务
  • H5 云计算
  • H5 云安全
  • H4 1元买热门后缀
  • H4 1元试用90天
  • H4 1元购50个邮箱账号
  • H3 (empty)
  • H4 域名注册
  • H4 免费试用
  • H4 SSL证书
  • H4 域名交易
  • H4 企业型虚机
  • H3 明星产品推荐
  • H3 稳定、安全、可信赖的云产品
  • H4 虚拟主机
  • H4 邮箱
  • H4 云主机
  • H4 企业建站
  • H3 专业机构的权威认证
  • H4 为超过 1000万 个域名提供注册服务
  • H4 2023 年度影响力 注册平台
  • H4 五星级 域名注册服务机构
  • H4 累计超 27万 网站使用新网服务器
  • H3 优质合作伙伴
  • H4 售前咨询电话
  • H4 售前咨询
  • H4 域名信息查询（WHOIS）
  • H4 售后咨询 (7*24小时)
  • H4 售前咨询电话
  • H4 提示
  • H2 商品已成功加入购物车
  • H4 电话咨询，获取超值优惠 skipped
  • 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

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

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

D
Alt Text Quality
Action
2 of 112 images have issues
FIX
2 of 112 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
106 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
112 images 4 good alt text 106 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

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
Form Accessibility
Action
14 of 14 controls have issues
FIX
14 of 14 controls have issues
Critical::
11 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea id="temp-new-sydh-domain">; <textarea id="temp-new-sydh-cloud">; <textarea id="temp-new-sydh-service">; <textarea id="temp-new-sydh-hot">; <textarea id="temp-new-sydh-safe">; <textarea id="temp-new-syceiling">; <textarea id="temp-new-cummerbund-1">; <textarea id="temp-new-cummerbund-2">; <textarea id="temp-new-cummerbund-3">; <textarea id="temp-new-sy-operation"> (+1 more)
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="prefix" id="prefix">; <input type="text" id="suffixSearchInput">; <input type="text" name="brank" id="brandQueryInput">
14 controls
0 labeled
3 placeholder only
11 unlabeled
ControlTypeLabelMethod
#prefixtext(请输入域名查询，如：xinnet)placeholder only
#suffixSearchInputtext(搜索后缀)placeholder only
#brandQueryInputtext(请输入您想检索的商标名称、申请号、申请人名称)placeholder only
#temp-new-sydh-hottextarea(none)none
#temp-new-sydh-safetextarea(none)none
#temp-new-syceilingtextarea(none)none
#temp-new-sydh-domaintextarea(none)none
#temp-new-sydh-cloudtextarea(none)none
#temp-new-sydh-servicetextarea(none)none
#temp-new-cummerbund-1textarea(none)none
#temp-new-cummerbund-2textarea(none)none
#temp-new-cummerbund-3textarea(none)none
#temp-new-sy-operationtextarea(none)none
#temp-new-floattextarea(none)none

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

<textarea id="temp-new-sydh-domain">; <textarea id="temp-new-sydh-cloud">; <textarea id="temp-new-sydh-service">; <textarea id="temp-new-sydh-hot">; <textarea id="temp-new-sydh-safe">; <textarea id="temp-new-syceiling">; <textarea id="temp-new-cummerbund-1">; <textarea id="temp-new-cummerbund-2">; <textarea id="temp-new-cummerbund-3">; <textarea id="temp-new-sy-operation"> (+1 more)

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="prefix" id="prefix">; <input type="text" id="suffixSearchInput">; <input type="text" name="brank" id="brandQueryInput">

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
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 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.
D
Lighthouse Accessibility Audits
Action
Score 53/100 — 5 failing, 7 passed
FIX
53

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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#app-main > div.product > div.item > img.bgImg div#app-main > div.product > div.item > img.bgImg
div#app-main > div.product > div.item > img.bgImg div#app-main > div.product > div.item > img.bgImg
div#app-main > div.product > div.item > img.bgImg div#app-main > div.product > div.item > img.bgImg
div.footer > div.row2 > a > img.gaIcon div.footer > div.row2 > a > img.gaIcon

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#app-header > div.van-row > div.col1 > a.logo div#app-header > div.van-row > div.col1 > a.logo
div#app-header > div.van-row > div.col2 > a.account div#app-header > div.van-row > div.col2 > a.account

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>`
●Form elements have associated labels
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●Touch targets have sufficient size and spacing.
●The page contains a heading, skip link, or landmark region
●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 a valid value for its `[lang]` attribute
○`<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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 新网404页面 - 新网数码 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
a 云计算
2.22:1
#000000
on
#2B476C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

1 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
h2 商品已成功加…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 全部产品17.47:13.0:1
#000000
#DEECF9
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
title 云服务器_网站…21.00:14.5:1
#000000
#FFFFFF
Pass
span 产品分类21.00:14.5:1
#000000
#FFFFFF
Pass
a 热门产品17.84:14.5:1
#000000
#E2EEFA
Pass
a 域名18.01:14.5:1
#000000
#E3EFFB
Pass
a 企业服务18.14:14.5:1
#000000
#E4F0FA
Pass
a 云计算2.22:14.5:1
#000000
#2B476C
Fail
a 云安全18.16:14.5:1
#000000
#E4F0FB
Pass
div 热门产品9.49:14.5:1
#000000
#AAAFB3
Pass
a 域名注册18.04:14.5:1
#000000
#E4EFFB
Pass
em HOT18.32:14.5:1
#000000
#E5F1FC
Pass
a 域名交易18.35:14.5:1
#000000
#E6F1FC
Pass
em NEW18.19:14.5:1
#000000
#E5F0FB
Pass
a 域名转入18.39:14.5:1
#000000
#E7F1FC
Pass
a SSL证书18.22:14.5:1
#000000
#E6F0FB
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