Skip to content
https://foundersave.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
7
REVIEW
2
PASS
15
INFO
0
Checks
24
15 PASS 2 REVIEW 7 FIX
D
Mobile-Readable Font Sizes
Action
67% of visible text renders at >= 12 CSS px (77 below threshold)
FIX
67% of visible text renders at >= 12 CSS px (77 below threshold)
Warning::
77 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> 9.0px ("POPULAR"); <a> 11.0px ("95% Off Xero"); <a> 11.0px ("Intercom 93% Off First Year"); <a> 11.0px ("$5k free Deel credits"); <a> 11.0px ("up to 20% off Google Workspace").
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title FounderSave — More runway. Less overhead. ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Mobile Keyboard & Autofill
Action
2/3 eligible field(s) missing autocomplete or inputmode
REVIEW
2/3 eligible field(s) missing autocomplete or inputmode
Warning::
2 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: search, email.
Got: <input type="search">, <input type="email" name="email" id="newsletter-email">
C
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 Startup Software Deals, SaaS Discounts &…
1.18:1
#000000
on
#0F172A
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The software platfor…19.40:13.0:1
#000000
#F4F6F9
Pass
h2 Curated perks. Zero …19.40:13.0:1
#000000
#F4F6F9
Pass
h2 Choose a startup off…19.40:13.0:1
#000000
#F4F6F9
Pass
title Startup Software Dea…1.18:14.5:1
#000000
#0F172A
Fail
a Skip to content20.96:14.5:1
#000000
#FEFFFF
Pass
span POPULAR20.96:14.5:1
#000000
#FEFFFF
Pass
a 95% Off Xero19.75:14.5:1
#000000
#F6F8FC
Pass
span •18.78:14.5:1
#000000
#EFF2FC
Pass
a Intercom 93% Off Fir…17.95:14.5:1
#000000
#E8EDFC
Pass
span •18.64:14.5:1
#000000
#EEF1FD
Pass
a $5k free Deel credit…19.40:14.5:1
#000000
#F3F6FC
Pass
span •19.91:14.5:1
#000000
#F7F9FC
Pass
a up to 20% off Google…20.62:14.5:1
#000000
#FCFDFE
Pass
span •21.00:14.5:1
#000000
#FFFFFF
Pass
a 1 Year Auth0 Free20.28:14.5:1
#000000
#FAFBFD
Pass
span •19.91:14.5:1
#000000
#F7F9FC
Pass
span OFFER19.91:14.5:1
#000000
#F7F9FC
Pass
a FORMATION & SOFTWARE…19.91:14.5:1
#000000
#F7F9FC
Pass
span Explore deals19.91:14.5:1
#000000
#F7F9FC
Pass
span POPULAR19.91:14.5:1
#000000
#F7F9FC
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.

A+
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN CONTENTINFO footer
A
Heading Hierarchy
28 headings, 1 skip(s)
PASS
28 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 The software platform for scaling your startup runway
  • H2 Curated perks. Zero inflated claims.
  • H3 1Password
  • H3 800.com
  • H3 AdCreative
  • H3 Adzooma
  • H3 Agree.com
  • H3 Ahrefs
  • H3 Aircall
  • H3 Airwallex
  • H3 Algolia
  • H3 Amplitude
  • H3 Amplitude Plus
  • H3 Anthropic (API)
  • H3 Anytime Mailbox
  • H3 Apify
  • H3 Apollo
  • H3 Appwrite
  • H3 Argonaut
  • H3 AroundDeal
  • H3 Asana
  • H3 AssemblyAI
  • H3 Attio
  • H3 Audiense
  • H3 Auth0
  • H3 Autodesk Fusion
  • H2 Choose a startup offer with the full costs in view
  • H4 Stay ahead on founder perks skipped

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 28 heading(s) have substantive, well-formed text
PASS
All 28 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
24 image(s) with good alt text
24 images 24 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 28 controls labeled
PASS
All 28 controls labeled
Info::
28 control(s) properly labeled
28 controls
28 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchSearch dealsnone
selectselectCategorynone
selectselectAccess tiernone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
#newsletter-emailemailNewsletter emailfor/id
A+
Form Input Types
28 form control(s) checked, no type mismatches
PASS
28 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
28 form control(s) checked, no input-semantic issues
PASS
28 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 25 passed
PASS
95

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
TECH div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
COMMS div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
AI div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
MARKETING div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
SALES div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
MARKETING div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
COMMS div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
FINANCE div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
TECH div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
MARKETING div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
MARKETING div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
AI div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
PRODUCTIVITY div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
TECH div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
SALES div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
TECH div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
CLOUD div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
SALES div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
PRODUCTIVITY div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
AI div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
CRM div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
MARKETING div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
TECH div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category
PRODUCTIVITY div.fp-card-body > div.fp-card-title-row > div.fp-card-heading > span.category

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
Stay ahead on founder perks div.fb-footer-grid > div > div.fb-newsletter-card > h4

These are opportunities to improve keyboard navigation in your application.

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
Get this deal article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Apply for this perk article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
Visit provider site article.deal-card > div.fp-card-body > div.fp-card-footer > button.ui-button
○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
●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.
●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
●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
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●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 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback