Skip to content
https://moe.best

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
9
REVIEW
5
PASS
10
INFO
0
Checks
24
10 PASS 5 REVIEW 9 FIX
F
Alt Text Quality
Action
20 of 20 images have issues
FIX
20 of 20 images have issues
Critical::
20 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
20 image-in-link without alt text
An image inside a link with no alt creates an empty link.
20 images 20 missing
IssueCount
missing20 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
Mobile Keyboard & Autofill
Action
3/3 eligible field(s) missing autocomplete or inputmode
FIX
3/3 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name, current-password.
Got: <input type="text" name="name" id="navbar-login-user">, <input type="password" name="password" id="navbar-login-password">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search.
Got: <input type="search" name="s" id="search_input">
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
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: #7266ba
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::
2 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 2 <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
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN ASIDE CONTENTINFO (missing!)

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

B
Form Input Quality
2 input-semantic issue(s) across 3 form control(s)
REVIEW
2 input-semantic issue(s) across 3 form control(s)
Info::
1 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="password">.
Info::
1 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text" name="name">.
B
Mobile-Readable Font Sizes
95% of visible text renders at >= 12 CSS px (10 below threshold)
REVIEW
95% of visible text renders at >= 12 CSS px (10 below threshold)
Info::
10 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <b> 11.0px ("17"); <b> 11.0px ("20"); <b> 11.0px ("23"); <b> 11.0px ("10"); <b> 11.0px ("10").
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 1 pass AA only
title 神代綺凛の随波逐流 - 平时都…
3.34:1
#000000
on
#6051B5
needs 4.5:1 (normal text)
16px · top of page (header area)
span LOLI! NEKO!
2.49:1
#000000
on
#4F4484
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
small 2018-3-28 22:52:58
2.79:1
#000000
on
#724668
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Login
1.58:1
#000000
on
#392A41
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
h1 神代綺凛の随…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Popular articles21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Latest comments21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Random articles21.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 Tag cloud21.00:13.0:1
#000000
#FFFFFF
Pass
title 神代綺凛の随…3.34:14.5:1
#000000
#6051B5
Fail
span LOLI! NEKO!2.49:14.5:1
#000000
#4F4484
Fail
span About me17.82:14.5:1
#000000
#FAEBCC
Pass
span 留言板17.82:14.5:1
#000000
#FAEBCC
Pass
span New thing17.82:14.5:1
#000000
#FAEBCC
Pass
strong New thing17.82:13.0:1
#000000
#FAEBCC
Pass
span 把公主链接下…9.50:14.5:1
#000000
#E9999C
Pass
small 2018-7-3 15:38:235.37:14.5:1
#000000
#AF6F78
Pass
span 退坑公主链接…11.00:14.5:1
#000000
#FAA3B9
Pass
small 2018-6-3 22:45:3718.44:14.5:1
#000000
#FEEDE3
Pass
span 今天 Steam 收到…8.47:14.5:1
#000000
#E28BA5
Pass
small 2018-3-28 22:52:582.79:14.5:1
#000000
#724668
Fail
span Login1.58:14.5:1
#000000
#392A41
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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 6 failing, 22 passed
REVIEW
72

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
LOLI! NEKO! body#body > div#alllayout > header#header

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
© 2016-2026 Copyright JindaiKirin | SiteMap body#body > div#alllayout > footer#footer

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#alllayout > header#header > div.navbar-header > button.pull-right div#alllayout > header#header > div.navbar-header > button.pull-right
div#alllayout > header#header > div.navbar-header > button.pull-left div#alllayout > header#header > div.navbar-header > button.pull-left

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 > a > span.thumb-lg > img.img-full div > a > span.thumb-lg > img.img-full
ul.list-group > li.list-group-item > a.pull-left > img.img-circle ul.list-group > li.list-group-item > a.pull-left > img.img-circle
ul.list-group > li.list-group-item > a.pull-left > img.img-circle ul.list-group > li.list-group-item > a.pull-left > img.img-circle
ul.list-group > li.list-group-item > a.pull-left > img.img-circle ul.list-group > li.list-group-item > a.pull-left > img.img-circle
ul.list-group > li.list-group-item > a.pull-left > img.img-circle ul.list-group > li.list-group-item > a.pull-left > img.img-circle
ul.list-group > li.list-group-item > a.pull-left > img.img-circle ul.list-group > li.list-group-item > a.pull-left > img.img-circle
ul.list-group > li.list-group-item > a.pull-left > img.img-circle ul.list-group > li.list-group-item > a.pull-left > img.img-circle
ul.list-group > li.list-group-item > a.pull-left > img.img-circle ul.list-group > li.list-group-item > a.pull-left > img.img-circle
ul.list-group > li.list-group-item > a.pull-left > img.img-circle ul.list-group > li.list-group-item > a.pull-left > img.img-circle

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#aside-user > div.dropdown > div > a div#aside-user > div.dropdown > div > a
div.blog-post > div.panel-small > div.index-post-img-small > a div.blog-post > div.panel-small > div.index-post-img-small > a
div.blog-post > div.panel-small > div.post-meta > a.ahover div.blog-post > div.panel-small > div.post-meta > a.ahover
div.blog-post > div.panel-small > div.index-post-img-small > a div.blog-post > div.panel-small > div.index-post-img-small > a
div.blog-post > div.panel-small > div.post-meta > a.ahover div.blog-post > div.panel-small > div.post-meta > a.ahover
div.blog-post > div.panel-small > div.index-post-img-small > a div.blog-post > div.panel-small > div.index-post-img-small > a
div.blog-post > div.panel-small > div.post-meta > a.ahover div.blog-post > div.panel-small > div.post-meta > a.ahover
div.blog-post > div.panel-small > div.index-post-img-small > a div.blog-post > div.panel-small > div.index-post-img-small > a
div.blog-post > div.panel-small > div.post-meta > a.ahover div.blog-post > div.panel-small > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
div.blog-post > div.panel > div.index-post-img > a div.blog-post > div.panel > div.index-post-img > a
div.blog-post > div.panel > div.post-meta > a.ahover div.blog-post > div.panel > div.post-meta > a.ahover
nav.text-center > ol.page-navigator > li.next > a nav.text-center > ol.page-navigator > li.next > a
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left
section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left
section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left
section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left

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
●`[role]`s are contained by their required parent element
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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 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
●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
●Uses ARIA roles only on compatible elements
●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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○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
34 headings
PASS
34 headings
Info::
Single H1 present
  • H1 神代綺凛の随波逐流
  • H2 置顶[已完结] 哔哩哔哩 Nekopara B站网页萌化主题
  • H2 置顶[FGO] 日服活动攻略搬运
  • H2 置顶[开源] 二次元搜图QQ机器人
  • H2 置顶[Pxder] Pixiv 插画下载器
  • H2 GitHub Actions 踩坑之——自己造！
  • H2 Revolt 搭建指南
  • H2 [CloudCone] 洛杉矶/KVM/支持支付宝/$2换IP/1Gbps
  • H2 在 Cloudflare Workers 上部署基于 Telegraf 框架的 Telegram Bot
  • H2 让 Vue 使用指定配置文件进行构建
  • H2 借助 redis 实现访问控制
  • H2 一个由不透明响应引发的灾难
  • H2 VSCode 等宽字体之坑
  • H2 GitHub Actions 初体验及踩坑记录
  • H2 油猴脚本入坑指南
  • H3 Popular articles
  • H4 [已完结] 哔哩哔哩 Nekopara B站网页萌化主题
  • H4 [开源] 二次元搜图QQ机器人
  • H4 [CloudCone] 洛杉矶/KVM/支持支付宝/$2换IP/1Gbps
  • H4 [Pxder] Pixiv 插画下载器
  • H4 [Pixiv] Nginx 真·反代P站
  • H3 Latest comments
  • H3 Random articles
  • H4 2017年度萌化小总结~
  • H4 油猴脚本入坑指南
  • H4 [FGO] 日服活动攻略搬运
  • H4 [Shell] nhentai一键批量下载
  • H4 [QQ空间] 自动批量删除所有说说
  • H3 博客信息
  • H3 主机推荐
  • H4 [CloudIPLC] NAT 主机的正确食用方法
  • H4 [CloudCone] 洛杉矶/KVM/支持支付宝/$2换IP/1Gbps
  • H4 [Vultr] 推出3.5刀有IPv4的套餐 支持支付宝Paypal IPv6 1Gbps 免费快照 小时计费 高性价比 日本/洛杉矶/新加坡
  • H3 Tag cloud
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
12 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: 12 all-caps heading(s)
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s" id="search_input">
Info::
2 control(s) properly labeled
3 controls
2 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#navbar-login-usertextusernamefor/id
#navbar-login-passwordpasswordpasswordfor/id
#search_inputsearch(Search projects...)placeholder only

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

<input type="search" name="s" id="search_input">

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

A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
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