Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 7 REVIEW 3 FIX

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.

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

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

Tap Target Adequacy

Action

9 tap target(s) too small or too close together

REVIEW

9 tap target(s) too small or too close together

9 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

Action

77% of visible text renders at >= 12 CSS px (43 below threshold)

REVIEW

77% of visible text renders at >= 12 CSS px (43 below threshold)

43 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 ("01"); <span> 10.0px ("Private atelier"); <p> 11.0px ("Private atelier assessment"); <p> 11.0px ("FacialHarmonyAI"); <p> 11.0px ("Analysis runs in your browser. Your phot...").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ 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

h1 AI Facial Harmony Analysis From One Phot…

1.08:1

#000000

#130C0A

needs 3.0:1 (large text)

32px · above the fold

h2 Know your proportions.

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Softly.

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What Is Facial Harmony?

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why Proportion Clarity Matters

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How the Atelier Assessment Works

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What People Notice

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready for your proportion study?

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Facial Harmony FAQ

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy & safety

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Eye Balance

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Jaw & Lower Face

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Golden Ratio Cues

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Facial harmony

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Harsh “rating” apps

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Understand proportion relationships

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Compare photos more fairly

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Know where scores come from

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Upload one clear photo

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Browser-side landmark map

1.16:1

#000000

#1A1514

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 AI Facial Harmony An…	1.08:1	3.0:1	#000000	#130C0A	Fail
h2 Know your proportion…	1.16:1	3.0:1	#000000	#1A1514	Fail
h2 Softly.	1.16:1	3.0:1	#000000	#1A1514	Fail
h2 What Is Facial Harmo…	1.16:1	3.0:1	#000000	#1A1514	Fail
h2 Why Proportion Clari…	1.16:1	3.0:1	#000000	#1A1514	Fail
h2 How the Atelier Asse…	1.16:1	3.0:1	#000000	#1A1514	Fail
h2 What People Notice	1.16:1	3.0:1	#000000	#1A1514	Fail
h2 Ready for your propo…	1.16:1	3.0:1	#000000	#1A1514	Fail
h2 Facial Harmony FAQ	1.16:1	3.0:1	#000000	#1A1514	Fail
h2 Privacy & safety	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Eye Balance	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Jaw & Lower Face	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Golden Ratio Cues	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Facial harmony	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Harsh “rating” a…	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Understand proportio…	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Compare photos more …	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Know where scores co…	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Upload one clear pho…	1.16:1	3.0:1	#000000	#1A1514	Fail
h3 Browser-side landmar…	1.16:1	3.0:1	#000000	#1A1514	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.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 22 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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
★ ★ ★ ★ ★ `div.site-shell > div.grid > article.flex > div.mb-3`
★ ★ ★ ★ ★ `div.site-shell > div.grid > article.flex > div.mb-3`
★ ★ ★ ★ ★ `div.site-shell > div.grid > article.flex > div.mb-3`
★ ★ ★ ★ ★ `div.site-shell > div.grid > article.flex > div.mb-3`
★ ★ ★ ★ ★ `div.site-shell > div.grid > article.flex > div.mb-3`
★ ★ ★ ★ ★ `div.site-shell > div.grid > article.flex > div.mb-3`

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
VOL. 01 `div.order-2 > div.flex > div.mt-12 > span.mt-3`
01 `section#how-it-works > div.site-shell > article.min-h-[260px] > span.mb-6`
02 `section#how-it-works > div.site-shell > article.min-h-[260px] > span.mb-6`
03 `section#how-it-works > div.site-shell > article.min-h-[260px] > span.mb-6`
04 `section#how-it-works > div.site-shell > article.min-h-[260px] > span.mb-6`
01 `section.bg-[var(--espresso,#1a1514)] > ul.site-shell > li.min-w-0 > p.mb-2`
02 `section.bg-[var(--espresso,#1a1514)] > ul.site-shell > li.min-w-0 > p.mb-2`
03 `section.bg-[var(--espresso,#1a1514)] > ul.site-shell > li.min-w-0 > p.mb-2`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Featured on FreeAI `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`
Featured on ToolDirs `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`
Featured on ToolPilot `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`
Powered by Startup Fast `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`
Featured on DeepLaunch.io `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`
Featured on First Look `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`
Listed on Turbo0 `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`
Listed on ToolRain `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`
NavFolders `div.max-w-[1120px] > section.mt-5 > div.flex > a.inline-flex`

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

●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

●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

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

●Elements with visible text labels have matching accessible names.

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

○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

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

Landmark Structure

21 landmarks

PASS

21 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

A+

Heading Hierarchy

31 headings

PASS

31 headings

Single H1 present

H1 AI Facial Harmony Analysis From One Photo
H2 Know your proportions.Softly.
H3 Eye Balance
H3 Jaw & Lower Face
H3 Golden Ratio Cues
H2 What Is Facial Harmony?
H3 Facial harmony
H3 Harsh “rating” apps
H2 Why Proportion Clarity Matters
H3 Understand proportion relationships
H3 Compare photos more fairly
H3 Know where scores come from
H2 How the Atelier Assessment Works
H3 Upload one clear photo
H3 Browser-side landmark map
H3 Free preview you can read
H3 Unlock the full report
H2 What People Notice
H2 Ready for your proportion study?
H3 See an Example Atelier Report
H3 Your Atelier Assessment
H2 Facial Harmony FAQ
H3 Is FacialHarmonyAI free?
H3 Where does the photo analysis run?
H3 What is facial harmony vs face symmetry?
H3 Do you rank or shame faces?
H3 What photo works best?
H3 Is this a medical or surgical assessment?
H3 What is in the $9.99 full report?
H3 Can I delete my report?
H2 Privacy & safety

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 20 images OK

PASS

All 20 images OK

3 decorative image(s) correctly marked

17 image(s) with good alt text

20 images 17 good alt text 3 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) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="file">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
input	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

Link & Button Quality

31 links, 4 buttons — all OK

PASS

31 links, 4 buttons — all OK

9 link(s) open in new tab without warning

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

Got: https://www.freeai.run; https://tooldirs.com; https://www.toolpilot.ai; https://startupfa.st; https://deeplaunch.io; https://firstlook.tools; https://turbo0.com/item/facialharmonyai; https://toolrain.com/item/facialharmonyai; https://navfolders.com

22 link(s) with descriptive text

31 links

0 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.freeai.run	Featured on FreeAI	new tab	Add '(opens in new tab)' to text
https://tooldirs.com	Featured on ToolDirs	new tab	Add '(opens in new tab)' to text
https://www.toolpilot.ai	Featured on ToolPilot	new tab	Add '(opens in new tab)' to text
https://startupfa.st	Powered by Startup Fast	new tab	Add '(opens in new tab)' to text
https://deeplaunch.io	Featured on DeepLaunch.io	new tab	Add '(opens in new tab)' to text
https://firstlook.tools	Featured on First Look	new tab	Add '(opens in new tab)' to text
https://turbo0.com/item/facialharmonyai	Listed on Turbo0	new tab	Add '(opens in new tab)' to text
https://toolrain.com/item/facialharmonya…	Listed on ToolRain	new tab	Add '(opens in new tab)' to text
https://navfolders.com	NavFolders	new tab	Add '(opens in new tab)' to text

26 links and buttons have descriptive text

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

https://www.freeai.run; https://tooldirs.com; https://www.toolpilot.ai; https://startupfa.st; https://deeplaunch.io; https://firstlook.tools; https://turbo0.com/item/facialharmonyai; https://toolrain.com/item/facialharmonyai; https://navfolders.com

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+

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.

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