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

Link & Button Quality

Action

11 issue(s) across 362 links and 31 buttons

FIX

11 issue(s) across 362 links and 31 buttons

3 link(s) with no accessible text

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

Got: /collections/new-arrivals; /collections/new-arrivals; /collections/new-arrivals

6 link(s) open in new tab without warning

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

Got: https://www.instagram.com/urbansavageactive/; https://www.facebook.com/urbansavageactive; https://www.pinterest.com/urbansavageactive/; https://www.instagram.com/urbansavageactive/; https://www.facebook.com/urbansavageactive; https://www.pinterest.com/urbansavageactive/

8 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.collapsible-trigger (#357 on page); button.collapsible-trigger (#380 on page); button.collapsible-trigger (#390 on page); button.collapsible-trigger (#413 on page); button.collapsible-trigger (#443 on page); button.btn (#2374 on page); button.btn (#2377 on page); button.btn (#2380 on page)

353 link(s) with descriptive text

362 links

3 empty

0 generic text

6 new tab

8 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/urbansavageact…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/urbansavageacti…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/urbansavageact…	Pinterest	new tab	Add '(opens in new tab)' to text
/collections/new-arrivals	(empty)	empty	Add link text or aria-label
/collections/new-arrivals	(empty)	empty	Add link text or aria-label
/collections/new-arrivals	(empty)	empty	Add link text or aria-label
https://www.instagram.com/urbansavageact…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/urbansavageacti…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/urbansavageact…	Pinterest	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

376 links and buttons have descriptive text

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

/collections/new-arrivals; /collections/new-arrivals; /collections/new-arrivals

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

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

https://www.instagram.com/urbansavageactive/; https://www.facebook.com/urbansavageactive; https://www.pinterest.com/urbansavageactive/; https://www.instagram.com/urbansavageactive/; https://www.facebook.com/urbansavageactive; https://www.pinterest.com/urbansavageactive/

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.collapsible-trigger (#357 on page); button.collapsible-trigger (#380 on page); button.collapsible-trigger (#390 on page); button.collapsible-trigger (#413 on page); button.collapsible-trigger (#443 on page); button.btn (#2374 on page); button.btn (#2377 on page); button.btn (#2380 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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.

Got: #111111

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 ✗

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA 7 pass AA only

title Urban Savage – Urban Savage

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.79:1

#000000

#383838

needs 4.5:1 (normal text)

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

span Close menu

4.37:1

#000000

#727272

needs 4.5:1 (normal text)

16px · top of page (header area)

a NEW

3.70:1

#000000

#656769

needs 4.5:1 (normal text)

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

a NEW BOTTOMS

3.07:1

#000000

#585B5D

needs 4.5:1 (normal text)

16px · above the fold

a NEW TOPS

2.85:1

#000000

#545658

needs 4.5:1 (normal text)

16px · above the fold

a NEW SKIRTS/DRESSES

2.03:1

#000000

#443F3E

needs 4.5:1 (normal text)

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

a GIFT CARDS

2.03:1

#000000

#4D3D30

needs 4.5:1 (normal text)

16px · above the fold

a BOTTOMS

1.64:1

#000000

#343230

needs 4.5:1 (normal text)

16px · above the fold

a LEGGINGS

1.46:1

#000000

#2B2A28

needs 4.5:1 (normal text)

16px · above the fold

a CROP LEGGINGS

1.47:1

#000000

#2B2A2B

needs 4.5:1 (normal text)

16px · above the fold

a 7/8 LEGGINGS

1.47:1

#000000

#2B2A2A

needs 4.5:1 (normal text)

16px · above the fold

a ANKLE LEGGINGS

1.41:1

#000000

#282728

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 Currency	4.37:1	3.0:1	#000000	#727272	Pass
h2 New Arrivals	4.37:1	3.0:1	#000000	#727272	Pass
h2 PLEATED JACKET	4.37:1	3.0:1	#000000	#727272	Pass
h2 Our Best Selling Leg…	4.37:1	3.0:1	#000000	#727272	Pass
h2 BOW LEGGING & TOP	4.37:1	3.0:1	#000000	#727272	Pass
h2 Email Sign Up	4.37:1	3.0:1	#000000	#727272	Pass
h2 Currency	4.37:1	3.0:1	#000000	#727272	Pass
title Urban Savage – Urb…	1.12:1	4.5:1	#000000	#121212	Fail
a Skip to content	1.79:1	4.5:1	#000000	#383838	Fail
span Close menu	4.37:1	4.5:1	#000000	#727272	Fail
a NEW	3.70:1	4.5:1	#000000	#656769	Fail
a NEW BOTTOMS	3.07:1	4.5:1	#000000	#585B5D	Fail
a NEW TOPS	2.85:1	4.5:1	#000000	#545658	Fail
a NEW SKIRTS/DRESSES	2.03:1	4.5:1	#000000	#443F3E	Fail
a GIFT CARDS	2.03:1	4.5:1	#000000	#4D3D30	Fail
a BOTTOMS	1.64:1	4.5:1	#000000	#343230	Fail
a LEGGINGS	1.46:1	4.5:1	#000000	#2B2A28	Fail
a CROP LEGGINGS	1.47:1	4.5:1	#000000	#2B2A2B	Fail
a 7/8 LEGGINGS	1.47:1	4.5:1	#000000	#2B2A2A	Fail
a ANKLE LEGGINGS	1.41:1	4.5:1	#000000	#282728	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.

Lighthouse Accessibility Audits

Score 86/100 — 3 failing, 26 passed

REVIEW

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CART `div.header-item > div.site-nav > div.site-nav__icons > a.site-nav__link`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#newsletter-template--14463991775350__1630550276e13e9b0f > div.input-group > div.input-group-btn > button.btn `form#newsletter-template--14463991775350__1630550276e13e9b0f > div.input-group > div.input-group-btn > button.btn`

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.feature-row > div.feature-row__item > div > a `div.feature-row > div.feature-row__item > div > a`
div.feature-row > div.feature-row__item > div > a `div.feature-row > div.feature-row__item > div > 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.

○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 are valid and not misspelled

●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

●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

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

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

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

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

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

A+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

12 headings

PASS

12 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

1 empty heading(s)

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

H2 Currency
H1 Urban Savage
H1 Urban Savage duplicate H1
H2 Autumn Looks. Effortless Style.
H2 (empty)
H2 -
H2 New Arrivals
H2 PLEATED JACKET
H2 Our Best Selling Leggings
H2 BOW LEGGING & TOP
H2 Email Sign Up
H2 Currency

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H2: "-"

Got: 1 ≤2-char heading(s)

2 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: 2 all-caps heading(s)

A+

Alt Text Quality

All 57 images OK

PASS

All 57 images OK

5 decorative image(s) correctly marked

52 image(s) with good alt text

57 images 52 good alt text 5 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
q	search	Search our store	aria-label
#Email-template--14463991775350__1630550276e13e9b0f	email	Enter your email	for/id

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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

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

PASS

All 13 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

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.

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