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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #0a0a0a

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 ModePartial Dark Mode

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

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

6 landmarks

REVIEW

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Mobile-Readable Font Sizes

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

REVIEW

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

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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

h1 Your AI built the app.

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

32px · above the fold

h2 How it works

1.06:1

#000000

#090B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Watch an app go from forgetting to remem…

1.06:1

#000000

#090B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Edit your data like a spreadsheet.

1.06:1

#000000

#090B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Copy one link into your AI. Done.

1.06:1

#000000

#090B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your data is always yours.

1.06:1

#000000

#090B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Questions

1.06:1

#000000

#090B0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Founders get 40% off. Forever.

1.06:1

#000000

#090B0B

needs 3.0:1 (large text)

24px · bottom of viewport

title SimplestAPI: Make your Lovable app actua…

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

span SimplestAPI

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

span beta

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

button Sign in

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

span New

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

a End-user logins via JWKS, with the auth …

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

span We make it remember.

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

p The missing backend for your Lovable, Bo…

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

span No database setup

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

span Each user sees their own data

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

span Works with your existing login

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

span Free to start, no credit card

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Your AI built the ap…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 How it works	1.06:1	3.0:1	#000000	#090B0B	Fail
h2 Watch an app go from…	1.06:1	3.0:1	#000000	#090B0B	Fail
h2 Edit your data like …	1.06:1	3.0:1	#000000	#090B0B	Fail
h2 Copy one link into y…	1.06:1	3.0:1	#000000	#090B0B	Fail
h2 Your data is always …	1.06:1	3.0:1	#000000	#090B0B	Fail
h2 Questions	1.06:1	3.0:1	#000000	#090B0B	Fail
h2 Founders get 40% off…	1.06:1	3.0:1	#000000	#090B0B	Fail
title SimplestAPI: Make yo…	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span SimplestAPI	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span beta	1.06:1	4.5:1	#000000	#0A0A0A	Fail
button Sign in	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span New	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a End-user logins via …	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span We make it remember.	1.06:1	4.5:1	#000000	#0A0A0A	Fail
p The missing backend …	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span No database setup	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span Each user sees their…	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span Works with your exis…	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span Free to start, no cr…	1.06:1	4.5:1	#000000	#0A0A0A	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.

A+

Heading Hierarchy

8 headings

PASS

8 headings

Single H1 present

H1 Your AI built the app. We make it remember.
H2 How it works
H2 Watch an app go from forgetting to remembering.
H2 Edit your data like a spreadsheet.
H2 Copy one link into your AI. Done.
H2 Your data is always yours.
H2 Questions
H2 Founders get 40% off. Forever.

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 33 images OK

PASS

All 33 images OK

10 decorative image(s) correctly marked

23 image(s) with good alt text

33 images 23 good alt text 10 decorative

All images have appropriate alt text.

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: <textarea>

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
textarea	textarea	(Describe the app you want to build in plain English. Example: A directory app with categories, listings, and reviews. Each listing belongs to a category and has a name, description, address, and phone.)	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

42 links, 14 buttons — all OK

PASS

42 links, 14 buttons — all OK

24 link(s) open in new tab without warning

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

Got: https://madewith.dev/; https://logto.io/; https://www.producthunt.com/products/simplestapi?embed=true&utm_source=badge-…; https://nicklaunches.com/products/simplestapi/?utm_source=simplestapi.com&utm…; https://saastool.site/item/simplestapi; https://saascity.io/live/simplestapi; https://findly.tools/simplestapi?utm_source=simplestapi; https://weliketools.com/tool/simplestapi; https://startupbenchmarks.com/product/simplestapi; https://unitelist.com/product/simplestapi (+14 more)

18 link(s) with descriptive text

42 links

0 empty

0 generic text

24 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://madewith.dev/	madewith.dev	new tab	Add '(opens in new tab)' to text
https://logto.io/	Logto.io	new tab	Add '(opens in new tab)' to text
https://www.producthunt.com/products/sim…	SimplestAPI on Product Hunt	new tab	Add '(opens in new tab)' to text
https://nicklaunches.com/products/simple…	SimplestAPI on Nick Launches	new tab	Add '(opens in new tab)' to text
https://saastool.site/item/simplestapi	Featured on SaaSTool.site	new tab	Add '(opens in new tab)' to text
https://saascity.io/live/simplestapi	Featured on SaaSCity	new tab	Add '(opens in new tab)' to text
https://findly.tools/simplestapi?utm_sou…	Featured on Findly.tools	new tab	Add '(opens in new tab)' to text
https://weliketools.com/tool/simplestapi	We Like Tools	new tab	Add '(opens in new tab)' to text
https://startupbenchmarks.com/product/si…	Startup Benchmarks	new tab	Add '(opens in new tab)' to text
https://unitelist.com/product/simplestap…	Unite List	new tab	Add '(opens in new tab)' to text
https://appalist.com/ai/simplestapi	Appa List	new tab	Add '(opens in new tab)' to text
https://superaiboom.com/ai/simplestapi	Super AI Boom	new tab	Add '(opens in new tab)' to text
https://smartkithub.com/product/simplest…	Smart Kit Hub	new tab	Add '(opens in new tab)' to text
https://www.producthunt.com/products/sim…	SimplestAPI on Product Hunt	new tab	Add '(opens in new tab)' to text
https://nicklaunches.com/products/simple…	SimplestAPI on Nick Launches	new tab	Add '(opens in new tab)' to text
https://saastool.site/item/simplestapi	Featured on SaaSTool.site	new tab	Add '(opens in new tab)' to text
https://saascity.io/live/simplestapi	Featured on SaaSCity	new tab	Add '(opens in new tab)' to text
https://findly.tools/simplestapi?utm_sou…	Featured on Findly.tools	new tab	Add '(opens in new tab)' to text
https://weliketools.com/tool/simplestapi	We Like Tools	new tab	Add '(opens in new tab)' to text
https://startupbenchmarks.com/product/si…	Startup Benchmarks	new tab	Add '(opens in new tab)' to text
https://unitelist.com/product/simplestap…	Unite List	new tab	Add '(opens in new tab)' to text
https://appalist.com/ai/simplestapi	Appa List	new tab	Add '(opens in new tab)' to text
https://superaiboom.com/ai/simplestapi	Super AI Boom	new tab	Add '(opens in new tab)' to text
https://smartkithub.com/product/simplest…	Smart Kit Hub	new tab	Add '(opens in new tab)' to text

32 links and buttons have descriptive text

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

https://madewith.dev/; https://logto.io/; https://www.producthunt.com/products/simplestapi?embed=true&utm_source=badge-…; https://nicklaunches.com/products/simplestapi/?utm_source=simplestapi.com&utm…; https://saastool.site/item/simplestapi; https://saascity.io/live/simplestapi; https://findly.tools/simplestapi?utm_source=simplestapi; https://weliketools.com/tool/simplestapi; https://startupbenchmarks.com/product/simplestapi; https://unitelist.com/product/simplestapi (+14 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

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+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

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

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

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

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 23 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
SimplestAPI on Product Hunt `div.mt-8 > div.badge-marquee > div.badge-track > div.badge-row`

These are opportunities to improve the usage of ARIA in your application which 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
Sign in `header.sticky > div.mx-auto > nav.flex > button.rounded-lg`
Describe your app `div.relative > div.flex > div.flex > span.text-neutral-500`
No credit card `div.relative > div.flex > div.flex > span.text-xs`
title `table.w-full > thead.text-neutral-500 > tr.border-b > th.px-4`
done `table.w-full > thead.text-neutral-500 > tr.border-b > th.px-4`
priority `table.w-full > thead.text-neutral-500 > tr.border-b > th.px-4`
false `table.w-full > tbody.font-mono > tr.border-b > td.px-4`
true `table.w-full > tbody.font-mono > tr.border-b > td.px-4`
false `table.w-full > tbody.font-mono > tr > td.px-4`
# Acme API · LLM docs `pre.shiki > code > span.line > span`
## todos `pre.shiki > code > span.line > span`
## /ask `pre.shiki > code > span.line > span`
# one click → your whole database as plain SQL `pre.shiki > code > span.line > span`
See all features → `div.border-t > div.container > div.flex > a.inline-flex`
Claim a Founder seat `div.container > div.rounded-2xl > div.mt-8 > a.inline-flex`

These are opportunities to improve the legibility of your content.

○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

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

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

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

●`<td>` elements in a large `<table>` have one or more table headers.

○`[accesskey]` values are unique

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

○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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○`[lang]` attributes have a valid value

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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