Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

Link & Button Quality

Action

7 issue(s) across 203 links and 14 buttons

FIX

7 issue(s) across 203 links and 14 buttons

4 link(s) with no accessible text

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

Got: /corp/special/answer/; /biz/about/ai/; /mobile/special/sports/; /mobile/network/tsunageru/

9 link(s) open in new tab without warning

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

Got: https://www.ymobile.jp/; https://www.linemo.jp/?utm_source=softbank&utm_medium=web&utm_campaign=top&ut…; https://www.ymobile.jp/; https://www.linemo.jp/?utm_source=softbank&utm_medium=web&utm_campaign=top&ut…; https://line.naver.jp/ti/p/%40softbank; https://twitter.com/SoftBank; https://www.facebook.com/SoftBank; https://www.instagram.com/softbank_official/; https://www.youtube.com/user/SoftBank

3 button(s) with no accessible text

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

Got: button.top-page-carousel-01-controls_prev (#184 on page); button.top-page-carousel-01-controls_next (#185 on page); button.sb-appshell-v1-pagetop_button (#1001 on page)

190 link(s) with descriptive text

203 links

4 empty

0 generic text

9 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.ymobile.jp/	ワイモバイル	new tab	Add '(opens in new tab)' to text
https://www.linemo.jp/?utm_source=softba…	ラインモ	new tab	Add '(opens in new tab)' to text
https://www.ymobile.jp/	ワイモバイル	new tab	Add '(opens in new tab)' to text
https://www.linemo.jp/?utm_source=softba…	ラインモ	new tab	Add '(opens in new tab)' to text
/corp/special/answer/	(empty)	empty	Add link text or aria-label
/biz/about/ai/	(empty)	empty	Add link text or aria-label
/mobile/special/sports/	(empty)	empty	Add link text or aria-label
/mobile/network/tsunageru/	(empty)	empty	Add link text or aria-label
https://line.naver.jp/ti/p/%40softbank	LINE	new tab	Add '(opens in new tab)' to text
https://twitter.com/SoftBank	X（旧 Twitter）	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/SoftBank	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/softbank_offic…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/SoftBank	YouTube	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

201 links and buttons have descriptive text

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

/corp/special/answer/; /biz/about/ai/; /mobile/special/sports/; /mobile/network/tsunageru/

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.ymobile.jp/; https://www.linemo.jp/?utm_source=softbank&utm_medium=web&utm_campaign=top&ut…; https://www.ymobile.jp/; https://www.linemo.jp/?utm_source=softbank&utm_medium=web&utm_campaign=top&ut…; https://line.naver.jp/ti/p/%40softbank; https://twitter.com/SoftBank; https://www.facebook.com/SoftBank; https://www.instagram.com/softbank_official/; https://www.youtube.com/user/SoftBank

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.

button.top-page-carousel-01-controls_prev (#184 on page); button.top-page-carousel-01-controls_next (#185 on page); button.sb-appshell-v1-pagetop_button (#1001 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-1fqryb

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://softbank.jp/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://softbank.jp/manifest.json

Manifest contains invalid JSON.

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.

Landmark Structure

Action

9 landmarks

REVIEW

9 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Heading Hierarchy

8 headings

REVIEW

8 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 ソフトバンクの取り組み
H3 社会課題に、アンサーを。
H3 AI
H3 スポーツ
H3 ネットワーク
H2 ソフトバンク最前線
H2 ソフトバンクの改善活動
H2 プレスリリース

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

span オンライン

4.09:1

#000000

#D91901

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 ソフトバンク�…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 ソフトバンク�…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 ソフトバンク�…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h2 プレスリリー�…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h3 社会課題に、�…	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h3 スポーツ	17.46:1	3.0:1	#000000	#EAEAEA	Pass
h3 ネットワーク	17.46:1	3.0:1	#000000	#EAEAEA	Pass
title ソフトバンク	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 災害用伝言板	14.41:1	4.5:1	#000000	#D4D6D8	Pass
span Disaster Message Boa…	14.41:1	4.5:1	#000000	#D4D6D8	Pass
a 登録・確認す�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 利用方法をみ�…	18.10:1	4.5:1	#000000	#EEEEEE	Pass
span My SoftBank	17.94:1	4.5:1	#000000	#EDEDED	Pass
span サポート	18.43:1	4.5:1	#000000	#F0F0F0	Pass
span 店舗を探す	10.40:1	4.5:1	#000000	#F0A399	Pass
span オンライン	4.09:1	4.5:1	#000000	#D91901	Fail
span ショップ	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span モバイル	18.10:1	4.5:1	#000000	#EEEEEE	Pass
span ワイモバイル	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span ラインモ	18.93:1	4.5:1	#000000	#F3F3F3	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.

Lighthouse Accessibility Audits

Score 82/100 — 4 failing, 20 passed

REVIEW

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.top-page-menu-section > div.top-page-menu-icons-row > a.top-page-menu-item > span.top-page-menu-label`
ワイモバイル `div.top-page-menu-section > div.top-page-menu-icons-row > a.top-page-menu-item > span.top-page-menu-label`
ラインモ `div.top-page-menu-section > div.top-page-menu-icons-row > a.top-page-menu-item > span.top-page-menu-label`
インターネット固定電話 `div.top-page-menu-section > div.top-page-menu-icons-row > a.top-page-menu-item > span.top-page-menu-label`
でんき `div.top-page-menu-section > div.top-page-menu-icons-row > a.top-page-menu-item > span.top-page-menu-label`
法人のお客さま `div.top-page-menu-section > div.top-page-menu-icons-row > a.top-page-menu-item > span.top-page-menu-label`
企業・IR `div.top-page-menu-section > div.top-page-menu-icons-row > a.top-page-menu-item > span.top-page-menu-label`
ネットワーク `div.top-page-menu-section > div.top-page-menu-icons-row > a.top-page-menu-item > span.top-page-menu-label`
My SoftBank `div.top-page-layout-service > div.top-page-menu-section > div.top-page-sub-menu > a.top-page-sub-btn`
サポート `div.top-page-layout-service > div.top-page-menu-section > div.top-page-sub-menu > a.top-page-sub-btn`
店舗を探す `div.top-page-layout-service > div.top-page-menu-section > div.top-page-sub-menu > a.top-page-sub-btn`
オンラインショップ `div.top-page-layout-service > div.top-page-menu-section > div.top-page-sub-menu > a.top-page-sub-btn`
ENGLISH `div.top-page-layout-service > div.top-page-menu-section > div.top-page-english-link > a`
製品／料金のお知らせ `section.top-page-section-01 > div.section-info-product-notice > aside.section-info-notices > header.section-info-notices_header`
料金 `li.section-info-notices_list-item > a.section-info-notices_link > div.section-info-notices_categories > span.section-info-notices_label`
2026年4月10日 `li.section-info-notices_list-item > a.section-info-notices_link > div.section-info-notices_categories > span.section-info-notices_date`
ソフトバンクニュースを見る `main.contents-area > section.top-page-section-01 > p.top-page-frontline-button-container > a.top-page-frontline-button`
詳しくはこちら `main.contents-area > section.top-page-section-01 > p.top-page-improvement-button-container > a.top-page-improvement-button`
テクノロジー `ul.top-page-list-news > li.top-page-list-news_item > a.top-page-link-news > span.top-page-link-news_label`
製品・サービス・料金 `ul.top-page-list-news > li.top-page-list-news_item > a.top-page-link-news > span.top-page-link-news_label`
製品・サービス・料金 `ul.top-page-list-news > li.top-page-list-news_item > a.top-page-link-news > span.top-page-link-news_label`
製品・サービス・料金 `ul.top-page-list-news > li.top-page-list-news_item > a.top-page-link-news > span.top-page-link-news_label`
一覧を見る `main.contents-area > section.top-page-section-01 > p.top-page-press-button-container > a.top-page-press-button`

These are opportunities to improve the legibility of your content.

Names and labels

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.top-page-section-01 > div.top-page-layout-col2 > section.top-page-layout-col2_item > a.top-page-link-initiatives-all `section.top-page-section-01 > div.top-page-layout-col2 > section.top-page-layout-col2_item > a.top-page-link-initiatives-all`
section.top-page-section-01 > div.top-page-layout-col2 > section.top-page-layout-col2_item > a.top-page-link-initiatives-all `section.top-page-section-01 > div.top-page-layout-col2 > section.top-page-layout-col2_item > a.top-page-link-initiatives-all`
section.top-page-section-01 > div.top-page-layout-col2 > section.top-page-layout-col2_item > a.top-page-link-initiatives-all `section.top-page-section-01 > div.top-page-layout-col2 > section.top-page-layout-col2_item > a.top-page-link-initiatives-all`
section.top-page-section-01 > div.top-page-layout-col2 > section.top-page-layout-col2_item > a.top-page-link-initiatives-all `section.top-page-section-01 > div.top-page-layout-col2 > section.top-page-layout-col2_item > a.top-page-link-initiatives-all`

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`

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
スライド 1 `div.top-page-carousel-01 > div.top-page-carousel-01-pagination > div.top-page-carousel-01-pagination_dots > button.top-page-carousel-01-pagination_dot`
スライド 2 `div.top-page-carousel-01 > div.top-page-carousel-01-pagination > div.top-page-carousel-01-pagination_dots > button.top-page-carousel-01-pagination_dot`
スライド 3 `div.top-page-carousel-01 > div.top-page-carousel-01-pagination > div.top-page-carousel-01-pagination_dots > button.top-page-carousel-01-pagination_dot`
スライド 4 `div.top-page-carousel-01 > div.top-page-carousel-01-pagination > div.top-page-carousel-01-pagination_dots > button.top-page-carousel-01-pagination_dot`
スライド 5 `div.top-page-carousel-01 > div.top-page-carousel-01-pagination > div.top-page-carousel-01-pagination_dots > button.top-page-carousel-01-pagination_dot`
スライド 6 `div.top-page-carousel-01 > div.top-page-carousel-01-pagination > div.top-page-carousel-01-pagination_dots > button.top-page-carousel-01-pagination_dot`

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

●Image elements have `[alt]` attributes

●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

●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

●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

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

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

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

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

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

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

Alt Text Quality

All 115 images OK

PASS

All 115 images OK

51 image(s) with alt text over 125 characters

64 image(s) with good alt text

115 images 64 good alt text

Issue	Count
too long	51 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /site/set/common/p/css/rf2017-ph1-print.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /site/set/common/p/css/rf2017-ph1-print.css ✓Inline @media print Not detected ✗

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.