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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
29
GRADE
F
FIX
12
REVIEW
1
PASS
0
INFO
0
Checks
13
1 REVIEW 12 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
88 headings, 8 skip(s)
FIX
88 headings, 8 skip(s)
Warning::
Multiple H1 headings (63 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
7 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 账户服务
  • H2 存款与贷款
  • H2 信用卡
  • H2 外汇业务
  • H2 投资理财
  • H2 私人银行
  • H2 金融市场
  • H1 (empty)
  • H1 业务办理 duplicate H1
  • H1 指南·推荐 duplicate H1
  • H1 (empty)
  • H1 业务办理 duplicate H1
  • H1 指南·推荐 duplicate H1
  • H1 (empty)
  • H1 业务办理 duplicate H1
  • H1 指南·推荐 duplicate H1
  • H1 (empty)
  • H1 业务办理 duplicate H1
  • H1 指南·推荐 duplicate H1
  • H1 (empty)
  • H1 业务办理 duplicate H1
  • H1 指南·推荐 duplicate H1
  • H1 (empty)
  • H1 业务办理 duplicate H1
  • H1 指南·推荐 duplicate H1
  • H1 (empty)
  • H1 业务办理 duplicate H1
  • H1 指南·推荐 duplicate H1
  • H4 工银理财·天天鑫添益 skipped
  • H2 1.23%
  • H1 投资期限　每天开放 duplicate H1
  • H1 起购金额 1 元 | 低风险 | 代销 duplicate H1
  • H1 理财产品过往业绩不代表其未来表现，不等于理财产品实际收益，投资须谨慎。业绩来源：本理财产品过往业绩由产品管理人工银理财有限责任公司基�� duplicate H1
  • H4 工银理财·添利宝鑫享 skipped
  • H2 1.4005%
  • H1 投资期限　无固定期 duplicate H1
  • H1 起购金额 1 元 | 低风险 | 代销 duplicate H1
  • H1 理财产品过往业绩不代表其未来表现，不等于理财产品实际收益，投资须谨慎。业绩来源：本理财产品过往业绩由产品管理人工银理财有限责任公司基�� duplicate H1
  • H1 2026版熊猫金币 duplicate H1
  • H1 大师传世金（珍藏版） duplicate H1
  • H1 如意金积存 duplicate H1
  • H1 个人积存金 duplicate H1
  • H4 工银纯债债券基金A skipped
  • H2 0.4806%
  • H1 推荐理由：优质产品 稳健增长聚焦纯债追求风险收益平衡 duplicate H1
  • H5 万家北证50成份指数型发起式A skipped
  • H2 主要投资行业：制造业、信息传输、软件和信...基金类型：股票型
  • H5 汇添富北交所创新精选两年定开混合A skipped
  • H2 主要投资行业：制造业、信息传输、软件和信...基金类型：混合型
  • H5 财通智慧成长混合C skipped
  • H2 主要投资行业：信息传输、软件和信息技术服...基金类型：混合型
  • H5 大成景阳领先基金 skipped
  • H2 主要投资行业：制造业、交通运输、仓储和邮...基金类型：股票型
  • H1 个人结汇 duplicate H1
  • H1 账户外汇 duplicate H1
  • H1 个人购汇 duplicate H1
  • H1 携带外汇出境许可证 duplicate H1
  • H5 工银安盛人寿盛世相守养老年金保险 skipped
  • H5 工银安盛人寿财富鑫享两全保险（分红型）
  • H5 工银安盛鑫福传家终身寿（2024版）（私银）
  • H5 工银安盛安心保医疗保证续保版（有社保）
  • H1 个人购汇 duplicate H1
  • H1 国际汇款 duplicate H1
  • H1 “汇市通”外汇买卖 duplicate H1
  • H1 个人结汇 duplicate H1
  • H1 外汇存款 duplicate H1
  • H1 账户外汇 duplicate H1
  • H1 客户服务抖音 duplicate H1
  • H1 个人手机银行 duplicate H1
  • H1 企业手机银行 duplicate H1
  • H1 小微融资 duplicate H1
  • H1 创业担保贷款 duplicate H1
  • H1 小企业周转贷款 duplicate H1
  • H1 工银e支付 duplicate H1
  • H1 跨境汇款 duplicate H1
  • H1 余额变动提醒 duplicate H1
  • H1 途牛信用卡 duplicate H1
  • H1 工银无界白金数字卡 duplicate H1
  • H1 工银生肖信用卡 duplicate H1
  • H1 工银速汇 duplicate H1
  • H1 即期结售汇 duplicate H1
  • H1 个人资信证明 duplicate H1
  • H1 融e借 duplicate H1
  • H1 住房公积金贷款 duplicate H1
  • H1 个人家居消费贷款 duplicate H1
  • H1 优惠活动 duplicate H1
  • H1 财政贴息 分期减负 duplicate H1
  • H1 工银爱旅行 随机一分游 duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

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

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

F
Alt Text Quality
Action
69 of 85 images have issues
FIX
69 of 85 images have issues
Critical::
69 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
48 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
16 image(s) with good alt text
85 images 16 good alt text 69 missing
IssueCount
missing69 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

D
Form Accessibility
Action
5 of 5 controls have issues
FIX
5 of 5 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="button">; <input type="button">; <input type="button">; <input id="robotFloatTextQuestion">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="KeyWord" id="KeyWord">
5 controls
0 labeled
1 placeholder only
4 unlabeled
ControlTypeLabelMethod
#KeyWordtext(请输入关键字)placeholder only
inputbutton(none)none
inputbutton(none)none
inputbutton(none)none
#robotFloatTextQuestioninput(none)none

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

<input type="button">; <input type="button">; <input type="button">; <input id="robotFloatTextQuestion">

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="KeyWord" id="KeyWord">

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 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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 53/100 — 10 failing, 15 passed
FIX
53

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
链接，无障碍模式读屏软件服务通道。 body > a#ariaTipText

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body body

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
服务热线 95588　|　隐私保密声明 打开无障碍　|　电脑版 div#webpartdivID33d40ffe-ae42-0e36-5fd0-d49b3e9ddc10 > div.divContent_ONE > div > span.STYLE71

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
body > a#ariaTipText > img body > a#ariaTipText > img
div#headwap > div#icbchead_logo_div > a > img.imright div#headwap > div#icbchead_logo_div > a > img.imright
div#ivsii5 > ul#ifkbkd > li#i1lhpd > img div#ivsii5 > ul#ifkbkd > li#i1lhpd > img
div#ivsii5 > ul#ifkbkd > li#iyft59 > img div#ivsii5 > ul#ifkbkd > li#iyft59 > img
div#ivsii5 > ul#ifkbkd > li#i2atsr > img div#ivsii5 > ul#ifkbkd > li#i2atsr > img
div#iu7ive > ul#irgbrj > li#iqelvw > img div#iu7ive > ul#irgbrj > li#iqelvw > img
div#iu7ive > ul#irgbrj > li#iwg384 > img div#iu7ive > ul#irgbrj > li#iwg384 > img
div#iu7ive > ul#irgbrj > li#i4db4f > img div#iu7ive > ul#irgbrj > li#i4db4f > img
ul#Jl7 > li#isud0m > a.text2sy > img ul#Jl7 > li#isud0m > a.text2sy > img
div#idt2av > ul#i66och > li#i35jkp > img div#idt2av > ul#i66och > li#i35jkp > img
div#idt2av > ul#i66och > li#ihsivu > img div#idt2av > ul#i66och > li#ihsivu > img
div#idt2av > ul#i66och > li#i7mgt9 > img div#idt2av > ul#i66och > li#i7mgt9 > img
div > div > a.data-collecting-sign > img div > div > a.data-collecting-sign > img
div > div > a.data-collecting-sign > img div > div > a.data-collecting-sign > img
div#i2ora6 > ul#iq0ccl > li#i0jcco > img div#i2ora6 > ul#iq0ccl > li#i0jcco > img
div#i2ora6 > ul#iq0ccl > li#ivbr96 > img div#i2ora6 > ul#iq0ccl > li#ivbr96 > img
div#i2ora6 > ul#iq0ccl > li#ivodv6 > img div#i2ora6 > ul#iq0ccl > li#ivodv6 > img
div#i2ora6 > ul#iq0ccl > li#iru8ol > img div#i2ora6 > ul#iq0ccl > li#iru8ol > img
div > div > a.data-collecting-sign > img div > div > a.data-collecting-sign > img
div > div > a.data-collecting-sign > img div > div > a.data-collecting-sign > img
div#idp3qj > ul#imbp9v > li#ihwkbm > img div#idp3qj > ul#imbp9v > li#ihwkbm > img
div#idp3qj > ul#imbp9v > li#i9z25u > img div#idp3qj > ul#imbp9v > li#i9z25u > img
div#idp3qj > ul#imbp9v > li#iowope > img div#idp3qj > ul#imbp9v > li#iowope > img
div#idp3qj > ul#imbp9v > li#itgkyc > img div#idp3qj > ul#imbp9v > li#itgkyc > img
div#i7ccrl > ul#i2tqsl > li#iral1y > img div#i7ccrl > ul#i2tqsl > li#iral1y > img
div#i7ccrl > ul#i2tqsl > li#i9mx6j > img div#i7ccrl > ul#i2tqsl > li#i9mx6j > img
div#i7ccrl > ul#i2tqsl > li#idakn8 > img div#i7ccrl > ul#i2tqsl > li#idakn8 > img
div#i7ccrl > ul#i2tqsl > li#iif30d > img div#i7ccrl > ul#i2tqsl > li#iif30d > img
div#i94vwm > div#iiuiib > a.data-collecting-sign > img div#i94vwm > div#iiuiib > a.data-collecting-sign > img
div#ize8z5 > div#if4b5e > a.data-collecting-sign > img div#ize8z5 > div#if4b5e > a.data-collecting-sign > img
div#i7ccrlv2 > ul#i2tqslv2 > li#iral1yv2 > img div#i7ccrlv2 > ul#i2tqslv2 > li#iral1yv2 > img
div#i7ccrlv2 > ul#i2tqslv2 > li#i9mx6jv2 > img div#i7ccrlv2 > ul#i2tqslv2 > li#i9mx6jv2 > img
div#i7ccrlv2 > ul#i2tqslv2 > li#idakn8v2 > img div#i7ccrlv2 > ul#i2tqslv2 > li#idakn8v2 > img
div#i7ccrlv2 > ul#i2tqslv2 > li#iif30dv2 > img div#i7ccrlv2 > ul#i2tqslv2 > li#iif30dv2 > img
div#webpartdivIDa500a43c-c6e6-7bc7-b42e-d51a23f0a7a6 > div.Box > div#icbc_gg > img div#webpartdivIDa500a43c-c6e6-7bc7-b42e-d51a23f0a7a6 > div.Box > div#icbc_gg > img
div#i3qy3x > ul > li#ip4n7h > img div#i3qy3x > ul > li#ip4n7h > img
div.Box > div#icbc_znwxv2 > a > img div.Box > div#icbc_znwxv2 > a > img
table#8e5be58a6c53e60409b7c603117390d3 > tr > td > img table#8e5be58a6c53e60409b7c603117390d3 > tr > td > img
table#8e5be58a6c53e60409b7c603117390d3 > tr > td > img table#8e5be58a6c53e60409b7c603117390d3 > tr > td > img
table#8e5be58a6c53e60409b7c603117390d3 > tr > td > img table#8e5be58a6c53e60409b7c603117390d3 > tr > td > img
table#927dbccc6f5c5971fa682de9edc9cfd2 > tr > td > img table#927dbccc6f5c5971fa682de9edc9cfd2 > tr > td > img
table#927dbccc6f5c5971fa682de9edc9cfd2 > tr > td > img table#927dbccc6f5c5971fa682de9edc9cfd2 > tr > td > img
table#927dbccc6f5c5971fa682de9edc9cfd2 > tr > td > img table#927dbccc6f5c5971fa682de9edc9cfd2 > tr > td > img
table#2a17dd9e35edb529a6db775d8eae84c4 > tr > td > img table#2a17dd9e35edb529a6db775d8eae84c4 > tr > td > img
table#2a17dd9e35edb529a6db775d8eae84c4 > tr > td > img table#2a17dd9e35edb529a6db775d8eae84c4 > tr > td > img
table#2a17dd9e35edb529a6db775d8eae84c4 > tr > td > img table#2a17dd9e35edb529a6db775d8eae84c4 > tr > td > img
table#b4c3a224189ce306bb130fefa767ffae > tr > td > img table#b4c3a224189ce306bb130fefa767ffae > tr > td > img
table#b4c3a224189ce306bb130fefa767ffae > tr > td > img table#b4c3a224189ce306bb130fefa767ffae > tr > td > img
table#b4c3a224189ce306bb130fefa767ffae > tr > td > img table#b4c3a224189ce306bb130fefa767ffae > tr > td > img
div.divContent_ONE > div > li > img div.divContent_ONE > div > li > img
div.divContent_ONE > div > li > img div.divContent_ONE > div > li > img
div.footer_bg > ul#iod3o5 > li#i8sll8 > img div.footer_bg > ul#iod3o5 > li#i8sll8 > 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
tbody > tr > td > input#txtRobotQuestion tbody > tr > td > input#txtRobotQuestion

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#webpartdivIDc02e386d-2639-7a5f-8f9d-2fa952cb3a3e > div#headwap > div#icbchead_logo_div > a div#webpartdivIDc02e386d-2639-7a5f-8f9d-2fa952cb3a3e > div#headwap > div#icbchead_logo_div > a
div#i5uebm > ul#Jl7 > li#isud0m > a.text2sy div#i5uebm > ul#Jl7 > li#isud0m > a.text2sy
li > div > div > a.data-collecting-sign li > div > div > a.data-collecting-sign
li > div > div > a.data-collecting-sign li > div > div > a.data-collecting-sign
li > div > div > a.data-collecting-sign li > div > div > a.data-collecting-sign
li > div > div > a.data-collecting-sign li > div > div > a.data-collecting-sign
li#ilrbgg > div#i94vwm > div#iiuiib > a.data-collecting-sign li#ilrbgg > div#i94vwm > div#iiuiib > a.data-collecting-sign
li#i6wuel > div#ize8z5 > div#if4b5e > a.data-collecting-sign li#i6wuel > div#ize8z5 > div#if4b5e > a.data-collecting-sign
div#WapMain > div.Box > div#icbc_znwxv2 > a div#WapMain > div.Box > div#icbc_znwxv2 > 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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#webpartdivID33d40ffe-ae42-0e36-5fd0-d49b3e9ddc10 > div.divContent_ONE > div > li div#webpartdivID33d40ffe-ae42-0e36-5fd0-d49b3e9ddc10 > div.divContent_ONE > div > li
div#webpartdivID33d40ffe-ae42-0e36-5fd0-d49b3e9ddc10 > div.divContent_ONE > div > li div#webpartdivID33d40ffe-ae42-0e36-5fd0-d49b3e9ddc10 > div.divContent_ONE > div > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

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
精选理财 li > div > div > a.data-collecting-sign
更多精选 点击拥有 li > div > div > a.data-collecting-sign
稳健持有 li > div > div > a.data-collecting-sign
财富增长 稳健保障 li > div > div > a.data-collecting-sign

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[aria-*]` attributes have valid values
●`[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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●Deprecated ARIA roles were not used
●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
○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 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
○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 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
○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
○`<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
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 18 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 业务办理18.76:13.0:1
#000000
#F2F2F2
Pass
h1 指南·推荐18.76:13.0:1
#000000
#F2F2F2
Pass
h1 业务办理3.72:13.0:1
#000000
#CF0D18
Pass
h1 指南·推荐3.72:13.0:1
#000000
#CF0D18
Pass
h1 业务办理3.72:13.0:1
#000000
#CF0D18
Pass
h1 指南·推荐3.72:13.0:1
#000000
#CF0D18
Pass
h1 业务办理3.72:13.0:1
#000000
#CF0D18
Pass
h1 指南·推荐3.72:13.0:1
#000000
#CF0D18
Pass
h1 业务办理3.72:13.0:1
#000000
#CF0D18
Pass
h1 指南·推荐3.72:13.0:1
#000000
#CF0D18
Pass
h1 业务办理3.72:13.0:1
#000000
#CF0D18
Pass
h1 指南·推荐3.72:13.0:1
#000000
#CF0D18
Pass
h1 业务办理3.72:13.0:1
#000000
#CF0D18
Pass
h1 指南·推荐3.72:13.0:1
#000000
#CF0D18
Pass
h1 投资期限3.72:13.0:1
#000000
#CF0D18
Pass
h1 起购金额3.72:13.0:1
#000000
#CF0D18
Pass
h1 元 | 低风险 | …3.72:13.0:1
#000000
#CF0D18
Pass
h1 业绩来源：3.72:13.0:1
#000000
#CF0D18
Pass
h1 投资期限3.72:13.0:1
#000000
#CF0D18
Pass
h1 起购金额3.72:13.0:1
#000000
#CF0D18
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