Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 3 REVIEW 7 FIX

Alt Text Quality

Action

65 of 142 images have issues

FIX

65 of 142 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image(s) with filename as alt text

55 image(s) with generic alt text

72 decorative image(s) correctly marked

5 image(s) with good alt text

142 images 5 good alt text 72 decorative 62 generic 3 missing

Issue	Count
missing	3 image(s)
filename	7 image(s)
generic	55 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Link & Button Quality

Action

16 issue(s) across 426 links and 27 buttons

FIX

16 issue(s) across 426 links and 27 buttons

12 link(s) with no accessible text

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

Got: https://www.stevemadden.com/collections/mens-all-products; https://www.stevemadden.com/collections/mens-winter-outfits; https://www.stevemadden.com/collections/womens-all-products; https://www.stevemadden.com/collections/mens-all-products; https://www.stevemadden.com/collections/kids-shoes; https://www.stevemadden.com/collections/bags-accessories; https://www.stevemadden.com/collections/all-clothing; https://www.stevemadden.com/pages/wedding; https://www.stevemadden.com/pages/new-and-now; https://www.stevemadden.com/pages/deals (+2 more)

4 link(s) with generic text

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

Got: https://www.stevemadden.com/pages/shippingpolicy ("Learn More"); https://www.stevemadden.com/collections/buy-with-prime ("here"); https://www.stevemadden.com/pages/shippingpolicy ("Learn More"); /pages/stevemadden ("Learn More")

10 image-only link(s) without alt text

1 link(s) open in new tab without warning

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

Got: https://www.instagram.com/stevemadden/?hl=en

399 link(s) with descriptive text

426 links

12 empty

4 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.stevemadden.com/pages/shippi…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Shippingpolicy
https://www.stevemadden.com/collections/…	here	generic text	Replace with descriptive text
Before: here Suggested: Buy With Prime
https://www.stevemadden.com/pages/shippi…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Shippingpolicy
https://www.stevemadden.com/collections/…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/collections/…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/collections/…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/collections/…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/collections/…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/collections/…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/collections/…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/pages/weddin…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/pages/new-an…	(empty)	empty	Add link text or aria-label
https://www.stevemadden.com/pages/deals	(empty)	empty	Add link text or aria-label
/collections/jelly	JELLIES	img no alt	Add alt attribute to the image
/collections/pretty-prints	FUN PRINTS	img no alt	Add alt attribute to the image
/collections/crochet-woven-raffia	RAFFIA & CROCHET	img no alt	Add alt attribute to the image
/collections/flip-flops	THONG SANDALS	img no alt	Add alt attribute to the image
/collections/womens-heels	HEELS …	img no alt	Add alt attribute to the image
/collections/how-to-style-spring-boots	SPRING BOOTS …	img no alt	Add alt attribute to the image
/collections/color-shop	SPRING COLOR SHOP …	img no alt	Add alt attribute to the image
/collections/festival-shop	FESTIVAL …	img no alt	Add alt attribute to the image
/collections/make-it-a-match	MAKE IT A MATCH …	img no alt	Add alt attribute to the image
/collections/spring-apparel	SPRING APPAREL …	img no alt	Add alt attribute to the image
/collections/all-whats-new	(empty)	empty	Add link text or aria-label
/collections/all-whats-new	(empty)	empty	Add link text or aria-label
https://www.instagram.com/stevemadden/?h…	@stevemadden	new tab	Add '(opens in new tab)' to text
/pages/stevemadden	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Stevemadden

426 links and buttons have descriptive text

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

https://www.stevemadden.com/collections/mens-all-products; https://www.stevemadden.com/collections/mens-winter-outfits; https://www.stevemadden.com/collections/womens-all-products; https://www.stevemadden.com/collections/mens-all-products; https://www.stevemadden.com/collections/kids-shoes; https://www.stevemadden.com/collections/bags-accessories; https://www.stevemadden.com/collections/all-clothing; https://www.stevemadden.com/pages/wedding; https://www.stevemadden.com/pages/new-and-now; https://www.stevemadden.com/pages/deals (+2 more)

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.

https://www.stevemadden.com/pages/shippingpolicy ("Learn More"); https://www.stevemadden.com/collections/buy-with-prime ("here"); https://www.stevemadden.com/pages/shippingpolicy ("Learn More"); /pages/stevemadden ("Learn 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

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

https://www.instagram.com/stevemadden/?hl=en

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

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 ✗

Heading Hierarchy

Action

12 headings, 1 skip(s)

REVIEW

12 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Your cart is empty
H2 Your cart (0)
H2 Estimated total
H2 SHOW US HOW YOU WEAR IT
H4 No one else can do it like you. Follow @stevemadden and tag us for a chance to get featured on our page. skipped
H2 CUSTOMER SERVICE
H2 ABOUT THE COMPANY
H2 SITE TERMS
H2 SALES & PROMOTIONS
H2 STORE LOCATOR
H2 SM PASS
H3 1-888-SMADDEN

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – Steve Madden ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

h2 Your cart is empty

1.30:1

#000000

#1D230F

needs 3.0:1 (large text)

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

title Steve Madden® Official Site | Free Ship…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

title Steve Madden® Official Site | Free Ship…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Skip to menu

1.52:1

#000000

#44250E

needs 4.5:1 (normal text)

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

a Skip to content

1.64:1

#000000

#383218

needs 4.5:1 (normal text)

16px · above the fold

a Click to view our Accessibility Statemen…

1.70:1

#000000

#33371A

needs 4.5:1 (normal text)

16px · above the fold

a Skip to footer

1.08:1

#000000

#090E0A

needs 4.5:1 (normal text)

16px · above the fold

a Continue shopping

1.87:1

#000000

#4D3713

needs 4.5:1 (normal text)

16px · above the fold

3 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 Your cart is empty	1.30:1	3.0:1	#000000	#1D230F	Fail
h2 Estimated total	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SHOW US HOW YOU WEAR…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 CUSTOMER SERVICE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ABOUT THE COMPANY	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SITE TERMS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SALES & PROMOTIONS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 STORE LOCATOR	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SM PASS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 1-888-SMADDEN	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Steve Madden® Offic…	1.00:1	4.5:1	#000000	#000000	Fail
title Steve Madden® Offic…	3.66:1	4.5:1	#000000	#666666	Fail
a My Wishlist	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to chat support	13.08:1	4.5:1	#000000	#CCCCCC	Pass
a Skip to header	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to menu	1.52:1	4.5:1	#000000	#44250E	Fail
a Skip to content	1.64:1	4.5:1	#000000	#383218	Fail
a Click to view our Ac…	1.70:1	4.5:1	#000000	#33371A	Fail
a Skip to footer	1.08:1	4.5:1	#000000	#090E0A	Fail
a Continue shopping	1.87:1	4.5:1	#000000	#4D3713	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

13 landmarks

PASS

13 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <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

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search" name="q" id="Search-In-Modal header__serach__desk">

4 control(s) properly labeled

5 controls

4 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#discount-code-input	text	Discount Code	for/id
#Search-In-Modal	search	Search input	for/id
#Search-In-Modal	text	Search input field	aria-label
#NewsletterForm--sections--15710688510085__footer	email	Email address	for/id
#Search-In-Modal header__serach__desk	search	(Search)	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

Lighthouse Accessibility Audits

Score 92/100 — 4 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
No one else can do it like you. Follow @stevemadden and tag us for a chance to … `div.container > div.display_flex > div.wraper_title > h4.section-title-subtitle`

These are opportunities to improve keyboard navigation in your application.

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--15710691459205__home_XGeLP4 > div.main-content-container > div.xy-section-container > a `div#shopify-section-template--15710691459205__home_XGeLP4 > div.main-content-container > div.xy-section-container > a`
div#shopify-section-template--15710691459205__home_XGeLP4 > div.main-content-container > div.xy-section-container > a `div#shopify-section-template--15710691459205__home_XGeLP4 > div.main-content-container > div.xy-section-container > a`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ADD+ `div#gallery > a.product-card > div.product-price-container > button.buy-button`
ADD+ `div#gallery > a.product-card > div.product-price-container > button.buy-button`
ADD+ `div#gallery > a.product-card > div.product-price-container > button.buy-button`
ADD+ `div#gallery > a.product-card > div.product-price-container > button.buy-button`

These items highlight common accessibility best practices.

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
GO `div.footer-block__newsletter > form#ContactFooter > div.newsletter-form__field-wrapper > button#Subscribe`

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

●`button`, `link`, and `menuitem` elements have accessible names

●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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

○`[accesskey]` values are unique

○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

○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

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