Skip to content
https://gitee.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
F
Heading Hierarchy
Action
63 headings, 3 skip(s)
FIX
63 headings, 3 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::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 企业级 DevOps 研发效能平台
  • H4 AI 协作 skipped
  • H4 项目协同
  • H4 代码管理
  • H4 代码扫描
  • H4 持续集成
  • H4 测试管理
  • H4 制品管理
  • H4 效能度量
  • H2 丰富又活跃的开源社区
  • H2 专业的私有化部署服务
  • H2 为您量身定制的企业降本增效服务
  • H3 Gitee DevOps 效能管理专家团队
  • H4 解决管理难题
  • H5 69% 的管理者指出，软件成本过高是主要门槛
  • H5 83% 的管理者认为建立度量体系是增效的重要前提
  • H4 突破研发困局
  • H5 90% 的开发者表示不合适的协同模式是导致效率低下的首要原因
  • H5 70% 的开发者认为集成、测试、部署等重复性劳动是项目交付的最大阻碍
  • H2 多种产品形态满足使用
  • H4 社区版 skipped
  • H4 社区版
  • H4 企业版/专业版
  • H4 企业版/专业版
  • H4 旗舰版
  • H4 旗舰版
  • H2 丰富的行业实践经验
  • H3 帮助各行业、各类规模性组织获得数字化转型成功
  • H3 大金融行业
  • H3 大制造行业
  • H3 大健康行业
  • H3 互联网/IT
  • H3 国资 • 信创
  • H3 科研教育
  • H3 大传媒行业
  • H3 大消费行业
  • H3 大金融行业
  • H3 大制造行业
  • H3 大健康行业
  • H3 互联网/IT
  • H3 国资 • 信创
  • H3 科研教育
  • H3 大传媒行业
  • H3 大消费行业
  • H3 大金融行业
  • H3 大制造行业
  • H3 大健康行业
  • H3 互联网/IT
  • H3 国资 • 信创
  • H3 科研教育
  • H3 大传媒行业
  • H3 大消费行业
  • H3 大金融行业
  • H3 大制造行业
  • H3 大健康行业
  • H3 互联网/IT
  • H3 国资 • 信创
  • H3 科研教育
  • H3 大传媒行业
  • H3 大消费行业
  • H2 更多服务
  • H4 <img alt="icon-heart" loading="lazy" decoding="async" data-nimg="intrinsic" style="position:absolute;top:0;left:0;bottom:0;right:0;box-sizing:border-box;padding:0;border:none;margin:auto;display:block skipped
  • 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

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

D
Alt Text Quality
Action
75 of 327 images have issues
FIX
75 of 327 images have issues
Critical::
11 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
64 image(s) with generic alt text
Info::
96 decorative image(s) correctly marked
Info::
156 image(s) with good alt text
327 images 156 good alt text 96 decorative 64 generic 11 missing
IssueCount
missing11 image(s)
generic64 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

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::
8 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 8 <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.
B
Landmark Structure
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
8 of 8 <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 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
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">; <input type="text">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(搜开源)placeholder only
inputtext(请输入你的手机号码)placeholder only
inputtext(请输入你的手机号码)placeholder only

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

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

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 你所访问的页面不存在 (404) ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 24 passed
REVIEW
82

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
企业版免费注册 div.sm:flex > a.mr-4 > button.ant-btn > span
专业版预约演示 div.sm:flex > span.inline-block > button.ant-btn > span
了解更多 div.ModulesBox-module-scss-module__50ulFW__module-introduction > div.ModulesBox-module-scss-module__50ulFW__introduction-list > div.ModulesBox-module-scss-module__50ulFW__introduction-item > a.ModulesBox-module-scss-module__50ulFW__link-more
免费注册 div.flex > a.inline-flex > button.ant-btn > span
预约演示 div.flex > a.text-link-primary > button.ant-btn > span
联系我们 div.flex > a.text-link-primary > button.ant-btn > span
预约顾问咨询 div > div.SpecsBar-module-scss-module__s8JqWq__specs-bar > button.ant-btn > span
企业版免费注册 div.index-module-scss-module__kRIr0q__btns-wrap > a.mr-4 > button.ant-btn > span
查看更多行业龙头数字化转型实践 div.flex > a.sm:flex-1 > button.ant-btn > span
申请公益支持 div.flex > div.mr-10 > button.ant-btn > span
联系我们 div.flex > div.w-[50%] > button.ant-btn > span
Gitee 封面人物 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
GVP 项目 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
Gitee 博客 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
Gitee 公益计划 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
Gitee 持续集成 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
OpenAPI div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
MCP server div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
帮助文档 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
在线自助服务 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
更新日志 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
关于我们 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
加入我们 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
使用条款 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
意见建议 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
合作伙伴 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > a.text-desc
client@oschina.cn div.flex > nav.mt-4 > a.text-desc > span
企业版在线使用：400-606-0201 div.flex > nav.mt-4 > a.text-desc > span
专业版私有部署：赖经理 13058176526 div.footer-module-scss-module__LGd1tG__footer-wrapper > div.flex > nav.mt-4 > div.inline-block
专业版私有部署： div.flex > nav.mt-4 > div.inline-block > span
京ICP备2025119063号 div.flex > div.flex > div.mb-1 > a.>sm:mr-4
中 文 div.flex > div.mb-1 > div.space-x-1 > a.text-gray-400
English div.flex > div.mb-1 > div.space-x-1 > a.text-gray-400
京公网安备11011502039387号 div.flex > div.next-dark-mode > a.text-[#8c92a4] > span.next-dark-mode
购买咨询 div#__next > div.index-module-scss-module__9ZkxBG__mobile-toolbar > button.ant-btn > span.index-module-scss-module__9ZkxBG__text

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
AI 协作 div.ModulesBox-module-scss-module__50ulFW__module-introduction > div.ModulesBox-module-scss-module__50ulFW__introduction-list > div.ModulesBox-module-scss-module__50ulFW__introduction-item > h4.text-2xl
社区版 div.index-module-scss-module__kRIr0q__edition-list > div.index-module-scss-module__kRIr0q__edition-box > div.index-module-scss-module__kRIr0q__edition-box-content > h4
Gitee 公益支持计划 div.index-module-scss-module__P-t6vW__section-inner > div.flex > div.mr-10 > h4.color-[#111111]

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.flex > div.relative > span > img div.flex > div.relative > span > img
div.flex > div.relative > span > img div.flex > div.relative > span > img
div.flex > div.relative > span > img div.flex > div.relative > span > img
div.flex > div.relative > span > img div.flex > div.relative > span > img
div.flex > div.relative > span > img div.flex > div.relative > span > img
div.flex > div.relative > span > img div.flex > div.relative > span > img
div.flex > div.relative > span > img div.flex > div.relative > span > img
div.flex > div.relative > span > img div.flex > div.relative > span > img
div.index-module-scss-module__kRIr0q__edition-box > div.index-module-scss-module__kRIr0q__edition-box-img > span > img div.index-module-scss-module__kRIr0q__edition-box > div.index-module-scss-module__kRIr0q__edition-box-img > span > img
div.index-module-scss-module__kRIr0q__edition-box > div.index-module-scss-module__kRIr0q__edition-box-img > span > img div.index-module-scss-module__kRIr0q__edition-box > div.index-module-scss-module__kRIr0q__edition-box-img > span > img
div.index-module-scss-module__kRIr0q__edition-box > div.index-module-scss-module__kRIr0q__edition-box-img > span > img div.index-module-scss-module__kRIr0q__edition-box > div.index-module-scss-module__kRIr0q__edition-box-img > span > img

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
免费注册 div.box-border > div.flex > div.flex > a.inline-flex

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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<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
○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>`.
○All heading elements contain content.
○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.
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 企业级 DevOps 研…6.60:13.0:1
#000000
#6594C6
Pass
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
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 Gitee DevOps 效能…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
h3 大健康行业21.00:13.0:1
#000000
#FFFFFF
Pass
h3 互联网/IT21.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
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
h3 大健康行业21.00:13.0:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback