Skip to content
https://www.gov.cn

Accessibility

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

D
Heading Hierarchy
Action
26 headings, 1 skip(s)
FIX
26 headings, 1 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::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 习近平同莫桑比克总统查波会谈
  • H2 习近平同莫桑比克总统查波会谈
  • H4 习近平同莫桑比克总统查波会谈 skipped
  • H4 习近平会见老挝人民革命党中央总书记、国家主席特使沙伦赛
  • H4 一季度服务业增加值占国内生产总值比重为61.7%
  • H2 要闻
  • H2 最新政策
  • H3 国务院政策文件库
  • H2 政策解读
  • H2 政务联播
  • H3 建言征集 | 回应关切
  • H2 (empty)
  • H3 以人民为中心
  • H2 为民服务 更多 >>
  • H3 激发市场活力
  • H2 为企服务 更多 >>
  • H3 加强政府自身建设
  • H2 政务联播
  • H2 政策解读
  • H2 国务院政策文件库
  • H2 (empty)
  • 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

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
34 of 50 images have issues
FIX
34 of 50 images have issues
Critical::
34 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
31 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
16 decorative image(s) correctly marked
50 images 16 decorative 34 missing
IssueCount
missing34 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::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="headSearchword">; <input type="btn">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="headSearchword">; <input>; <input type="text">
5 controls
0 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
headSearchwordtext(请输入关键字……)placeholder only
inputinput(搜政策......)placeholder only
inputtext(搜政策......)placeholder only
headSearchwordtext(none)none
inputbtn(none)none

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

<input type="text" name="headSearchword">; <input type="btn">

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="headSearchword">; <input>; <input type="text">

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
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::
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
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 60/100 — 9 failing, 15 passed
FIX
60

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
EN div.main > div.header > div.container > a.lang

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
习近平同莫桑比克总统查波会谈 div.slidesjs-container > div.slidesjs-control > div.item > h4

These are opportunities to improve keyboard navigation in your application.

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.header > div.container > a.logo > img div.header > div.container > a.logo > img
div.header > div.container > a.logo > img.wordlogo div.header > div.container > a.logo > img.wordlogo
div.item > div.pic > a > img div.item > div.pic > a > img
div.item > div.pic > a > img div.item > div.pic > a > img
div.item > div.pic > a > img div.item > div.pic > a > img
div.ctx > div.item > a.more > img div.ctx > div.item > a.more > img
div.banner > div.gwygzjxs_banner > a > img div.banner > div.gwygzjxs_banner > a > img
div.ctx > div.item > a.more > img div.ctx > div.item > a.more > img
div.tabs > div.policyImg > a > img div.tabs > div.policyImg > a > img
div.ctx > div.item > a.more > img div.ctx > div.item > a.more > img
div.box > div.search > a > img div.box > div.search > a > img
div.state > h2 > a > img div.state > h2 > a > img
div.swiper-wrapper > div.swiper-slide > a > img div.swiper-wrapper > div.swiper-slide > a > img
div.ctx > div.item > a.more > img div.ctx > div.item > a.more > img
div.container > div.banner > a > img div.container > div.banner > a > img
div.newfooter > div.box > a.left > img#imgConac div.newfooter > div.box > a.left > img#imgConac

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.main > div.header > div.container > a.logo div.main > div.header > div.container > a.logo
div.main > div.header > div.container > a#searchBtn div.main > div.header > div.container > a#searchBtn
div.slidesjs-control > div.item > div.pic > a div.slidesjs-control > div.item > div.pic > a
div.slidesjs-control > div.item > div.pic > a div.slidesjs-control > div.item > div.pic > a
div.slidesjs-control > div.item > div.pic > a div.slidesjs-control > div.item > div.pic > a
div.container > div.banner > div.gwygzjxs_banner > a div.container > div.banner > div.gwygzjxs_banner > a
div.news > div.tabs > div.policyImg > a div.news > div.tabs > div.policyImg > a
div.container > div.state > h2 > a div.container > div.state > h2 > a
div.swiper-container > div.swiper-wrapper > div.swiper-slide > a div.swiper-container > div.swiper-wrapper > div.swiper-slide > a
div.main > div.container > div.banner > a div.main > div.container > div.banner > a
div.container > div.newfooter > div.box > a.left div.container > div.newfooter > div.box > a.left

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
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 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
●Form elements have associated labels
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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.
○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
○Image elements do not have `[alt]` attributes that are redundant text.
○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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 中国政府网 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
a 无障碍
3.69:1
#000000
on
#CE0B1B
needs 4.5:1 (normal text)
16px · above the fold
div https://www.gov.cn/
3.69:1
#000000
on
#CE0B1B
needs 4.5:1 (normal text)
16px · above the fold
a 习近平同莫桑比克总统查波会…
3.69:1
#000000
on
#CE0B1B
needs 4.5:1 (normal text)
16px · above the fold
a 两国元首一致同意将双边关系…
3.69:1
#000000
on
#CE0B1B
needs 4.5:1 (normal text)
16px · above the fold
a 中方愿同莫方加强发展战略对…
3.69:1
#000000
on
#CE0B1B
needs 4.5:1 (normal text)
16px · above the fold
a 联合声明
3.69:1
#000000
on
#CE0B1B
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 施政为民21.00:13.0:1
#000000
#FFFFFF
Pass
h2 激发活力21.00:13.0:1
#000000
#FFFFFF
Pass
h2 政府建设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 中国政府网_中…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 个人中心21.00:14.5:1
#000000
#FFFFFF
Pass
a 退出21.00:14.5:1
#000000
#FFFFFF
Pass
a 邮箱9.89:14.5:1
#000000
#EB9DA4
Pass
a 无障碍3.69:14.5:1
#000000
#CE0B1B
Fail
div https://www.gov.cn/3.69:14.5:1
#000000
#CE0B1B
Fail
a 习近平同莫桑…3.69:14.5:1
#000000
#CE0B1B
Fail
a 两国元首一致…3.69:14.5:1
#000000
#CE0B1B
Fail
a 中方愿同莫方…3.69:14.5:1
#000000
#CE0B1B
Fail
a 联合声明3.69:14.5:1
#000000
#CE0B1B
Fail

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