Skip to content
https://sohu.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Alt Text Quality
Action
61 of 150 images have issues
FIX
61 of 150 images have issues
Critical::
60 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
60 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with generic alt text
Info::
15 decorative image(s) correctly marked
Info::
74 image(s) with good alt text
150 images 74 good alt text 15 decorative 1 generic 60 missing
IssueCount
missing60 image(s)
generic1 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
HTTP 502, bare page
FIX
HTTP 502, bare page
Warning::
Unexpected status code: HTTP 502
Expected HTTP 404 but received 502. This may confuse search engine crawlers.
Got: HTTP 502
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 502 ✗Page Title 502 Bad Gateway ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 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
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 header NAV MAIN (missing!) CONTENTINFO footer

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

B
Heading Hierarchy
7 headings
REVIEW
7 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H4 北京电影节开幕式红毯：高圆圆舒淇好美，高叶造型亮眼，尹正瘦了
  • H3 条件选车更多筛选 >
  • H4 爆笑来袭！赵本山宋小宝师徒合作，观众根本扛不住
  • H4 杯子给到周深后，他一个动作引白鹿爆笑不止，“坏”的太明显！
  • H4 “盘腿抱灯柱”挑战爆火，医生：非要模仿的话，请带上朋友救你
  • H4 4岁男孩自我介绍完就开始出题，主持人想说话都插不进去
  • 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

C
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="search-input" id="search-input">; <input type="text">; <input type="text">; <input type="text">
4 controls
0 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#search-inputtext(none)none
inputtext(none)none
inputtext(none)none
inputtext(none)none

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

<input type="text" name="search-input" id="search-input">; <input type="text">; <input type="text">; <input type="text">

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

B
Favicon & Branding
12 icon(s) detected
REVIEW
12 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
title 搜狐
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
div 添加
1.02:1
#000000
on
#110000
needs 4.5:1 (normal text)
16px · above the fold
span 搜狐网首页
1.02:1
#000000
on
#0F0001
needs 4.5:1 (normal text)
16px · above the fold
div 网页至浏览器收藏夹
2.46:1
#000000
on
#634637
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
h3 条件选车21.00:13.0:1
#000000
#FFFFFF
Pass
title 搜狐1.32:14.5:1
#000000
#222222
Fail
a 无障碍21.00:14.5:1
#000000
#FFFFFF
Pass
a 关怀版19.95:14.5:1
#000000
#F9F9F9
Pass
div 设为默认首页21.00:14.5:1
#000000
#FFFFFF
Pass
a 下载APP21.00:14.5:1
#000000
#FFFFFF
Pass
a 登录21.00:14.5:1
#000000
#FFFFFF
Pass
div 关闭皮肤21.00:14.5:1
#000000
#FFFFFF
Pass
div 添加1.02:14.5:1
#000000
#110000
Fail
span 搜狐网首页1.02:14.5:1
#000000
#0F0001
Fail
div 网页至浏览器…2.46:14.5:1
#000000
#634637
Fail
div [ctrl\command+D] 添…20.37:14.5:1
#000000
#FFFBF5
Pass
div 30天不再提示20.37:14.5:1
#000000
#FFFBF5
Pass
a 搜狐首页21.00:14.5:1
#000000
#FFFFFF
Pass
div 搜狐号21.00:14.5:1
#000000
#FFFFFF
Pass
strong 新闻21.00:13.0:1
#000000
#FFFFFF
Pass
a 军事21.00:14.5:1
#000000
#FFFFFF
Pass
a 专题21.00:14.5:1
#000000
#FFFFFF
Pass
strong 财经21.00:13.0: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.

A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: 搜狐首页
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: minimal-ui
PWA Install Criteria ✓ Installable
Name 搜狐首页 ✓192×192 icon ✓512×512 icon ✓Start URL https://www.sohu.com?_trans_=000012_pckjyy&from=home ✓Display Mode minimal-ui ✓
Name 搜狐首页 Display Mode minimal-ui Theme Color #141416 Background Color #ffffff Icons 5 icon(s)
A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 21 passed
PASS
91

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.header-box > a.header-search > section.header-query
4055.55 +28.34 div.stock_hqnew > div#FT_index > a > span.e1
股票搜索 li.stock_s1 > form#searchForm > i.stock_txt > input.stock_kw
查行情 div.stock_search > ul > li.stock_s2 > a#smtbtn
查看更多 div.content-left > div#RecommendFeed > div.recommend-more > button.recommend-more-btn
Copyright © 2026 Sohu All Rights Reserved div.content-left > div.cbd-plate > footer.copyright > p
京ICP证030367号 div.content-left > div.cbd-plate > footer.copyright > a
搜狐公司 版权所有 div.content-left > div.cbd-plate > footer.copyright > p.company-font

These are opportunities to improve the legibility of your content.

Names and labels

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
div.f > div > div > iframe div.f > div > div > iframe
div.f > div > div > iframe div.f > div > div > iframe
a.anchor-el > div > div > iframe a.anchor-el > div > div > iframe

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.

○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Document has a main landmark.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○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 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.
○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.
○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