Skip to content
https://hotpepper.jp

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 障害告知画面 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✗ Multiple Sizes Missing
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
16 of 49 images have issues
REVIEW
16 of 49 images have issues
Critical::
16 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
5 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
49 images 28 good alt text 5 decorative 16 missing
IssueCount
missing16 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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

19 pass 1 fail WCAG AA
h2 都道府県からお店を探す
1.41:1
#000000
on
#3E2003
needs 3.0:1 (large text)
24px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 全国のグルメ…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 都道府県から…1.41:13.0:1
#000000
#3E2003
Fail
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 中国・四国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.

C
Lighthouse Accessibility Audits
Action
Score 73/100 — 4 failing, 14 passed
REVIEW
73

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrapper > div.hpg-header > div.my-menu-drawer-wrap > button.drawer-close-btn div.wrapper > div.hpg-header > div.my-menu-drawer-wrap > button.drawer-close-btn

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.app-bottom-modal-content > div.app-bottom-modal-inner > div.app-bottom-modal-close-btn > a div.app-bottom-modal-content > div.app-bottom-modal-inner > div.app-bottom-modal-close-btn > 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.

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
マイメニュー body.fixed-body > div.wrapper > div.hpg-header > button.my-menu-btn
div.search-freeword-layout > div.search-freeword-wrap > div.freeword-wrap > input.freeword-input div.search-freeword-layout > div.search-freeword-wrap > div.freeword-wrap > input.freeword-input
ネット予約でポイントたまる・つかえる div.main-contents > div.member-point-header-wrap > div.point-wrap > p.text
掲載情報について div.wrapper > div.main-contents > div.about-published-info-link > a
対象日時のネット予約でポイントが最大8倍たまるお店はこちら！ポイントプラスでお得にポイントをためよう！ ul.topic-link-list > li > a > p.caption
予算に合った飲み放題付きプラン、こだわりの料理、メニューなど、幹事さんのお店探しを強力にサポート！お店探しの決定版！ ul.topic-link-list > li > a > p.caption
インテリアや雰囲気にこだわったオシャレな個室も！体にやさしいヘルシー料理も！女子会向けサービスが充実しているお得な居酒屋やランチだって！女子会におすすめなお店… ul.topic-link-list > li > a > p.caption
誕生日や記念日のお祝いに利用したいレストラン・居酒屋などのお店を徹底リサーチ！友人や職場の仲間との誕生日飲み会にも、大切なあの人との記念日デートにも、素敵なひ… ul.topic-link-list > li > a > p.caption
定番の焼肉食べ放題やスイーツ食べ放題から、ちょっと贅沢なしゃぶしゃぶ食べ放題や寿司食べ放題まで。ランチビュッフェやホテルバイキングも、食べ放題お店探しの決定版！ ul.topic-link-list > li > a > p.caption
大切な人との記念日デートや取引先との接待・食事会、非日常の贅沢なひとときを味わう自分へのご褒美ディナーなど、特別な日に行きたいプレミアムなレストラン探しならコ… ul.topic-link-list > li > a > p.caption
ログイン div.content > div.content-body > div.cap-member-wrap > a.login-btn
ホットペッパーグルメについて div.main-contents > ul > li > a
サイトマップ div.main-contents > ul > li > a
サイトマップ2 div.main-contents > ul > li.site-map-border > a
3,000円分割引チケット！ li > a > span.info > span.caption
春のポイントUPフェア li > a > span.info > span.caption
マイルがたまるお店をご紹介 li > a > span.info > span.caption
急ぎの飲み会でもネット予約OK！ li > a > span.info > span.caption
よくある問い合わせ div.hpg-footer > ul.policy-link-list > li > a
プライバシーポリシー div.hpg-footer > ul.policy-link-list > li > a
利用規約 div.hpg-footer > ul.policy-link-list > li > a
このままWeb版をつかう div.app-bottom-modal-content > div.app-bottom-modal-inner > div.app-bottom-modal-stay-web-link-wrap > a.app-bottom-modal-stay-web-link

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
関東 東京 神奈川 埼玉 千葉 茨城 栃木 群馬 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list
関西 滋賀 京都 大阪 兵庫 奈良 和歌山 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list
東海 岐阜 静岡 愛知 三重 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list
北海道 北海道 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list
東北 青森 岩手 宮城 秋田 山形 福島 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list
北陸・甲信越 新潟 富山 石川 福井 山梨 長野 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list
中国 鳥取 島根 岡山 広島 山口 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list
四国 徳島 香川 愛媛 高知 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list
九州・沖縄 福岡 佐賀 長崎 熊本 大分 宮崎 鹿児島 沖縄 div.content > div.accordion-wrap > div.accordion-content > ul.panel-link-list

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

○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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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
○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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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
○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
61 headings
PASS
61 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 都道府県からお店を探す
  • H2 クイック検索でお店を探す
  • H1 全国のグルメ情報、レストラン・居酒屋のネット予約・クーポン検索 なら｜HOT PEPPER Gourmet duplicate H1
  • H2 お知らせ
  • H2 おすすめのグルメ情報
  • H3 ポイントプラスで最大8倍
  • H3 女子会完全ガイド
  • H3 誕生日・記念日プロデュース
  • H3 目的別食べ放題ナビゲーター
  • H3 プレミアムレストランガイド
  • H3 結婚式二次会&貸切パーティー会場ナビ
  • H3 HOT PEPPER グルメ × じゃらんおすすめご当地グルメ大集合！
  • H2 ピックアップ店舗
  • H3 燈 ともる
  • H3 ぴこぴこ精肉店 春日
  • H3 赤から 上野駅前店
  • H3 青木商店
  • H3 コート・ダジュール 海老名店
  • H3 焼肉わたなべ
  • H3 居酒屋あさひ
  • H3 忍家 つくば研究学園駅前店
  • H2 おすすめのエリアから探す
  • H3 関東
  • H3 関西
  • H3 中部
  • H3 北海道・東北
  • H3 北陸・甲信越
  • H3 中国・四国
  • H3 九州・沖縄
  • H2 おすすめの駅から探す
  • H3 関東
  • H3 関西
  • H3 中部
  • H3 北海道・東北
  • H3 北陸・甲信越
  • H3 中国・四国
  • H3 九州・沖縄
  • H2 注目のキーワードから探す
  • H2 新着のグルメ特集
  • H3 春初夏グルメ・宴会パーフェクトガイド
  • H2 グルメ情報をいろいろな条件で探す
  • H3 料理・ジャンルから探す
  • H3 チェーン店一覧から探す
  • H3 ネット予約できるお店から探す
  • H3 グルメ関連ワードから探す
  • H3 キーワードから探す
  • H3 駅から探す
  • H3 ランチのあるお店から探す
  • H3 スポット情報から探す
  • H2 ホットペッパーグルメのお役立ちコンテンツ
  • H3 ポイントがつかえます！
  • H3 ホットペッパーカラオケ検索
  • H3 アプリでサクサクお店探し
  • H3 楽々スケジュール調整「調整くん」
  • H3 飲み会を楽しもう！「飲み会なんでも研究所」
  • H3 「飲み会幹事カンペキマニュアル」
  • H3 スマホ版ホットペッパーグルメ
  • H2 ホットペッパー関連サイト
  • H3 ホットペッパービューティー
  • H2 ランキングから探す

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

A
Form Accessibility
1 of 80 controls have issues
PASS
1 of 80 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="radio" name="area">
Info::
79 control(s) properly labeled
80 controls
79 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#SA41radio北海道for/id
#SA51radio青森for/id
#SA54radio秋田for/id
#SA55radio山形for/id
#SA52radio岩手for/id
#SA53radio宮城for/id
#SA56radio福島for/id
#SA11radio東京for/id
#SA12radio神奈川for/id
#SA13radio埼玉for/id
#SA14radio千葉for/id
#SA16radio栃木for/id
#SA15radio茨城for/id
#SA17radio群馬for/id
#SA61radio新潟for/id
#SA65radio山梨for/id
#SA66radio長野for/id
#SA63radio石川for/id
#SA62radio富山for/id
#SA64radio福井for/id
#SA33radio愛知for/id
#SA31radio岐阜for/id
#SA32radio静岡for/id
#SA34radio三重for/id
#SA23radio大阪for/id
#SA24radio兵庫for/id
#SA22radio京都for/id
#SA21radio滋賀for/id
#SA25radio奈良for/id
#SA26radio和歌山for/id
#SA73radio岡山for/id
#SA74radio広島for/id
#SA71radio鳥取for/id
#SA72radio島根for/id
#SA75radio山口for/id
#SA82radio香川for/id
#SA81radio徳島for/id
#SA83radio愛媛for/id
#SA84radio高知for/id
#SA91radio福岡for/id
#SA92radio佐賀for/id
#SA93radio長崎for/id
#SA94radio熊本for/id
#SA95radio大分for/id
#SA96radio宮崎for/id
#SA97radio鹿児島for/id
#SA98radio沖縄for/id
#allGenreradioお店のジャンルすべてfor/id
#G001radio居酒屋for/id
#G002radioダイニングバー・バルfor/id
#G003radio創作料理for/id
#G004radio和食for/id
#G005radio洋食for/id
#G006radioイタリアン・フレンチfor/id
#G007radio中華for/id
#G008radio焼肉・ホルモンfor/id
#G017radio韓国料理for/id
#G009radioアジア・エスニック料理for/id
#G010radio各国料理for/id
#G011radioカラオケ・パーティfor/id
#G012radioバー・カクテルfor/id
#G013radioラーメンfor/id
#G016radioお好み焼き・もんじゃfor/id
#G014radioカフェ・スイーツfor/id
#G015radioその他グルメfor/id
#allBudgetradioこだわらないfor/id
#B009radio～500円for/id
#B010radio501～1000円for/id
#B011radio1001～1500円for/id
#B001radio1501～2000円for/id
#B002radio2001～3000円for/id
#B003radio3001～4000円for/id
#B008radio4001～5000円for/id
#B004radio5001～7000円for/id
#B005radio7001～10000円for/id
#B006radio10001～15000円for/id
#B012radio15001～20000円for/id
#B013radio20001～30000円for/id
#B014radio30001円～for/id
arearadio(none)none

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

<input type="radio" name="area">

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

A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Hotpepper
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Hotpepper ✓192×192 icon ✓512×512 icon ✗Start URL ./index.html ✓Display Mode standalone ✓
Name Hotpepper Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 1 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback