Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" id="vcs-hero-email">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" id="vcs-hero-email">

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.

Mobile-Readable Font Sizes

Action

80% of visible text renders at >= 12 CSS px (40 below threshold)

REVIEW

80% of visible text renders at >= 12 CSS px (40 below threshold)

40 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: <div> 11.0px ("vcsift.com/search"); <div> 11.0px ("Stage: Seed"); <div> 11.0px ("Sector: SaaS"); <div> 11.0px ("+ Filter"); <span> 11.0px ("2,841 investors").

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

4 icon(s) detected

REVIEW

4 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 Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 80/100 — 3 failing, 12 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.max-w-6xl > div.relative > div.flex > button.md:hidden `div.max-w-6xl > div.relative > div.flex > button.md:hidden`

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
3-day free trial · No credit card required `section > div.max-w-5xl > div > p`
Investors `div.max-w-5xl > div > div > div`
Email addresses `div.max-w-5xl > div > div > div`
Countries `div.max-w-5xl > div > div > div`
Data updates `div.max-w-5xl > div > div > div`
LIVE PREVIEW `section > div.max-w-5xl > div > p`
vcsift.com/search `div.max-w-5xl > div > div > div`
Search by name, firm, location… `div > div > div > span`
+ Filter `div > div > div > div`
2,841 investors `div > div > div > span`
SC `div > div.investor-card > div.flex > div.investor-avatar`
SaaS `div.flex > div.flex-1 > div.flex > span.tag-badge`
VC Firm `div.flex > div.flex-1 > div.flex > span.tag-badge`
PK `div > div.investor-card > div.flex > div.investor-avatar`
Seed `div.flex > div.flex-1 > div.flex > span.tag-badge`
Fintech `div.flex > div.flex-1 > div.flex > span.tag-badge`
VC Firm `div.flex > div.flex-1 > div.flex > span.tag-badge`
Unlock Email `div.flex > div.flex-1 > div.mt-3 > a`
Unlock LinkedIn `div.flex > div.flex-1 > div.mt-3 > a`
STEP 02 `div > div > div > span`
STEP 03 `div > div > div > span`
31k+ `div.max-w-5xl > div > a > span`
28k+ `div.max-w-5xl > div > a > span`
22k+ `div.max-w-5xl > div > a > span`
18k+ `div.max-w-5xl > div > a > span`
15k+ `div.max-w-5xl > div > a > span`
12k+ `div.max-w-5xl > div > a > span`
9k+ `div.max-w-5xl > div > a > span`
8k+ `div.max-w-5xl > div > a > span`
SC `div > div > div > div`
CEO, Series A SaaS `div > div > div > div`
MR `div > div > div > div`
COO, B2B Startup `div > div > div > div`
JP `div > div > div > div`
Head of Fundraising `div > div > div > div`
/ year `div > div > div > span`
3-day free trial `div.max-w-5xl > div > div > div`
/ year `div > div > div > span`
3-day free trial `div.max-w-5xl > div > div > div`
Find & contact 250,000+ VC investors worldwide. `div.max-w-6xl > div.grid > div.col-span-2 > p`
DIRECTORY `div.max-w-6xl > div.grid > div > h4`
PRODUCT `div.max-w-6xl > div.grid > div > h4`
RESOURCES `div.max-w-6xl > div.grid > div > h4`
INVESTMENT STAGE `div > div.grid > div > h4`
TOP SECTORS `div > div.grid > div > h4`
TOP COUNTRIES `div > div.grid > div > h4`
INVESTOR TYPES `div > div.grid > div > h4`
© 2026 VC Sift. All rights reserved. `footer > div.max-w-6xl > div > div`
Privacy `div.max-w-6xl > div > div > a`
Terms `div.max-w-6xl > div > div > a`
Data Removal `div.max-w-6xl > div > div > a`

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
DIRECTORY `div.max-w-6xl > div.grid > div > h4`

These are opportunities to improve keyboard navigation in your application.

○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-hidden="true"]` is not present on the document `<body>`

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

●Document has a `<title>` element

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

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

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

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

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

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

○Image elements have `[alt]` attributes

○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

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

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

Landmark Structure

4 landmarks

PASS

4 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

Heading Hierarchy

23 headings, 1 skip(s)

PASS

23 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Find investorsready to fund your startup
H2 See what you get access to
H2 Three steps to your next investor
H3 Search & filter
H3 Unlock contact info
H3 Export & outreach
H2 Browse by sector
H2 Built for the whole fundraising process
H3 Founders
H3 Startups
H3 Advisors
H3 Consultants
H2 Trusted by founders worldwide
H2 Simple, transparent pricing
H2 Questions & answers
H2 Start finding investorstoday
H4 Directory skipped
H4 Product
H4 Resources
H4 Investment Stage
H4 Top Sectors
H4 Top Countries
H4 Investor Types

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

A+

Heading Text Quality

All 23 heading(s) have substantive, well-formed text

PASS

All 23 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="email" id="vcs-hero-email">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#vcs-hero-email	email	(Your work email)	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

Link & Button Quality

1 issue(s) across 83 links and 2 buttons

PASS

1 issue(s) across 83 links and 2 buttons

1 button(s) with no accessible text

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

Got: button.md:hidden (#61 on page)

83 link(s) with descriptive text

83 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label

84 links and buttons have descriptive text

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

button.md:hidden (#61 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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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)

Element	Ratio	Required	FG	BG	Result
h1 Find investors	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h1 ready to fund your s…	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 See what you get acc…	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 Three steps to your …	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 Browse by sector	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 Built for the whole …	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 Trusted by founders …	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 Simple, transparent …	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 Questions & answers	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 Start finding invest…	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h2 today	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h3 Search & filter	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h3 Unlock contact info	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h3 Export & outreach	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h3 Founders	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h3 Startups	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h3 Advisors	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
h3 Consultants	19.90:1	3.0:1	#09090B	#FFFFFF	Pass
title VCSift — Find & Co…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span VC Sift	19.90:1	4.5:1	#09090B	#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.

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