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

Landmark Structure

15 landmarks

REVIEW

15 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

90% of visible text renders at >= 12 CSS px (28 below threshold)

REVIEW

90% of visible text renders at >= 12 CSS px (28 below threshold)

28 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 ("2 credits"); <span> 10.0px ("2 credits"); <span> 10.0px ("2 credits"); <span> 10.0px ("2 credits"); <span> 10.0px ("2 credits").

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.

A+

Heading Hierarchy

53 headings

PASS

53 headings

Single H1 present

H1 EDIT ANY PHOTO BY TYPING WHAT YOU WANT
H2 Editor
H2 Create
H2 Result
H2 Studio-ready product shots from everyday clutter
H2 THREE STEPS. NO LAYERS.
H3 Upload
H3 Describe
H3 Download
H2 SEVEN MODES. ONE OMNICREATOR WORKSPACE.
H3 Replace background
H3 Remove objects & watermarks
H3 Product photo
H3 Change outfit
H3 Relight
H3 Custom edit
H3 Text to image
H2 ONE EDITOR. SIX EVERYDAY JOBS.
H3 Background Replace
H3 Object Removal
H3 Product Photos
H3 Outfit Change
H3 Photo Relighting
H3 Text to Image
H2 WHAT ONE PROMPT CAN DO
H3 Product photo
H3 Replace background
H3 Remove objects & watermarks
H2 WHY NOT JUST USE…
H2 What we promise
H3 Failed edits are free
H3 Free daily credits
H3 Your photos are not kept
H3 Reply in 1 business day
H3 No surprise charges
H3 Full-size downloads
H3 Tried it? Tell us
H2 OMNICREATOR FAQ
H3 How do free credits work in Omni Creator?
H3 What file types work?
H3 How do you handle my photos?
H3 Can I use results commercially?
H3 What content is not allowed?
H3 Will every edit look perfect?
H3 How long does a generation take?
H3 Are paid plans available?
H3 Do I need an account?
H3 How fast is support?
H2 YOUR NEXT EDIT IS ONE PROMPT AWAY
H2 GUIDES & PROMPT TIPS
H3 AI Image Editing Prompts: 12 Patterns
H3 AI Product Photos for E-commerce
H3 Relight Photos with AI: Light Prompts

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

9 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 9 all-caps heading(s)

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

6 decorative image(s) correctly marked

16 image(s) with good alt text

22 images 16 good alt text 6 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#studio-image	file	Photo (required)	for/id
#studio-prompt	textarea	Prompt	for/id
input	range	Product photo: Drag to compare before and after	aria-label
input	range	Replace background: Drag to compare before and after	aria-label
input	range	Remove objects & watermarks: Drag to compare before and after	aria-label

A+

Link & Button Quality

78 links, 36 buttons — all OK

PASS

78 links, 36 buttons — all OK

1 link(s) open in new tab without warning

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

Got: mailto:support@omnicreator.art

77 link(s) with descriptive text

78 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	Omni Creator	img no alt	Add alt attribute to the image
/	Omni Creator	img no alt	Add alt attribute to the image
/blog/ai-image-editing-prompts	PromptingAI Image Editing Prom…	img no alt	Add alt attribute to the image
/blog/ai-product-photos-for-ecommerce	E-commerceAI Product Photos fo…	img no alt	Add alt attribute to the image
/blog/relight-photos-with-ai	GuidesRelight Photos with AI: …	img no alt	Add alt attribute to the image
mailto:support@omnicreator.art	Email support	new tab	Add '(opens in new tab)' to text

113 links and buttons have descriptive text

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

mailto:support@omnicreator.art

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

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

5 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: Omni Creator

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

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

Name Omni Creator Display Mode standalone Theme Color #e5e5e5 Background Color #e5e5e5 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+

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 EDIT ANY PHOTO BY TY…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 Editor	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 Create	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 Result	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 Studio-ready product…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 THREE STEPS. NO LAYE…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 SEVEN MODES. ONE OMN…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 ONE EDITOR. SIX EVER…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 WHAT ONE PROMPT CAN …	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 WHY NOT JUST USE…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 What we promise	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 OMNICREATOR FAQ	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 YOUR NEXT EDIT IS ON…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h2 GUIDES & PROMPT TIPS	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h3 Upload	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h3 Describe	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h3 Download	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h3 Replace background	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h3 Remove objects & wat…	16.67:1	3.0:1	#000000	#E5E5E5	Pass
h3 Product photo	16.67:1	3.0:1	#000000	#E5E5E5	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 97/100 — 2 failing, 29 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
Daily check-in · +10 credits `div.flex > div.flex > div.flex > span.text-xs`
MODES `div.container-oc > div.flex > div.flex > p.font-mono`
2 credits `div.flex > div.flex > button.shrink-0 > span.ml-1.5`
2 credits `div.flex > div.flex > button.shrink-0 > span.ml-1.5`
2 credits `div.flex > div.flex > button.shrink-0 > span.ml-1.5`
2 credits `div.flex > div.flex > button.shrink-0 > span.ml-1.5`
2 credits `div.flex > div.flex > button.shrink-0 > span.ml-1.5`
1 credit `div.flex > div.flex > button.shrink-0 > span.ml-1.5`
PHOTO (REQUIRED) `div.rounded-[32px] > form.flex > div.flex > label.flex`
Output keeps your photo’s aspect ratio. `div.grid > div.rounded-[32px] > form.flex > p.flex`
PROMPT `div.rounded-[32px] > form.flex > div.flex > label.flex`
Try an example `form.flex > div.flex > div.flex > p.text-xs`
0/4000 `div.rounded-[32px] > form.flex > div.flex > p.text-right`
Pick an example below or upload your own. Sign in with Google to generate in th… `div.rounded-[32px] > div.mt-4 > div.flex > span.max-w-sm`
TRY AN EXAMPLE CASE `div.mt-4 > div.flex > div.mt-1 > p.mb-2`
Examples load into the editor — sign in to Generate. `div.mt-4 > div.flex > div.mt-1 > p.mt-2`
01 `div.mt-12 > a.group > div.flex > span.font-mono`
02 `div.mt-12 > a.group > div.flex > span.font-mono`
03 `div.mt-12 > a.group > div.flex > span.font-mono`
04 `div.mt-12 > a.group > div.flex > span.font-mono`
05 `div.mt-12 > a.group > div.flex > span.font-mono`
06 `div.mt-12 > a.group > div.flex > span.font-mono`
07 `div.mt-12 > a.group > div.flex > span.font-mono`
AI BACKGROUND REPLACE `div.grid > a.group > div > p.font-mono`
AI OBJECT REMOVER `div.grid > a.group > div > p.font-mono`
AI PRODUCT PHOTOGRAPHY `div.grid > a.group > div > p.font-mono`
AI OUTFIT CHANGER `div.grid > a.group > div > p.font-mono`
AI RELIGHTING `div.grid > a.group > div > p.font-mono`
AI TEXT TO IMAGE `div.grid > a.group > div > p.font-mono`
“Clean white studio product shot” `div.mt-12 > div.group > div.flex > p.min-h-[2.5rem]`
“Soft new background, subject kept sharp” `div.mt-12 > div.group > div.flex > p.min-h-[2.5rem]`
“Remove unwanted objects naturally” `div.mt-12 > div.group > div.flex > p.min-h-[2.5rem]`
Based on publicly described features as of 2026; competitors change often. Pick… `div.flex > section#why > div.container-oc > p.mt-4`
01 `div.mt-12 > div.flex > div.flex > span.font-mono`
02 `div.mt-12 > div.flex > div.flex > span.font-mono`
03 `div.mt-12 > div.flex > div.flex > span.font-mono`
04 `div.mt-12 > div.flex > div.flex > span.font-mono`
05 `div.mt-12 > div.flex > div.flex > span.font-mono`
06 `div.mt-12 > div.flex > div.flex > span.font-mono`

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

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

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

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

○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

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

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