Skip to content
https://cuhk.edu.hk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: My app
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name My app 192×192 icon 512×512 icon Start URL Display Mode
Name My app Icons 6 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
4 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 4 <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
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 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="image" id="siteSearchbox_submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="query" id="sitesearchbox">; <input type="search" name="query" id="sitesearchbox_m">
3 controls
0 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#sitesearchboxsearch(Search)placeholder only
#sitesearchbox_msearch(Search)placeholder only
#siteSearchbox_submitimage(none)none

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

<input type="image" id="siteSearchbox_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="search" name="query" id="sitesearchbox">; <input type="search" name="query" id="sitesearchbox_m">

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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title CUHK :: The page cannot be found Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
12 icon(s) detected
REVIEW
12 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
a Library
1.76:1
#000000
on
#6F0F15
needs 4.5:1 (normal text)
16px · top of page (header area)
a CUHK A-Z
2.03:1
#000000
on
#80141A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Giving to CUHK
2.51:1
#000000
on
#981A23
needs 4.5:1 (normal text)
16px · above the fold
a Shortcuts
2.30:1
#000000
on
#8F161F
needs 4.5:1 (normal text)
16px · above the fold
a Postgraduate Admissions
2.13:1
#000000
on
#85161C
needs 4.5:1 (normal text)
16px · above the fold
a Undergraduate Admissions
2.08:1
#000000
on
#6E1E6F
needs 4.5:1 (normal text)
16px · above the fold
a University Almanac
2.08:1
#000000
on
#6E1E6F
needs 4.5:1 (normal text)
16px · above the fold
a Registration & Examinations
2.99:1
#000000
on
#764393
needs 4.5:1 (normal text)
16px · mid-page
a Student Job Link
2.99:1
#000000
on
#764393
needs 4.5:1 (normal text)
16px · mid-page
a Email
2.99:1
#000000
on
#764393
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 News12.77:13.0:1
#000000
#D6C7BE
Pass
title The Chinese Universi…21.00:14.5:1
#000000
#FFFFFF
Pass
a MyCUHK21.00:14.5:1
#000000
#FFFFFF
Pass
a Library1.76:14.5:1
#000000
#6F0F15
Fail
a CUHK A-Z2.03:14.5:1
#000000
#80141A
Fail
a Giving to CUHK2.51:14.5:1
#000000
#981A23
Fail
a Shortcuts2.30:14.5:1
#000000
#8F161F
Fail
a Postgraduate Admissi…2.13:14.5:1
#000000
#85161C
Fail
a Undergraduate Admiss…2.08:14.5:1
#000000
#6E1E6F
Fail
a University Almanac2.08:14.5:1
#000000
#6E1E6F
Fail
a Facts and Figures21.00:14.5:1
#000000
#FFFFFF
Pass
a ITSC21.00:14.5:1
#000000
#FFFFFF
Pass
a Library21.00:14.5:1
#000000
#FFFFFF
Pass
a Knowledge Transfer21.00:14.5:1
#000000
#FFFFFF
Pass
a University Publicati…21.00:14.5:1
#000000
#FFFFFF
Pass
a CU Learning Manageme…21.00:14.5:1
#000000
#FFFFFF
Pass
a Registration & Exami…2.99:14.5:1
#000000
#764393
Fail
a Student Job Link2.99:14.5:1
#000000
#764393
Fail
a Email2.99:14.5:1
#000000
#764393
Fail
a System Availability14.31:14.5:1
#000000
#D9D7B2
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 3 failing, 22 passed
REVIEW
85

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Conversations with four distinguished leaders Honorary graduates of 96th Congre… main > section#feature-container > div#feature > div.carousel-inner
CUHK SWK International Conference on “Enhancing Social Inclusion and Sustainabi… section#upcoming-events > div#upcoming-content > div#upcoming-page-wrapper > div.carousel-inner

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Conversations with four distinguished leaders Honorary graduates of 96th Congre… main > section#feature-container > div#feature > div.carousel-inner
CUHK SWK International Conference on “Enhancing Social Inclusion and Sustainabi… section#upcoming-events > div#upcoming-content > div#upcoming-page-wrapper > div.carousel-inner

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.

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
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
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
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
Image elements do not have `[alt]` attributes that are redundant text.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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.
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
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+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 News
A+
Alt Text Quality
All 20 images OK
PASS
All 20 images OK
Info::
20 image(s) with good alt text
20 images 20 good alt text
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback