Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

21 PASS 2 REVIEW 1 FIX

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Search functionality detected

Got: role-search

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Favicon & Branding

8 icon(s) detected

REVIEW

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Nu11Cyber

1.03:1

#000000

#050505

needs 3.0:1 (large text)

32px · above the fold

h2 最新研究

1.04:1

#000000

#060606

needs 3.0:1 (large text)

24px · above the fold

h2 通告栏

1.04:1

#000000

#070707

needs 3.0:1 (large text)

24px · mid-page

title Nu11Cyber | 网络安全研究团队 | C…

1.02:1

#000000

#030303

needs 4.5:1 (normal text)

16px · top of page (header area)

a 跳到主内容

1.02:1

#000000

#030303

needs 4.5:1 (normal text)

16px · top of page (header area)

span Nu11Cyber

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · top of page (header area)

button Nu11Cyber

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · top of page (header area)

span ≡

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

button 研究

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

span ●

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

button 成员

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

span ⌕

1.03:1

#000000

#050505

needs 4.5:1 (normal text)

16px · above the fold

p 面向内部成员与公开读者的安�…

1.03:1

#000000

#050505

needs 4.5:1 (normal text)

16px · above the fold

button 全部

1.08:1

#000000

#0D0D0D

needs 4.5:1 (normal text)

16px · mid-page

div 暂无可见研究。

1.04:1

#000000

#070707

needs 4.5:1 (normal text)

16px · mid-page

button 30天内

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · mid-page

div 暂无通告。

1.05:1

#000000

#080808

needs 4.5:1 (normal text)

16px · mid-page

1.05:1

#000000

#090909

needs 4.5:1 (normal text)

16px · mid-page

a 隐私政策

1.05:1

#000000

#090909

needs 4.5:1 (normal text)

16px · mid-page

a 服务条款

1.05:1

#000000

#090909

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Nu11Cyber	1.03:1	3.0:1	#000000	#050505	Fail
h2 最新研究	1.04:1	3.0:1	#000000	#060606	Fail
h2 通告栏	1.04:1	3.0:1	#000000	#070707	Fail
title Nu11Cyber \| 网络�…	1.02:1	4.5:1	#000000	#030303	Fail
a 跳到主内容	1.02:1	4.5:1	#000000	#030303	Fail
span Nu11Cyber	1.02:1	4.5:1	#000000	#040404	Fail
button Nu11Cyber	1.02:1	4.5:1	#000000	#040404	Fail
span ≡	1.02:1	4.5:1	#000000	#040404	Fail
button 研究	1.02:1	4.5:1	#000000	#040404	Fail
span ●	1.02:1	4.5:1	#000000	#040404	Fail
button 成员	1.02:1	4.5:1	#000000	#040404	Fail
span ⌕	1.03:1	4.5:1	#000000	#050505	Fail
p 面向内部成员�…	1.03:1	4.5:1	#000000	#050505	Fail
button 全部	1.08:1	4.5:1	#000000	#0D0D0D	Fail
div 暂无可见研究�…	1.04:1	4.5:1	#000000	#070707	Fail
button 30天内	1.06:1	4.5:1	#000000	#0A0A0A	Fail
div 暂无通告。	1.05:1	4.5:1	#000000	#080808	Fail
p © 2026 Nu11Cyber. A…	1.05:1	4.5:1	#000000	#090909	Fail
a 隐私政策	1.05:1	4.5:1	#000000	#090909	Fail
a 服务条款	1.05:1	4.5:1	#000000	#090909	Fail

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.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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.

Search landmark present

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

A+

Heading Hierarchy

3 headings

PASS

3 headings

Single H1 present

H1 Nu11Cyber
H2 最新研究
H2 通告栏

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

1 decorative image(s) correctly marked

3 image(s) with good alt text

4 images 3 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	input	搜索研究文章	aria-label

A+

Link & Button Quality

9 links, 5 buttons — all OK

PASS

9 links, 5 buttons — all OK

9 link(s) with descriptive text

9 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

14 links and buttons have descriptive text

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "zh-CN"

PASS

Lang attribute set to "zh-CN"

<html lang="zh-CN"> is set and valid

Got: zh-CN

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 18 visible text node(s) render at >= 12 CSS pixels

PASS

All 18 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 · Nu11Cyber ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Nu11Cyber

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Nu11Cyber ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Nu11Cyber Display Mode standalone Theme Color #000000 Background Color #070b12 Icons 3 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: dark light

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta dark light ✓Dark theme-color #000000 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /print.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /print.css ✓Inline @media print Not detected ✗

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 23 passed

PASS

100

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.

○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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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

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