Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 5 REVIEW 2 FIX

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

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

Form Accessibility

Action

5 of 6 controls have issues

REVIEW

5 of 6 controls have issues

5 control(s) without accessible label

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

Got: <input type="file">; <input type="file">; <input type="file">; <input type="file">; <input type="file">

1 control(s) properly labeled

6 controls

1 labeled

0 placeholder only

5 unlabeled

Control	Type	Label	Method
textarea	textarea	Describe the product ad to generate… e.g. 9:16 UGC hook of hands unboxing sleek matte packaging on a sunlit marble counter, crisp product close-up.	aria-label
input	file	(none)	none
input	file	(none)	none
input	file	(none)	none
input	file	(none)	none
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

Mobile-Readable Font Sizes

Action

72% of visible text renders at >= 12 CSS px (94 below threshold)

REVIEW

72% of visible text renders at >= 12 CSS px (94 below threshold)

94 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 ("29"); <span> 11.0px ("31"); <span> 11.0px ("79"); <span> 9.0px ("Limited Time Offer"); <a> 11.0px ("View Annual Plan").

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title AIProductAds — AI Product Ad Generator ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 #f7f8fa ✓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 Featured product ad styles

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AIProductAds clips makers are shipping

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Turn product photos and prompts into ad-…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 From one product photo to campaign-ready…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How the AI Product Ad Generator works

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Video ads, product photos, and UGC — o…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built for ecommerce platforms and ad pla…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Multi-model AI for product ads

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What is AIProductAds?

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why Choose AIProductAds for Product Ads?

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built for ecommerce brands & marketers

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Key features of AIProductAds

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AIProductAds FAQ — AI Product Ad Gener…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to try the AI Product Ad Generator…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 UGC

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Car Vacuum Cleaning UGC

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cleaning Water Gun UGC

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Snack Watch-Party UGC

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Makeup Cleanser UGC

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Action Camera Travel UGC

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Featured product ad …	1.00:1	3.0:1	#000000	#000000	Fail
h2 AIProductAds clips m…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Turn product photos …	1.00:1	3.0:1	#000000	#000000	Fail
h2 From one product pho…	1.00:1	3.0:1	#000000	#000000	Fail
h2 How the AI Product A…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Video ads, product p…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Built for ecommerce …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Multi-model AI for p…	1.00:1	3.0:1	#000000	#000000	Fail
h2 What is AIProductAds…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Why Choose AIProduct…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Built for ecommerce …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Key features of AIPr…	1.00:1	3.0:1	#000000	#000000	Fail
h2 AIProductAds FAQ —…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Ready to try the AI …	1.00:1	3.0:1	#000000	#000000	Fail
h3 UGC	1.00:1	3.0:1	#000000	#000000	Fail
h3 Car Vacuum Cleaning …	1.00:1	3.0:1	#000000	#000000	Fail
h3 Cleaning Water Gun U…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Snack Watch-Party UG…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Makeup Cleanser UGC	1.00:1	3.0:1	#000000	#000000	Fail
h3 Action Camera Travel…	1.00:1	3.0:1	#000000	#000000	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.

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

48 headings

PASS

48 headings

Single H1 present

H1 AIProductAdsAI Product Ad Generator for Video Ads & Product Images
H2 Featured product ad styles
H3 UGC
H3 Car Vacuum Cleaning UGC
H3 Cleaning Water Gun UGC
H3 Snack Watch-Party UGC
H3 Makeup Cleanser UGC
H3 Action Camera Travel UGC
H3 Lash Beauty UGC
H2 AIProductAds clips makers are shipping
H2 Turn product photos and prompts into ad-ready creatives
H2 From one product photo to campaign-ready assets
H3 Video ads
H3 Product images
H3 Multi-ratio export
H3 Credit-based plans
H2 How the AI Product Ad Generator works
H3 Upload a product photo
H3 Choose style and prompt
H3 Generate video ads & images
H2 Video ads, product photos, and UGC — one studio brand
H3 AI Video Ads
H3 AI Product Photos
H3 AI UGC Ads
H2 Built for ecommerce platforms and ad placements
H2 Multi-model AI for product ads
H2 What is AIProductAds?
H2 Why Choose AIProductAds for Product Ads?
H3 High-Impact Studio Production
H3 Studio-grade product motion
H3 Ad-ready video & image assets
H3 All-in-one ad studio SaaS
H3 Iterate with prompts, not full reshoots
H3 Purpose-built for ecommerce ads
H2 Built for ecommerce brands & marketers
H3 Ecommerce sellers
H3 Performance marketers
H3 Ad agencies
H3 DTC brand founders
H3 Social media managers
H3 Creative directors & designers
H2 Key features of AIProductAds
H3 Photo-to-video ads
H3 Synced voice & sound
H3 Up to 15-second clips
H3 Studio 24fps motion
H2 AIProductAds FAQ — AI Product Ad Generator
H2 Ready to try the AI Product Ad Generator?

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 75 images OK

PASS

All 75 images OK

57 decorative image(s) correctly marked

18 image(s) with good alt text

75 images 18 good alt text 57 decorative

All images have appropriate alt text.

A+

Link & Button Quality

81 links, 52 buttons — all OK

PASS

81 links, 52 buttons — all OK

81 link(s) with descriptive text

81 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

133 links and buttons have descriptive text

A+

Form Input Types

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

6 form control(s) checked, no input-semantic issues

PASS

6 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

Favicon & Branding

8 icon(s) detected

PASS

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: AIProductAds

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

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

Name AIProductAds Display Mode standalone Theme Color #f7f8fa Background Color #f7f8fa Icons 3 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

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.

A+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 27 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
Typical case from the product-ad library. Use Try Now on a case card to fill th… `div.border-t > div.flex > div > p.mt-2`
Showcase · product photo → ad creative `section#outcomes > div.mx-auto > figure.mx-auto > figcaption.border-t`
ASPECT RATIOS `main.flex-1 > section#platforms > div.mx-auto > span.mr-1`
IMAGE `a.flex > div.flex > div.min-w-0 > span.text-[10px]`
IMAGE `a.flex > div.flex > div.min-w-0 > span.text-[10px]`
IMAGE `a.flex > div.flex > div.min-w-0 > span.text-[10px]`
KEY CAPABILITIES FOR E-COMMERCE & MARKETING `section#what-section > div.mx-auto > div.mt-10 > p.mb-4`
01 `div.rounded-2xl > div.flex > div.min-w-0 > span.font-display`
02 `div.rounded-2xl > div.flex > div.min-w-0 > span.font-display`
03 `div.rounded-2xl > div.flex > div.min-w-0 > span.font-display`
04 `div.rounded-2xl > div.flex > div.min-w-0 > span.font-display`
05 `div.rounded-2xl > div.flex > div.min-w-0 > span.font-display`
06 `div.rounded-2xl > div.flex > div.min-w-0 > span.font-display`
01 `div.mt-12 > article.group > div.flex > span.font-display`
02 `div.mt-12 > article.group > div.flex > span.font-display`
03 `div.mt-12 > article.group > div.flex > span.font-display`
04 `div.mt-12 > article.group > div.flex > span.font-display`
05 `div.mt-12 > article.group > div.flex > span.font-display`
06 `div.mt-12 > article.group > div.flex > span.font-display`
AIProductAds is an AI Product Ad Generator that turns product photos into video… `div.mx-auto > div.flex > details.group > div.px-5`

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

●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

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

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

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

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

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

○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

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