Skip to content
https://22.cn

Accessibility

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

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
Alt Text Quality
Action
67 of 80 images have issues
FIX
67 of 80 images have issues
Critical::
67 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
39 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
12 image(s) with good alt text
80 images 12 good alt text 67 missing
IssueCount
missing67 image(s)
too long1 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
31 of 31 controls have issues
FIX
31 of 31 controls have issues
Critical::
28 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" id="searchWrapBtn">; <input type="checkbox" id="domainsuffix_com">; <input type="checkbox" id="domainsuffix_cn">; <input type="checkbox" id="domainsuffix_net">; <input type="checkbox" id="domainsuffix_com_cn">; <input type="checkbox" id="domainsuffix_cc">; <input type="checkbox" id="domainsuffix_club">; <input type="checkbox" id="domainsuffix_me">; <input type="checkbox" id="domainsuffix_shop">; <input type="checkbox" id="domainsuffix_中国"> (+18 more)
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input id="searchPanelInput">; <input type="text">; <textarea>
31 controls
0 labeled
3 placeholder only
28 unlabeled
ControlTypeLabelMethod
#searchPanelInputinput(请输入关键字,如22/22.cn)placeholder only
inputtext(请输入您要查询的域名)placeholder only
textareatextarea(请输入您的问题,使用 Shift + Enter 换行。)placeholder only
#domainsuffix_comcheckbox(none)none
#domainsuffix_cncheckbox(none)none
#domainsuffix_netcheckbox(none)none
#domainsuffix_com_cncheckbox(none)none
#domainsuffix_cccheckbox(none)none
#domainsuffix_clubcheckbox(none)none
#domainsuffix_mecheckbox(none)none
#domainsuffix_shopcheckbox(none)none
#domainsuffix_中国checkbox(none)none
#domainsuffix_vipcheckbox(none)none
#domainsuffix_ltdcheckbox(none)none
#domainsuffix_linkcheckbox(none)none
#domainsuffix_fitcheckbox(none)none
#domainsuffix_workcheckbox(none)none
#domainsuffix_mobicheckbox(none)none
#domainsuffix_storecheckbox(none)none
#domainsuffix_sitecheckbox(none)none
#domainsuffix_infocheckbox(none)none
#domainsuffix_groupcheckbox(none)none
#domainsuffix_bizcheckbox(none)none
#domainsuffix_asiacheckbox(none)none
#domainsuffix_tvcheckbox(none)none
#domainsuffix_网络checkbox(none)none
#domainsuffix_公司checkbox(none)none
#radio-all-indexradio(none)none
#radio-notall-indexradio(none)none
#radio-n-indexradio(none)none
#searchWrapBtnbutton(none)none

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

<input type="button" id="searchWrapBtn">; <input type="checkbox" id="domainsuffix_com">; <input type="checkbox" id="domainsuffix_cn">; <input type="checkbox" id="domainsuffix_net">; <input type="checkbox" id="domainsuffix_com_cn">; <input type="checkbox" id="domainsuffix_cc">; <input type="checkbox" id="domainsuffix_club">; <input type="checkbox" id="domainsuffix_me">; <input type="checkbox" id="domainsuffix_shop">; <input type="checkbox" id="domainsuffix_中国"> (+18 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 id="searchPanelInput">; <input type="text">; <textarea>

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
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-f97uki
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.

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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://22.cn/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://22.cn/manifest.json

Manifest contains invalid JSON.

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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
B
Heading Hierarchy
174 headings
REVIEW
174 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 最新公告 (3条未读)
  • H4 域名注册
  • H4 预订竞价
  • H5 域名预订
  • H5 域名竞价
  • H4 交易中心
  • H5 淘域名
  • H5 域名拍卖
  • H5 域名中介
  • H5 域名代购
  • H4 云服务
  • H5 网站建设
  • H5 云虚拟主机
  • H5 云服务器
  • H4 SSL证书
  • H4 商标注册
  • H4 更多服务
  • H3 域名注册常见问题
  • H3 网络品牌保护
  • H3 域名相关服务
  • H3 新顶级域名
  • H3 国内域名
  • H3 国际域名
  • H3 域名预订指南
  • H3 域名竞价拍卖
  • H3 过期释放预订
  • H3 域名交易中心常见问题
  • H3 微闪拍
  • H3 经纪.中介
  • H3 平台一口价
  • H3 域名拍卖
  • H3 商标交易
  • H3 版权登记
  • H3 专利申请
  • H3 法律服务
  • H3 商标服务
  • H3 商标查询
  • H3 商标注册
  • H3 精选分类
  • H3 商标交易
  • H3 更多服务
  • H3 网站代建
  • H3 行业方案
  • H3 自助建站
  • H3 云虚拟机常见问题
  • H3 主机管理
  • H3 云服务器
  • H3 证书帮助
  • H3 证书服务
  • H3 证书品牌
  • H3 证书类型
  • H3 域名类型
  • H3 ePower引擎
  • H3 爱名市场
  • H4 .com
  • H4 .cn
  • H4 .net
  • H4 .com.cn
  • H4 .cc
  • H4 .club
  • H4 .me
  • H4 .shop
  • H4 .中国
  • H4 .vip
  • H4 .ltd
  • H4 .link
  • H4 .fit
  • H4 .work
  • H4 .mobi
  • H4 .store
  • H4 .site
  • H4 .info
  • H4 .group
  • H4 .biz
  • H4 .asia
  • H4 .tv
  • H4 .网络
  • H4 .公司
  • H3 [资讯]
  • H3 [公告]
  • H3 热门预订推荐
  • H3 热门竞价推荐
  • H3 即将结束的竞价
  • H3 平价好名推荐
  • H3 精品拍卖推荐
  • H3 即将结束的拍卖
  • H3 商标注册
  • H3 保姆注册
  • H3 普通注册
  • H3 国际商标
  • H3 商标服务
  • H3 商标续展
  • H3 商标驳回复审
  • H3 商标转让
  • H3 版权服务
  • H3 软件著作权
  • H3 美术著作权
  • H3 文字著作权
  • H3 保姆注册
  • H3 普通注册
  • H3 国际商标
  • H3 商标续展
  • H3 商标驳回复审
  • H3 商标转让
  • H3 软件著作权
  • H3 美术著作权
  • H3 文字著作权
  • H3 数字化网站建设
  • H3 基础网站版
  • H3 门户网站版
  • H3 门户网站版
  • H3 网站代建服务
  • H3 企业、个人网站建设服务
  • H3 商城网站建设服务
  • H3 商城小程序建设服务
  • H3 内容生产服务
  • H3 短视频剪辑
  • H3 原创软文撰写
  • H3 网站关键词优化
  • H3 基础网站版
  • H3 门户网站版
  • H3 商城网站版
  • H3 企业、个人网站建设服务
  • H3 商城网站建设服务
  • H3 商城小程序建设服务
  • H3 短视频剪辑
  • H3 原创软文撰写
  • H3 网站关键词优化
  • H3 云虚拟主机-共享经济版2G
  • H3 国内共享经济版2G
  • H3 云虚拟主机-独享普惠版2G
  • H3 国内独享普惠版2G
  • H3 云虚拟主机-独享专业版4G
  • H3 国内独享专业版4G
  • H3 云服务器-入门型
  • H3 入门型
  • H3 云服务器-标准型
  • H3 标准型
  • H3 云服务器-商务型
  • H3 商务型
  • H3 云服务器-入门型
  • H3 云服务器-标准型
  • H3 云服务器-商务型
  • H3 SSL热销产品
  • H3 域名型 单域名 DV
  • H3 域名型 多域名 DV
  • H3 域名型 通配符 DV
  • H3 企业级证书推荐
  • H3 企业型 单域名 EV
  • H3 企业型 多域名 OV
  • H3 企业型 通配符 OV
  • H3 证书省心装服务
  • H3 DV型证书省心装服务
  • H3 OV型证书省心装服务
  • H3 EV型证书省心装服务
  • H3 域名型 单域名 DV
  • H3 域名型 多域名 DV
  • H3 域名型 通配符 DV
  • H3 企业型 单域名 EV
  • H3 企业型 多域名 OV
  • H3 企业型 通配符 OV
  • H3 DV型证书省心装服务
  • H3 OV型证书省心装服务
  • H3 EV型证书省心装服务
  • H3 可信品牌 值得信赖
  • H3 域名交易 屈指可数
  • H3 商标注册 全国前十
  • H3 生态完整 高性价比
  • H3 安全可靠 专业守护
  • H3 解析快速 稳定可靠
  • H3 域名资讯我要爆料更多>>
  • H3 帮助知识更多>>
  • 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

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 6 failing, 22 passed
REVIEW
75

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
div.main-container > div.banner-search > div.search-input > input.search-text div.main-container > div.banner-search > div.search-input > input.search-text
4月域名促销,注册15元起 div.flex-viewport > ul.slides > li.activity-list > a.hui
499 div.text > div.text-list > div.price > span.font-18
300 div.text > div.text-list > div.price > span.font-18
2700 div.text > div.text-list > div.price > span.font-18
350 div.text > div.text-list > div.price > span.font-18
800 div.text > div.text-list > div.price > span.font-18
2200 div.text > div.text-list > div.price > span.font-18
20G免费网络防御 div.text > div.text-list > p > span.redt
230 div.text > div.text-list > div.price > span.font-18
20G免费网络防御 div.text > div.text-list > p > span.redt
472 div.text > div.text-list > div.price > span.font-18
20G免费网络防御 div.text > div.text-list > p > span.redt
1268 div.text > div.text-list > div.price > span.font-18
190 div.text > div.text-list > div.price > span.font-18
500 div.text > div.text-list > div.price > span.font-18
1000 div.text > div.text-list > div.price > span.font-18

These are opportunities to improve the legibility of your content.

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.menu-logo-content > div.logo > a > img.hidden-lg div.menu-logo-content > div.logo > a > img.hidden-lg
div.menu-logo-content > div > a > img.hidden-lg div.menu-logo-content > div > a > img.hidden-lg
ul.slides > li > a > img.visible-xs ul.slides > li > a > img.visible-xs
ul.slides > li.flex-active-slide > a > img.visible-xs ul.slides > li.flex-active-slide > a > img.visible-xs
ul.slides > li > a > img.visible-xs ul.slides > li > a > img.visible-xs
ul.slides > li > a > img.visible-xs ul.slides > li > a > img.visible-xs
ul.slides > li > a > img.visible-xs ul.slides > li > a > img.visible-xs
ul.slides > li.activity-list > a > img ul.slides > li.activity-list > a > img
ul.slides > li.activity-list > a > img ul.slides > li.activity-list > a > img
ul.slides > li.activity-list > a > img ul.slides > li.activity-list > a > img
ul.slides > li.activity-list > a > img ul.slides > li.activity-list > a > img
div.col-md-4 > div.about-domain > div.about-domain-img > img div.col-md-4 > div.about-domain > div.about-domain-img > img
div.col-md-4 > div.about-domain > div.about-domain-img > img div.col-md-4 > div.about-domain > div.about-domain-img > img
div.col-md-4 > div.about-domain > div.about-domain-img > img div.col-md-4 > div.about-domain > div.about-domain-img > img
div.col-md-4 > div.about-domain > div.about-domain-img > img div.col-md-4 > div.about-domain > div.about-domain-img > img
div.col-md-4 > div.about-domain > div.about-domain-img > img div.col-md-4 > div.about-domain > div.about-domain-img > img
div.col-md-4 > div.about-domain > div.about-domain-img > img div.col-md-4 > div.about-domain > div.about-domain-img > img
li > div.promise-thumb > div.thumb-container > img li > div.promise-thumb > div.thumb-container > img
li > div.promise-thumb > div.thumb-container > img li > div.promise-thumb > div.thumb-container > img
li > div.promise-thumb > div.thumb-container > img li > div.promise-thumb > div.thumb-container > img
li > div.promise-thumb > div.thumb-container > img li > div.promise-thumb > div.thumb-container > img
li > div.promise-thumb > div.thumb-container > img li > div.promise-thumb > div.thumb-container > img
li > div.promise-thumb > div.thumb-container > img li > div.promise-thumb > div.thumb-container > img
div.main-container > div > a > img div.main-container > div > a > 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.menu-content > div.menu-logo-content > div.logo > a div.menu-content > div.menu-logo-content > div.logo > a
div.flex-viewport > ul.slides > li > a div.flex-viewport > ul.slides > li > a
div.flex-viewport > ul.slides > li > a div.flex-viewport > ul.slides > li > a
div.flex-viewport > ul.slides > li.flex-active-slide > a div.flex-viewport > ul.slides > li.flex-active-slide > a
div.flex-viewport > ul.slides > li.flex-active-slide > a div.flex-viewport > ul.slides > li.flex-active-slide > a
div.flex-viewport > ul.slides > li > a div.flex-viewport > ul.slides > li > a
div.flex-viewport > ul.slides > li > a div.flex-viewport > ul.slides > li > a
div.flex-viewport > ul.slides > li > a div.flex-viewport > ul.slides > li > a
div.flex-viewport > ul.slides > li > a div.flex-viewport > ul.slides > li > a
div.flex-viewport > ul.slides > li > a div.flex-viewport > ul.slides > li > a
div.flex-viewport > ul.slides > li > a div.flex-viewport > ul.slides > li > a
div.flex-viewport > ul.slides > li.activity-list > a div.flex-viewport > ul.slides > li.activity-list > a
div.flex-viewport > ul.slides > li.activity-list > a div.flex-viewport > ul.slides > li.activity-list > a
div.flex-viewport > ul.slides > li.activity-list > a div.flex-viewport > ul.slides > li.activity-list > a
div.flex-viewport > ul.slides > li.activity-list > a div.flex-viewport > ul.slides > li.activity-list > a
div.activity > ul.flex-direction-nav > li.flex-nav-prev > a.flex-prev div.activity > ul.flex-direction-nav > li.flex-nav-prev > a.flex-prev
div.activity > ul.flex-direction-nav > li.flex-nav-next > a.flex-next div.activity > ul.flex-direction-nav > li.flex-nav-next > a.flex-next
div.customer-scroll > ul.flex-direction-nav > li.flex-nav-prev > a.flex-prev div.customer-scroll > ul.flex-direction-nav > li.flex-nav-prev > a.flex-prev
div.customer-scroll > ul.flex-direction-nav > li.flex-nav-next > a.flex-next div.customer-scroll > ul.flex-direction-nav > li.flex-nav-next > a.flex-next
body > div#layui-layer1 > span.layui-layer-setwin > a.layui-layer-ico body > div#layui-layer1 > span.layui-layer-setwin > a.layui-layer-ico

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.activity > ul.flex-direction-nav > li.flex-nav-prev > a.flex-prev div.activity > ul.flex-direction-nav > li.flex-nav-prev > a.flex-prev
div.activity > ul.flex-direction-nav > li.flex-nav-next > a.flex-next div.activity > ul.flex-direction-nav > li.flex-nav-next > a.flex-next

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Form elements have associated labels
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
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
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
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.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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 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
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 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
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
`<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.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 最新公告19.95:13.0:1
#000000
#F9F9F9
Pass
h3 热门预订推荐19.95:13.0:1
#000000
#F9F9F9
Pass
h3 热门竞价推荐19.95:13.0:1
#000000
#F9F9F9
Pass
h3 即将结束的竞…19.95:13.0:1
#000000
#F9F9F9
Pass
h3 平价好名推荐19.95:13.0:1
#000000
#F9F9F9
Pass
h3 精品拍卖推荐19.95:13.0:1
#000000
#F9F9F9
Pass
h3 即将结束的拍…19.95:13.0:1
#000000
#F9F9F9
Pass
h3 商标注册19.95:13.0:1
#000000
#F9F9F9
Pass
h3 保姆注册19.95:13.0:1
#000000
#F9F9F9
Pass
h3 普通注册19.95:13.0:1
#000000
#F9F9F9
Pass
h3 国际商标19.95:13.0:1
#000000
#F9F9F9
Pass
h3 商标服务19.95:13.0:1
#000000
#F9F9F9
Pass
h3 商标续展19.95:13.0:1
#000000
#F9F9F9
Pass
h3 商标驳回复审19.95:13.0:1
#000000
#F9F9F9
Pass
h3 商标转让19.95:13.0:1
#000000
#F9F9F9
Pass
h3 版权服务19.95:13.0:1
#000000
#F9F9F9
Pass
h3 软件著作权19.95:13.0:1
#000000
#F9F9F9
Pass
h3 美术著作权19.95:13.0:1
#000000
#F9F9F9
Pass
h3 文字著作权19.95:13.0:1
#000000
#F9F9F9
Pass
h3 保姆注册19.95:13.0:1
#000000
#F9F9F9
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