Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

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

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.

Mobile-Readable Font Sizes

Action

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

REVIEW

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

59 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> 11.0px ("AI photo splitter for scans"); <span> 10.0px ("Before"); <span> 10.0px ("After"); <p> 11.0px ("You upload"); <p> 11.0px ("You download").

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.

Landmark Structure

6 landmarks

PASS

6 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

32 headings

PASS

32 headings

Single H1 present

H1 AI Auto Cropper — Split One Scan into Separate Photos
H2 One scan in. Every photo out.
H2 How It Works
H3 Upload
H3 Detect
H3 Adjust (optional)
H3 Download
H2 What is AI Auto Cropper?
H2 Practical Scanning Scenarios
H3 Family photo albums
H3 Flatbed batch scanning
H3 Instant & small prints
H3 Archives & genealogy
H3 Postcards & printed cards
H3 Single scans with borders
H2 Why use AI Auto Cropper?
H2 Scans split into separate photos
H3 Four prints on an album page
H3 Black-and-white prints on a dark page
H3 Mixed sizes on the scanner glass
H3 Six instant photos in one pass
H2 How AI Auto Cropper Compares
H3 You stay in control
H3 Large archive or a tricky scan?
H2 Simple pricing, free while in preview
H3 Planned paid plans
H4 Pro Personal
H4 Pro Commercial
H2 Frequently Asked Questions
H2 Ready to split your album scans?
H2 Related tools
H2 Related articles

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

22 image(s) with good alt text

22 images 22 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	file	Select files	aria-label

A+

Link & Button Quality

51 links, 13 buttons — all OK

PASS

51 links, 13 buttons — all OK

51 link(s) with descriptive text

51 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

64 links and buttons have descriptive text

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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

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

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 Auto Cropper

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name AI Auto Cropper ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name AI Auto Cropper Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

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 AI Auto Cropper — …	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 One scan in. Every p…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 How It Works	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 What is AI Auto Crop…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Practical Scanning S…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Why use AI Auto Crop…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Scans split into sep…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 How AI Auto Cropper …	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Simple pricing, free…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Frequently Asked Que…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Ready to split your …	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Related tools	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h2 Related articles	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Upload	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Detect	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Adjust (optional)	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Download	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Family photo albums	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Flatbed batch scanni…	19.14:1	3.0:1	#000000	#F7F4EF	Pass
h3 Instant & small prin…	19.14:1	3.0:1	#000000	#F7F4EF	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+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 25 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
You download `div.rounded-[20px] > div.mt-3 > div.rounded-xl > p.text-[11px]`
EXAMPLE · ALBUM PAGE `div.grid > div.min-w-0 > div.space-y-3 > p.text-[11px]`
Everything runs in your browser. Files are never uploaded. `div.grid > div.order-first > button.flex > span.mt-3`
PLANNED PRICE `div.mx-auto > div.relative > div.mt-5 > p.text-[10.5px]`
$12 `div.relative > div.mt-5 > div.mt-1 > span.text-[14px]`
LICENSE `div.relative > div.mt-5 > div.mt-3 > p.text-[10.5px]`
Commercial / client work not included `div.mx-auto > div.relative > ul.mt-5 > li.flex`
For studios `div > div.mx-auto > div.relative > span.absolute`
PLANNED PRICE `div.mx-auto > div.relative > div.mt-5 > p.text-[10.5px]`
LICENSE `div.relative > div.mt-5 > div.mt-3 > p.text-[10.5px]`

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
🇺🇸 EN `div.rw-container > div.ml-auto > div.relative > button.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

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

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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