Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

9 PASS 9 REVIEW 6 FIX

404 Error Page

Action

HTTP 502, bare page

FIX

HTTP 502, bare page

Unexpected status code: HTTP 502

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

Got: HTTP 502

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 502 ✗Page Title 502 Bad Gateway ✓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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

4 landmarks

REVIEW

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

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

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

Heading Hierarchy

3 headings

REVIEW

3 headings

No H1 heading found

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

H2 Prime Delivery
H2 Our Signature Collection
H2 As Worn By You

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

Link & Button Quality

Action

8 issue(s) across 247 links and 20 buttons

REVIEW

8 issue(s) across 247 links and 20 buttons

7 link(s) with no accessible text

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

Got: a.lSPrev (#1094 on page); a.lSNext (#1095 on page); #; #; #; #; #

1 button(s) with no accessible text

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

Got: button.woot-elements--right (#1407 on page)

240 link(s) with descriptive text

247 links

7 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

259 links and buttons have descriptive text

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

a.lSPrev (#1094 on page); a.lSNext (#1095 on page); #; #; #; #; #

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

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

button.woot-elements--right (#1407 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

Mobile Keyboard & Autofill

Action

1/2 eligible field(s) missing autocomplete or inputmode

REVIEW

1/2 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email" id="email_016JB91TTR00000000003NNPRZ">

Iframe Accessibility

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

REVIEW

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

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.

Tap Target Adequacy

Action

5 tap target(s) too small or too close together

REVIEW

5 tap target(s) too small or too close together

5 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

Action

86% of visible text renders at >= 12 CSS px (46 below threshold)

REVIEW

86% of visible text renders at >= 12 CSS px (46 below threshold)

46 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: <span> 11.0px ("29% OFF"); <span> 11.5px ("Prime Delivery"); <span> 11.0px ("34% OFF"); <span> 11.5px ("Prime Delivery"); <span> 11.0px ("24% OFF").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA 3 pass AA only

title FJackets: 100% Real Leather Jackets, Coa…

3.66:1

#000000

#CC0C2F

needs 4.5:1 (normal text)

16px · top of page (header area)

span Until Jan 31st, 2027

3.66:1

#000000

#CC0C2F

needs 4.5:1 (normal text)

16px · above the fold

a Select Items

4.37:1

#000000

#7A6F77

needs 4.5:1 (normal text)

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

b SD25

1.96:1

#000000

#394038

needs 3.0:1 (large text)

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

a Select Items

1.06:1

#000000

#070B08

needs 4.5:1 (normal text)

16px · mid-page

2 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 Prime Delivery	8.33:1	3.0:1	#000000	#CD9871	Pass
h2 Our Signature Collec…	8.33:1	3.0:1	#000000	#CD9871	Pass
h2 As Worn By You	8.33:1	3.0:1	#000000	#CD9871	Pass
title FJackets: 100% Real …	3.66:1	4.5:1	#000000	#CC0C2F	Fail
b 11.11 Sale,	10.02:1	3.0:1	#000000	#EB9EAC	Pass
span Extra $25 OFF, Code:	21.00:1	4.5:1	#000000	#FFFFFF	Pass
b SD25	13.17:1	3.0:1	#000000	#C8CDD7	Pass
a Select Items	19.26:1	4.5:1	#000000	#F5F5F5	Pass
b Free Extended Holida…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
span Until Jan 31st, 2027	3.66:1	4.5:1	#000000	#CC0C2F	Fail
b 11.11 Sale,	3.66:1	3.0:1	#000000	#CC0C2F	Pass
span Extra $25 OFF, Code:	19.25:1	4.5:1	#000000	#F5F5F4	Pass
b SD25	19.26:1	3.0:1	#000000	#F5F5F5	Pass
a Select Items	4.37:1	4.5:1	#000000	#7A6F77	Fail
b Free Extended Holida…	6.39:1	3.0:1	#000000	#B58362	Pass
span Until Jan 31st, 2027	6.45:1	4.5:1	#000000	#B58463	Pass
b 11.11 Sale,	6.69:1	3.0:1	#000000	#B88764	Pass
span Extra $25 OFF, Code:	5.43:1	4.5:1	#000000	#A7775A	Pass
b SD25	1.96:1	3.0:1	#000000	#394038	Fail
a Select Items	1.06:1	4.5:1	#000000	#070B08	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 — 4 failing, 23 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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
11.11 Sale, Extra $25 OFF, Code: SD25 Select Items Free Extended Holiday Return… `body > div.newsticker > div.fj-tl-view`

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.

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
Free exchanges included `div.in > div.it > div > span`
No middlemen markups `div.in > div.it > div > span`
with PayPal or Klarna `div.in > div.it > div > span`
Chat with us 24/7 `div.in > div.it > div > span`
$280 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
$327 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
$299 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
$317 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
$309 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
$293 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
72 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$303 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
41 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$339 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
71 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$307 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
45 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$281 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
52 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$325 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
81 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$311 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
38 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$299 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
94 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$330 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
27 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$350 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
63 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$293 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
52 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$350 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`
60 `div.fj-card > div.fj-card-meta > div.fj-card-rate > span.fj-card-rc`
$309 `div.fj-card > div.fj-card-meta > div.fj-card-pr > span.was`

These are opportunities to improve the legibility of your content.

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
body > div#Outer > main.fj-home > a `body > div#Outer > main.fj-home > a`
body > div#Outer > main.fj-home > a `body > div#Outer > main.fj-home > a`
body > div#Outer > main.fj-home > a `body > div#Outer > main.fj-home > a`
body > div#Outer > main.fj-home > a `body > div#Outer > main.fj-home > a`
body > div#Outer > main.fj-home > a `body > div#Outer > main.fj-home > 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
1 `div.lSSlideOuter > ul.lSPager > li.active > a`
2 `div.lSSlideOuter > ul.lSPager > li > a`
3 `div.lSSlideOuter > ul.lSPager > li > a`
4 `div.lSSlideOuter > ul.lSPager > li > a`
5 `div.lSSlideOuter > ul.lSPager > li > a`

These items highlight common accessibility best practices.

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

●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

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 53 images OK

PASS

All 53 images OK

53 image(s) with good alt text

53 images 53 good alt text

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_query	text	Search products	aria-label
#email_016JB91TTR00000000003NNPRZ	email	Email	for/id

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "search_query" should use type="search" (currently type="text")

Field name "search_query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

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+

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

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.

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