Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 3 REVIEW 9 FIX

Heading Hierarchy

Action

48 headings, 1 skip(s)

FIX

48 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

11 empty heading(s)

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

H1 (empty)
H3 検索履歴 skipped
H3 検索履歴
H2 最近見たお店
H2 予約したお店
H2 楽天ポイント貯まる！
H2 エリアから探す
H2 東京
H2 神奈川
H2 大阪
H2 愛知
H2 京都
H2 福岡
H3 人気のエリア
H3 都道府県から探す
H2 料理ジャンルから探す
H2 居酒屋
H2 焼肉
H2 イタリアン
H2 条件・こだわりから探す
H2 個室
H2 食べ放題
H2 大人数で宴会
H2 トレンドグルメ
H2 アロマ鍋
H2 お米グルメ
H2 抹茶
H2 おすすめ特集
H2 旅行・観光におすすめご当地グルメ・ランキング・記事やお土産情報も！
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 (empty)
H2 ぐるなびの関連サービス
H3 大人のレストランガイド
H3 こちら秘書室
H3 PREMIUM GOURMET CLUB
H2 キャンペーン・お知らせ
H3 楽天ぐるなびアプリで毎日お得に！
H3 楽天ぐるなびアプリで毎日お得に！
H2 トップページに関するアンケート
H3 楽天ぐるなび都道府県

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Alt Text Quality

Action

21 of 86 images have issues

FIX

21 of 86 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

An image inside a link with no alt creates an empty link.

20 image(s) with filename as alt text

1 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

63 image(s) with good alt text

86 images 63 good alt text 1 decorative 20 generic 1 missing

Issue	Count
missing	1 image(s)
filename	20 image(s)
too long	1 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

Form Accessibility

Action

7 of 17 controls have issues

FIX

7 of 17 controls have issues

5 control(s) without accessible label

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

Got: <input type="reset">; <input type="reset">; <input type="reset">; <input type="text">; <input type="reset">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" id="js-suggest-sp-area">; <input type="search" id="js-suggest-sp-shop">

10 control(s) properly labeled

17 controls

10 labeled

2 placeholder only

5 unlabeled

Control	Type	Label	Method
#js-suggest-area	text		none
#js-suggest-shop	text		none
input	text		none
input	text		none
plans-time	text		none
plans-number	text		none
srv	checkbox		none
kods	checkbox		none
time	select		none
number	select		none
#js-suggest-sp-area	search	(エリア・駅)	placeholder only
#js-suggest-sp-shop	search	(ジャンル・店名)	placeholder only
input	reset	(none)	none
input	text	(none)	none
input	reset	(none)	none
input	reset	(none)	none
input	reset	(none)	none

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

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.

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

Link & Button Quality

Action

66 issue(s) across 309 links and 7 buttons

FIX

66 issue(s) across 309 links and 7 buttons

63 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://r.gnavi.co.jp/plan/campaign/bonus/?sc_lid=cp_home_main_pc; https://r.gnavi.co.jp/plan/campaign/bonus/?sc_lid=cp_home_main_sp; https://member.gnavi.co.jp/kanjirank/rakuten-card/?sc_cid=krank-card_home_mai…; https://member.gnavi.co.jp/kanjirank/rakuten-card/?sc_cid=krank-card_home_mai…; https://r.gnavi.co.jp/special-feature/privateroom/?sc_lid=sp_00066_home; https://r.gnavi.co.jp/special-feature/privateroom/?sc_lid=sp_00066_home; https://member.gnavi.co.jp/kanjirank/?sc_lid=kanjrank_home_main_pc_cp; https://member.gnavi.co.jp/kanjirank/?sc_lid=kanjrank_home_main_sp_cp; https://r.gnavi.co.jp/special-feature/izakaya/?sc_lid=sp_izakaya_home; https://r.gnavi.co.jp/special-feature/izakaya/?sc_lid=sp_izakaya_home (+53 more)

5 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.gnavi.co.jp/apps/; https://apps.apple.com/jp/app/id311691979?utm_source=weblp&utm_medium=ban…; https://play.google.com/store/apps/details?id=jp.co.gnavi.activity&utm_so…; https://apps.apple.com/jp/app/id311691979?utm_source=weblp&utm_medium=ban…; https://play.google.com/store/apps/details?id=jp.co.gnavi.activity&utm_so…

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: input[type="reset"].p-suggest__reset (#659 on page); input[type="reset"].p-suggest__reset (#662 on page); button.c-pagetop__button (#2165 on page)

241 link(s) with descriptive text

309 links

63 empty

0 generic text

5 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://r.gnavi.co.jp/plan/campaign/bonu…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/campaign/bonu…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/rak…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/rak…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/pr…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/pr…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/?sc…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/?sc…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/iz…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/iz…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/ya…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/ya…	(empty)	empty	Add link text or aria-label
https://lp.gurunavi.com/henai/?sc_lid=ho…	(empty)	empty	Add link text or aria-label
https://lp.gurunavi.com/henai/?sc_lid=ho…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/bpml/?sc_lid=…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/bpml/?sc_lid=…	(empty)	empty	Add link text or aria-label
https://dining.rakuten.co.jp/campaign/gn…	(empty)	empty	Add link text or aria-label
https://dining.rakuten.co.jp/campaign/gn…	(empty)	empty	Add link text or aria-label
https://www.gnavi.co.jp/apps/?sc_lid=cp_…	(empty)	empty	Add link text or aria-label
https://www.gnavi.co.jp/apps/?sc_lid=cp_…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/campaign/bonu…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/campaign/bonu…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/rak…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/rak…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/pr…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/pr…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/?sc…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/?sc…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/iz…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/iz…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/ya…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/ya…	(empty)	empty	Add link text or aria-label
https://lp.gurunavi.com/henai/?sc_lid=ho…	(empty)	empty	Add link text or aria-label
https://lp.gurunavi.com/henai/?sc_lid=ho…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/bpml/?sc_lid=…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/bpml/?sc_lid=…	(empty)	empty	Add link text or aria-label
https://dining.rakuten.co.jp/campaign/gn…	(empty)	empty	Add link text or aria-label
https://dining.rakuten.co.jp/campaign/gn…	(empty)	empty	Add link text or aria-label
https://www.gnavi.co.jp/apps/?sc_lid=cp_…	(empty)	empty	Add link text or aria-label
https://www.gnavi.co.jp/apps/?sc_lid=cp_…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/campaign/bonu…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/campaign/bonu…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/rak…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/rak…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/pr…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/pr…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/?sc…	(empty)	empty	Add link text or aria-label
https://member.gnavi.co.jp/kanjirank/?sc…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/iz…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/iz…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/ya…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/special-feature/ya…	(empty)	empty	Add link text or aria-label
https://lp.gurunavi.com/henai/?sc_lid=ho…	(empty)	empty	Add link text or aria-label
https://lp.gurunavi.com/henai/?sc_lid=ho…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/bpml/?sc_lid=…	(empty)	empty	Add link text or aria-label
https://r.gnavi.co.jp/plan/bpml/?sc_lid=…	(empty)	empty	Add link text or aria-label
https://dining.rakuten.co.jp/campaign/gn…	(empty)	empty	Add link text or aria-label
https://dining.rakuten.co.jp/campaign/gn…	(empty)	empty	Add link text or aria-label
https://www.gnavi.co.jp/apps/?sc_lid=cp_…	(empty)	empty	Add link text or aria-label
https://www.gnavi.co.jp/apps/?sc_lid=cp_…	(empty)	empty	Add link text or aria-label
#js-suggest	(empty)	empty	Add link text or aria-label
#js-plans	(empty)	empty	Add link text or aria-label
https://www.gnavi.co.jp/apps/	楽天ぐるなびアプリで…	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/jp/app/id31169197…	App Storeからダウンロー…	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Google Playからダウンロ�…	new tab	Add '(opens in new tab)' to text
https://www.gnavi.co.jp/apps/	(empty)	empty	Add link text or aria-label
https://apps.apple.com/jp/app/id31169197…	App Storeからダウンロー…	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Google Playからダウンロ�…	new tab	Add '(opens in new tab)' to text
<input>	(empty)	empty	Add button text or aria-label
<input>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

245 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://r.gnavi.co.jp/plan/campaign/bonus/?sc_lid=cp_home_main_pc; https://r.gnavi.co.jp/plan/campaign/bonus/?sc_lid=cp_home_main_sp; https://member.gnavi.co.jp/kanjirank/rakuten-card/?sc_cid=krank-card_home_mai…; https://member.gnavi.co.jp/kanjirank/rakuten-card/?sc_cid=krank-card_home_mai…; https://r.gnavi.co.jp/special-feature/privateroom/?sc_lid=sp_00066_home; https://r.gnavi.co.jp/special-feature/privateroom/?sc_lid=sp_00066_home; https://member.gnavi.co.jp/kanjirank/?sc_lid=kanjrank_home_main_pc_cp; https://member.gnavi.co.jp/kanjirank/?sc_lid=kanjrank_home_main_sp_cp; https://r.gnavi.co.jp/special-feature/izakaya/?sc_lid=sp_izakaya_home; https://r.gnavi.co.jp/special-feature/izakaya/?sc_lid=sp_izakaya_home (+53 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.gnavi.co.jp/apps/; https://apps.apple.com/jp/app/id311691979?utm_source=weblp&utm_medium=ban…; https://play.google.com/store/apps/details?id=jp.co.gnavi.activity&utm_so…; https://apps.apple.com/jp/app/id311691979?utm_source=weblp&utm_medium=ban…; https://play.google.com/store/apps/details?id=jp.co.gnavi.activity&utm_so…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

input[type="reset"].p-suggest__reset (#659 on page); input[type="reset"].p-suggest__reset (#662 on page); button.c-pagetop__button (#2165 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Lighthouse Accessibility Audits

Action

Score 62/100 — 11 failing, 21 passed

FIX

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
ぐるなびグループぐるなび選りすぐり「美食の殿堂」飲食店の経営支援結納・顔合わせ、結婚式場、二次会手土産・贈り物・ギフト情報上海ぐるなび … `div#root > nav.relatedLink > div.accordion`
ぐるなびからのお知らせ「アンケートモニター」募集中ぐるなびスタッフ募集悪質なキャッチにご注意ください `div#root > nav.relatedLink > div.accordion`
飲食店・食関連企業の方ぐるなび PRO for 飲食店ぐるなび大学のご案内ぐるなび登録のご案内（加盟店募集）ぐるなびウェディング加盟のご案内 `div#root > nav.relatedLink > div.accordion`
楽天ぐるなび外国語版 English 簡体字繁体字 한국어 `div#root > nav.relatedLink > div.accordion`

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.

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
body#top > article.l-article > div#js-scrolltop > button.c-pagetop__button `body#top > article.l-article > div#js-scrolltop > button.c-pagetop__button`

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.p-suggest__head > div.p-suggest__wrapper > form.js-submit-action > input.p-suggest__reset `div.p-suggest__head > div.p-suggest__wrapper > form.js-submit-action > input.p-suggest__reset`
div.p-suggest__head > div.p-suggest__wrapper > form.js-submit-action > input.p-suggest__reset `div.p-suggest__head > div.p-suggest__wrapper > form.js-submit-action > input.p-suggest__reset`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
指定なし 0:00 0:30 1:00 1:30 2:00 2:30 3:00 3:30 4:00 4:30 5:00 5:30 6:00 6:30 7:00… `div.p-plans__box > div.p-plans__input > label.p-plans__selectarea > select.p-plans__select`
指定なし 1名 2名 3名 4名 5名 6名 7名 8名 9名 10名 11名 12名 13名 14名 15名 16名 17名 18名 19名 20名 21名… `div.p-plans__box > div.p-plans__input > label.p-plans__selectarea > select.p-plans__select`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#js-questant > div.p-questionnaire__wrap > div#questant-embed-1328627 > iframe `div#js-questant > div.p-questionnaire__wrap > div#questant-embed-1328627 > iframe`

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.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item `div.swiper-wrapper > div.swiper-slide > div.c-swiper__contents > a.c-swiper-mv__item`
main.l-main > div#js-suggest > div.p-suggest__head > a.p-suggest__back `main.l-main > div#js-suggest > div.p-suggest__head > a.p-suggest__back`
body#top > main.l-main > div#js-plans > a.p-search__menu--back `body#top > main.l-main > div#js-plans > a.p-search__menu--back`

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
インストール `div#js-app > div.p-webapp__wrap > a#js-app-install > div.p-webapp__button`
開く `div#js-app > div.p-webapp__wrap > a#js-app-install > div.p-webapp__button`
予約履歴 `div.c-header__box > div.c-header__container > a.c-header__reserv > div.c-header__text`
ログイン `div.c-header__box > div.c-header__container > a.c-header__login > div.c-header__text`
検索する `div.p-search__inner > div.p-search__contents > div.p-search__submit > button.c-button`
検索する `main.l-main > div#js-suggest > div.p-suggest__setting > a.c-button`
最近見たお店 `section.p-contents > div.p-history__wrap > div.p-history__box > h2.p-history__title`
新宿 `li.swiper-slide > a.p-contents__link > dl.c-vertical > dd.c-vertical__caption`
品川 `li.swiper-slide > a.p-contents__link > dl.c-vertical > dd.c-vertical__caption`
聖蹟桜ヶ丘 `li.swiper-slide > a.p-contents__link > dl.c-vertical > dd.c-vertical__caption`
吉祥寺 `li.swiper-slide > a.p-contents__link > dl.c-vertical > dd.c-vertical__caption`
対象店舗を見る `section.p-contents > div.p-rakuten__wrap > div.p-rakuten__box > a.c-button`
もっと見る `div.p-areas__container > div.c-label > div.p-contents__more > div.toggle-more`
もっと見る `div.p-cassete__container > div.c-label > div.p-contents__more > div.toggle-more`
もっと見る `div.p-cassete__container > div.c-label > div.p-contents__more > div.toggle-more`

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.p-contents__list > li.swiper-slide > span.p-contents__link > dl.c-vertical `ul.p-contents__list > li.swiper-slide > span.p-contents__link > dl.c-vertical`
ul.p-contents__list > li.swiper-slide > span.p-contents__link > dl.c-vertical `ul.p-contents__list > li.swiper-slide > span.p-contents__link > dl.c-vertical`
ul.p-contents__list > li.swiper-slide > span.p-contents__link > dl.c-vertical `ul.p-contents__list > li.swiper-slide > span.p-contents__link > dl.c-vertical`
ul.p-contents__list > li.swiper-slide > span.p-contents__link > dl.c-vertical `ul.p-contents__list > li.swiper-slide > span.p-contents__link > dl.c-vertical`

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.p-contents__more-wrap > div.p-areas__container > div.c-label > ul#more-area`
宴会・カラオケ海鮮・魚介鍋バー・バル韓国料理もつ鍋ジンギスカンもんじゃ焼き牛タンステーキかに料理カフェ・スイーツうなぎ水炊き焼肉・… `div.p-contents__more-wrap > div.p-cassete__container > div.c-label > ul#more-genre`
駐車場有女子会におすすめ接待に使えるデートにおすすめ誕生日特典あり二次会におすすめ記念日におすすめ夜景が見える日曜営業カップルシート一人で… `div.p-contents__more-wrap > div.p-cassete__container > div.c-label > ul#more-condition`

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`

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
Go to slide 1 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 7 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 8 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 9 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 10 `div.c-swiper-mv > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`button`, `link`, and `menuitem` elements have accessible names

●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

●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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

○`[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 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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<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

○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

○Identical links have the same purpose.

○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.

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

No <nav> landmark found

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title お探しのページは見つかりません | ぐるなび-宴会・グルメ情報検索サイト ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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)

Element	Ratio	Required	FG	BG	Result
h2 最近見たお店	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 予約したお店	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 貯まる！	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 エリアから探�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 東京	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 神奈川	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 大阪	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 愛知	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 京都	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 福岡	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 料理ジャンル�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 居酒屋	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 焼肉	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 イタリアン	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 条件・こだわ�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 個室	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 食べ放題	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 大人数で宴会	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 トレンドグル�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 アロマ鍋	21.00:1	3.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.