Skip to content
https://peraichi.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 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
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 (missing!) ASIDE 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
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ 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.
C
Alt Text Quality
Action
10 of 140 images have issues
REVIEW
10 of 140 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
27 decorative image(s) correctly marked
Info::
103 image(s) with good alt text
140 images 103 good alt text 27 decorative 10 missing
IssueCount
missing10 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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title お探しのページは見つかりませんでした - ホームページ作成ならペライチ ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 26 passed
REVIEW
87

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.l-header-upper > div.l-header-upper__container > div#js-mobile-nav > button.l-header-mobile-nav__btn
What's Peraichi? div.p-top-new-overview__container > div.p-top-new-overview__desc > div.p-top-new-overview__title > p.u-weight-bold
専門知識は必要なし！ div.p-top-new-overview__func-lists > a > div.p-top-new-overview__func-item > div.p-top-new-overview__func-item--note
カンタン操作で div.p-top-new-overview__func-item--img > div.p-top-new-overview__func-item--desc > h3 > span.p-top-new-overview__func-item--desc__secondary
アイデアをその場で形に！ div.p-top-new-overview__func-lists > a > div.p-top-new-overview__func-item > div.p-top-new-overview__func-item--note
わずか30分で div.p-top-new-overview__func-item--img > div.p-top-new-overview__func-item--desc > h3 > span.p-top-new-overview__func-item--desc__secondary
疑問も不安もその場で解消！ div.p-top-new-overview__func-lists > a > div.p-top-new-overview__func-item > div.p-top-new-overview__func-item--note
安心サポートで div.p-top-new-overview__func-item--img > div.p-top-new-overview__func-item--desc > h3 > span.p-top-new-overview__func-item--desc__secondary
ペライチ予約 div.p-top-new-features__item > div.p-top-new-features__item-name > div.p-top-new-features__item-main > p.u-color-primary
詳しく見る div.p-top-new-features__others--start > div.p-top-new-features__item > div.u-flex > a.p-top-common-button
ペライチ決済 div.p-top-new-features__item > div.p-top-new-features__item-name > div.p-top-new-features__item-main > p.u-color-primary
詳しく見る div.p-top-new-features__others--start > div.p-top-new-features__item > div.u-flex > a.p-top-common-button
フォーム div.p-top-new-features__item > div.p-top-new-features__item-name > div.p-top-new-features__item-main > p.u-color-primary
詳しく見る div.p-top-new-features__others--start > div.p-top-new-features__item > div.u-flex > a.p-top-common-button
こんなサイトも、あんなサイトも。自分だけのサイトが作れます！ div.u-bgcolor-white > div.u-pb-md > div.u-pt-md > p.p-top-new-features__others--title
メルマガ配信 div.p-top-new-features__item > div.p-top-new-features__item-name > div.p-top-new-features__item-main > p.u-color-primary
詳しく見る div.p-top-new-features__others--end > div.p-top-new-features__item > div.u-flex > a.p-top-common-button
ペライチ公式note div.p-top-new-university > div.p-top-new-university__top > div.u-mt-md > a.c-btn
例えば、こんなコンテンツを発信しています div.p-top-new-university > div.p-top-new-university__bottom > div.p-top-new-university__bottom-title > span
2026.04.17 li.u-border-bottom > a.link--inherit > div.u-inline-block > span.u-color-gray-dark
2026.04.02 li.u-border-bottom > a.link--inherit > div.u-inline-block > span.u-color-gray-dark
2026.03.30 li.u-border-bottom > a.link--inherit > div.u-inline-block > span.u-color-gray-dark
2026.03.16 li.u-border-bottom > a.link--inherit > div.u-inline-block > span.u-color-gray-dark
2026.03.03 li.u-border-bottom > a.link--inherit > div.u-inline-block > span.u-color-gray-dark
ログイン body._fallback_style > footer#footer > div.u-align-center > a.link--underline
会員登録 body._fallback_style > footer#footer > div.u-align-center > a.link--underline
ペライチとは、株式会社ペライチが運営するホームページ作成サービスです。専門知識が無くてもスピーディかつ簡単にホームページが制作できます。ペライチの特徴は、直観… body._fallback_style > footer#footer > div.u-align-center > p.l-footer__overview-desc

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 4 5 6 div.p-top-new-mainvisual__container > div.p-top-new-mainvisual__main-slider > div.p-top-new-mainvisual__fv-sp > ul#js-top-new-fv-slider-sp
1 2 3 4 5 6 7 8 div.p-top-new-features__first-template > div.p-top-new-features__first-template__container > div.p-top-new-feature__example-pages > ul#js-top-new-example-pages-sp-slider
コーポレートサイト 教室予約 ポートフォリオ ネットショップ ホテル予約 資料請求 コーポレートサイト 教室予約 ポートフォリオ ネットショップ ホテル予約 … div.u-bgcolor-white > div.u-pb-md > div.u-pt-md > ul#js-top-new-template-slider

These are opportunities to improve the experience of reading tabular or list data using 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

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-*]` 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
●Image elements have `[alt]` attributes
●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
●`<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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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.
○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+
Heading Hierarchy
47 headings
PASS
47 headings
Info::
Single H1 present
  • H1 初期費用0円、ページ完成までわずか30分 ホームページ作成は ペライチ
  • H2 ペライチとは？
  • H3 充実の機能を カンタン操作で
  • H3 ページ完成まで わずか30分で
  • H3 国産サービスならではの 安心サポートで
  • H2 専門知識は必要なし カンタン操作で本格的なホームページを作成
  • H3 感覚的な操作で、ページのレイアウトを自由にカスタマイズ
  • H3 プロが作成した、600種類以上のテンプレートが使い放題！
  • H3 面倒な作業は不要で、 URLもカンタン設定
  • H3 フォームや予約・決済など、 さまざまなコンバージョン機能を実装可能！
  • H4 予約管理業務の工数を大幅削減！
  • H4 決済をもっと自由に、手軽に。
  • H4 お問合せや受付など幅広く活用！
  • H4 ネットショップ
  • H4 ホテル予約
  • H4 資料請求
  • H4 コーポレートサイト
  • H4 教室予約
  • H4 ポートフォリオ
  • H4 コーポレートサイト
  • H4 教室予約
  • H4 ポートフォリオ
  • H4 ネットショップ
  • H4 ホテル予約
  • H4 資料請求
  • H4 コーポレートサイト
  • H4 教室予約
  • H4 ポートフォリオ
  • H4 ネットショップ
  • H4 ホテル予約
  • H4 資料請求
  • H4 コーポレートサイト
  • H4 教室予約
  • H4 ポートフォリオ
  • H3 メルマガ配信で リピーター増加や売上拡大をサポート
  • H4 リピーターを増やせる！
  • H2 アイデアをその場で形に！スピーディーなページ制作でビジネスの機会損失を回避
  • H3 場所や時間を選ばずに ページを更新
  • H3 コピーライティングも AIにおまかせ
  • H3 ABテスト用ページも ワンクリックで
  • H2 疑問も不安もその場で解消！ 国産サービスならではの安心サポート
  • H3 その場で質問が出来る チャットサポート
  • H3 マンツーマンで併走する オンライン個別サポート
  • H3 ビジネスノウハウを学べる 会員限定セミナー
  • H2 選ばれて、累計60万ユーザー突破 たくさんのお声をいただいております！
  • H2 よくある質問
  • H2 新着情報
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
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 600種類以上の…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 面倒な作業は…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 URLもカンタン…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