Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 7 REVIEW 5 FIX

Link & Button Quality

Action

6 issue(s) across 451 links and 24 buttons

FIX

6 issue(s) across 451 links and 24 buttons

5 link(s) with no accessible text

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

Got: https://ignite.camp-fire.jp/subscribe; https://www.facebook.com/campfirejp; https://x.com/campfirejp; https://www.instagram.com/campfire_jp/; https://page.line.me/iqs4598g?openQrModal=true

15 link(s) open in new tab without warning

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

Got: /readyfor_overseas; /term; /privacy; https://help.camp-fire.jp/hc/ja/海外支援に関する特約; /readyfor; /form/po-document-service; /ai-assistant/form/counsel?conversion_location=toppage_footer_banner; /academy/seminar; https://app.adjust.com/19un3oms; https://app.adjust.com/19un3oms (+5 more)

1 button(s) with no accessible text

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

Got: button#gtm-search-modal-button

431 link(s) with descriptive text

451 links

5 empty

0 generic text

15 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/readyfor_overseas	GET IN TOUCH	new tab	Add '(opens in new tab)' to text
/term	Terms of Use	new tab	Add '(opens in new tab)' to text
/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://help.camp-fire.jp/hc/ja/海外�…	International Support Terms	new tab	Add '(opens in new tab)' to text
/readyfor?ref=toppage_header_readyfor_20…	プロジェクトを掲載す…	img no alt	Add alt attribute to the image
/curations/chiba_900th	2026年の「千葉開府９�…	img no alt	Add alt attribute to the image
/curations/hiokoshi	HIOKOSHI(ヒオコシ):地域�…	img no alt	Add alt attribute to the image
/curations/r7_tokyo_newmarket	【東京都中小企業振興…	img no alt	Add alt attribute to the image
/curations/mottainaimirai	MOTTAINAIみらい	img no alt	Add alt attribute to the image
/curations/shonan-biz	湘南ビジネスコンテス…	img no alt	Add alt attribute to the image
/curations/sandwich	大分のクラウドファン…	img no alt	Add alt attribute to the image
/readyfor	プロジェクトの作成は…	new tab	Add '(opens in new tab)' to text
/form/po-document-service	無料のまとめ資料はこ…	new tab	Add '(opens in new tab)' to text
/ai-assistant/form/counsel?conversion_lo…	無料相談はこちら	new tab	Add '(opens in new tab)' to text
/academy/seminar	説明会への参加はこち…	new tab	Add '(opens in new tab)' to text
https://app.adjust.com/19un3oms	App Storeからダウンロー…	new tab	Add '(opens in new tab)' to text
https://app.adjust.com/19un3oms	Google Playで手に入れよ�…	new tab	Add '(opens in new tab)' to text
/readyfor	プロジェクトの作成は…	new tab	Add '(opens in new tab)' to text
/form/po-document-service	無料のまとめ資料はこ…	new tab	Add '(opens in new tab)' to text
/ai-assistant/form/counsel?conversion_lo…	無料相談はこちら	new tab	Add '(opens in new tab)' to text
/academy/seminar	説明会への参加はこち…	new tab	Add '(opens in new tab)' to text
https://live4.co/	Livefor株式会社	new tab	Add '(opens in new tab)' to text
https://ignite.camp-fire.jp/subscribe	(empty)	empty	Add link text or aria-label
https://www.facebook.com/campfirejp	(empty)	empty	Add link text or aria-label
https://x.com/campfirejp	(empty)	empty	Add link text or aria-label
https://www.instagram.com/campfire_jp/	(empty)	empty	Add link text or aria-label
https://page.line.me/iqs4598g?openQrModa…	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

454 links and buttons have descriptive text

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

https://ignite.camp-fire.jp/subscribe; https://www.facebook.com/campfirejp; https://x.com/campfirejp; https://www.instagram.com/campfire_jp/; https://page.line.me/iqs4598g?openQrModal=true

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.

/readyfor_overseas; /term; /privacy; https://help.camp-fire.jp/hc/ja/海外支援に関する特約; /readyfor; /form/po-document-service; /ai-assistant/form/counsel?conversion_location=toppage_footer_banner; /academy/seminar; https://app.adjust.com/19un3oms; https://app.adjust.com/19un3oms (+5 more)

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#gtm-search-modal-button

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

Web Manifest

Action

Not found

FIX

Not found

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.

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.

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

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

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

Heading Hierarchy

Action

10 headings, 1 skip(s)

REVIEW

10 headings, 1 skip(s)

No H1 heading found

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

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H3 Welcome, International users
H3 カテゴリーからさがす
H3 地域からさがす
H3 すべてのプロジェクトをまとめて見る
H6 カテゴリー skipped
H6 起案サポート
H6 CAMPFIREアカデミー
H6 サービス
H6 CAMPFIREについて
H6 CAMPFIRE GROUP

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Alt Text Quality

Action

9 of 170 images have issues

REVIEW

9 of 170 images have issues

9 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

108 decorative image(s) correctly marked

53 image(s) with good alt text

170 images 53 good alt text 108 decorative 9 missing

Issue	Count
missing	9 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

Form Accessibility

2 of 4 controls have issues

REVIEW

2 of 4 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="search" name="word" id="header-search">; <input type="search" name="word">

2 control(s) properly labeled

4 controls

2 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
input	checkbox		none
input	checkbox		none
#header-search	search	(キーワード検索)	placeholder only
word	search	(キーワードからさがす)	placeholder only

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

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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h3 Welcome,

1.34:1

#000000

#2E201E

needs 3.0:1 (large text)

19px · above the fold · over background image/gradient

h3 カテゴリーからさがす

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 地域からさがす

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 すべてのプロジェクトをまと�…

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

title クラウドファンディング - CAMP…

1.25:1

#000000

#331316

needs 4.5:1 (normal text)

16px · top of page (header area)

p Please get in touch if you have any ques…

1.45:1

#000000

#332627

needs 4.5:1 (normal text)

16px · top of page (header area)

a GET IN TOUCH

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · top of page (header area)

button no thanks!

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · top of page (header area)

span International users

1.13:1

#000000

#2A0602

needs 4.5:1 (normal text)

16px · above the fold

p This site is available to users outside …

1.17:1

#000000

#27110E

needs 4.5:1 (normal text)

16px · above the fold

p ※ Some features may not be available d…

1.15:1

#000000

#171412

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span I agree to the

1.44:1

#000000

#2E2823

needs 4.5:1 (normal text)

16px · above the fold

a Terms of Use

1.39:1

#000000

#2D251E

needs 4.5:1 (normal text)

16px · above the fold

span and

1.39:1

#000000

#2C2520

needs 4.5:1 (normal text)

16px · above the fold

a Privacy Policy

1.20:1

#000000

#201812

needs 4.5:1 (normal text)

16px · above the fold

span I agree to the

1.26:1

#000000

#251C1B

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a International Support Terms

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · mid-page

button Continue

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · mid-page

span プロジェクトを掲載するには

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · mid-page

span はじめる

1.66:1

#000000

#323333

needs 4.5:1 (normal text)

16px · mid-page

3 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)

Element	Ratio	Required	FG	BG	Result
h3 Welcome,	1.34:1	3.0:1	#000000	#2E201E	Fail
h3 カテゴリーか�…	1.66:1	3.0:1	#000000	#333333	Fail
h3 地域からさが�…	1.66:1	3.0:1	#000000	#333333	Fail
h3 すべてのプロ�…	1.66:1	3.0:1	#000000	#333333	Fail
title クラウドファ�…	1.25:1	4.5:1	#000000	#331316	Fail
p Please get in touch …	1.45:1	4.5:1	#000000	#332627	Fail
a GET IN TOUCH	1.66:1	4.5:1	#000000	#333333	Fail
button no thanks!	1.66:1	4.5:1	#000000	#333333	Fail
span International users	1.13:1	4.5:1	#000000	#2A0602	Fail
p This site is availab…	1.17:1	4.5:1	#000000	#27110E	Fail
p ※ Some features ma…	1.15:1	4.5:1	#000000	#171412	Fail
span I agree to the	1.44:1	4.5:1	#000000	#2E2823	Fail
a Terms of Use	1.39:1	4.5:1	#000000	#2D251E	Fail
span and	1.39:1	4.5:1	#000000	#2C2520	Fail
a Privacy Policy	1.20:1	4.5:1	#000000	#201812	Fail
span I agree to the	1.26:1	4.5:1	#000000	#251C1B	Fail
a International Suppor…	1.66:1	4.5:1	#000000	#333333	Fail
button Continue	1.66:1	4.5:1	#000000	#333333	Fail
span プロジェクト�…	1.66:1	4.5:1	#000000	#333333	Fail
span はじめる	1.66:1	4.5:1	#000000	#323333	Fail

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

Action

Score 73/100 — 6 failing, 17 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.

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
div.navigation > div.pj-created-search > div.pj-search-sp > button#gtm-search-modal-button `div.navigation > div.pj-created-search > div.pj-search-sp > button#gtm-search-modal-button`

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
div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a `div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a`
div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a `div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a`
div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a `div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a`
div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a `div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a`
div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a `div.footer-bottom-wrap > ul.social-link > li.svelte-1hebvmg > a`

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
Terms of Use `div.inner > label.agreement-container > span > a.link`
Privacy Policy `div.inner > label.agreement-container > span > a.link`
International Support Terms `div.inner > label.agreement-container > span > a.link`
もっとみる `section.section > div.header > div.row > a#gtm-toppage-to-recommended-list-page-from-title`
おすすめをもっとみる `div.container > div.main > section.section > a#gtm-toppage-to-recommended-list-page-from-bottom`
毎日更新 `div.main > section.section > div.header > div.subtitle`
人気ランキング `section.section > div.header > div.row > div.title`
もっとみる `section.section > div.header > div.row > a#gtm-toppage-to-popularity-ranking-list-page-from-title`
12位以降もみる `div.main > section.section > a#gtm-toppage-to-popularity-ranking-list-page-from-bottom > div.more-sp`
総合 `section.section > div.link-list > a#gtm-toppage-to-popularity-ranking-category-page-link-all > span`
数量限定品やお得なリターンも！ `div.main > section.section > div.header > div.subtitle`
注目のリターンをもっとみる `div.container > div.main > section.section > a#gtm-toppage-to-popular-rewards-list-page-from-bottom`
お見逃しはありませんか？ `div.main > section.section > div.header > div.subtitle`
もっとみる `section.section > div.header > div.row > a#gtm-toppage-to-last-spurt-projects-list-page-from-title`
12日 `div.project-list > div.project-wrap > div.remaining-time > span.svelte-1ydgsbg`
7日 `div.project-list > div.project-wrap > div.remaining-time > span.svelte-1ydgsbg`
9日 `div.project-list > div.project-wrap > div.remaining-time > span.svelte-1ydgsbg`
8日 `div.project-list > div.project-wrap > div.remaining-time > span.svelte-1ydgsbg`
もうすぐ終了をもっとみる `div.container > div.main > section.section > a#gtm-toppage-to-last-spurt-projects-list-page-from-bottom`
注目するなら今！ `div.main > section.section > div.header > div.subtitle`
もっとみる `section.section > div.header > div.row > a#gtm-toppage-to-coming-soon-projects-list-page-from-title`
まもなく公開をもっとみる `div.container > div.main > section.section > a#gtm-toppage-to-coming-soon-projects-list-page-from-bottom`
もっとみる `section.section > div.container > div.head > a#top_to_curation_channels_list_page`
もっとみる `section.section > div.container > div.head > a#top_to_community_projects_list_page`
プロジェクトの作成はこちら `div.inner > div.links > div.links-ready > a.link`
無料のまとめ資料はこちら `div.inner > div.links > div.links-ready > a.link`
無料相談はこちら `div.inner > div.links > div > a.link`
説明会への参加はこちら `div.inner > div.links > div > a.link`
各種規定 `div.footer-main-content > div.service-and-about > div.about > p.provisions`
「QRコード」は株式会社デンソーウェーブの登録商標です。 `footer.footer > div.container > div.footer-bottom > p.qr-code-note`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
カテゴリー `div.container > div.footer-main-content > div.category > h6.main-content-title`

These are opportunities to improve keyboard navigation in your application.

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
プロダクト `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
東京 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
まちづくり・地域活性化 `div.body > div.tags > div.content > a.tag`
愛知 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
山梨 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
山梨 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
東京 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
山梨 `div.body > div.tags > div.content > a.tag`
まちづくり・地域活性化 `div.body > div.tags > div.content > a.tag`
愛知 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
東京 `div.body > div.tags > div.content > a.tag`
アート・写真 `div.body > div.tags > div.content > a.tag`
書籍・雑誌出版 `div.body > div.tags > div.content > a.tag`
神奈川 `div.body > div.tags > div.content > a.tag`
フード・飲食店 `div.body > div.tags > div.content > a.tag`
福岡 `div.body > div.tags > div.content > a.tag`
まちづくり・地域活性化 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
山梨 `div.body > div.tags > div.content > a.tag`
音楽 `div.body > div.tags > div.content > a.tag`
フード・飲食店 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
東京 `div.body > div.tags > div.content > a.tag`
スポーツ `div.body > div.tags > div.content > a.tag`
栃木 `div.body > div.tags > div.content > a.tag`
プロダクト `div.body > div.tags > div.content > a.tag`
テクノロジー・ガジェット `div.body > div.tags > div.content > a.tag`
映像・映画 `div.body > div.tags > div.content > a.tag`
東京 `div.body > div.tags > div.content > a.tag`
ゲーム・サービス開発 `div.body > div.tags > div.content > a.tag`
まちづくり・地域活性化 `div.body > div.tags > div.content > a.tag`
岩手 `div.body > div.tags > div.content > a.tag`
フード・飲食店 `div.body > div.tags > div.content > a.tag`
山形 `div.body > div.tags > div.content > a.tag`
チャレンジ `div.body > div.tags > div.content > a.tag`
チャレンジ `div.body > div.tags > div.content > a.tag`
神奈川 `div.body > div.tags > div.content > a.tag`
テクノロジー・ガジェット `div.body > div.tags > div.content > a.tag`
まちづくり・地域活性化 `div.body > div.tags > div.content > a.tag`
大分 `div.body > div.tags > div.content > a.tag`
スポーツ `div.body > div.tags > div.content > a.tag`
まちづくり・地域活性化 `div.body > div.tags > div.content > a.tag`
北海道 `div.body > div.tags > div.content > a.tag`
書籍・雑誌出版 `div.body > div.tags > div.content > a.tag`
フード・飲食店 `div.body > div.tags > div.content > a.tag`
沖縄 `div.body > div.tags > div.content > a.tag`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●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

●Document has a main landmark.

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

○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

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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title クラウドファンディング - CAMPFIRE (キャンプファイヤー) ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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