Skip to content
https://rakuten.co.jp

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
37
GRADE
F
FIX
9
REVIEW
3
PASS
1
INFO
0
Checks
13
1 PASS 3 REVIEW 9 FIX
D
Landmark Structure
Action
19 landmarks
FIX
19 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
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 (missing!) MAIN (missing!) ASIDE CONTENTINFO (missing!)

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
Heading Hierarchy
Action
181 headings
FIX
181 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
58 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 最近チェックした商品
  • H2 もう一度購入
  • H2 楽天スーパーDEAL
  • H2 あなたにおすすめのクーポン有効期間：#MON#月#DATE#日(#WDAY#)#HOUR#:#MIN#まで
  • H2 人気商品ランキング
  • H2 人気商品ランキング
  • H2 Pickup! 注目商品
  • H2 有名ブランド・ショップ
  • H2 最近チェックしたショップ
  • H2 あなたにおすすめの商品をチェック
  • H2 24時間タイムセール毎日10時更新
  • H2 有名ブランド特集
  • H2 (empty)
  • H2 ジャンル
  • H3 ファッション・インナー
  • H4 レディースファッション
  • H4 メンズファッション
  • H3 キッズ・ベビーファッション
  • H4 インナー・下着・ナイトウェア
  • H4 関連サービス
  • H5 (empty)
  • H3 ファッション小物
  • H4 バッグ・小物・ブランド雑貨
  • H4 靴
  • H4 腕時計
  • H4 ジュエリー・アクセサリー
  • H4 関連サービス
  • H5 (empty)
  • H3 食品・スイーツ
  • H4 食品
  • H4 スイーツ・お菓子
  • H4 関連サービス
  • H5 楽天マート
  • H3 ドリンク・お酒
  • H4 水・ソフトドリンク
  • H4 ビール・洋酒
  • H4 日本酒・焼酎
  • H4 ワイン
  • H4 関連サービス
  • H5 (empty)
  • H5 (empty)
  • H3 日用雑貨・キッチン用品
  • H4 日用品雑貨・文房具・手芸
  • H4 キッチン用品・食器・調理器具
  • H4 関連サービス
  • H5 (empty)
  • H5 (empty)
  • H3 コスメ・健康・医薬品
  • H4 美容・コスメ・香水
  • H4 ダイエット・健康
  • H4 医薬品・コンタクト・介護
  • H4 関連サービス
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H3 キッズ・ベビー・玩具
  • H4 キッズ・ベビー・マタニティ
  • H4 おもちゃ
  • H4 関連サービス
  • H5 (empty)
  • H3 家電・TV・カメラ
  • H4 家電
  • H4 TV・オーディオ・カメラ
  • H4 関連サービス
  • H5 (empty)
  • H3 PC・スマホ・通信
  • H4 パソコン・周辺機器
  • H4 スマートフォン・タブレット
  • H4 関連サービス
  • H5 (empty)
  • H5 (empty)
  • H3 スポーツ・ゴルフ
  • H4 ゴルフ
  • H4 スポーツ・アウトドア
  • H4 関連サービス
  • H5 (empty)
  • H5 Jリーグ公式ストア
  • H3 車・バイク
  • H4 車・バイク
  • H4 車用品・バイク用品
  • H4 関連サービス
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H3 インテリア・寝具・収納
  • H4 インテリア・寝具・収納
  • H4 関連サービス
  • H3 ペット・花・DIY工具
  • H4 ペット・ペットグッズ
  • H4 花・ガーデン・DIY
  • H4 関連サービス
  • H5 楽天ペット保険
  • H5 (empty)
  • H3 サービス・リフォーム
  • H4 サービス・リフォーム
  • H4 関連サービス
  • H5 住宅・不動産
  • H3 ゲーム・ホビー・楽器
  • H4 テレビゲーム
  • H4 ホビー
  • H4 楽器・音響機器
  • H3 本・電子書籍・音楽
  • H4 本
  • H4 CD・DVD
  • H4 関連サービス
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H2 楽天のサービス
  • H3 旅行・暮らし
  • H4 旅行・暮らし
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 楽天マート
  • H5 (empty)
  • H5 楽天ガス
  • H3 本・エンタメ
  • H4 本・エンタメ
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H3 金融・マネー
  • H4 金融・マネー
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H5 (empty)
  • H4 関連サービス
  • H5 楽天証券確定拠出年金
  • H5 楽天超かんたん保険
  • H5 楽天銀行住宅ローン
  • H5 自動車保険一括見積り
  • H5 楽天ペイ（オンライン）
  • H2 季節の特集
  • H2 ショップ・ブランド
  • H2 かしこく、お得に
  • H2 エコ・リユース
  • H2 コラボ企画
  • H2 トレンド
  • H2 シーン別
  • H2 便利な配送サービス
  • H2 (empty)
  • H2 楽天グループのおすすめ特集
  • H2 楽天市場ガイド
  • H2 楽天でビジネス
  • H2 楽天市場アプリ
  • H2 楽天のサービス
  • H3 お買い物
  • H3 カード・決済
  • H3 銀行・証券・保険
  • H3 旅行・レジャー
  • H3 モバイル・通信・情報
  • H3 動画・エンタメ
  • H3 暮らし
  • H3 ポイント
  • H3 Global

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

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

F
Alt Text Quality
Action
191 of 365 images have issues
FIX
191 of 365 images have issues
Critical::
191 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
82 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
103 decorative image(s) correctly marked
Info::
71 image(s) with good alt text
365 images 71 good alt text 103 decorative 191 missing
IssueCount
missing191 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
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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
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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" id="lightBox_closeButtonError">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="sitem" id="common-header-search-input">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#common-header-search-inputsearch(キーワード検索)placeholder only
#lightBox_closeButtonErrorbutton(none)none

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

<input type="button" id="lightBox_closeButtonError">

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="sitem" id="common-header-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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 8 failing, 20 passed
REVIEW
70

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Show cart div.top-row--QN2vt > div.top-row-right--1F8Nv > div.spacer--3hYb9 > a.button--1YPpl
ログイン div.button-group-wrapper--1BnbG > div.container--1f9KH > div.container-link--1V2xO > a.button--1YPpl
会員登録 div.button-group-wrapper--1BnbG > div.container--1f9KH > div.container-link--1V2xO > a.button--1YPpl
お気に入り div > div.container--3snA3 > div.main-buttons--3fWkN > a.button--1YPpl
閲覧履歴 div > div.container--3snA3 > div.main-buttons--3fWkN > a.button--1YPpl
購入履歴 div > div.container--3snA3 > div.main-buttons--3fWkN > a.button--1YPpl
myクーポン div > div.container--3snA3 > div.main-buttons--3fWkN > a.button--1YPpl
ログイン div.container--2grkW > div.spacer--3hYb9 > div.spacer--3hYb9 > a.button--1YPpl
新規会員登録はこちら div.container--2grkW > div.spacer--3hYb9 > div.registration-link--nRfc4 > a.button--1YPpl
すべて見る div.title-wrapper--1eivO > div.sub-title-wrapper--zI_Bz > div > a.button--1YPpl
ご利用ガイド div.container--y7h8c > div.container--G4ZgU > div.spacer--3hYb9 > a.button--1YPpl
ヘルプ div.container--y7h8c > div.container--G4ZgU > div.spacer--3hYb9 > a.button--1YPpl

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div > div.etsy-banner--1r0bv > div body > div > div.etsy-banner--1r0bv > div
body > div > div.etsy-banner--1r0bv > div.close-button-container--1Nt3j body > div > div.etsy-banner--1r0bv > div.close-button-container--1Nt3j
div.top-row--QN2vt > div.top-row-left--3YyH1 > div.spacer--3hYb9 > div.hamburger-container--3ZHwt div.top-row--QN2vt > div.top-row-left--3YyH1 > div.spacer--3hYb9 > div.hamburger-container--3ZHwt

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.

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
掲載アイテム全品20%以上OFF！ a.container--gpVqv > div.content--3IBRF > div.content-text--1aLnW > div.text-display--2HKHe
まとめ買いでさらにお得！ a.container--gpVqv > div.content--3IBRF > div.content-text--1aLnW > div.text-display--2HKHe
必見！注目アイテムをチェック a.container--gpVqv > div.content--3IBRF > div.content-text--1aLnW > div.text-display--2HKHe

These are opportunities to improve the legibility of your content.

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
a.link-wrapper--1G0sw > div.container--3tUHo > div.aspect-ratio-box--14W6l > img.image--aJFXw a.link-wrapper--1G0sw > div.container--3tUHo > div.aspect-ratio-box--14W6l > img.image--aJFXw

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
body > div > div.ad-banner--1HCUr > a body > div > div.ad-banner--1HCUr > a
body > div#mkdiv_header_pitari > div > a body > div#mkdiv_header_pitari > div > a
div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp
div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp
div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp
div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp
div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp div.swiper-container > div.swiper-wrapper > div.swiper-slide > a.link--3Wnxp
div.free--3104i > div.container--17oFq > div > a div.free--3104i > div.container--17oFq > div > a
div.swiper-slide > div.container--17oFq > div > a div.swiper-slide > div.container--17oFq > div > a
div.swiper-slide > div.container--17oFq > div > a div.swiper-slide > div.container--17oFq > div > a
div.swiper-slide > div.container--17oFq > div > a div.swiper-slide > div.container--17oFq > div > a
div.swiper-slide > div.container--17oFq > div > a div.swiper-slide > div.container--17oFq > div > a
body > div > div.spacer--3hYb9 > a.link-wrapper--1G0sw body > div > div.spacer--3hYb9 > a.link-wrapper--1G0sw
body > div > div#ecosystem_bnr > a body > div > div#ecosystem_bnr > a
div.container--G4ZgU > div.spacer--3hYb9 > div.spacer--3hYb9 > a div.container--G4ZgU > div.spacer--3hYb9 > div.spacer--3hYb9 > a

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

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
新規会員登録はこちら div.container--2grkW > div.spacer--3hYb9 > div.registration-link--nRfc4 > a.button--1YPpl
Language div.spacer--3hYb9 > div > span.reference--1AAIT > button.button--1YPpl

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>`
●`[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
●Form elements have associated labels
●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
●No element has a `[tabindex]` value greater than 0
●Deprecated ARIA roles were not used
●The page contains a heading, skip link, or landmark region
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○`<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
○Heading elements appear in a sequentially-descending order
○`<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
○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.
○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.
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 最近チェック…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 もう一度購入12.87:13.0:1
#000000
#EFBFBF
Pass
h2 楽天スーパーDE…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 あなたにおす…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 人気商品ラン…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 人気商品ラン…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 Pickup! 注目商品12.87:13.0:1
#000000
#EFBFBF
Pass
h2 有名ブランド…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 最近チェック…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 あなたにおす…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 24時間タイムセ…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 有名ブランド…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 ジャンル12.87:13.0:1
#000000
#EFBFBF
Pass
h2 楽天のサービ…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 季節の特集12.87:13.0:1
#000000
#EFBFBF
Pass
h2 ショップ・ブ…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 かしこく、お…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 エコ・リユー…12.87:13.0:1
#000000
#EFBFBF
Pass
h2 コラボ企画12.87:13.0:1
#000000
#EFBFBF
Pass
h2 トレンド12.87:13.0:1
#000000
#EFBFBF
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