Skip to content
https://qiita.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
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: xwpktg32-_c4jozoj_usmdui-zah-hcrjf6zc_fofbk
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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
31 headings
REVIEW
31 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 【初心者エンジニア向け】開発を前に進めるための行動3選
  • H2 一人で悩み続けてしまう新人エンジニアへ。その時間、無駄かもしれません。
  • H2 Claude Codeの利用状況をチームで可視化するダッシュボードをOSSで公開しました
  • H2 【Claude Design】見せてもらおうか Claude Designの性能とやらを
  • H2 【Obsidian】作図が簡単にできるプラグイン「Excalidraw」の紹介
  • H2 n8nで植物の水やりリマインドBOTを作ってみた（Discord連携）
  • H2 React初心者がつまずきやすいJavaScript記法をわかりやすく整理してみた
  • H2 Claude Code実行中にターミナルを閉じても大丈夫にする方法（tmux）
  • H2 Docker環境を1台のサーバーで共存させる：80/443ポート競合を解決する実践構成
  • H2 関数型インターフェース入門 — Function / Predicate / Consumer / Supplier を整理する
  • H2 Claude Codeを使って分かった「開発で詰まるポイントの正体」
  • H2 Claude Code × MagicPod MCPでテストケースメンテナンスレビューを自動化してみた
  • H2 n8nでBBCニュースを自動翻訳・要約してDiscordに通知する仕組みを作ってみた
  • H2 レイヤードアーキテクチャを図とコードでやさしく理解する（C# / ASP.NET Core）
  • H2 == と equals() の違いを完全に理解する — なぜStringの比較は equals() を使うのか
  • H2 【初心者必見】今から追いつくClaude Code 入門・徹底解説
  • H2 [TypeScriptシリーズ - Part 5] Branded Types
  • H2 [Frontend Performance] パフォーマンスは「最後にやるもの」ではない
  • H2 [TypeScriptシリーズ - Part 6] Dependency Injection in TypeScript
  • H2 記憶を持たないLLMの記憶 ― コンテキスト/メモリー/ハーネスエンジニアリング入門の前に
  • H2 【対策】XSS・CSRF・クライアントサイドセキュリティ完全対策ガイド
  • H2 Claude Code の週次タスクを安定させたくて、MCPを捨てて公式CLI（bee / Pup）に移行した話
  • H2 [TypeScriptシリーズ - Part 4] Variance
  • H2 [Frontend Performance - Part 1] ブラウザの描画処理を理解する（Rendering Pipeline入門）
  • H2 React Hook Form 入門 Part 1 — 仕組みを理解してから使う
  • H2 【徹底解説】DBスペシャリストなりぞこないが教える、データベースの教科書（設計もあるよ）
  • H2 Claude Codeで開発を自動化するSkills 5選
  • H2 5分でわかる！データリネージとは？
  • H2 # [TypeScriptシリーズ - Part 3] Template Literal Types
  • H2 [Frontend Performance - Part 2] Reflow / Repaint / Compositeの違いとは？ブラウザが重くなる瞬間を理解する）
  • H2 Why don't you log in to Qiita to read more recommended articles?

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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: <select>
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">; <input type="text" name="q">
3 controls
0 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
qsearch(Search)placeholder only
qtext(Search)placeholder only
selectselect(none)none

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

<select>

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="q">; <input type="text" name="q">

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
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Landmark Structure
67 landmarks
PASS
67 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Global" SEARCH MAIN CONTENTINFO footer

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
Alt Text Quality
1 of 81 images have issues
PASS
1 of 81 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
11 decorative image(s) correctly marked
Info::
69 image(s) with good alt text
81 images 69 good alt text 11 decorative 1 missing
IssueCount
missing1 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

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found - Qiita - Qiita ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Qiita
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Qiita ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa ✓Display Mode standalone ✓
Name Qiita Display Mode standalone Theme Color #67c751 Background Color #fff Icons 4 icon(s)
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)
ElementRatioRequiredFGBGResult
h2 Why don't you log in…16.67:13.0:1
#000000
#E5E5E5
Pass
title Qiita21.00:14.5:1
#000000
#FFFFFF
Pass
span search21.00:14.5:1
#000000
#FFFFFF
Pass
span search21.00:14.5:1
#000000
#FFFFFF
Pass
span Search19.40:14.5:1
#000000
#F5F6F6
Pass
a Login19.40:14.5:1
#000000
#F5F6F6
Pass
a Signup19.40:14.5:1
#000000
#F5F6F6
Pass
span search19.40:14.5:1
#000000
#F5F6F6
Pass
a Trend19.40:14.5:1
#000000
#F5F6F6
Pass
a Stock List19.40:14.5:1
#000000
#F5F6F6
Pass
a Question19.40:14.5:1
#000000
#F5F6F6
Pass
a Qiita Conference19.40:14.5:1
#000000
#F5F6F6
Pass
a Official Event20.08:14.5:1
#000000
#F9FAFA
Pass
a Official Column21.00:14.5:1
#000000
#FFFFFF
Pass
span open_in_new21.00:14.5:1
#000000
#FFFFFF
Pass
a Organization21.00:14.5:1
#000000
#FFFFFF
Pass
a Qiita Careers21.00:14.5:1
#000000
#FFFFFF
Pass
span open_in_new21.00:14.5:1
#000000
#FFFFFF
Pass
a AI x Dev x Team21.00:14.5:1
#000000
#FFFFFF
Pass
span open_in_new21.00:14.5:1
#000000
#FFFFFF
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 92/100 — 3 failing, 25 passed
PASS
92

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.

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
body > div.coins-optin-dialog > div.coins-optin-dialog-icon > img body > div.coins-optin-dialog > div.coins-optin-dialog-icon > img

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All div.style-1p79y90 > div.style-ymwvwh > div.style-k008qs > button.style-rsiuq2
flag 新人プログラマ応援 - みんなで新人を育てよう！ main.style-13bbk6m > div.style-1p44k52 > article.style-1w7apwp > a.style-hayto5
@masa20057 header.style-12s080b > div.style-1jaw0rg > p.style-7d8kow > a.style-1h2ruwl
株式会社PRUM header.style-12s080b > div.style-1jaw0rg > p.style-7d8kow > a.style-1h2ruwl
flag 新人プログラマ応援 - みんなで新人を育てよう！ main.style-13bbk6m > div.style-1p44k52 > article.style-1w7apwp > a.style-hayto5
@hitomin_poke(ひとみん) header.style-12s080b > div.style-1jaw0rg > p.style-7d8kow > a.style-1h2ruwl
新人エンジニア footer.style-wr1ke6 > ul.style-1av12sx > li > a.style-19h8hex
flag 新人プログラマ応援 - みんなで新人を育てよう！ main.style-13bbk6m > div.style-1p44k52 > article.style-1w7apwp > a.style-hayto5
@take-yoda(依田 健人) header.style-12s080b > div.style-1jaw0rg > p.style-7d8kow > a.style-1h2ruwl
flag 新人プログラマ応援 - みんなで新人を育てよう！ main.style-13bbk6m > div.style-1p44k52 > article.style-1w7apwp > a.style-hayto5
@i-inose(Izuru Inose) header.style-12s080b > div.style-1jaw0rg > p.style-7d8kow > a.style-1h2ruwl
flag 新人プログラマ応援 - みんなで新人を育てよう！ main.style-13bbk6m > div.style-1p44k52 > article.style-1w7apwp > a.style-hayto5
@miruky(miruky) header.style-12s080b > div.style-1jaw0rg > p.style-7d8kow > a.style-1h2ruwl
ClaudeCode footer.style-wr1ke6 > ul.style-1av12sx > li > a.style-19h8hex
flag 新人プログラマ応援 - みんなで新人を育てよう！ main.style-13bbk6m > div.style-1p44k52 > article.style-1w7apwp > a.style-hayto5
@yushibats header.style-12s080b > div.style-1jaw0rg > p.style-7d8kow > a.style-1h2ruwl
日本オラクル株式会社 header.style-12s080b > div.style-1jaw0rg > p.style-7d8kow > a.style-1h2ruwl

These items highlight common accessibility best practices.

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
Remarkable items.Refreshed at every 5 a.m.and 5 p.m. rss_feed div.style-1r8xejc > main.style-13bbk6m > div.style-7jelsc > a.style-1a1bxcj
○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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●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 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
○`<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.
○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.

Send Feedback