Skip to content
https://ameblo.jp

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
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
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.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 MAIN ASIDE 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

B
404 Error Page
HTTP 404, custom page
REVIEW
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
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
A+
Heading Hierarchy
24 headings
PASS
24 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 Amebaでブログを書こう
  • H2 注目の情報・キャンペーン
  • H3 Amebaを始めよう！こちらから無料で登録
  • H3 Amebaってどんなサービス？
  • H3 Amebaを始めよう！こちらから無料で登録
  • H3 いい商品・サービスを探す
  • H4 記事から探す
  • H4 カテゴリから探す
  • H3 公式トップブロガーランキング
  • H3 トップブロガー・ブロガーの人気記事
  • H3 トップブロガーズマガジンへ
  • H3 公式ジャンルカテゴリ
  • H3 Amebaを始めよう！こちらから無料で登録
  • H2 Amebaを始めよう！ダウンロードはこちら
  • H3 Amebaのお得な情報・キャンペーン
  • H3 Amebaの使い方
  • H3 芸能人・有名人のインタビュー・特集
  • H3 芸能人・有名人の最新記事
  • H3 Amebaを始めよう！こちらから無料で登録
  • H2 Amebaを始めよう！ダウンロードはこちら
  • H3 Amebaに関連する機能・サービス
  • H3 安心・安全への取り組み
  • H2 Amebaのサービス

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A
Alt Text Quality
All 128 images OK
PASS
All 128 images OK
Info::
10 image(s) with alt text over 125 characters
Info::
68 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
128 images 50 good alt text 68 decorative
IssueCount
too long10 image(s)
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
h2 でブログを書…9.40:13.0:1
#000000
#ADAEA9
Pass
h2 注目の情報・…8.62:13.0:1
#000000
#A7A6A2
Pass
h2 を始めよう！21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ダウンロード…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 を始めよう！21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ダウンロード…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Amebaのサービス21.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 Amebaってどんな…21.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 いい商品・サ…21.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 人気記事21.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 を始めよう！21.00:13.0:1
#000000
#FFFFFF
Pass
h3 登録21.00:13.0: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 96/100 — 2 failing, 25 passed
PASS
96

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ブログで役立つ情報を発信中！ div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
Amebaの商品比較メディア div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
納得の進路・高校を見つけるなら div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
クレカ・ローン情報をご紹介！ div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
わが子の100点塾探しするなら div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
全部教えて！と言われる美容法 div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
ブログで役立つ情報を発信中！ div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
Amebaの商品比較メディア div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
納得の進路・高校を見つけるなら div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
クレカ・ローン情報をご紹介！ div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
わが子の100点塾探しするなら div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
全部教えて！と言われる美容法 div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
ブログで役立つ情報を発信中！ div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
Amebaの商品比較メディア div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
納得の進路・高校を見つけるなら div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY
クレカ・ローン情報をご紹介！ div > section.CampaignCarousel_CarouselContainer__EBhgM > ul.CampaignCarousel_List__dm5_b > li.CampaignCarousel_ListItem__JgrgY

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
もっと見る aside.NewTopBloggerRankingList_Block__jwu3d > div.NewTopBloggerRankingList_Item__a24GY > div.NewTopBloggerRankingItem_MoreButtonContainer__NGnz3 > a.spui-LinkButton
もっと見る aside.NewTopBloggerRankingList_Block__jwu3d > div.NewTopBloggerRankingList_Item__a24GY > div.NewTopBloggerRankingItem_MoreButtonContainer__NGnz3 > a.spui-LinkButton
もっと見る aside.NewTopBloggerRankingList_Block__jwu3d > div.NewTopBloggerRankingList_Item__a24GY > div.NewTopBloggerRankingItem_MoreButtonContainer__NGnz3 > a.spui-LinkButton
○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
●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
●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.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●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
●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 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
○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.
○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.
○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