Skip to content
https://so-net.ne.jp

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Alt Text Quality
Action
8 of 177 images have issues
FIX
8 of 177 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
18 image(s) with alt text over 125 characters
Info::
60 decorative image(s) correctly marked
Info::
91 image(s) with good alt text
177 images 91 good alt text 60 decorative 8 missing
IssueCount
missing8 image(s)
too long18 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

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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation
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
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header SEARCH 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

B
Form Accessibility
2 of 10 controls have issues
REVIEW
2 of 10 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="q">; <input type="text" name="q">
Info::
8 control(s) properly labeled
10 controls
8 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
doctypeselectnone
sortselectnone
pagemaxselectnone
imgsizeselectnone
doctypeselectnone
sortselectnone
pagemaxselectnone
imgsizeselectnone
qtext(So-net内を検索)placeholder only
qtext(So-net内を検索)placeholder only

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

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

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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title ページが見つかりません(404 Not Found) | So-net ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 26 passed
REVIEW
85

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
form.mf_finder_searchBox_form > div.mf_finder_searchBox_items_wrapper > div.mf_finder_searchBox_items > button.mf_finder_searchBox_submit form.mf_finder_searchBox_form > div.mf_finder_searchBox_items_wrapper > div.mf_finder_searchBox_items > button.mf_finder_searchBox_submit

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
section > div._bar__cVO9_ > div._bar-body__cVO9_ > a._link__cVO9_ section > div._bar__cVO9_ > div._bar-body__cVO9_ > a._link__cVO9_

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.unq-top-layout-application__contents > div.unq-top-button-application > div.unq-top-button-application__item > a.unq-top-button-application__link
新規申し込み特典※3 ul.unq-top-list-service > li.unq-top-list-service__item > div.unq-top-list-service__price > em.unq-top-list-service__price-lead
※3 li.unq-top-list-service__item > div.unq-top-list-service__price > em.unq-top-list-service__price-lead > sup

These are opportunities to improve the legibility of your content.

Best practices

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
停止 div.mod-carousel__ui-inner > div.mod-carousel__control > div.mod-carousel__play > button.mod-carousel__play-button
6枚目のスライドへ div.mod-carousel__ui-inner > div.mod-carousel__control > div.mod-carousel__pager > button.mod-carousel__pager-button
停止 div.mod-carousel__ui-inner > div.mod-carousel__control > div.mod-carousel__play > button.mod-carousel__play-button
4枚目のスライドへ div.mod-carousel__ui-inner > div.mod-carousel__control > div.mod-carousel__pager > button.mod-carousel__pager-button

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
●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.
●`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
●`<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
●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
●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.
●Identical links have the same purpose.
○`[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
○`<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
○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>`.
○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
29 headings
PASS
29 headings
Info::
Single H1 present
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 So-net
  • H2 会員情報
  • H3 会員さまによく利用されるメニュー
  • H2 新規ご入会のお客さま
  • H2 新規ご入会のお客さま
  • H2 相談しながらお申し込み
  • H2 契約内容の確認や変更、ご利用ガイド等はこちらからご覧ください。
  • H2 (empty)
  • H3 (empty)
  • H3 (empty)
  • H2 おすすめの接続サービス
  • H3 超高速・快適さハイレベル
  • H3 コスパが高いスタンダード
  • H3 auやUQmobileのユーザーにおすすめ
  • H2 ピックアップ
  • H2 特典・キャンペーン
  • H2 重要なお知らせ
  • H2 会員特典・ポイント
  • H2 ピックアップ
  • H2 おすすめオプション
  • H2 ご利用中のお客さま
  • H3 よく閲覧されているサポート情報
  • H3 ご利用ガイド
  • H3 会員特典・ポイント
  • H2 おすすめオプション
  • H2 お申し込み特典・キャンペーン
  • H2 おすすめ情報
  • H3 ソニーの新着情報
  • 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+
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
h1 So-net17.61:13.0:1
#000000
#FFE4F0
Pass
h2 会員情報17.61:13.0:1
#000000
#FFE4F0
Pass
h2 契約内容の確…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 ご利用ガイド…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 おすすめの接…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 ピックアップ17.61:13.0:1
#000000
#FFE4F0
Pass
h2 特典・キャン…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 重要なお知ら…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 会員特典・ポ…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 ピックアップ17.61:13.0:1
#000000
#FFE4F0
Pass
h2 おすすめオプ…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 ご利用中のお…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 おすすめオプ…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 お申し込み特…17.61:13.0:1
#000000
#FFE4F0
Pass
h2 おすすめ情報17.61:13.0:1
#000000
#FFE4F0
Pass
h2 お知らせ17.61:13.0:1
#000000
#FFE4F0
Pass
h3 会員さまによ…17.61:13.0:1
#000000
#FFE4F0
Pass
h3 超高速・快適…17.61:13.0:1
#000000
#FFE4F0
Pass
h3 コスパが高い…17.61:13.0:1
#000000
#FFE4F0
Pass
h3 auやUQmobileのユ…17.61:13.0:1
#000000
#FFE4F0
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.

Send Feedback