Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 REVIEW 6 FIX

Link & Button Quality

Action

4 issue(s) across 26 links and 11 buttons

FIX

4 issue(s) across 26 links and 11 buttons

2 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a#ariaTipText; a[href="http://www.beian.gov.cn/portal/registerSystemInfo?recordcode=11010802020088"]

20 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://zhuanlan.zhihu.com; /roundtable; /explore; /app; /contact; https://app.mokahr.com/apply/zhihu; /org/signup; //ir.zhihu.com; https://tsm.miit.gov.cn/dxxzsp/; https://beian.miit.gov.cn/ (+10 more)

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.Button (#118 on page); button.Button (#133 on page); button.Button (#136 on page); button.Button (#139 on page)

4 link(s) with descriptive text

26 links

0 empty

0 generic text

20 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
javascript:void(0)	欢迎进入知乎 - 有问�…	img no alt	Add alt attribute to the image
https://zhuanlan.zhihu.com	知乎专栏	new tab	Add '(opens in new tab)' to text
/roundtable	圆桌	new tab	Add '(opens in new tab)' to text
/explore	发现	new tab	Add '(opens in new tab)' to text
/app	移动应用	new tab	Add '(opens in new tab)' to text
/contact	联系我们	new tab	Add '(opens in new tab)' to text
https://app.mokahr.com/apply/zhihu	来知乎工作	new tab	Add '(opens in new tab)' to text
/org/signup	注册机构号	new tab	Add '(opens in new tab)' to text
//ir.zhihu.com	Investor Relations	new tab	Add '(opens in new tab)' to text
https://tsm.miit.gov.cn/dxxzsp/	京ICP证110745号	new tab	Add '(opens in new tab)' to text
https://beian.miit.gov.cn/	京ICP备13052560号-1	new tab	Add '(opens in new tab)' to text
http://www.beian.gov.cn/portal/registerS…	京公网安备 11010802020088…	new tab	Add '(opens in new tab)' to text
https://www.zhihu.com/certificates	互联网新闻信息服务许…	new tab	Add '(opens in new tab)' to text
https://www.zhihu.com/certificates	京网文[2025]0422-132 号	new tab	Add '(opens in new tab)' to text
https://pic4.zhimg.com/v2-69619662ff377c…	出版物经营许可证	new tab	Add '(opens in new tab)' to text
https://picx.zhimg.com/80/v2-7475facab3f…	药品医疗器械网络信息…	new tab	Add '(opens in new tab)' to text
https://pic1.zhimg.com/v2-185764ce177e34…	广播电视节目制作经营…	new tab	Add '(opens in new tab)' to text
https://www.zhihu.com/certificates	互联网宗教信息服务许…	new tab	Add '(opens in new tab)' to text
https://zhuanlan.zhihu.com/p/28852607	侵权举报	new tab	Add '(opens in new tab)' to text
http://www.12377.cn	网上有害信息举报专区	new tab	Add '(opens in new tab)' to text
/term/child-jubao	儿童色情信息举报专区	new tab	Add '(opens in new tab)' to text
/term/algorithm-recommend-report	互联网算法推荐举报专…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

11 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a#ariaTipText; a[href="http://www.beian.gov.cn/portal/registerSystemInfo?recordcode=11010802020088"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://zhuanlan.zhihu.com; /roundtable; /explore; /app; /contact; https://app.mokahr.com/apply/zhihu; /org/signup; //ir.zhihu.com; https://tsm.miit.gov.cn/dxxzsp/; https://beian.miit.gov.cn/ (+10 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.Button (#118 on page); button.Button (#133 on page); button.Button (#136 on page); button.Button (#139 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 403 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

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

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

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Alt Text Quality

Action

2 of 5 images have issues

REVIEW

2 of 5 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 decorative image(s) correctly marked

2 image(s) with good alt text

5 images 2 good alt text 1 decorative 2 missing

Issue	Count
missing	2 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

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Action

Score 71/100 — 5 failing, 17 passed

REVIEW

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.Body--Mobile > 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--Mobile `body.Body--Mobile`

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 > div.css-1ncvp5r > div > div.css-69z0b2`
打开App `div > div > div.css-1ncvp5r > button.Button`
搜索 `div.css-ms6bo9 > div.css-3f0re9 > div > div.css-cssrft`
赞同 3258 `div.ContentItem-actions > span > span > button.Button`
赞同 259 `div.ContentItem-actions > span > span > button.Button`
赞同 246 `div.ContentItem-actions > span > span > button.Button`
赞同 709 `div.ContentItem-actions > span > span > button.Button`
赞同 60 `div.ContentItem-actions > span > span > button.Button`
赞同 139 `div.ContentItem-actions > span > span > button.Button`
赞同 309 `div.ContentItem-actions > span > span > button.Button`
赞同 357 `div.ContentItem-actions > span > span > button.Button`
赞同 101 `div.ContentItem-actions > span > span > button.Button`
赞同 2622 `div.ContentItem-actions > span > span > button.Button`
赞同 52 `div.ContentItem-actions > span > span > button.Button`
赞同 45 `div.ContentItem-actions > span > span > button.Button`
赞同 72 `div.ContentItem-actions > span > span > button.Button`
赞同 37 `div.ContentItem-actions > span > span > button.Button`
赞同 124 `div.ContentItem-actions > span > span > button.Button`
App 内打开 `div > div.NotLoggedInTopstory > div.OpenInAppButton > button.Button`

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
body.Body--Mobile > a#ariaTipText > img `body.Body--Mobile > a#ariaTipText > img`
body.Body--Mobile > img `body.Body--Mobile > 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`

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

●Buttons have an accessible name

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[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 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

○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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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.

○Identical links have the same purpose.

○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

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
username	tel		none
digits	tel		none

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)

Element	Ratio	Required	FG	BG	Result
title 知乎 - 有问题�…	15.60:1	4.5:1	#000000	#B8E5F8	Pass
div 打开知乎App	15.60:1	4.5:1	#000000	#B8E5F8	Pass
div 在「我的页」�…	15.60:1	4.5:1	#000000	#B8E5F8	Pass
div 其他扫码方式�…	15.60:1	4.5:1	#000000	#B8E5F8	Pass
button 下载知乎App	17.54:1	4.5:1	#000000	#D4EFFB	Pass
button 无障碍模式	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div 验证码登录	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div 密码登录	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 开通机构号	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 中国 +86	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button 获取短信验证�…	20.29:1	4.5:1	#000000	#FBFBFB	Pass
div 获取语音验证�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button 登录/注册	8.87:1	4.5:1	#000000	#74AAFA	Pass
div 其他方式登录	8.87:1	4.5:1	#000000	#74AAFA	Pass
div 未注册手机验�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 《知乎协议》	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 《隐私保护指�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 知乎专栏	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 圆桌	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 发现	21.00:1	4.5: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.