Skip to content
https://fudan.edu.cn

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
37
GRADE
F
FIX
10
REVIEW
3
PASS
0
INFO
0
Checks
13
3 REVIEW 10 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
Alt Text Quality
Action
103 of 105 images have issues
FIX
103 of 105 images have issues
Critical::
103 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
86 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
105 images 2 decorative 103 missing
IssueCount
missing103 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-my5y1b
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
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 Missing
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found Inline @media print Not detected
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
F
Lighthouse Accessibility Audits
Action
Score 47/100 — 8 failing, 8 passed
FIX
47

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
14 li.news > div.news_box > div.news_date > div.news_year
16:00 div.news_wz > div.news_con > div.news_text > p.t1
14 li.news > div.news_box > div.news_date > div.news_year
13 li.news > div.news_box > div.news_date > div.news_year
15:30-17:30 div.news_wz > div.news_con > div.news_text > p.t1

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.head-left > div.sitelogo > a > img div.head-left > div.sitelogo > a > img
div.focus-container > div.focus-item > a > img div.focus-container > div.focus-item > a > img
div.focus-container > div.focus-item > a > img div.focus-container > div.focus-item > a > img
div.news_box > div.news_imgs > a.imgs > img div.news_box > div.news_imgs > a.imgs > img
div.news_box > div.news_imgs > a.imgs > img div.news_box > div.news_imgs > a.imgs > img
div.news_box > div.news_imgs > a.imgs > img div.news_box > div.news_imgs > a.imgs > img
div.news_box > div.news_imgs > a.imgs > img div.news_box > div.news_imgs > a.imgs > img
div.news_box > div.news_imgs > a.imgs > img div.news_box > div.news_imgs > a.imgs > img
div.news_box > div.news_imgs > a.imgs > img div.news_box > div.news_imgs > a.imgs > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_imgs > div.imgs > a.active > img div.news_imgs > div.imgs > a.active > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
div.news_box > div.news_imgs > a > img div.news_box > div.news_imgs > a > img
a.news_box > div.news_imgs > div.news_imgsbox > img a.news_box > div.news_imgs > div.news_imgsbox > 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.focus > div.focus-container > div.focus-item > a div.focus > div.focus-container > div.focus-item > a
div.focus > div.focus-container > div.focus-item > a div.focus > div.focus-container > div.focus-item > a
li.news > div.news_box > div.news_imgs > a.imgs li.news > div.news_box > div.news_imgs > a.imgs
li.news > div.news_box > div.news_imgs > a.imgs li.news > div.news_box > div.news_imgs > a.imgs
li.news > div.news_box > div.news_imgs > a.imgs li.news > div.news_box > div.news_imgs > a.imgs
li.news > div.news_box > div.news_imgs > a.imgs li.news > div.news_box > div.news_imgs > a.imgs
li.news > div.news_box > div.news_imgs > a.imgs li.news > div.news_box > div.news_imgs > a.imgs
li.news > div.news_box > div.news_imgs > a.imgs li.news > div.news_box > div.news_imgs > a.imgs
div.shares > ul > li.i1 > a div.shares > ul > li.i1 > a
div.shares > ul > li.i2 > a div.shares > ul > li.i2 > a
div.shares > ul > li.i3 > a div.shares > ul > li.i3 > a
div.shares > ul > li.i4 > a div.shares > ul > li.i4 > a
div.shares > ul > li.i5 > a div.shares > ul > li.i5 > a
div.shares > ul > li.i6 > a div.shares > ul > li.i6 > a
div.shares > ul > li.i7 > a div.shares > ul > li.i7 > a
div.shares > ul > li.i8 > a div.shares > ul > li.i8 > a
div.shares > ul > li.i9 > a div.shares > ul > li.i9 > a
div.foot-con > p.copyright > span > a div.foot-con > p.copyright > span > a
div.foot-con > p.copyright > span > a div.foot-con > p.copyright > span > 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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
教授别墅 春日的清晨,一场大雨过后,绿意葱茏的复旦校园弥漫着清新的气息。复旦教师第九宿舍东南侧,二幢红瓦黄墙的小楼,在薄雾中静静伫立,似在迎候着昔日的主人。二… div > div.news_conbox > div.news_con > ul.news_list

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
教授别墅 春日的清晨,一场大雨过后,绿意葱茏的复旦校园弥漫着清新的气息。复旦教师第九宿舍东南侧,二幢红瓦黄墙的小楼,在薄雾中静静伫立,似在迎候着昔日的主人。二… ul.news_list > div.slick-list > div.slick-track > li.news
松德堂 走进复旦大学上海医学院的东院,有一幢在众多大楼环抱中显得颇不显眼的楼房,它就是建造于1936年的“松德堂”,为纪念上海著名爱国实业家项松茂先生而命名的… ul.news_list > div.slick-list > div.slick-track > li.news
中山医院3号楼 具有中国建筑特色、呈现城垣城楼雄姿的中山医院3号楼,是1937年4月建成的。它是上世纪三十年代由中国人自己创设的一所规模较大的综合性医院———… ul.news_list > div.slick-list > div.slick-track > li.news
上医大一号楼 上医大一号楼自1937年落成后,一代代的上医人都喜欢将这具有东方艺术宫殿式建筑的大楼作为背景,拍下那令人难以忘怀的毕业照。它也是上医人踏上为人群… ul.news_list > div.slick-list > div.slick-track > li.news
教授别墅 春日的清晨,一场大雨过后,绿意葱茏的复旦校园弥漫着清新的气息。复旦教师第九宿舍东南侧,二幢红瓦黄墙的小楼,在薄雾中静静伫立,似在迎候着昔日的主人。二… ul.news_list > div.slick-list > div.slick-track > li.news
松德堂 走进复旦大学上海医学院的东院,有一幢在众多大楼环抱中显得颇不显眼的楼房,它就是建造于1936年的“松德堂”,为纪念上海著名爱国实业家项松茂先生而命名的… ul.news_list > div.slick-list > div.slick-track > li.news

These are opportunities to improve the experience of reading tabular or list data using 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

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-hidden="true"]` is not present on the document `<body>`
Buttons have an accessible name
Document has a `<title>` element
Links are distinguishable without relying on color.
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
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 use only permitted ARIA attributes
`[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
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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
Heading Hierarchy
17 headings
REVIEW
17 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 导航
  • H3 导航
  • H3 快速通道
  • H3 相关链接
  • H3 加入我们
  • H2 登《科学》杂志!复旦团队发现调控情绪的“闸门”,让患者实现“痛而不抑”
  • H3 新闻聚焦
  • H3 文化校历
  • H3 学在复旦
  • H3 专题网站
  • H3 复旦百科
  • H3 建筑 人物 书屋
  • H3 视觉复旦
  • H3 相关链接
  • H3 滚动搜索
  • H3 联系方式
  • H3 加入我们

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="keyword">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
keywordtext(请输入关键词...)placeholder only
submitsubmit(none)none

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

<input type="submit" name="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="keyword">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA 1 pass AA only
h3 导航
2.68:1
#000000
on
#204F9F
needs 3.0:1 (large text)
19px · top of page (header area)
title 复旦大学 Fudan University
2.59:1
#000000
on
#1F4D9A
needs 4.5:1 (normal text)
16px · top of page (header area)
span 复旦大学
2.68:1
#000000
on
#204F9F
needs 4.5:1 (normal text)
16px · top of page (header area)
a 复旦概况
1.20:1
#000000
on
#021548
needs 4.5:1 (normal text)
16px · top of page (header area)
a 复旦简介
2.35:1
#000000
on
#014893
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a 辉煌校史
1.67:1
#000000
on
#083364
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a 统计概览
1.09:1
#000000
on
#010C2B
needs 4.5:1 (normal text)
16px · above the fold

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 导航2.68:13.0:1
#000000
#204F9F
Fail
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
title 复旦大学 Fudan U…2.59:14.5:1
#000000
#1F4D9A
Fail
span 复旦大学2.68:14.5:1
#000000
#204F9F
Fail
a 复旦概况1.20:14.5:1
#000000
#021548
Fail
a 复旦简介2.35:14.5:1
#000000
#014893
Fail
a 治理架构5.77:14.5:1
#000000
#0191BB
Pass
a 辉煌校史1.67:14.5:1
#000000
#083364
Fail
a 统计概览1.09:14.5:1
#000000
#010C2B
Fail
a 复旦标志21.00:14.5:1
#000000
#FFFFFF
Pass
a 标识系统21.00:14.5:1
#000000
#FFFFFF
Pass
a 复旦章程21.00:14.5:1
#000000
#FFFFFF
Pass
a 访问复旦21.00:14.5:1
#000000
#FFFFFF
Pass
div 相关链接21.00:14.5:1
#000000
#FFFFFF
Pass
a 复旦年报21.00:14.5:1
#000000
#FFFFFF
Pass
a 规章制度21.00:14.5:1
#000000
#FFFFFF
Pass
a 历任领导21.00:14.5:1
#000000
#FFFFFF
Pass

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