Skip to content
https://qcloud.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
9
REVIEW
2
PASS
2
INFO
0
Checks
13
2 PASS 2 REVIEW 9 FIX
D
Alt Text Quality
Action
2 of 111 images have issues
FIX
2 of 111 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 decorative image(s) correctly marked
Info::
107 image(s) with good alt text
111 images 107 good alt text 2 decorative 2 missing
IssueCount
missing2 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
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-tz6x8w
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://qcloud.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://qcloud.com/manifest.json

Manifest contains invalid JSON.

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::
2 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 2 <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.
D
Lighthouse Accessibility Audits
Action
Score 69/100 — 8 failing, 18 passed
FIX
69

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
58同城 div.tpm-portal-panel__bd > div.tpm-portal-logo-wall > div.tpm-portal-logo-wall__track > div.tpm-portal-logo-wall__group
蘑菇街 div.tpm-portal-panel__bd > div.tpm-portal-logo-wall > div.tpm-portal-logo-wall__track > div.tpm-portal-logo-wall__group

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
搜索 div#navigationBarM > div.pls-m-nav-bar > div.pls-m-nav-bar-extra > a.pls-m-nav-btn
用户 div#navigationBarM > div.pls-m-nav-bar > div.pls-m-nav-bar-extra > a.pls-m-nav-btn
菜单 div#navigationBarM > div.pls-m-nav-bar > div.pls-m-nav-bar-extra > a.pls-m-nav-btn

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
与全球伙伴携手，深入产业共创价值 div.tpm-portal-panel > div.tpm-portal-panel__inner > div.tpm-portal-panel__hd > div.tpm-portal-panel__title

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.pls-footer-inner--mobile > div.pls-footer-blogroll-text--links > a.slide > img div.pls-footer-inner--mobile > div.pls-footer-blogroll-text--links > a.slide > 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#navigationBarM > div.pls-m-nav-bar > div.pls-m-nav-bar-main > a.pls-m-nav-logo div#navigationBarM > div.pls-m-nav-bar > div.pls-m-nav-bar-main > a.pls-m-nav-logo
div.tpm-portal-product__list > div.tpm-portal-product__list-content > div.tpm-portal-product__card > a.tpm-portal-product__card-link div.tpm-portal-product__list > div.tpm-portal-product__list-content > div.tpm-portal-product__card > a.tpm-portal-product__card-link
div.tpm-portal-product__list > div.tpm-portal-product__list-content > div.tpm-portal-product__card > a.tpm-portal-product__card-link div.tpm-portal-product__list > div.tpm-portal-product__list-content > div.tpm-portal-product__card > a.tpm-portal-product__card-link
div.tpm-portal-product__list > div.tpm-portal-product__list-content > div.tpm-portal-product__card > a.tpm-portal-product__card-link div.tpm-portal-product__list > div.tpm-portal-product__list-content > div.tpm-portal-product__card > a.tpm-portal-product__card-link
div.tpm-portal-product__list > div.tpm-portal-product__list-content > div.tpm-portal-product__card > a.tpm-portal-product__card-link div.tpm-portal-product__list > div.tpm-portal-product__list-content > div.tpm-portal-product__card > a.tpm-portal-product__card-link
div#swiper-wrapper-cf1910d91154865bb > div.swiper-slide > div.tpm-portal-developer__label > a.tpm-portal-developer__label-link div#swiper-wrapper-cf1910d91154865bb > div.swiper-slide > div.tpm-portal-developer__label > a.tpm-portal-developer__label-link
div#swiper-wrapper-cf1910d91154865bb > div.swiper-slide > div.tpm-portal-developer__label > a.tpm-portal-developer__label-link div#swiper-wrapper-cf1910d91154865bb > div.swiper-slide > div.tpm-portal-developer__label > a.tpm-portal-developer__label-link
div#swiper-wrapper-cf1910d91154865bb > div.swiper-slide > div.tpm-portal-developer__label > a.tpm-portal-developer__label-link div#swiper-wrapper-cf1910d91154865bb > div.swiper-slide > div.tpm-portal-developer__label > a.tpm-portal-developer__label-link
div#swiper-wrapper-cf1910d91154865bb > div.swiper-slide > div.tpm-portal-developer__label > a.tpm-portal-developer__label-link div#swiper-wrapper-cf1910d91154865bb > div.swiper-slide > div.tpm-portal-developer__label > a.tpm-portal-developer__label-link
div.tpm-portal-developer__inner > div.tpm-portal-developer__item-list > div.tpm-portal-developer__item > a.tpm-portal-developer__item-link div.tpm-portal-developer__inner > div.tpm-portal-developer__item-list > div.tpm-portal-developer__item > a.tpm-portal-developer__item-link
div.tpm-portal-developer__inner > div.tpm-portal-developer__item-list > div.tpm-portal-developer__item > a.tpm-portal-developer__item-link div.tpm-portal-developer__inner > div.tpm-portal-developer__item-list > div.tpm-portal-developer__item > a.tpm-portal-developer__item-link
div.tpm-portal-developer__inner > div.tpm-portal-developer__item-list > div.tpm-portal-developer__item > a.tpm-portal-developer__item-link div.tpm-portal-developer__inner > div.tpm-portal-developer__item-list > div.tpm-portal-developer__item > a.tpm-portal-developer__item-link
div.tpm-portal-developer__inner > div.tpm-portal-developer__item-list > div.tpm-portal-developer__item > a.tpm-portal-developer__item-link div.tpm-portal-developer__inner > div.tpm-portal-developer__item-list > div.tpm-portal-developer__item > a.tpm-portal-developer__item-link

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 1 div.tpm-portal-hero > div.tpm-portal-hero__pagination > div.tpm-portal-hero__pagination-bullets > span.tpm-portal-hero__pagination-bullet
Go to slide 2 div.tpm-portal-hero > div.tpm-portal-hero__pagination > div.tpm-portal-hero__pagination-bullets > span.tpm-portal-hero__pagination-bullet
Go to slide 3 div.tpm-portal-hero > div.tpm-portal-hero__pagination > div.tpm-portal-hero__pagination-bullets > span.tpm-portal-hero__pagination-bullet
Go to slide 4 div.tpm-portal-hero > div.tpm-portal-hero__pagination > div.tpm-portal-hero__pagination-bullets > span.tpm-portal-hero__pagination-bullet
Go to slide 5 div.tpm-portal-hero > div.tpm-portal-hero__pagination > div.tpm-portal-hero__pagination-bullets > span.tpm-portal-hero__pagination-bullet
深圳市腾讯计算机系统有限公司 div.pls-footer-blogroll > div.pls-footer-inner--mobile > div.pls-footer-blogroll-text--links > a.slide
粤公网安备44030502008569号 div.pls-footer-blogroll > div.pls-footer-inner--mobile > div.pls-footer-blogroll-text--links > a.slide
腾讯云计算（北京）有限责任公司 div.pls-footer-blogroll > div.pls-footer-inner--mobile > div.pls-footer-blogroll-text--links > a.slide
京ICP备11018762号 div.pls-footer-blogroll > div.pls-footer-inner--mobile > div.pls-footer-blogroll-text--links > a.slide
京D3-20230006 div.pls-footer-blogroll > div.pls-footer-inner--mobile > div.pls-footer-blogroll-text--links > a.slide

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
●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
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○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.
○`[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.
○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
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
10 headings
REVIEW
10 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 近期搜索热词
  • H3 近期搜索热词
  • H2 开启上云第一步
  • H3 热门推荐
  • H3 资源与社区
  • H3 支持服务
  • H3 腾讯云计算
  • H3 中国站
  • H3 关注或联系我们
  • 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

A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext搜索aria-label
inputtext(请输入搜索的关键词)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<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

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 开启上云第一…20.27:13.0:1
#000000
#F9FBFF
Pass
h3 近期搜索热词19.12:13.0:1
#000000
#F1F4FF
Pass
h3 近期搜索热词20.27:13.0:1
#000000
#F9FBFF
Pass
h3 关注或联系我…20.27:13.0:1
#000000
#F9FBFF
Pass
title 腾讯云 产业智…21.00:14.5:1
#000000
#FFFFFF
Pass
i 腾讯云21.00:14.5:1
#000000
#FFFFFF
Pass
a 更多17.12:14.5:1
#000000
#D8EAFE
Pass
li 腾讯云智能体…17.99:14.5:1
#000000
#E1EFFF
Pass
li SSL 证书15.59:14.5:1
#000000
#B1E6FC
Pass
li 域名11.49:14.5:1
#000000
#9BC2FA
Pass
li 短信12.71:14.5:1
#000000
#A7CCFE
Pass
li DeepSeek11.87:14.5:1
#000000
#9FC5FC
Pass
li 对象存储14.33:14.5:1
#000000
#BAD8FD
Pass
li OpenClaw17.19:14.5:1
#000000
#DAEAFF
Pass
li 云服务器19.28:14.5:1
#000000
#F2F5FF
Pass
button 关闭搜索19.25:14.5:1
#000000
#F1F5FF
Pass
a OpenClaw19.09:14.5:1
#000000
#F0F4FF
Pass
a 域名19.09:14.5:1
#000000
#F0F4FF
Pass
a SSL 证书18.93:14.5:1
#000000
#EFF3FF
Pass
a 短信20.11:14.5:1
#000000
#F8FAFF
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