Skip to content
https://shop-pro.jp

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Alt Text Quality
Action
6 of 91 images have issues
FIX
6 of 91 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
2 image(s) with filename as alt text
Info::
1 image(s) with alt text over 125 characters
Info::
37 decorative image(s) correctly marked
Info::
47 image(s) with good alt text
91 images 47 good alt text 37 decorative 2 generic 4 missing
IssueCount
missing4 image(s)
filename2 image(s)
too long1 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

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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title ��õ���Υڡ����ϸ��Ĥ����ޤ����Ǥ���|���顼�ߡ������å� ���Ҥ˶���EC�����ȹ��ۥ����ӥ� ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 27 passed
REVIEW
89

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
人気 No.1 div.plan-list__item > div.plan-card > div.plan-card__header > div.plan-card__badge
おすすめ div.plan-list__item > div.plan-card > div.plan-card__header > div.plan-card__badge
長期契約で月額費用がお得に！ dl.plan-card__emphasis > div > dd.plan-fee > p.plan-notice
FAQ div.c-section__title > div.section-title > div.section-title__text-unit > span.section-title__sub
AIに聞いてみる div.miibo-toast > button#chat-button > span.miibo-toast__content > span.miibo-toast__cta

These are opportunities to improve the legibility of your content.

Names and labels

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
div.gmoGroupHeader > div.gmoGroupHeader_logo > div.gmoGroupHeader_3wins > a div.gmoGroupHeader > div.gmoGroupHeader_logo > div.gmoGroupHeader_3wins > 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

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
バナーを閉じる main > div#js-popup-banner > div.popup-banner__container > button#js-popup-close

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
無料診断 div.gmoGroupHeader > div.gmoGroupHeader_secCont > div.gmoGroupHeader_sec > a
○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
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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.
○`[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
○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
○`<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.
○Image elements do not have `[alt]` attributes that are redundant text.
A
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV 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

A+
Heading Hierarchy
26 headings
PASS
26 headings
Info::
Single H1 present
  • H1 AIで伸ばすECカート 商品登録もページ更新もAIにおまかせ
  • H2 人×AIによるサポート
  • H2 導入事例
  • H2 ショップ運営を支える機能
  • H2 万全のセキュリティ
  • H2 事業フェーズで選べる3つのプラン
  • H3 レギュラー
  • H3 ラージ
  • H3 プレミアム
  • H3 商材別プラン
  • H2 開発中・提供予定の機能
  • H3 機能
  • H3 API
  • H2 お知らせ
  • H2 イベント・セミナー
  • H3 《4/30(木）》今日から追いつける！EC担当者のためのAI活用入門セミナー開催
  • H3 《全4回開催》本気でECを成長させたい方大募集！「ECグロースアカデミー」開講決定
  • H3 公式Webメディア
  • H2 よくある質問
  • H2 ビジネスの成長に必要な機能はすべて揃っています
  • H3 サービス資料
  • H3 ご相談窓口
  • H3 サービス情報
  • H3 サポート
  • H3 制作会社・提携会社さまへ
  • H3 トピックス
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 導入事例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 お知らせ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 必要な機能は21.00:13.0:1
#000000
#FFFFFF
Pass
h2 すべて揃って…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 API21.00:13.0:1
#000000
#FFFFFF
Pass
h3 《4/30(木）》今…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 《全4回開催》…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 公式Webメディ…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.

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

Send Feedback