Skip to content
https://4.cn

Accessibility

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

F
Alt Text Quality
Action
7 of 8 images have issues
FIX
7 of 8 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with good alt text
8 images 1 good alt text 7 missing
IssueCount
missing7 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
11 of 13 controls have issues
FIX
11 of 13 controls have issues
Critical::
8 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="keyword" id="keyword">; <input type="text" name="username" id="username">; <input type="password" name="password" id="password">; <input type="text" name="DomainName">; <input type="text" name="BudgetAmount">; <select name="BudgetCurrency" id="BudgetCurrency">; <input type="checkbox" name="Terms" id="Terms">; <input type="password" name="password">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea name="Comment" id="extraparams">; <input type="text" name="username">; <input type="text" name="Contact" id="Contact">
Info::
2 control(s) properly labeled
13 controls
2 labeled
3 placeholder only
8 unlabeled
ControlTypeLabelMethod
#hasAccount-1radionone
#hasAccount-0radionone
#extraparamstextarea(Please fill in your requirements&budget and leave it to us)placeholder only
usernametext(Your Email / Customer ID:)placeholder only
#Contacttext(Please fill in your phone number or email)placeholder only
#BudgetCurrencyselect(none)none
#keywordtext(none)none
#Termscheckbox(none)none
#usernametext(none)none
#passwordpassword(none)none
DomainNametext(none)none
passwordpassword(none)none
BudgetAmounttext(none)none

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

<input type="text" name="keyword" id="keyword">; <input type="text" name="username" id="username">; <input type="password" name="password" id="password">; <input type="text" name="DomainName">; <input type="text" name="BudgetAmount">; <select name="BudgetCurrency" id="BudgetCurrency">; <input type="checkbox" name="Terms" id="Terms">; <input type="password" name="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.

<textarea name="Comment" id="extraparams">; <input type="text" name="username">; <input type="text" name="Contact" id="Contact">

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

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://4.cn/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://4.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::
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 62/100 — 7 failing, 16 passed
FIX
62

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
Welcome to 4.CN Sign In Create an account body > div#top > div.wrapper > div.fl
Sign In div#top > div.wrapper > div.fl > a.orange
Create an account div#top > div.wrapper > div.fl > a.orange
Top Domains div#top > div.wrapper > div.fr > a.orange
Fee Policies div#top > div.wrapper > div.fr > a
Help Center div#top > div.wrapper > div.fr > a
Contact Us div#top > div.wrapper > div.fr > a
div.search-wrap > form#handleSearch > div.search-text-container > input#keyword div.search-wrap > form#handleSearch > div.search-text-container > input#keyword
BIN Sales div#nav > ul.fl > li > a.buynow-item
Bulk Sales div#nav > ul.fl > li > a.bulk-item
Hot Sales div#nav > ul.fl > li > a.hotsale-item
Live Auction div#nav > ul.fl > li > a.auction-item
Buy Domains div#nav > ul.fl > li > a.buy-domains-item
Sell Domains div#nav > ul.fl > li > a.sell-domains-item
Escrow div#nav > ul.fl > li > a.escrow-item
More >> div.gray-head > h2.head-h2 > span.fr > a.more
Category div.body > ol.list > li.cap > span.category
Listing Price div.body > ol.list > li.cap > span.price
Shopping div.body > ol.list > li > span.category
make offer div.body > ol.list > li > span.price
¥420,000 CNY div.body > ol.list > li > span.price
Uncategoried div.body > ol.list > li > span.category
make offer div.body > ol.list > li > span.price
Acronyms div.body > ol.list > li > span.category
$31,888 USD div.body > ol.list > li > span.price
Computers div.body > ol.list > li > span.category
make offer div.body > ol.list > li > span.price
Category div.body > ol.list > li.cap > span.category
Listing Price div.body > ol.list > li.cap > span.price
Uncategoried div.body > ol.list > li > span.category
make offer div.body > ol.list > li > span.price
Business div.body > ol.list > li > span.category
make offer div.body > ol.list > li > span.price
Uncategoried div.body > ol.list > li > span.category
make offer div.body > ol.list > li > span.price
Uncategoried div.body > ol.list > li > span.category
¥300,000 CNY div.body > ol.list > li > span.price
Uncategoried div.body > ol.list > li > span.category
make offer div.body > ol.list > li > span.price
div.login > form#index_login > div.ftext-wrap > input#username div.login > form#index_login > div.ftext-wrap > input#username
div.login > form#index_login > div.ftext-wrap > input#password div.login > form#index_login > div.ftext-wrap > input#password
Sign In form#index_login > p > button.sub-btn > span
Create an account div.login > form#index_login > p > a.reg_btn
div.entrust-box > dl.clearfix > dd > input.domain-name div.entrust-box > dl.clearfix > dd > input.domain-name
div.entrust-box > dl.clearfix > dd > input.budget div.entrust-box > dl.clearfix > dd > input.budget
I have an account dl.clearfix > dd > label > span
I am a new customer dl.clearfix > dd > label > span
dl.clearfix > dd#loginForm > div.ftext-wrap > input dl.clearfix > dd#loginForm > div.ftext-wrap > input
dl.clearfix > dd#loginForm > div.ftext-wrap > input dl.clearfix > dd#loginForm > div.ftext-wrap > input
Brokerage form#applybrokerage > div.entrust-box > p > a#submit
Time Left div.body > ol#closing_auctions > li.cap > span.time
Current Bid div.body > ol#closing_auctions > li.cap > span.price
Listing Price div.body > ol#featured_hotsale > li.cap > span.price
浙公网安备 33010402000519号 div.wrap > div > a > p

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.fr > span.nav-tool > a > img div.fr > span.nav-tool > a > img
div.fr > span.nav-tool > a > img div.fr > span.nav-tool > a > img
div#footer > div.wrap > a > img div#footer > div.wrap > a > img
div#footer > div.wrap > a > img div#footer > div.wrap > a > img
div#footer > div.wrap > a > img div#footer > div.wrap > a > img
div#footer > div.wrap > a > img div#footer > div.wrap > a > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.search-wrap > form#handleSearch > div.search-text-container > input#keyword div.search-wrap > form#handleSearch > div.search-text-container > input#keyword
div.login > form#index_login > div.ftext-wrap > input#username div.login > form#index_login > div.ftext-wrap > input#username
div.login > form#index_login > div.ftext-wrap > input#password div.login > form#index_login > div.ftext-wrap > input#password
div.entrust-box > dl.clearfix > dd > input.domain-name div.entrust-box > dl.clearfix > dd > input.domain-name
div.entrust-box > dl.clearfix > dd > input.budget div.entrust-box > dl.clearfix > dd > input.budget
dl.clearfix > dd#loginForm > div.ftext-wrap > input dl.clearfix > dd#loginForm > div.ftext-wrap > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CNY USD EUR div.entrust-box > dl.clearfix > dd > select#BudgetCurrency

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#footer > div.wrap > iframe body > div#footer > div.wrap > iframe

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
body > div#footer > div.wrap > a
body > div#footer > div.wrap > a
body > div#footer > div.wrap > a
body > div#footer > div.wrap > 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.

Best practices

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>`
●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
●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
●Touch targets have sufficient size and spacing.
●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
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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
○The page contains a heading, skip link, or landmark region
○ARIA IDs are unique
○No form fields have multiple labels
○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">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`[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.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Hierarchy
5 headings
PASS
5 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 More >>
  • H2 Featured DomainsMore >>
  • H2 Ending Soon AuctionsMore >>
  • H2 Spotlight HotsalesMore >>

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

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
h2 Featured Domains12.55:13.0:1
#000000
#C8C8C8
Pass
h2 Ending Soon Auctions12.55:13.0:1
#000000
#C8C8C8
Pass
h2 Spotlight Hotsales12.55:13.0:1
#000000
#C8C8C8
Pass
title 4.CN - Buy, Sell & P…21.00:14.5:1
#000000
#FFFFFF
Pass
div Welcome to 4.CN21.00:14.5:1
#000000
#FFFFFF
Pass
a Sign In21.00:14.5:1
#000000
#FFFFFF
Pass
a Create an account21.00:14.5:1
#000000
#FFFFFF
Pass
a Top Domains21.00:14.5:1
#000000
#FFFFFF
Pass
a Whois21.00:14.5:1
#000000
#FFFFFF
Pass
a Fee Policies21.00:14.5:1
#000000
#FFFFFF
Pass
a Help Center21.00:14.5:1
#000000
#FFFFFF
Pass
a Contact Us21.00:14.5:1
#000000
#FFFFFF
Pass
strong Search21.00:13.0:1
#000000
#FFFFFF
Pass
div Hot search:21.00:14.5:1
#000000
#FFFFFF
Pass
a Disyllable Pinyin.co…21.00:14.5:1
#000000
#FFFFFF
Pass
a Repeated Disyllable …21.00:14.5:1
#000000
#FFFFFF
Pass
a 2Letters21.00:14.5:1
#000000
#FFFFFF
Pass
a 3Letters.com21.00:14.5:1
#000000
#FFFFFF
Pass
a 3Numbers21.00:14.5:1
#000000
#FFFFFF
Pass
a 4Numbers.com21.00:14.5:1
#000000
#FFFFFF
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