Skip to content
https://infoseek.co.jp

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Form Accessibility
Action
4 of 4 controls have issues
FIX
4 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="search" id="search-btn">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="qt" id="qt1">; <input type="text" name="q" id="site-search-keyword">
4 controls
0 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#qt1text(ウェブを検索)placeholder only
#site-search-keywordtext(キーワード)placeholder only
#search-btnsubmit(none)none
inputsubmit(none)none

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

<input type="submit" name="search" id="search-btn">; <input type="submit">

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="qt" id="qt1">; <input type="text" name="q" id="site-search-keyword">

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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-7acpyh
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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 Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://infoseek.co.jp/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://infoseek.co.jp/manifest.json

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::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) 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

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 1 pass AA only
a ・楽天ブログラッキーくじ
2.95:1
#000000
on
#515961
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

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 Infoseekニュース…21.00:13.0:1
#000000
#FFFFFF
Pass
title Infoseek[インフ…10.52:14.5:1
#000000
#FF96CF
Pass
a 楽天Infoseek21.00:14.5:1
#000000
#FFFFFF
Pass
span ポイントを貯…21.00:14.5:1
#000000
#FFFFFF
Pass
b ★Infoseekミッシ…21.00:13.0:1
#000000
#FFFFFF
Pass
a 記事を読んだ…20.87:14.5:1
#000000
#FFFEFF
Pass
a 詳しくはこち…21.00:14.5:1
#000000
#FFFFFF
Pass
li ★Infoseek限定ラ…21.00:14.5:1
#000000
#FFFFFF
Pass
a 広告を見てラ…21.00:14.5:1
#000000
#FFFFFF
Pass
li ★毎日100万ポ…21.00:14.5:1
#000000
#FFFFFF
Pass
a エントリー不…21.00:14.5:1
#000000
#FFFFFF
Pass
b ■ポイントサ…19.60:13.0:1
#000000
#F7F7F7
Pass
a ・Infoseekラッキ…19.60:14.5:1
#000000
#F7F7F7
Pass
a ・不動産ラッ…8.88:14.5:1
#000000
#A5A9AD
Pass
a ・楽天ブログ…2.95:14.5:1
#000000
#515961
Fail
a ・ゲームセン…5.19:14.5:1
#000000
#797F85
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 22 passed
REVIEW
80

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > ins#geniee_overlay_outer > ins#geniee_overlay_inner > span#geniee_overlay_close body > ins#geniee_overlay_outer > ins#geniee_overlay_inner > span#geniee_overlay_close

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.

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.information_menu > div.infomenu_list > a.btn_weather > p.lead
THE ANSWER a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月21日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
集英社オンライン a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月21日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
Record China a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月21日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
日刊ゲンダイDIGITAL a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月21日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
読売新聞 a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月21日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
日刊ゲンダイDIGITAL a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月21日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
スポニチアネックス a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月19日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
プレジデントオンライン a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月21日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
スポニチアネックス a.item-label-href > span.video-label-box > span.video-label > span.tbl-data-field
2026年04月19日 div.videoCube > a.item-label-href > span.video-label-box > span.video-label
Verisure a.item-label-href > span.video-label-box > span.branding > span.branding-inner
(PR) span.branding > div.logoDiv > a.trc_mobile_disclosure_link > span
© Rakuten Group, Inc. footer#footer > div.rex-footer > div.rex-footer--inner > p.rex-footer-copyright

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
提供元企業 footer#footer > div.copyrights-text > p > a

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
大谷翔平 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
4月 変わる制度 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
GW特集 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
マスターズゴルフ div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
イラン情勢 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
春ドラマ div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
プロ野球 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
高市政権 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
京都 男児 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
皇室典範 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
ローマ教皇 div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item
りくりゅう div.swiper > div#swiper-wrapper-86afbc1092c89718f > ul.swiper-slide > li.trend-words__item

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

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
(PR) span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
○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
●Image elements have `[alt]` attributes
●ARIA attributes are used as specified for the element's role
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○Buttons have an accessible name
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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
○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
7 headings
PASS
7 headings
Info::
Single H1 present
  • H1 楽天Infoseek
  • H2 津波情報 気象庁発表
  • H2 地震情報
  • H2 ニュース速報
  • H2 ランキング
  • H2 ★ 話題のニュースをまとめ読み
  • H2 Infoseekニュース公式
A+
Alt Text Quality
All 20 images OK
PASS
All 20 images OK
Info::
2 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
20 images 18 good alt text 2 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback