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 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

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

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

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 ModePartial Dark Mode

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 ✗

Mobile-Readable Font Sizes

Action

87% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

87% of visible text renders at >= 12 CSS px (3 below threshold)

3 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: <small> 11.6px ("© 2026,"); <a> 11.6px ("di Lusso Clothing"); <a> 11.6px ("Powered by Shopify").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

9 pass 11 fail WCAG AA 1 pass AA only

a About us

1.53:1

#000000

#273020

needs 4.5:1 (normal text)

16px · above the fold

a Contact

1.12:1

#000000

#0F130D

needs 4.5:1 (normal text)

16px · above the fold

a Log in

3.82:1

#000000

#6E6861

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Facebook

1.11:1

#000000

#10110C

needs 4.5:1 (normal text)

16px · above the fold

span Home

1.13:1

#000000

#13140E

needs 4.5:1 (normal text)

16px · above the fold

span Online Store

2.02:1

#000000

#3E4043

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span About us

1.09:1

#000000

#0E0F0C

needs 4.5:1 (normal text)

16px · above the fold

span Contact

1.16:1

#000000

#191611

needs 4.5:1 (normal text)

16px · above the fold

label Search

1.08:1

#000000

#0B0D0F

needs 4.5:1 (normal text)

16px · above the fold

span Log in

3.04:1

#000000

#5B5A56

needs 4.5:1 (normal text)

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

span Cart

3.46:1

#000000

#705F55

needs 4.5:1 (normal text)

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

4 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
h2 Item added to your c…	12.08:1	3.0:1	#000000	#C7C4BF	Pass
h2 Tulsa's Destination …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Visit di Lusso in Hi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscribe to our ema…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title di Lusso Clothing Co…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Online Store	6.30:1	4.5:1	#000000	#8E8D86	Pass
a About us	1.53:1	4.5:1	#000000	#273020	Fail
a Contact	1.12:1	4.5:1	#000000	#0F130D	Fail
a Log in	3.82:1	4.5:1	#000000	#6E6861	Fail
span Facebook	1.11:1	4.5:1	#000000	#10110C	Fail
span Home	1.13:1	4.5:1	#000000	#13140E	Fail
span Online Store	2.02:1	4.5:1	#000000	#3E4043	Fail
span About us	1.09:1	4.5:1	#000000	#0E0F0C	Fail
span Contact	1.16:1	4.5:1	#000000	#191611	Fail
label Search	1.08:1	4.5:1	#000000	#0B0D0F	Fail
span Log in	3.04:1	4.5:1	#000000	#5B5A56	Fail
span Cart	3.46:1	4.5:1	#000000	#705F55	Fail
a View cart	21.00:1	4.5:1	#000000	#FFFFFF	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

Skip navigation link present

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

A+

Heading Hierarchy

5 headings

PASS

5 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H2 Item added to your cart
H2 Tulsa's Destination for Exceptional Menswear
H2 Visit di Lusso in Historic SoBo
H2 Subscribe to our emails

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

2 decorative image(s) correctly marked

1 image(s) with good alt text

3 images 1 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#Search-In-Modal	search	Search	for/id
#NewsletterForm--sections--27686214467898__footer	email	Email	for/id

A+

Link & Button Quality

21 links, 7 buttons — all OK

PASS

21 links, 7 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

20 link(s) with descriptive text

21 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.shopify.com?utm_campaign=pow…	Powered by Shopify	new tab	Add '(opens in new tab)' to text

27 links and buttons have descriptive text

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

https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

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

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

PASS

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

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

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

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
Subscribe to our emails `div.footer__content-top > div.footer-block--newsletter > div.footer-block__newsletter > h2.footer-block__heading`
form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--27686214467898__footer `form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--27686214467898__footer`
Email `form#ContactFooter > div.newsletter-form__field-wrapper > div.field > label.field__label`
Follow on `div.relative > button.group > span.cursor-pointer`

These are opportunities to improve the legibility of your content.

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

●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

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

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

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