Skip to content
https://58.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
33
GRADE
F
FIX
9
REVIEW
4
PASS
0
INFO
0
Checks
13
4 REVIEW 9 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
Heading Hierarchy
Action
47 headings, 3 skip(s)
FIX
47 headings, 3 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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::
Heading level skipped: H2 → H6 (missing H3)
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.
  • H2 北京
  • H3 客户
  • H3 商户
  • H3 房产
  • H3 汽车
  • H3 二手
  • H3 宠物
  • H3 招聘
  • H3 同城服务
  • H3 手机应用
  • H2 北京房产我要卖房
  • H2 二手车
  • H4 高价卖车 skipped
  • H2 新车
  • H2 汽车服务
  • H2 教育培训
  • H2 便民服务
  • H2 二手回收金属家具礼品服装
  • H2 二手市场特惠九成新家具
  • H6 家具·家电·车辆家具送货上门 skipped
  • H6 百货·设备  换季衣服便宜清
  • H6 数码·通讯
  • H2 宠物/宠物用品寄养
  • H2 北京招聘北京求职简历招聘会员校园招聘
  • H4 求职神器 央企国企热招 skipped
  • H4 热招职位
  • H2 北京兼职
  • H2 热门行业|场所企业推广
  • H2 求职简历超值简历套餐
  • H2 求职指南
  • H2 票务/卡券
  • H2 到家精选专区
  • H2 休闲娱乐
  • H2 #appDown{display: none}#wubaDaojiaList{display: block;}到家服务
  • H2 热门服务
  • H2 本地服务大全
  • H2 家政服务
  • H2 装修建材
  • H2 商务服务
  • H2 招商加盟
  • H2 婚庆摄影
  • H2 旅游酒店
  • H2 餐饮美食
  • H2 丽人
  • H2 农林牧副渔
  • H2 批发采购
  • H2 健康生活

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

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

F
Alt Text Quality
Action
14 of 18 images have issues
FIX
14 of 18 images have issues
Critical::
14 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
9 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
4 image(s) with good alt text
18 images 4 good alt text 14 missing
IssueCount
missing14 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
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-e9gym2
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://58.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://58.com/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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="key" id="keyword">; <input type="submit" name="button" id="searchbtn">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#keywordtext(none)none
#searchbtnsubmit(none)none

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

<input type="text" name="key" id="keyword">; <input type="submit" name="button" id="searchbtn">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
h2 热门行业|场所
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 商户
2.91:1
#000000
on
#575757
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 手机应用
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport

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
h2 热门行业|场所2.45:13.0:1
#000000
#4C4C4C
Fail
h3 客户16.37:13.0:1
#000000
#CDE7F7
Pass
h3 商户2.91:13.0:1
#000000
#575757
Fail
h3 手机应用2.45:13.0:1
#000000
#4C4C4C
Fail
title 【58同城 58.com…21.00:14.5:1
#000000
#FFFFFF
Pass
a 切换城市21.00:14.5:1
#000000
#FFFFFF
Pass
a 登录21.00:14.5:1
#000000
#FFFFFF
Pass
a 注册12.95:14.5:1
#000000
#FFBBAB
Pass
a 个人中心21.00:14.5:1
#000000
#FFFFFF
Pass
a 我的账户21.00:14.5:1
#000000
#FFFFFF
Pass
a 我的收藏21.00:14.5:1
#000000
#FFFFFF
Pass
a 我的求职21.00:14.5:1
#000000
#FFFFFF
Pass
a 举报中心21.00:14.5:1
#000000
#FFFFFF
Pass
a 商家中心20.65:14.5:1
#000000
#FDFDFD
Pass
a 我的发布16.37:14.5:1
#000000
#CDE7F7
Pass
a 我要招人21.00:14.5:1
#000000
#FFFFFF
Pass
a 账户资料21.00:14.5:1
#000000
#FFFFFF
Pass
a 我的资金16.37:14.5:1
#000000
#CDE7F7
Pass
a 商家推广21.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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 4 failing, 11 passed
REVIEW
72

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.header > div.login > span > a.publish
A(以A为开头的城市名) div.body_div > div.city_box > h4 > p
B(以B为开头的城市名) div.body_div > div.city_box > h4 > p
C(以C为开头的城市名) div.body_div > div.city_box > h4 > p
D(以D为开头的城市名) div.body_div > div.city_box > h4 > p
E(以E为开头的城市名) div.body_div > div.city_box > h4 > p
F(以F为开头的城市名) div.body_div > div.city_box > h4 > p
G(以G为开头的城市名) div.body_div > div.city_box > h4 > p
H(以H为开头的城市名) div.body_div > div.city_box > h4 > p
J(以J为开头的城市名) div.body_div > div.city_box > h4 > p
K(以K为开头的城市名) div.body_div > div.city_box > h4 > p
L(以L为开头的城市名) div.body_div > div.city_box > h4 > p
M(以M为开头的城市名) div.body_div > div.city_box > h4 > p
N(以N为开头的城市名) div.body_div > div.city_box > h4 > p
P(以P为开头的城市名) div.body_div > div.city_box > h4 > p
Q(以Q为开头的城市名) div.body_div > div.city_box > h4 > p
R(以R为开头的城市名) div.body_div > div.city_box > h4 > p
S(以S为开头的城市名) div.body_div > div.city_box > h4 > p
T(以T为开头的城市名) div.body_div > div.city_box > h4 > p
W(以W为开头的城市名) div.body_div > div.city_box > h4 > p
X(以X为开头的城市名) div.body_div > div.city_box > h4 > p
Y(以Y为开头的城市名) div.body_div > div.city_box > h4 > p
Z(以Z为开头的城市名) div.body_div > div.city_box > h4 > p
普通版 div.body_div > div.newFooter > p.footer_nav > a
电脑版 div.body_div > div.newFooter > p.footer_nav > a
客户端 div.body_div > div.newFooter > p.footer_nav > a#gotodownload
手机58网：58.com    京公网备案信息11010502000809 京ICP证060405号 | 京ICP备10012705号-2 body > div.body_div > div.newFooter > p.footer_bot
060405 div.body_div > div.newFooter > p.footer_bot > a
10012705 div.body_div > div.newFooter > p.footer_bot > a

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
body > img body > img
body > img body > img

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

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
●Links are distinguishable without relying on color.
●Links have a discernible name
●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.
●Heading elements appear in a sequentially-descending order
○`[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
○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 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
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback