Skip to content
https://www.ne.jp

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
1
PASS
6
INFO
0
Checks
13
6 PASS 1 REVIEW 6 FIX
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 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #003894
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 ModePartial Dark Mode
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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="kw">; <input type="text" name="kw">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
kwtext(サイト内検索)placeholder only
kwtext(サイト内検索)placeholder only

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

<input type="text" name="kw">; <input type="text" name="kw">

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

A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
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 CONTENTINFO footer

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

A+
Heading Hierarchy
43 headings
PASS
43 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 顧客満足度No.1獲得
  • H3 品質を追求し、価格もこだわり抜く
  • H2 おすすめサービス
  • H3 家で使う
  • H4 AsahiNet 光
  • H4 AsahiNet 光 クロスコース
  • H4 ASAHIネット 光 with フレッツ
  • H3 外で使う
  • H4 ASAHIネット LTE 「ANSIM」
  • H4 ASAHIネット WiMAX +5G
  • H3 オプション
  • H4 マカフィー® マルチアクセス
  • H4 ノートン™ ID アドバイザー
  • H4 i-フィルター
  • H3 ご検討中の方へ
  • H2 キャンペーン・特典
  • H3 AsahiNet 光 × auセット割
  • H3 固定IP無料セット
  • H3 ASAHIネット auひかり 特典
  • H3 ご友人・知人紹介特典
  • H3 AsahiNet 光 スタートキャンペーン
  • H3 WiMAX +5G スタートキャンペーン
  • H3 AsahiNet 光 クロスコーススタートキャンペーン
  • H3 ASAHIネット 光 with フレッツ キャンペーン
  • H3 かんしゃ割
  • H3 AsahiNet 光 × auセット割
  • H3 固定IP無料セット
  • H3 ASAHIネット auひかり 特典
  • H3 ご友人・知人紹介特典
  • H3 AsahiNet 光 スタートキャンペーン
  • H3 WiMAX +5G スタートキャンペーン
  • H3 AsahiNet 光 クロスコーススタートキャンペーン
  • H3 ASAHIネット 光 with フレッツ キャンペーン
  • H3 かんしゃ割
  • H3 AsahiNet 光 × auセット割
  • H3 固定IP無料セット
  • H3 ASAHIネット auひかり 特典
  • H3 ご友人・知人紹介特典
  • H2 ご利用中のお客様
  • H2 お客様からよくあるご質問
  • H2 お客様の「知りたい」「困った」の解決方法をご案内します。
  • H2 お知らせ

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
Alt Text Quality
All 70 images OK
PASS
All 70 images OK
Info::
25 image(s) with alt text over 125 characters
Info::
21 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
70 images 24 good alt text 21 decorative
IssueCount
too long25 image(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 顧客満足度No.1…19.89:13.0:1
#000000
#F2FAFF
Pass
h2 おすすめサー…19.89:13.0:1
#000000
#F2FAFF
Pass
h2 キャンペーン…19.89:13.0:1
#000000
#F2FAFF
Pass
h2 ご利用中のお…19.89:13.0:1
#000000
#F2FAFF
Pass
h2 お客様からよ…19.89:13.0:1
#000000
#F2FAFF
Pass
h2 お客様の19.89:13.0:1
#000000
#F2FAFF
Pass
h2 「知りたい」…19.89:13.0:1
#000000
#F2FAFF
Pass
h2 解決方法をご…19.89:13.0:1
#000000
#F2FAFF
Pass
h2 お知らせ19.89:13.0:1
#000000
#F2FAFF
Pass
h3 品質を追求し…19.89:13.0:1
#000000
#F2FAFF
Pass
h3 価格もこだわ…19.89:13.0:1
#000000
#F2FAFF
Pass
h3 家で使う19.89:13.0:1
#000000
#F2FAFF
Pass
h3 外で使う19.89:13.0:1
#000000
#F2FAFF
Pass
h3 オプション19.89:13.0:1
#000000
#F2FAFF
Pass
h3 ご検討中の方…19.89:13.0:1
#000000
#F2FAFF
Pass
h3 AsahiNet 光 × au…19.89:13.0:1
#000000
#F2FAFF
Pass
h3 固定IP無料セッ…19.89:13.0:1
#000000
#F2FAFF
Pass
h3 ASAHIネット auひ…19.89:13.0:1
#000000
#F2FAFF
Pass
h3 ご友人・知人…19.89:13.0:1
#000000
#F2FAFF
Pass
h3 AsahiNet 光 スタ…19.89:13.0:1
#000000
#F2FAFF
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.

A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 31 passed
PASS
97

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
顧客満足度No.1獲得 section.m-section-lv2--bg-primary > div.m-top-content > div.m-container > h2.m-top-content__heading-1
家で使う ul.m-recommend-tab__row > li.m-recommend-tab__col > button.m-recommend-tab__button > span.m-recommend-tab__button-label

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●`<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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<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.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback