Skip to content
https://tencent.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
38
GRADE
F
FIX
9
REVIEW
3
PASS
1
INFO
0
Checks
13
1 PASS 3 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
56 headings, 9 skip(s)
FIX
56 headings, 9 skip(s)
Info::
Single H1 present
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: 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: 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::
5 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Tencent腾讯
  • H2 Welcome to China Easy Pay with Weixin Pay
  • H5 Tencent is improving payment services so that visitors to China can better enjoy vibrant international tourism and cultural exchanges. skipped
  • H2 Tencent Announces 2025 Annual and Fourth Quarter Results
  • H5 (empty)
  • H2 Tencent Kicks Off 2026 Global Campus Recruitment Program
  • H5 (empty)
  • H2 Tourism Malaysia and Weixin Pay Formalize Strategic Collaboration to Enhance Travel Experience
  • H5 (empty)
  • H2 Tencent has been named one of TIME’s World’s Best Companies 2025
  • H5 (empty)
  • H2 Welcome to China Easy Pay with Weixin Pay
  • H5 Tencent is improving payment services so that visitors to China can better enjoy vibrant international tourism and cultural exchanges. skipped
  • H2 Tencent Announces 2025 Annual and Fourth Quarter Results
  • H5 (empty)
  • H4 What's New
  • H3 Making Video Games Possible – Even for the Visually Impaired
  • H3 Connecting Care to Prevent Breast and Cervical Cancers
  • H3 How AI Can Enhance Advertising Campaigns – And Work Better for Businesses
  • H3 How Tencent Built a Workplace for Humans and Wildlife
  • H3 Games for Change and Tencent Games Expand Raising Good Gamers with New Program to Help Families Navigate Positive Play in Video Games
  • H3 Tencent Malaysia Secures "Malaysia Digital" Status, Strengthening Local Capabilities to Advance Regional Innovation
  • H3 Tencent and City University of Hong Kong Launch “WeTech Academy Principals’ AI Open Class x Tencent AI Campus Tour”
  • H2 About Us
  • H2 Our Culture
  • H2 Our Offices
  • H2 Connecting users in everyday life
  • H2 Connecting enterprises to digital upgrade
  • H2 Connecting the now and the future
  • H2 Connecting users in everyday life
  • H2 Connecting enterprises to digital upgrade
  • H2 Connecting the now and the future
  • H3 Communications and Social
  • H3 Digital Content
  • H3 FinTech Services
  • H3 Tools
  • H3 Tencent Marketing Solution
  • H3 Tencent Cloud
  • H3 Smart Industries
  • H3 Artificial Intelligence
  • H3 Internet of Things
  • H3 Tencent Media Lab
  • H3 Tencent Exploration
  • H3 Tencent Great Wall Protection Project
  • H3 Carbon Neutrality
  • H3 99 Giving Day
  • H3 Tencent Great Wall Protection Project
  • H3 Carbon Neutrality
  • H2 Connecting responsibility with trust
  • H5 Using technology to make every good deed more impactful skipped
  • H2 Connecting talent with development
  • H5 Stimulating vitality, supporting growth skipped
  • H3 Follow Us
  • H3 Join Us
  • H3 Contact Us
  • H3 Legal Information

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

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
8 of 43 images have issues
FIX
8 of 43 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with filename as alt text
Info::
35 image(s) with good alt text
43 images 35 good alt text 1 generic 7 missing
IssueCount
missing7 image(s)
filename1 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
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.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found - Tencent 腾讯 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Tencent腾讯
1.04:1
#000000
on
#00070E
needs 3.0:1 (large text)
32px · top of page (header area)
h2 Welcome to China Easy Pay with Weixin Pa…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tencent Announces 2025 Annual and Fourth…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tencent Kicks Off 2026 Global Campus Rec…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tourism Malaysia and Weixin Pay Formaliz…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tencent has been named one of TIME’s W…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Welcome to China Easy Pay with Weixin Pa…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tencent Announces 2025 Annual and Fourth…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About Us
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Culture
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Offices
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting users in everyday life
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting enterprises to digital upgrad…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting the now and the future
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting users in everyday life
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting enterprises to digital upgrad…
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting the now and the future
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 responsibility with trust
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting
1.53:1
#000000
on
#2B2E2E
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Tencent腾讯1.04:13.0:1
#000000
#00070E
Fail
h2 Welcome to China Eas…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Tencent Announces 20…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Tencent Kicks Off 20…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Tourism Malaysia and…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Tencent has been nam…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Welcome to China Eas…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Tencent Announces 20…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 About Us1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Our Culture1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Our Offices1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Connecting users in …1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Connecting enterpris…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Connecting the now a…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Connecting users in …1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Connecting enterpris…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Connecting the now a…1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Connecting1.53:13.0:1
#000000
#2B2E2E
Fail
h2 responsibility with …1.53:13.0:1
#000000
#2B2E2E
Fail
h2 Connecting1.53:13.0:1
#000000
#2B2E2E
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.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 7 failing, 20 passed
REVIEW
75

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
2026.04.15 div.ten_card_col4 > div.ten_card > div.ten_card_body > span.ten_tagline
Games for Change and Tencent Games Expand Raising Good Gamers with New Program … div.ten_card > div.ten_card_body > a > h3
Games for Change today announced the launch of a new program. div.ten_card > div.ten_card_body > a > p
粤网文[2023]2882-203号 粤B2-20090059-1 粤公网安备 44030502008569号 Copyright © 1998 - 2026… div.wrap_footer > div.footer_con > div.footer_area > p.copyright
粤网文[2023]2882-203号 div.footer_con > div.footer_area > p.copyright > a.flag_num
粤B2-20090059-1 div.footer_con > div.footer_area > p.copyright > a.flag_num
粤公网安备 44030502008569号 div.footer_con > div.footer_area > p.copyright > a.flag_num

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
Tencent is improving payment services so that visitors to China can better enjo… a > div.ten_banner_text > div.ten_main > h5
a > div.ten_banner_text > div.ten_main > h5 a > div.ten_banner_text > div.ten_main > h5
a > div.ten_banner_text > div.ten_main > h5 a > div.ten_banner_text > div.ten_main > h5
a > div.ten_banner_text > div.ten_main > h5 a > div.ten_banner_text > div.ten_main > h5
a > div.ten_banner_text > div.ten_main > h5 a > div.ten_banner_text > div.ten_main > h5
Tencent is improving payment services so that visitors to China can better enjo… a > div.ten_banner_text > div.ten_main > h5
a > div.ten_banner_text > div.ten_main > h5 a > div.ten_banner_text > div.ten_main > h5
Using technology to make every good deed more impactful div.ten_main > div.ten_subbanner_txt > a > h5
Stimulating vitality, supporting growth div.ten_subbanner_txt > div.ten_main > a > h5

These are opportunities to improve keyboard navigation in your application.

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
div.ten_card > div.ten_img > a > img.auto-height div.ten_card > div.ten_img > a > img.auto-height
div.ten_card > div.ten_img > a > img.auto-height div.ten_card > div.ten_img > a > img.auto-height
div.ten_card > div.ten_img > a > img.auto-height div.ten_card > div.ten_img > a > img.auto-height
div.ten_card > div.ten_img > a > img div.ten_card > div.ten_img > a > img
div.ten_card > div.ten_img > a > img div.ten_card > div.ten_img > a > img
div.ten_card > div.ten_img > a > img.auto-height div.ten_card > div.ten_img > a > img.auto-height
div.ten_card > div.ten_img > a > img div.ten_card > div.ten_img > a > img

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.ten_card_col3 > div.ten_card > div.ten_img > a div.ten_card_col3 > div.ten_card > div.ten_img > a
div.second_line_card_container > div.ten_card > div.ten_img > a div.second_line_card_container > div.ten_card > div.ten_img > a
div.second_line_card_container > div.ten_card > div.ten_img > a div.second_line_card_container > div.ten_card > div.ten_img > a
div.ten_card_col3 > div.ten_card > div.ten_img > a div.ten_card_col3 > div.ten_card > div.ten_img > a
div.ten_card_col4 > div.ten_card > div.ten_img > a div.ten_card_col4 > div.ten_card > div.ten_img > a
div.ten_card_col4 > div.ten_card > div.ten_img > a div.ten_card_col4 > div.ten_card > div.ten_img > a
div.ten_card_col4 > div.ten_card > div.ten_img > a div.ten_card_col4 > div.ten_card > div.ten_img > a
div.focus_us > ul.focus_list > li > a div.focus_us > ul.focus_list > li > a
div.focus_us > ul.focus_list > li > a div.focus_us > ul.focus_list > li > a
div.focus_us > ul.focus_list > li > a div.focus_us > ul.focus_list > li > a
div.focus_us > ul.focus_list > li > a div.focus_us > ul.focus_list > li > 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.

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

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
Go to slide 2 div.ten_banner_nav > div.ten_main > div.ten_banner_bullet > span.swiper-pagination-bullet
Go to slide 3 div.ten_banner_nav > div.ten_main > div.ten_banner_bullet > span.swiper-pagination-bullet
Go to slide 4 div.ten_banner_nav > div.ten_main > div.ten_banner_bullet > span.swiper-pagination-bullet
Go to slide 5 div.ten_banner_nav > div.ten_main > div.ten_banner_bullet > span.swiper-pagination-bullet
Go to slide 1 div.ten_subbanner_nav > div.ten_main > div.ten_subbanner_bullet > span.swiper-pagination-bullet
Go to slide 2 div.ten_subbanner_nav > div.ten_main > div.ten_subbanner_bullet > span.swiper-pagination-bullet
粤网文[2023]2882-203号 div.footer_con > div.footer_area > p.copyright > a.flag_num
粤B2-20090059-1 div.footer_con > div.footer_area > p.copyright > a.flag_num
粤公网安备 44030502008569号 div.footer_con > div.footer_area > p.copyright > a.flag_num

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`button`, `link`, and `menuitem` elements have accessible names
●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 are distinguishable without relying on color.
●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
●`[lang]` attributes have a valid value
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Image elements do not have `[alt]` attributes that are redundant text.
○`[accesskey]` values are unique
○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 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
○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.
○`<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
○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.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback