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 5 REVIEW 7 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

No <nav> landmark found

No contentinfo (footer) landmark

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

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

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

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ 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://fundable.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://fundable.com/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.

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 ✗

Heading Hierarchy

19 headings, 1 skip(s)

REVIEW

19 headings, 1 skip(s)

Multiple H1 headings (7 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H3 → H6 (missing H4)

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

H1 Startup Fundraising Platform
H1 Startup Fundraising Platform duplicate H1
H1 Startup Fundraising Platform duplicate H1
H1 Startup Fundraising Platform duplicate H1
H1 Startup Fundraising Platform duplicate H1
H1 Startup Fundraising Platform duplicate H1
H1 Startup Fundraising Platform duplicate H1
H2 Featured Companies on Fundable
H3 Over a decade of Fundraising Success
H2 $700,000,000+
H2 20,000+
H2 Recently Funded Companies on Fundable
H3 Ready to Get Started?
H6 Get Started skipped
H6 Browse
H6 Resources
H6 Legal
H6 Follow
H3 Select an image to upload:

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

7 of 7 images have issues

REVIEW

7 of 7 images have issues

7 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 images 7 missing

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

Link & Button Quality

Action

3 issue(s) across 68 links and 3 buttons

REVIEW

3 issue(s) across 68 links and 3 buttons

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /raise-capital#self-managed ("Learn More"); /raise-capital#guided ("Learn More")

14 link(s) open in new tab without warning

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

Got: https://www.startups.com/; https://www.bizplan.com/; https://clarity.fm/; https://www.fundable.com/; https://www.launchrock.com/; https://www.zirtual.com/; https://twitter.com/startupsco; https://www.linkedin.com/company/startups-co; https://www.startups.com/; https://www.bizplan.com/ (+4 more)

1 button(s) with no accessible text

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

Got: button.Nav__mobileNavOpen___8nmr (#134 on page)

52 link(s) with descriptive text

68 links

0 empty

2 generic text

14 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.startups.com/	Accelerator	new tab	Add '(opens in new tab)' to text
https://www.bizplan.com/	Planning	new tab	Add '(opens in new tab)' to text
https://clarity.fm/	Mentors	new tab	Add '(opens in new tab)' to text
https://www.fundable.com/	Funding	new tab	Add '(opens in new tab)' to text
https://www.launchrock.com/	Customers	new tab	Add '(opens in new tab)' to text
https://www.zirtual.com/	Assistants	new tab	Add '(opens in new tab)' to text
/raise-capital#self-managed	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Raise Capital#Self Managed
/raise-capital#guided	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Raise Capital#Guided
https://twitter.com/startupsco	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/startup…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.startups.com/	Online Accelerator	new tab	Add '(opens in new tab)' to text
https://www.bizplan.com/	Startup Planning	new tab	Add '(opens in new tab)' to text
https://clarity.fm/	Access Mentors	new tab	Add '(opens in new tab)' to text
https://www.fundable.com/	Secure Funding	new tab	Add '(opens in new tab)' to text
https://www.launchrock.com/	Reach Customers	new tab	Add '(opens in new tab)' to text
https://www.zirtual.com/	Virtual Assistants	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

54 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/raise-capital#self-managed ("Learn More"); /raise-capital#guided ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.startups.com/; https://www.bizplan.com/; https://clarity.fm/; https://www.fundable.com/; https://www.launchrock.com/; https://www.zirtual.com/; https://twitter.com/startupsco; https://www.linkedin.com/company/startups-co; https://www.startups.com/; https://www.bizplan.com/ (+4 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.Nav__mobileNavOpen___8nmr (#134 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA

h1 Startup Fundraising Platform

2.98:1

#000000

#57595A

needs 3.0:1 (large text)

32px · mid-page · over background image/gradient

title Fundable | Startup Fundraising Platform

1.20:1

#000000

#1D181F

needs 4.5:1 (normal text)

16px · top of page (header area)

a the

1.20:1

#000000

#1D181F

needs 4.5:1 (normal text)

16px · top of page (header area)

1 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
h1 Startup Fundraising …	2.98:1	3.0:1	#000000	#57595A	Fail
h1 Startup Fundraising …	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h1 Startup Fundraising …	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h1 Startup Fundraising …	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h1 Startup Fundraising …	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h1 Startup Fundraising …	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h1 Startup Fundraising …	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h2 Featured Companies o…	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h2 $700,000,000+	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h2 20,000+	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h2 Recently Funded Comp…	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h3 Over a decade of Fun…	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h3 Ready to Get Started…	18.30:1	3.0:1	#000000	#ECF0F1	Pass
h3 Select an image to u…	18.30:1	3.0:1	#000000	#ECF0F1	Pass
title Fundable \| Startup F…	1.20:1	4.5:1	#000000	#1D181F	Fail
a the	1.20:1	4.5:1	#000000	#1D181F	Fail
strong startups.com	5.71:1	3.0:1	#000000	#838685	Pass
a platform	8.04:1	4.5:1	#000000	#9DA1A0	Pass
a about startups.com	9.05:1	4.5:1	#000000	#A7ABAA	Pass
a New: Introducing the…	8.53:1	4.5:1	#000000	#A2A6A4	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 80/100 — 5 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 > div.Nav__component__3p5vb > div.layout__wrapper__3Ecno > button.Nav__mobileNavOpen___8nmr `div > div.Nav__component__3p5vb > div.layout__wrapper__3Ecno > button.Nav__mobileNavOpen___8nmr`

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
GET STARTED `div.bg-overlay-x > div.content > div.text > a.btn`
@ Clearwater, FL, United States `a > div > div.location > div`
@ Trélex, Switzerland `a > div > div.location > div`
@ Fort Lauderdale, FL, United States `a > div > div.location > div`
@ Fort Lauderdale, FL, United States `a > div > div.location > div`
@ Private `a > div > div.location > div`
@ Long Beach, CA, United States `a > div > div.location > div`
@ Palo Alto, CA, United States `a > div > div.location > div`
@ Jersey City, NJ, United States `a > div > div.location > div`
View More `div.span12 > div.company-tile-grid > div > a.btn`
Funding Committed `section.callout-1 > div > div.span6 > p`
Accredited Investors `section.callout-1 > div > div.span6 > p`
@ Costa Mesa, CA `a > div > div.location > div`
RAISED $2,000,000 `div > div.metric > div.text > strong`
@ Boston, MA `a > div > div.location > div`
RAISED $5,200,000 `div > div.metric > div.text > strong`
@ Fremont, CA `a > div > div.location > div`
RAISED $3,000,000 `div > div.metric > div.text > strong`
@ Las Vegas, NV `a > div > div.location > div`
RAISED $2,216,900 `div > div.metric > div.text > strong`
@ France `a > div > div.location > div`
RAISED $430,646 `div > div.metric > div.text > strong`
@ Private `a > div > div.location > div`
RAISED $3,068,000 `div > div.metric > div.text > strong`
@ Dallas, TX `a > div > div.location > div`
RAISED $712,400 `div > div.metric > div.text > strong`
@ Temecula, CA `a > div > div.location > div`
RAISED $500,000 `div > div.metric > div.text > strong`
View More `div.span12 > div.company-tile-grid > div > a.btn`
Host your raise on Fundable `div.plans > div.plan > ul > li`
Secure data room for prospective investor materials `div.plans > div.plan > ul > li`
Email-only support `div.plans > div.plan > ul > li`
Marketing outreach templates `div.plans > div.plan > ul > li`
Membership in Startups.com Accelerator `div.plans > div.plan > ul > li`
Online Accelerator `div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span`
Startup Planning `div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span`
Access Mentors `div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span`
Secure Funding `div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span`
Reach Customers `div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span`
Virtual Assistants `div.layout__c1of6__reh-q > a.PlatformFooter__product__22OKY > div.PlatformFooter__productTag__zegMN > span`
Copyright © 2026 Startups.com. All rights reserved. `section.PlatformFooter__component__3q3YT > div.layout__wrapper__3Ecno > div.layout__c1of1__3k6dX > p`
Fundable is a software as a service funding platform. Fundable is not a registe… `body > div > div > p`

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
GET STARTED `div.Footer__wrapper__2J7pb > div.Footer__column__1bqCR > a > h6.Footer__categoryFirst__If9MK`

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`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○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

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

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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 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" id="editor-upload-modal-uploader">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#editor-upload-modal-uploader	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

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