Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

404 Error Page

Action

HTTP 429, custom page

FIX

HTTP 429, custom page

Unexpected status code: HTTP 429

Expected HTTP 404 but received 429. This may confuse search engine crawlers.

Got: HTTP 429

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 429 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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 ✗

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="search" name="q">; <input type="search" name="q">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search	(Search products)	placeholder only
q	search	(what are you looking for?)	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

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

title Oddli

2.07:1

#000000

#434236

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

2.09:1

#000000

#434335

needs 4.5:1 (normal text)

16px · top of page (header area)

div Menu

2.10:1

#000000

#444336

needs 4.5:1 (normal text)

16px · top of page (header area)

span Shop All

2.14:1

#000000

#454437

needs 4.5:1 (normal text)

16px · top of page (header area)

a Basics

2.17:1

#000000

#464537

needs 4.5:1 (normal text)

16px · above the fold

a Knits

2.20:1

#000000

#474639

needs 4.5:1 (normal text)

16px · above the fold

a Swim

2.24:1

#000000

#48473B

needs 4.5:1 (normal text)

16px · above the fold

a Stories

2.31:1

#000000

#49493E

needs 4.5:1 (normal text)

16px · above the fold

a Oddli Club

2.28:1

#000000

#49483D

needs 4.5:1 (normal text)

16px · above the fold

a Instagram

2.35:1

#000000

#4B4A40

needs 4.5:1 (normal text)

16px · above the fold

a TikTok

2.71:1

#000000

#664D45

needs 4.5:1 (normal text)

16px · above the fold

p Menu

2.86:1

#000000

#6B5047

needs 4.5:1 (normal text)

16px · above the fold

p Shop All

2.96:1

#000000

#6E5248

needs 4.5:1 (normal text)

16px · above the fold

button Back

2.80:1

#000000

#665044

needs 4.5:1 (normal text)

16px · mid-page

a New In

2.67:1

#000000

#5D4F45

needs 4.5:1 (normal text)

16px · mid-page

a Best Sellers

3.68:1

#000000

#696662

needs 4.5:1 (normal text)

16px · mid-page

span Tops

3.15:1

#000000

#5F5C55

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

span Bottoms

2.76:1

#000000

#5A5344

needs 4.5:1 (normal text)

16px · mid-page

span Swim

2.26:1

#000000

#4B4738

needs 4.5:1 (normal text)

16px · mid-page

a Dresses

2.10:1

#000000

#444336

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Oddli	2.07:1	4.5:1	#000000	#434236	Fail
a Skip to content	2.09:1	4.5:1	#000000	#434335	Fail
div Menu	2.10:1	4.5:1	#000000	#444336	Fail
span Shop All	2.14:1	4.5:1	#000000	#454437	Fail
a Basics	2.17:1	4.5:1	#000000	#464537	Fail
a Knits	2.20:1	4.5:1	#000000	#474639	Fail
a Swim	2.24:1	4.5:1	#000000	#48473B	Fail
a Stories	2.31:1	4.5:1	#000000	#49493E	Fail
a Oddli Club	2.28:1	4.5:1	#000000	#49483D	Fail
a Instagram	2.35:1	4.5:1	#000000	#4B4A40	Fail
a TikTok	2.71:1	4.5:1	#000000	#664D45	Fail
p Menu	2.86:1	4.5:1	#000000	#6B5047	Fail
p Shop All	2.96:1	4.5:1	#000000	#6E5248	Fail
button Back	2.80:1	4.5:1	#000000	#665044	Fail
a New In	2.67:1	4.5:1	#000000	#5D4F45	Fail
a Best Sellers	3.68:1	4.5:1	#000000	#696662	Fail
span Tops	3.15:1	4.5:1	#000000	#5F5C55	Fail
span Bottoms	2.76:1	4.5:1	#000000	#5A5344	Fail
span Swim	2.26:1	4.5:1	#000000	#4B4738	Fail
a Dresses	2.10:1	4.5:1	#000000	#444336	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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Text Quality

No headings to evaluate -- check is N/A

PASS

No headings to evaluate -- check is N/A

A+

Alt Text Quality

All 211 images OK

PASS

All 211 images OK

11 decorative image(s) correctly marked

200 image(s) with good alt text

211 images 200 good alt text 11 decorative

All images have appropriate alt text.

Link & Button Quality

2 issue(s) across 188 links and 16 buttons

PASS

2 issue(s) across 188 links and 16 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /collections/oddli-x-jaden-edwards

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /blogs/stories ("Read More")

186 link(s) with descriptive text

188 links

1 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/blogs/stories	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Stories
/collections/oddli-x-jaden-edwards	(empty)	empty	Add link text or aria-label
/collections/knits	SHOP KNITWEAR	img no alt	Add alt attribute to the image
/collections/swimwear	SHOP SWIM	img no alt	Add alt attribute to the image
/collections/basics	SHOP BASICS	img no alt	Add alt attribute to the image
/collections/all	SHOP ALL	img no alt	Add alt attribute to the image

202 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/collections/oddli-x-jaden-edwards

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/blogs/stories ("Read More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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 101 visible text node(s) render at >= 12 CSS pixels

PASS

All 101 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 96/100 — 1 failing, 24 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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#shopify-section-template--20004299047108__hero_Jz3Kwd > div.flex > div.flex-1 > a.block `div#shopify-section-template--20004299047108__hero_Jz3Kwd > div.flex > div.flex-1 > a.block`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○Heading elements appear in a sequentially-descending order

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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