Skip to content
https://tabelog.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 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 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 header MAIN (missing!) 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
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 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://tabelog.com/site.webmanifest contains invalid JSON. Browsers cannot parse it.
Got: https://tabelog.com/site.webmanifest

Manifest contains invalid JSON.

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
Alt Text Quality
1 of 154 images have issues
REVIEW
1 of 154 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
7 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
144 image(s) with good alt text
154 images 144 good alt text 2 decorative 1 missing
IssueCount
missing1 image(s)
too long7 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
Form Accessibility
Action
4 of 7 controls have issues
REVIEW
4 of 7 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="submit" name="commit">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="sa" id="sa">; <input type="text" name="sk" id="sk">; <input type="text" name="sw" id="sw">
Info::
3 control(s) properly labeled
7 controls
3 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
#js-global-search-datetextnone
#js-svt-headerselectnone
#js-svps-headerselectnone
#sktext(キーワード [例:焼肉、店名、個室])placeholder only
#satext(エリア・駅 [例:銀座、渋谷])placeholder only
#swtext(ユーザー名)placeholder only
commitsubmit(none)none

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

<input type="submit" name="commit">

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="text" name="sa" id="sa">; <input type="text" name="sk" id="sk">; <input type="text" name="sw" id="sw">

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
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 エリアから探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 料理ジャンルから探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 特集
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 利用シーンから探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 こだわり条件から探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 注目のグルメ記事
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 閲覧履歴
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 会員登録/ログイン
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 食べログ限定企画
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 [PR] 今月のお店
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 食べログおすすめコンテンツ
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Tabelog Award 2026
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 百名店
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ユーザーを探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 コースから探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 宴会を楽しむ
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ジャンル別ランキングから探…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 個室・設備から探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 特別なシーンから探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 その他条件、目的から探す
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 エリアから探…1.00:13.0:1
#000000
#000000
Fail
h2 料理ジャンル…1.00:13.0:1
#000000
#000000
Fail
h2 特集1.00:13.0:1
#000000
#000000
Fail
h2 利用シーンか…1.00:13.0:1
#000000
#000000
Fail
h2 こだわり条件…1.00:13.0:1
#000000
#000000
Fail
h2 注目のグルメ…1.00:13.0:1
#000000
#000000
Fail
h2 閲覧履歴1.00:13.0:1
#000000
#000000
Fail
h2 会員登録/ログ…1.00:13.0:1
#000000
#000000
Fail
h2 食べログ限定…1.00:13.0:1
#000000
#000000
Fail
h2 [PR] 今月のお店1.00:13.0:1
#000000
#000000
Fail
h2 食べログおす…1.00:13.0:1
#000000
#000000
Fail
h2 The Tabelog Award 20…1.00:13.0:1
#000000
#000000
Fail
h2 百名店1.00:13.0:1
#000000
#000000
Fail
h2 ユーザーを探…1.00:13.0:1
#000000
#000000
Fail
h2 コースから探…1.00:13.0:1
#000000
#000000
Fail
h2 宴会を楽しむ1.00:13.0:1
#000000
#000000
Fail
h2 ジャンル別ラ…1.00:13.0:1
#000000
#000000
Fail
h2 個室・設備か…1.00:13.0:1
#000000
#000000
Fail
h2 特別なシーン…1.00:13.0:1
#000000
#000000
Fail
h2 その他条件、…1.00:13.0:1
#000000
#000000
Fail

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.

B
Lighthouse Accessibility Audits
Score 83/100 — 4 failing, 27 passed
REVIEW
83

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.rsttop-container > div.rsttop-container__kv > div.rsttop-container__webtoapp-btn > a.js-analytics
Open in Multilingual App div.c-bottom-sheet > div.c-lang-switch__inner > div.c-lang-switch__install-box > a.c-lang-switch__btn
Continue on the web div.c-lang-switch__inner > div.c-lang-switch__install-box > p.c-lang-switch__install-box-text > span

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
li.rsttop-feature-list__item > a.rsttop-feature-list__target > div.rsttop-feature-list__img > img li.rsttop-feature-list__item > a.rsttop-feature-list__target > div.rsttop-feature-list__img > img
li.rsttop-feature-list__item > a.rsttop-feature-list__target > div.rsttop-feature-list__img > img li.rsttop-feature-list__item > a.rsttop-feature-list__target > div.rsttop-feature-list__img > img
li.rsttop-feature-list__item > a.rsttop-feature-list__target > div.rsttop-feature-list__img > img li.rsttop-feature-list__item > a.rsttop-feature-list__target > div.rsttop-feature-list__img > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.rsttop-container__search-inner > li.rsttop-container__search-area > div.rsttop-container__search-area-inner > input.rsttop-container__search-input ul.rsttop-container__search-inner > li.rsttop-container__search-area > div.rsttop-container__search-area-inner > input.rsttop-container__search-input
ul.rsttop-container__search-inner > li.rsttop-container__search-genre > div.rsttop-container__search-genre-inner > input.rsttop-container__search-input ul.rsttop-container__search-inner > li.rsttop-container__search-genre > div.rsttop-container__search-genre-inner > input.rsttop-container__search-input

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

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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
●`<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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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 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.
○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>`.
○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
35 headings
PASS
35 headings
Info::
Single H1 present
  • H1 全国のグルメ・レストランガイド 食べログ
  • H2 エリアから探す
  • H3 東京都内
  • H3 その他のエリア
  • H3 人気ジャンル
  • H3 北海道・東北
  • H3 関東
  • H3 中部
  • H3 関西
  • H3 中国・四国
  • H3 九州・沖縄
  • H2 料理ジャンルから探す
  • H2 特集
  • H2 利用シーンから探す
  • H2 こだわり条件から探す
  • H2 注目のグルメ記事
  • H3 食べログマガジン 新着記事
  • H3 全国の食べログまとめ アクセスランキング
  • H2 閲覧履歴
  • H2 会員登録/ログイン
  • H2 食べログ限定企画
  • H2 [PR] 今月のお店
  • H2 食べログおすすめコンテンツ
  • H2 The Tabelog Award 2026
  • H2 百名店うまいもの、いま食べるなら、このお店。
  • H2 ユーザーを探す
  • H2 コースから探す
  • H2 宴会を楽しむ
  • H2 ジャンル別ランキングから探す
  • H2 個室・設備から探す
  • H2 特別なシーンから探す
  • H2 その他条件、目的から探す
  • H2 レストラン新規登録
  • H2 店舗運営者の方へ
  • H2 食べログは カカクコム グループです。
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback