Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 4 REVIEW 2 FIX

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (4 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (4 below threshold)

4 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("家具配置"); <span> 10.0px ("家具消し"); <span> 10.0px ("青空加工"); <span> 10.0px ("写真補正").

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title ページが見つかりません｜Virtual Staging ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light

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: #f8f9fb

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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

title 無料で試せるAIバーチャルス�…

1.66:1

#000000

#0B3558

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 無料で試せる	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 AIバーチャルス…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 15秒でわかるバ…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 バーチャルス�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 バーチャルス�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 そのままReels・…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ポータル用の�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ZIPひとつで、�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 CG加工でも、	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 安心して掲載�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 バーチャルス�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 外注のホーム�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 1物件ずつ、わ�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 バーチャルス�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 よくある質問	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 まずは無料で�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 関連ツール	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 お役立ち記事	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title 無料で試せるAI…	1.66:1	4.5:1	#000000	#0B3558	Fail
span 無料デモ	21.00:1	4.5:1	#000000	#FFFFFF	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.

Landmark Structure

16 landmarks

PASS

16 landmarks

<main> landmark present

1 <nav> landmark(s) 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

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

28 headings

PASS

28 headings

Single H1 present

H1 無料で試せるAIバーチャルステージング｜Virtual Staging
H2 AIバーチャルステージングを生成
H2 15秒でわかるバーチャルステージングの流れ
H2 バーチャルステージングで、変わること・変わらないこと。
H2 バーチャルステージングから入稿まで、5ステップ。
H2 そのままReels・TikTok・LINEへ
H2 ポータル用の文章と、英語・中国語の参考訳を同時に。
H2 ZIPひとつで、そのまま入稿。
H2 CG加工でも、安心して掲載できる設計に。
H2 バーチャルステージングが役立つ、賃貸の現場
H2 外注のホームステージングとも、単画像ツールとも違う選択肢。
H2 1物件ずつ、わかりやすい料金。
H2 バーチャルステージングとは
H2 よくある質問
H3 Q.バーチャルステージングとは何ですか？
H3 Q.無料でどこまで使えますか？
H3 Q.注記は外せますか？
H3 Q.SUUMOやHOME'Sに掲載できますか？
H3 Q.間取りや窓の形が変わることはありますか？
H3 Q.1物件で何枚まで加工できますか？
H3 Q.動画の長さはどのくらいですか？
H3 Q.請求書払いはできますか？
H3 Q.アップロードした写真の権利や保存期間は？
H3 Q.英語・中国語の紹介文は正確ですか？
H3 Q.AI加工（ステージング・家具消し・青空）はすぐ使えますか？
H2 まずは無料で、バーチャルステージングを生成してみる。
H2 関連ツール
H2 お役立ち記事

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

26 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 26 all-caps heading(s)

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

3 decorative image(s) correctly marked

10 image(s) with good alt text

13 images 10 good alt text 3 decorative

All images have appropriate alt text.

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

1 control(s) without accessible label

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

Got: <input type="file">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
select	select	部屋タイプ	none
select	select	スタイル	none
select	select	CG注記（外せません）	none
select	select	注記の位置	none
input	file	(none)	none

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

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

Link & Button Quality

79 links, 41 buttons — all OK

PASS

79 links, 41 buttons — all OK

8 link(s) open in new tab without warning

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

Got: https://chatgpt.com/?prompt=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%…; https://www.perplexity.ai/search/new/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%…; https://claude.ai/new/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%82%…; https://www.google.com/search?udm=50&aep=11&q=%E3%83%90%E3%83%BC%E3%83%81%E3%…; https://grok.com/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%82%B9%E3…; https://www.doubao.com/chat/url-action?action=%7B%22pluginId%22%3A%22Send_Mes…; https://chat.deepseek.com/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3…; https://www.kimi.com/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%82%B…

71 link(s) with descriptive text

79 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/blog/homestaging-toha	ホームステージング基…	img no alt	Add alt attribute to the image
/blog/akushitsu-taisaku-idea	空室対策空室対策アイ…	img no alt	Add alt attribute to the image
/blog/cg-chuki-rule	広告表示・コンプライ…	img no alt	Add alt attribute to the image
https://chatgpt.com/?prompt=%E3%83%90%E3…	ChatGPT	new tab	Add '(opens in new tab)' to text
https://www.perplexity.ai/search/new/?q=…	Perplexity	new tab	Add '(opens in new tab)' to text
https://claude.ai/new/?q=%E3%83%90%E3%83…	Claude	new tab	Add '(opens in new tab)' to text
https://www.google.com/search?udm=50&aep…	Gemini	new tab	Add '(opens in new tab)' to text
https://grok.com/?q=%E3%83%90%E3%83%BC%E…	Grok	new tab	Add '(opens in new tab)' to text
https://www.doubao.com/chat/url-action?a…	豆包	new tab	Add '(opens in new tab)' to text
https://chat.deepseek.com/?q=%E3%83%90%E…	DeepSeek	new tab	Add '(opens in new tab)' to text
https://www.kimi.com/?q=%E3%83%90%E3%83%…	Kimi	new tab	Add '(opens in new tab)' to text

112 links and buttons have descriptive text

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

https://chatgpt.com/?prompt=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%…; https://www.perplexity.ai/search/new/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%…; https://claude.ai/new/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%82%…; https://www.google.com/search?udm=50&aep=11&q=%E3%83%90%E3%83%BC%E3%83%81%E3%…; https://grok.com/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%82%B9%E3…; https://www.doubao.com/chat/url-action?action=%7B%22pluginId%22%3A%22Send_Mes…; https://chat.deepseek.com/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3…; https://www.kimi.com/?q=%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%82%B…

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

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "ja"

PASS

Lang attribute set to "ja"

<html lang="ja"> is set and valid

Got: ja

A+

Tabindex Anti-Patterns

3 explicit tabindex attribute(s) checked, no anti-patterns

PASS

3 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Virtual Staging｜空室掲載パック

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Virtual Staging｜空室掲載パック ✓192×192 icon ✓512×512 icon ✓Start URL /app ✓Display Mode standalone ✓

Name Virtual Staging｜空室掲載パック Display Mode standalone Theme Color #0b3558 Background Color #f8f9fb Icons 2 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 33 passed

PASS

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
AI加工を実行すると、写真は処理のため安全なクラウドストレージ（Cloudflare R2）にアップロードされます。 `div#generator > div.mt-4 > div.min-w-0 > p.mt-2`
日英中物件紹介文について → `div.vs-container > div.grid > div > a.mt-6`
ホームステージング `div.mx-auto > div.vs-prose > p > a`
CG注記 `div.mx-auto > div.vs-prose > p > a`
青空加工 `div.mx-auto > div.vs-prose > p > a`
家具消し `div.mx-auto > div.vs-prose > p > a`
縦型動画 `div.mx-auto > div.vs-prose > p > a`
多言語の紹介文 `div.mx-auto > div.vs-prose > p > a`
空室対策 `div.mx-auto > div.vs-prose > p > a`
すべての記事を見る → `div.mt-16 > div > div.mt-8 > a.text-[14px]`

These are opportunities to improve the legibility of your content.

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
Virtual Staging 空室掲載パック `div.flex > header.sticky > div.vs-container > a.shrink-0`
日本語 `div.vs-container > div.flex > div.relative > button.flex`

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

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●ARIA input fields have accessible names

●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

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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

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

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

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