Skip to content
https://seesaa.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 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>.
Warning::
No <nav> landmark found
Info::
No banner (header) 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!) MAIN (missing!) CONTENTINFO footer

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
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-ra0j4m
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://seesaa.net/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://seesaa.net/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Lighthouse Accessibility Audits
Action
Score 78/100 — 3 failing, 10 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.

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
マイブログ div.inner > ul > li > a.login
できるだけ人生や愛とは関係ない延長戦 li.cover > a > div.text > div.footer
Tokyo2072 li.cover > a > div.text > div.footer
安田プロの「ツイてる！」日記‐静岡県伊東・沼津のゴルフスクール・ラウンドレッスン‐安田ゴルフアカデミー li.cover > a > div.text > div.footer
いつもどこかで的中だ！！ li.cover > a > div.text > div.footer
木漏れ日の記録 a > div.media > div.body > div.footer
パッキャラマード祭り a > div.media > div.body > div.footer
主婦にも色々あるわけで～扶養内パート主婦ブログ～ a > div.media > div.body > div.footer
ポン散歩 a > div.media > div.body > div.footer
愛と平和のクランキン木村遊船クランカー号@琵琶湖 a > div.media > div.body > div.footer
令和6年森羅万象 a > div.media > div.body > div.footer
人気ブログランキング div.sp-scroll > div.boxes > div.box > h3.title-baloon
人気記事ランキング div.sp-scroll > div.boxes > div.box > h3.title-baloon
楽天市場ポイントキャンペーン a > div.media > div.body > div.footer
ブラブラブラウジング a > div.media > div.body > div.footer
カルチョまとめブログ a > div.media > div.body > div.footer
のんびりなまけにっき２ a > div.media > div.body > div.footer
リードメールメモ a > div.media > div.body > div.footer
2026-04-21 div.section-contents > ul.list-information > li > div.date
2026-04-14 div.section-contents > ul.list-information > li > div.date
2026-03-16 div.section-contents > ul.list-information > li > div.date
利用規約 div.inner > ul > li > a
プライバシーポリシー div.inner > ul > li > a
広告掲載について div.inner > ul > li > a
お問い合わせ div.inner > ul > li > a
Copyright(c) Shitaraba, Inc. All Rights Reserved body > footer.global-footer > div.inner > div.copyright

These are opportunities to improve the legibility of your content.

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` 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
●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
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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.
○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.
○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
19 headings
PASS
19 headings
Info::
Single H1 present
  • H1 アフィリエイトからまとめまで Seesaaブログで思いどおりに
  • H2 Seesaaブログは無料のブログサービスです
  • H3 安心の常時SSL対応
  • H3 AdSenseも、ads.txtも
  • H3 ポッドキャストをiTunesに登録！記事にも
  • H3 複数ブログも思いのままに
  • H2 プレミアムプラン 月額330円〜
  • H3 独自ドメイン購入機能
  • H3 容量無制限、転送量UP
  • H3 RSSフィード拡張
  • H2 最新記事
  • H2 カテゴリー
  • H2 Seesaaブログランキング
  • H3 人気ブログランキング
  • H3 人気記事ランキング
  • H2 お知らせ
  • H3 Seesaaブログ
  • H3 ヘルプ
  • H3 Seesaaのサービス
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
7 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
8 images 1 good alt text 7 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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
h1 アフィリエイ…11.56:13.0:1
#000000
#DDBB8C
Pass
h1 Seesaaブログで…10.29:13.0:1
#000000
#E7AA58
Pass
h2 Seesaaブログは9.35:13.0:1
#000000
#B8AB9D
Pass
h2 無料のブログ…18.94:13.0:1
#000000
#F7F3E8
Pass
h2 プレミアムプ…18.94:13.0:1
#000000
#F7F3E8
Pass
h2 最新記事18.94:13.0:1
#000000
#F7F3E8
Pass
h2 カテゴリー18.94:13.0:1
#000000
#F7F3E8
Pass
h2 Seesaaブログラ…18.94:13.0:1
#000000
#F7F3E8
Pass
h2 お知らせ18.94:13.0:1
#000000
#F7F3E8
Pass
h3 安心の常時SSL…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AdSenseも、ads.txt…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ポッドキャス…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 複数ブログも…19.59:13.0:1
#000000
#F9F7F0
Pass
h3 独自ドメイン…18.94:13.0:1
#000000
#F7F3E8
Pass
h3 容量無制限、…18.94:13.0:1
#000000
#F7F3E8
Pass
h3 RSSフィード拡…18.94:13.0:1
#000000
#F7F3E8
Pass
h3 人気ブログラ…18.94:13.0:1
#000000
#F7F3E8
Pass
h3 人気記事ラン…18.94:13.0:1
#000000
#F7F3E8
Pass
h3 Seesaaブログ18.94:13.0:1
#000000
#F7F3E8
Pass
h3 ヘルプ18.94:13.0:1
#000000
#F7F3E8
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.

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

Send Feedback