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 6 REVIEW 3 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

6 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 6 <nav> element(s)

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.

Landmark Structure

9 landmarks

REVIEW

9 landmarks

<main> landmark present

6 <nav> landmark(s) found

1 of 6 <nav> elements are unlabeled

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

No banner (header) 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

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

Link & Button Quality

1 issue(s) across 39 links and 8 buttons

REVIEW

1 issue(s) across 39 links and 8 buttons

2 link(s) open in new tab without warning

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

Got: /terms; /privacy

1 button(s) with no accessible text

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

Got: button#consent

37 link(s) with descriptive text

39 links

0 empty

0 generic text

2 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/terms	Terms	new tab	Add '(opens in new tab)' to text
/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

44 links and buttons have descriptive text

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

/terms; /privacy

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#consent

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

Mobile-Readable Font Sizes

Action

89% of visible text renders at >= 12 CSS px (24 below threshold)

REVIEW

89% of visible text renders at >= 12 CSS px (24 below threshold)

24 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: <p> 11.0px ("Public-web face search · free preview"); <div> 10.0px ("Secure airlock · TLS · purge 24h"); <div> 11.0px ("match · 94.2%"); <span> 11.0px ("18+ · consent"); <li> 11.0px ("Scan first, pay later").

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

h2 A reverse face search that tells you wha…

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Three steps through the airlock

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Everything you need to verify a profile

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built like a vault, priced like a coffee

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 For verifying, not for watching

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What a preview looks like

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How we compare

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What a search can (and can’t) tell you

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Scan for free. Pay only to unlock.

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently asked questions

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Check a photo before you trust it

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Upload a clear photo

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get a free preview

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Unlock with 1 credit

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Face Search

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Username Lookup

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Reverse Image Search

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Romance Scam Check

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Score bands, not fake certainty

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Source domain on every card

1.43:1

#000000

#1B2842

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 A reverse face searc…	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 Three steps through …	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 Everything you need …	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 Built like a vault, …	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 For verifying, not f…	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 What a preview looks…	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 How we compare	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 What a search can (a…	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 Scan for free. Pay o…	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 Frequently asked que…	1.43:1	3.0:1	#000000	#1B2842	Fail
h2 Check a photo before…	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Upload a clear photo	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Get a free preview	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Unlock with 1 credit	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Face Search	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Username Lookup	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Reverse Image Search	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Romance Scam Check	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Score bands, not fak…	1.43:1	3.0:1	#000000	#1B2842	Fail
h3 Source domain on eve…	1.43:1	3.0:1	#000000	#1B2842	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

39 headings

PASS

39 headings

Single H1 present

H1 Reverse Face Search & Social Profile Finder
H2 A reverse face search that tells you what it can’t do
H2 Three steps through the airlock
H3 Upload a clear photo
H3 Get a free preview
H3 Unlock with 1 credit
H2 Everything you need to verify a profile
H3 Face Search
H3 Username Lookup
H3 Reverse Image Search
H3 Romance Scam Check
H2 Built like a vault, priced like a coffee
H3 Score bands, not fake certainty
H3 Source domain on every card
H3 Hourly purge job
H3 Encrypted in transit
H3 Credits that never expire
H3 Abuse guardrails
H2 For verifying, not for watching
H3 Dating safety
H3 Find your own photos
H3 Marketplace & rental scams
H3 Creators & brand protection
H2 What a preview looks like
H2 How we compare
H2 What a search can (and can’t) tell you
H2 Scan for free. Pay only to unlock.
H3 Single
H3 Three-pack
H2 Frequently asked questions
H3 What does AI Social Finder actually search?
H3 Do I pay before I know if there are results?
H3 How much does it cost?
H3 What happens to the photo I upload?
H3 Is a match proof of someone's identity?
H3 Who is not allowed to use it?
H3 Can I search my own face to see where it appears?
H3 How accurate is it?
H2 Check a photo before you trust it

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

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="face-search-file">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#face-search-file	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

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

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: AI Social Finder

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name AI Social Finder ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa&utm_medium=install ✓Display Mode standalone ✓

Name AI Social Finder Display Mode standalone Theme Color #145FE4 Background Color #ffffff Icons 2 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

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+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 30 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.

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
per search, one-time `div.border-b > dl.mx-auto > div.px-4 > dd.mt-1`
full results free in every preview `div.border-b > dl.mx-auto > div.px-4 > dd.mt-1`
hard purge of photos & results `div.border-b > dl.mx-auto > div.px-4 > dd.mt-1`
subscriptions, upsells or data sales `div.border-b > dl.mx-auto > div.px-4 > dd.mt-1`
It is not `div.grid > div.grid > div.rounded-2xl > p.mb-4`
01 `div.mx-auto > ol.grid > li.relative > span.absolute`
02 `div.mx-auto > ol.grid > li.relative > span.absolute`
03 `div.mx-auto > ol.grid > li.relative > span.absolute`
similarity 92 `ul.space-y-3 > li.flex > div.min-w-0 > p.font-mono`
similarity 88 `ul.space-y-3 > li.flex > div.min-w-0 > p.font-mono`
similarity 74 `ul.space-y-3 > li.flex > div.min-w-0 > p.font-mono`
1 credit `div.mx-auto > div.relative > p.mt-4 > span.text-[#1D1D21]/60`
Purchases unavailable `div.mx-auto > div.mx-auto > div.relative > span.mt-8`
Paid checkout is currently turned off during this demonstration, so you will no… `div.flex > section#pricing > div.mx-auto > p.mt-6`
TOOLS `div.mx-auto > div.grid > nav > p.font-mono`
RESOURCES `div.mx-auto > div.grid > nav > p.font-mono`
COMPANY `div.mx-auto > div.grid > nav > p.font-mono`
LEGAL `div.mx-auto > div.grid > nav > p.font-mono`
© 2026 AI Social Finder. All rights reserved. `footer.bg-[#1D1D21] > div.mx-auto > div.flex > span`
LLMs.txt `footer.bg-[#1D1D21] > div.mx-auto > div.flex > a.hover:text-white`
Results come from publicly accessible web pages and may be inaccurate. Do not u… `footer.bg-[#1D1D21] > div.mx-auto > div.flex > span`

These are opportunities to improve the legibility of your content.

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
↓ Install App `div.flex > div.fixed > div.group > button.inline-flex`

○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

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

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

●Elements use only permitted ARIA attributes

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

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

●Deprecated ARIA roles were not used

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

●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

○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

○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

○Form elements have associated labels

○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

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

○Identical links have the same purpose.

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