Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 3 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #385477

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Mobile-Readable Font Sizes

Action

81% of visible text renders at >= 12 CSS px (5 below threshold)

REVIEW

81% of visible text renders at >= 12 CSS px (5 below threshold)

5 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: <span> 9.0px ("Chugoku"); <span> 9.0px ("Hikikomori"); <span> 9.0px ("Kyokai"); <span> 11.0px ("CHK"); <span> 11.0px ("CHK").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 欢迎加入CHK ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

6 headings

PASS

6 headings

Single H1 present

H1 WELCOME TOTHE CHKBLOG
H2 最新文章
H3 折腾七年，我决定清空重来
H3 网站重构改版
H2 随机文章
H2 最近在看

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

6 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: 6 all-caps heading(s)

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

5 decorative image(s) correctly marked

6 image(s) with good alt text

11 images 6 good alt text 5 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

15 links, 8 buttons — all OK

PASS

15 links, 8 buttons — all OK

6 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://bgm.tv/subject/633836; https://bgm.tv/subject/585820; https://bgm.tv/subject/412144; https://bgm.tv/subject/515594; https://bgm.tv/subject/638151; https://bgm.tv/subject/528828

9 link(s) with descriptive text

15 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/posts/zhetengqinian-wojuedingqingkongzh…	CHK折腾七年，我决定清…	img no alt	Add alt attribute to the image
/posts/wangzhanchonggougaiban	CHK网站重构改版作者因…	img no alt	Add alt attribute to the image
https://bgm.tv/subject/633836	在 Bangumi 查看 Re：从零…	new tab	Add '(opens in new tab)' to text
https://bgm.tv/subject/585820	在 Bangumi 查看 Clevatess I…	new tab	Add '(opens in new tab)' to text
https://bgm.tv/subject/412144	在 Bangumi 查看恋爱游�…	new tab	Add '(opens in new tab)' to text
https://bgm.tv/subject/515594	在 Bangumi 查看关于我�…	new tab	Add '(opens in new tab)' to text
https://bgm.tv/subject/638151	在 Bangumi 查看地狱模�…	new tab	Add '(opens in new tab)' to text
https://bgm.tv/subject/528828	在 Bangumi 查看骸骨骑�…	new tab	Add '(opens in new tab)' to text

17 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://bgm.tv/subject/633836; https://bgm.tv/subject/585820; https://bgm.tv/subject/412144; https://bgm.tv/subject/515594; https://bgm.tv/subject/638151; https://bgm.tv/subject/528828

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 最新文章	20.12:1	3.0:1	#000000	#FDFAF1	Pass
h2 随机文章	20.12:1	3.0:1	#000000	#FDFAF1	Pass
h2 最近在看	20.12:1	3.0:1	#000000	#FDFAF1	Pass
h3 折腾七年，我�…	20.12:1	3.0:1	#000000	#FDFAF1	Pass
h3 网站重构改版	20.12:1	3.0:1	#000000	#FDFAF1	Pass
title 欢迎加入CHK	20.12:1	4.5:1	#000000	#FDFAF1	Pass
a 欢迎加入CHK	20.12:1	4.5:1	#000000	#FDFAF1	Pass
a 主页	20.12:1	4.5:1	#000000	#FDFAF1	Pass
a 文章	20.12:1	4.5:1	#000000	#FDFAF1	Pass
a 说说	20.12:1	4.5:1	#000000	#FDFAF1	Pass
a 看番	20.12:1	4.5:1	#000000	#FDFAF1	Pass
a 关于	20.12:1	4.5:1	#000000	#FDFAF1	Pass
span WELCOME TO	20.12:1	4.5:1	#000000	#FDFAF1	Pass
span THE	20.12:1	4.5:1	#000000	#FDFAF1	Pass
span CHK	20.12:1	4.5:1	#000000	#FDFAF1	Pass
span BLOG	20.12:1	4.5:1	#000000	#FDFAF1	Pass
span Chugoku	20.12:1	4.5:1	#000000	#FDFAF1	Pass
span 中国	20.12:1	4.5:1	#000000	#FDFAF1	Pass
span Hikikomori	20.12:1	4.5:1	#000000	#FDFAF1	Pass
span ひきこもり	20.12:1	4.5:1	#000000	#FDFAF1	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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 17 passed

PASS

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
Chugoku 中国 `div.relative > button.mt-8 > span.mt-[12px] > span.relative`
Chugoku `button.mt-8 > span.mt-[12px] > span.relative > span.absolute`
Hikikomori ひきこもり `div.relative > button.mt-8 > span.mt-[12px] > span.relative`
Hikikomori `button.mt-8 > span.mt-[12px] > span.relative > span.absolute`
Kyokai 協会 `div.relative > button.mt-8 > span.mt-[12px] > span.relative`
Kyokai `button.mt-8 > span.mt-[12px] > span.relative > span.absolute`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chugoku 中国 Hikikomori ひきこもり Kyokai 協会 `div.pb-4 > section.relative > div.relative > button.mt-8`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●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

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

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

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

○Identical links have the same purpose.

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