Skip to content
https://www.nbmao.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
8
REVIEW
4
PASS
12
INFO
0
Checks
24
12 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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
9 of 14 images have issues
FIX
9 of 14 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
9 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
5 decorative image(s) correctly marked
14 images 5 decorative 9 missing
IssueCount
missing9 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

D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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
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: #282a2c
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="search-widgets">; <input type="text" name="s" id="search-footer">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-widgetstext(搜点什么呢?)placeholder only
#search-footertext(搜点什么呢?)placeholder only

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

<input type="text" name="s" id="search-widgets">; <input type="text" name="s" id="search-footer">

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, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 4 pass AA only
title 笨猫博客 - 关注互联网，生活…
2.77:1
#000000
on
#5F5243
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 笨猫博客3.46:13.0:1
#000000
#6E6053
Pass
title 笨猫博客 - 关…2.77:14.5:1
#000000
#5F5243
Fail
a 🍟首页8.82:14.5:1
#000000
#B7A593
Pass
a 🍘目录5.78:14.5:1
#000000
#938471
Pass
a 🥝VPS教程6.78:14.5:1
#000000
#A0907D
Pass
a 🍾猫玩技术5.47:14.5:1
#000000
#977D6C
Pass
a 🍹干货分享12.41:14.5:1
#000000
#CEC8A3
Pass
a 🍏软件分享9.51:14.5:1
#000000
#C0AC8A
Pass
a 🍩一只猫10.35:14.5:1
#000000
#BDB5A9
Pass
a 🍋工具19.26:14.5:1
#000000
#F5F5F5
Pass
a 🌽IP路由追踪19.26:14.5:1
#000000
#F5F5F5
Pass
a 🍐域名Whois查…19.26:14.5:1
#000000
#F5F5F5
Pass
a 🥘域名被墙查…19.26:14.5:1
#000000
#F5F5F5
Pass
a 🍧IP正常检测19.26:14.5:1
#000000
#F5F5F5
Pass
a 🔥IP端口检测19.26:14.5:1
#000000
#F5F5F5
Pass
a 🍆短网址19.26:14.5:1
#000000
#F5F5F5
Pass
a 🐟VIP音乐播放19.26:14.5:1
#000000
#F5F5F5
Pass
a 🍯KMS激活19.26:14.5:1
#000000
#F5F5F5
Pass
a 🍓链接19.26:14.5:1
#000000
#F5F5F5
Pass
a 🍪联系19.26:14.5:1
#000000
#F5F5F5
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 5 failing, 17 passed
REVIEW
78

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.

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
基于 Cloudflare Workers + D1 的自托管 2FA/TOTP 验证码管理工具、分享链接功能 div.article-panel > div.a-post > div.header > h3.title

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.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > img
div.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > img
div.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > img
div.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > img
div.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > img
div.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > img
div.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > img
div.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > img
div.article-panel > div.a-thumb > a > img div.article-panel > div.a-thumb > a > 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.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > a
div.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > a
div.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > a
div.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > a
div.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > a
div.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > a
div.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > a
div.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > a
div.col-lg-8 > div.article-panel > div.a-thumb > a div.col-lg-8 > div.article-panel > div.a-thumb > 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.

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-*]` 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
●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
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●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-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 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
○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.
○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
10 headings, 1 skip(s)
PASS
10 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 笨猫博客
  • H3 基于 Cloudflare Workers + D1 的自托管 2FA/TOTP 验证码管理工具、分享链接功能 skipped
  • H3 cloudflare-light-blog： 基于 Cloudflare Workers + D1 + R2 构建的轻量级博客系统
  • H3 LiteMark 书签管理系统 基础ai mcp 支持cf works部署 docker部署
  • H3 komari-theme-Lumina探针主题开源！
  • H3 BitWarden是跑在Cloudflare上的？教你薅干大善人
  • H3 YouTube油管8K视频下载工具：yt-dlp+aria2，王炸组合，榨干你的VPS、电脑带宽
  • H3 IP-Sentinel 分布式哨兵系统v3.1.0重装上阵！让你的小鸡完美伪装成“当地人”
  • H3 NodeWarden -云端备份、大附件处理、直传链路 和 网页端密码库体验
  • H3 it-toolbox开发者工具箱 — 72 款实用工具，基于 Cloudflare Pages Functions 全栈部署

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
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
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "zh-Hans"
PASS
Lang attribute set to "zh-Hans"
Info::
<html lang="zh-Hans"> is set and valid
Got: zh-Hans
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://support.nodeget.com/page/promotion?id={mao}")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 89 visible text node(s) render at >= 12 CSS pixels
PASS
All 89 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback