Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 5 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

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.

Landmark Structure

9 landmarks

REVIEW

9 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

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

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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 Outfit Describer

2.07:1

#000000

#612B6D

needs 3.0:1 (large text)

32px · above the fold

h2 From a reference image to search-ready l…

1.60:1

#000000

#501952

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A shorter path from sample to storefront…

1.60:1

#000000

#501952

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Made for the details that sell the piece…

1.60:1

#000000

#501952

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Outfit Description Pricing

1.60:1

#000000

#501952

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently asked questions

1.60:1

#000000

#501952

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Writing for the rack and the search bar

1.60:1

#000000

#501952

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Give the next product a better first dra…

1.60:1

#000000

#501952

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Bring a reference

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep the details

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Search with context

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Start with the product

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Set the editorial direction

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Refine and publish

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Read the visual evidence

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Write in a chosen voice

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep global copy natural

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Leave with usable copy

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI Outfit Description Generator for E-co…

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

h3 The Ultimate Guide to AI Fashion Technol…

1.60:1

#000000

#501952

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Outfit Describer	2.07:1	3.0:1	#000000	#612B6D	Fail
h2 From a reference ima…	1.60:1	3.0:1	#000000	#501952	Fail
h2 A shorter path from …	1.60:1	3.0:1	#000000	#501952	Fail
h2 Made for the details…	1.60:1	3.0:1	#000000	#501952	Fail
h2 Outfit Description P…	1.60:1	3.0:1	#000000	#501952	Fail
h2 Frequently asked que…	1.60:1	3.0:1	#000000	#501952	Fail
h2 Writing for the rack…	1.60:1	3.0:1	#000000	#501952	Fail
h2 Give the next produc…	1.60:1	3.0:1	#000000	#501952	Fail
h3 Bring a reference	1.60:1	3.0:1	#000000	#501952	Fail
h3 Keep the details	1.60:1	3.0:1	#000000	#501952	Fail
h3 Search with context	1.60:1	3.0:1	#000000	#501952	Fail
h3 Start with the produ…	1.60:1	3.0:1	#000000	#501952	Fail
h3 Set the editorial di…	1.60:1	3.0:1	#000000	#501952	Fail
h3 Refine and publish	1.60:1	3.0:1	#000000	#501952	Fail
h3 Read the visual evid…	1.60:1	3.0:1	#000000	#501952	Fail
h3 Write in a chosen vo…	1.60:1	3.0:1	#000000	#501952	Fail
h3 Keep global copy nat…	1.60:1	3.0:1	#000000	#501952	Fail
h3 Leave with usable co…	1.60:1	3.0:1	#000000	#501952	Fail
h3 AI Outfit Descriptio…	1.60:1	3.0:1	#000000	#501952	Fail
h3 The Ultimate Guide t…	1.60:1	3.0:1	#000000	#501952	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

26 headings

PASS

26 headings

Single H1 present

H1 Outfit Describer
H2 From a reference image to search-ready language.
H3 Bring a reference
H3 Keep the details
H3 Search with context
H2 A shorter path from sample to storefront.
H3 Start with the product
H3 Set the editorial direction
H3 Refine and publish
H2 Made for the details that sell the piece.
H3 Read the visual evidence
H3 Write in a chosen voice
H3 Keep global copy natural
H3 Leave with usable copy
H2 Outfit Description Pricing
H2 Frequently asked questions
H3 Do I need both an image and product details?
H3 What can I create with the studio?
H3 What makes a good product image?
H3 How are credits used?
H3 Are product images kept private?
H2 Writing for the rack and the search bar
H3 AI Outfit Description Generator for E-commerce - Boost Your Product Listings
H3 The Ultimate Guide to AI Fashion Technology in 2025
H3 E-commerce Product Description Best Practices for Fashion Brands
H2 Give the next product a better first draft.

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

1 decorative image(s) correctly marked

7 image(s) with good alt text

8 images 7 good alt text 1 decorative

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <textarea>

1 control(s) properly labeled

2 controls

1 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	file	Click to upload an outfit imageJPG, PNG, WEBP or AVIF. Up to 10 MB.	none
textarea	textarea	(Add a specific instruction for this image, or start with a template above.)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+

Link & Button Quality

24 links, 25 buttons — all OK

PASS

24 links, 25 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@outfitdescription.com

23 link(s) with descriptive text

24 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
mailto:support@outfitdescription.com	Email support	new tab	Add '(opens in new tab)' to text

48 links and buttons have descriptive text

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

mailto:support@outfitdescription.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

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

2 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

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

PASS

20 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+

Mobile-Readable Font Sizes

All 134 visible text node(s) render at >= 12 CSS pixels

PASS

All 134 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 25 passed

PASS

100

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.

○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

●Background and foreground colors have a sufficient contrast ratio

●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

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

○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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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