Skip to content
https://sina.com.cn

Accessibility

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

F
Alt Text Quality
Action
66 of 102 images have issues
FIX
66 of 102 images have issues
Critical::
66 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
64 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
36 image(s) with good alt text
102 images 36 good alt text 66 missing
IssueCount
missing66 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
18 of 19 controls have issues
FIX
18 of 19 controls have issues
Critical::
15 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="SerchType" id="slt_01">; <input type="text" name="SerchKey">; <input type="submit" name="SearchSubButton">; <input type="submit" id="J_searchType">; <select name="country" id="SI_Slt_02">; <input type="text" name="q" id="textSuggest">; <input type="submit">; <textarea>; <textarea>; <select name="s_type" id="SI_Slt_04"> (+5 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="loginname">; <input type="password" name="password">; <input type="text" name="vsn">
Info::
1 control(s) properly labeled
19 controls
1 labeled
3 placeholder only
15 unlabeled
ControlTypeLabelMethod
remembercheckboxnone
passwordpassword(请输入密码)placeholder only
vsntext(请输入微盾动态码)placeholder only
loginnametext(微博/博客/邮箱/手机号)placeholder only
#SI_Slt_02select(none)none
#textSuggesttext(none)none
inputsubmit(none)none
textareatextarea(none)none
textareatextarea(none)none
#SI_Slt_04select(none)none
sktext(none)none
inputsubmit(none)none
textareatextarea(none)none
textareatextarea(none)none
#slt_01select(none)none
SerchKeytext(none)none
doortext(none)none
SearchSubButtonsubmit(none)none
#J_searchTypesubmit(none)none

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

<select name="SerchType" id="slt_01">; <input type="text" name="SerchKey">; <input type="submit" name="SearchSubButton">; <input type="submit" id="J_searchType">; <select name="country" id="SI_Slt_02">; <input type="text" name="q" id="textSuggest">; <input type="submit">; <textarea>; <textarea>; <select name="s_type" id="SI_Slt_04"> (+5 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="loginname">; <input type="password" name="password">; <input type="text" name="vsn">

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
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title ҳ��û���ҵ� ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
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::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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 65/100 — 6 failing, 15 passed
FIX
65

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
图集 li.swiper-slide > a.home_banner > h2.swiper-slide_cite > span.sw_mark_txt
点击查看更多 section#j_card_yaowen > section.s_card_it > a > ins.most
查看全部实时热点 section#j_card_tnews > section.s_card > a.j_callST > ins.most
点击查看更多 section#j_card_tnews > section#j_card_miniVideo > a > ins.most
点击查看更多 section#j_card_sports > section.s_card_it > a > ins.most
点击查看更多 section#j_card_ent > section.s_card_it > a > ins.most
点击查看更多 section#j_card_finance > section.s_card_it > a > ins.most
点击查看更多 section#j_card_tech > section.s_card_it > a > ins.most
点击查看更多 section#j_card_auto > section.s_card_it > a > ins.most
点击查看更多 section#j_card_house > section.s_card_it > a > ins.most
点击查看更多 section#j_card_edu > section.s_card_it > a > ins.most
点击查看更多 section#j_card_fashion > section.s_card_it > a > ins.most
点击查看更多 section#j_card_games > section.s_card_it > a > ins.most
导航 footer.ft > address.ft_ad > nav.ft_down > a.ft_down_a
客户端下载 footer.ft > address.ft_ad > nav.ft_down > a.ft_down_a
广告营销 footer.ft > address.ft_ad > nav.ft_down > a.ft_down_a
反馈 footer.ft > address.ft_ad > nav.ft_down > a.ft_down_a
新浪网违法和不良信息举报电话：400-052-0066 main.page_main > footer.ft > address.ft_ad > p.ft_down_p1
违法和不良信息举报中心 footer.ft > address.ft_ad > p.ft_down_p2 > a
(京)网药械信息备字（2024）第 00220 号 main.page_main > footer.ft > address.ft_ad > p.ft_down_p2
Sina.cn(京ICP证000007)  2026-04-17 01:38 main.page_main > footer.ft > address.ft_ad > p.ft_down_p3
Sina.cn(京ICP证000007) footer.ft > address.ft_ad > p.ft_down_p3 > a
打开新浪新闻 body > div#float-btn > div.callUp_btn_txt

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
section#j_card_tnews > div > section#j_card_yaowen > img.j_callST section#j_card_tnews > div > section#j_card_yaowen > img.j_callST
main.page_main > section#j_card_tnews > section#j_card_aichatBanner > img.j_callST main.page_main > section#j_card_tnews > section#j_card_aichatBanner > img.j_callST
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width
div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width div.cm_sw_scroll > div.cm_sw_content > figure.video_con_fig > img.img_width

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 > main.page_main > div.j_sax > iframe body > main.page_main > div.j_sax > iframe
div > section#j_card_yaowen > div#_57da484a61091896PDPS000000057683 > iframe div > section#j_card_yaowen > div#_57da484a61091896PDPS000000057683 > iframe
div > section#j_card_yaowen > div#_ea57590861091896PDPS000000057779 > iframe div > section#j_card_yaowen > div#_ea57590861091896PDPS000000057779 > iframe
section#j_card_tnews > div.s_card_sp_da > div#_a877c81812118577PDPS000000058118 > iframe section#j_card_tnews > div.s_card_sp_da > div#_a877c81812118577PDPS000000058118 > iframe
section#j_card_tnews > div.s_card_sp_da > div#_ec00b82361090701PDPS000000057778 > iframe section#j_card_tnews > div.s_card_sp_da > div#_ec00b82361090701PDPS000000057778 > iframe
section#j_card_sports > section.s_card_it > div#_358a996561091910PDPS000000065801 > iframe section#j_card_sports > section.s_card_it > div#_358a996561091910PDPS000000065801 > iframe
section#j_card_sports > section.s_card_it > div#_e2cf489b61091910PDPS000000060104 > iframe section#j_card_sports > section.s_card_it > div#_e2cf489b61091910PDPS000000060104 > iframe
section#j_card_tnews > div.s_card_sp_da > div#_191b59f761090701PDPS000000057780 > iframe section#j_card_tnews > div.s_card_sp_da > div#_191b59f761090701PDPS000000057780 > iframe
section#j_card_ent > section.s_card_it > div#_65dd7b4161091910PDPS000000065802 > iframe section#j_card_ent > section.s_card_it > div#_65dd7b4161091910PDPS000000065802 > iframe
section#j_card_ent > section.s_card_it > div#_19aec84a61091910PDPS000000057781 > iframe section#j_card_ent > section.s_card_it > div#_19aec84a61091910PDPS000000057781 > 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
div.hd_top_row > div.hd_top_row_template > nav.hd_set > a.hd_s_search div.hd_top_row > div.hd_top_row_template > nav.hd_set > a.hd_s_search
div.hd_top_row > div.hd_top_row_template > nav.hd_set > a#loginBox div.hd_top_row > div.hd_top_row_template > nav.hd_set > a#loginBox
section#j_card_house > section.s_card_it > figure.i_gx2 > a.i_gx2_a section#j_card_house > section.s_card_it > figure.i_gx2 > a.i_gx2_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.

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.

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

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●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
●Document has a main landmark.
●All heading elements contain content.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○`<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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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>`.
○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.
B
Heading Hierarchy
12 headings
REVIEW
12 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 新闻
  • H3 新闻
  • H3 新浪产品
  • H4 车型大全新浪e站
  • H4 车型大全新浪e站
  • 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

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 新闻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 新浪网20.47:14.5:1
#000000
#FCFCFC
Pass
i 设为首页20.13:14.5:1
#000000
#FAFAFB
Pass
i 我的菜单21.00:14.5:1
#000000
#FFFFFF
Pass
i 手机新浪网21.00:14.5:1
#000000
#FFFFFF
Pass
i 移动客户端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 新浪财经7.05:14.5:1
#000000
#979963
Pass
a 黑猫投诉10.84:14.5:1
#000000
#99BFDC
Pass
a 新浪博客7.46:14.5:1
#000000
#66A0CB
Pass
a 新浪众测20.47:14.5:1
#000000
#FCFCFC
Pass
a 新浪邮箱客户…20.12:14.5:1
#000000
#FAFAFA
Pass
a 关闭置顶21.00:14.5:1
#000000
#FFFFFF
Pass
i 登录21.00:14.5:1
#000000
#FFFFFF
Pass
span 您好，21.00:14.5:1
#000000
#FFFFFF
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.

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

Send Feedback