Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 5 REVIEW 6 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 ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

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 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

12 landmarks

REVIEW

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

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

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

Action

39 headings

REVIEW

39 headings

Multiple H1 headings (2 found)

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

5 empty heading(s)

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

H2 Your cart is empty
H2 Your cart
H2 Estimated total
H2 Country/region
H1 (empty)
H2 FOR THE REBELS, THE DREAMERS AND THE DOERS
H2 New Season, new colours
H3 Fern Stripe Merino Base Layer
H3 Fern Stripe Merino Base Layer
H3 Betty Merino Stripe Headband
H3 Betty Merino Stripe Headband
H3 Suzie Jeans
H3 Suzie Jeans
H3 Betty Merino Fine Stripe Neck Warmer
H3 Betty Merino Fine Stripe Neck Warmer
H3 Fern Textured Merino Base Layer
H3 Fern Textured Merino Base Layer
H2 Meet Suzie
H2 OUR FIRST EVER JEANS!
H2 (empty)
H2 Shop by Collection
H2 (empty)
H2 (empty)
H2 (empty)
H3 Use It or Lose It: Why Our High Streets Matter More Than Ever
H3 Use It or Lose It: Why Our High Streets Matter ...
H3 Finding Freedom Outdoors, On Her Own Terms
H3 Finding Freedom Outdoors, On Her Own Terms
H3 Use It or Lose It: Why Our High Streets Matter More Than Ever
H3 Use It or Lose It: Why Our High Streets Matter ...
H3 Move the way you move by Ana Norrie-Toch
H3 Move the way you move by Ana Norrie-Toch
H1 Get 10% off duplicate H1
H2 Information
H2 Contact
H2 Shop
H2 Country/region
H3 Ready to Save 10% on Your
H3 Next Adventure?

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

Link & Button Quality

1 issue(s) across 710 links and 44 buttons

REVIEW

1 issue(s) across 710 links and 44 buttons

1 link(s) with generic text

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

Got: https://findraclothing.myshopify.com/policies/privacy-policy ("Learn more")

7 link(s) open in new tab without warning

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

Got: https://www.reviews.io/company-reviews/store/findraclothing.com; https://findraclothing.com/policies/privacy-policy; http://hello@findra.co.uk; mailto:hello@findraclothing.com; tel://+441896870313; https://maps.app.goo.gl/cunYTaGM1czhQdnT6; tel://+441896208170

702 link(s) with descriptive text

710 links

0 empty

1 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://findraclothing.myshopify.com/pol…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Privacy Policy
/collections/womens-outdoor-clothing-acc…	Shop All Accessories	img no alt	Add alt attribute to the image
https://www.reviews.io/company-reviews/s…	Read more reviews on REVIEWS.i…	new tab	Add '(opens in new tab)' to text
https://findraclothing.com/policies/priv…	Privacy Policy	new tab	Add '(opens in new tab)' to text
http://hello@findra.co.uk	hello@findraclothing.com	new tab	Add '(opens in new tab)' to text
mailto:hello@findraclothing.com	hello@findraclothing.com	new tab	Add '(opens in new tab)' to text
tel://+441896870313	+44 (0)1896 870313	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/cunYTaGM1czhQdnT…	FINDRA Clothing83 High Street,…	new tab	Add '(opens in new tab)' to text
tel://+441896208170	+44 (0)1896 208170	new tab	Add '(opens in new tab)' to text

746 links and buttons have descriptive text

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

https://findraclothing.myshopify.com/policies/privacy-policy ("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.reviews.io/company-reviews/store/findraclothing.com; https://findraclothing.com/policies/privacy-policy; http://hello@findra.co.uk; mailto:hello@findraclothing.com; tel://+441896870313; https://maps.app.goo.gl/cunYTaGM1czhQdnT6; tel://+441896208170

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

Mobile Keyboard & Autofill

Action

3/5 eligible field(s) missing autocomplete or inputmode

REVIEW

3/5 eligible field(s) missing autocomplete or inputmode

3 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: search, email.

Got: <input type="search" name="q" id="Search-In-Modal">, <input type="email" name="email" id="email_01M3YR9AF68A7N9E7FYQE58R94">, <input type="email" name="email" id="email_01M1E04NE564AZK7SKGXMTNQZY">

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h2 Your cart is empty

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your cart

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Estimated total

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Country/region

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 New Season, new colours

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Meet Suzie

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 OUR FIRST EVER JEANS!

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Shop by Collection

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Country/region

1.99:1

#000000

#3F3F3F

needs 3.0:1 (large text)

24px · bottom of viewport

title FINDRA Outdoor Clothing | Style, Comfort…

1.17:1

#000000

#161718

needs 4.5:1 (normal text)

16px · top of page (header area)

span This website uses cookies to ensure you …

1.17:1

#000000

#161718

needs 4.5:1 (normal text)

16px · top of page (header area)

a Learn more

1.41:1

#000000

#272728

needs 4.5:1 (normal text)

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

button Preferences

2.03:1

#000000

#404040

needs 4.5:1 (normal text)

16px · top of page (header area)

button Accept

2.03:1

#000000

#404040

needs 4.5:1 (normal text)

16px · above the fold

button ✕

1.61:1

#000000

#313130

needs 4.5:1 (normal text)

16px · above the fold

span Manage consent preferences

1.66:1

#000000

#323332

needs 4.5:1 (normal text)

16px · above the fold

a Reject all

1.64:1

#000000

#333231

needs 4.5:1 (normal text)

16px · above the fold

a Accept all

1.60:1

#000000

#313030

needs 4.5:1 (normal text)

16px · above the fold

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
h2 Your cart is empty	1.99:1	3.0:1	#000000	#3F3F3F	Fail
h2 Your cart	1.99:1	3.0:1	#000000	#3F3F3F	Fail
h2 Estimated total	1.99:1	3.0:1	#000000	#3F3F3F	Fail
h2 Country/region	1.99:1	3.0:1	#000000	#3F3F3F	Fail
h2 New Season, new colo…	1.99:1	3.0:1	#000000	#3F3F3F	Fail
h2 Meet Suzie	1.99:1	3.0:1	#000000	#3F3F3F	Fail
h2 OUR FIRST EVER JEANS…	1.99:1	3.0:1	#000000	#3F3F3F	Fail
h2 Shop by Collection	1.99:1	3.0:1	#000000	#3F3F3F	Fail
h2 Country/region	1.99:1	3.0:1	#000000	#3F3F3F	Fail
title FINDRA Outdoor Cloth…	1.17:1	4.5:1	#000000	#161718	Fail
span This website uses co…	1.17:1	4.5:1	#000000	#161718	Fail
a Learn more	1.41:1	4.5:1	#000000	#272728	Fail
button Preferences	2.03:1	4.5:1	#000000	#404040	Fail
button Accept	2.03:1	4.5:1	#000000	#404040	Fail
button ✕	1.61:1	4.5:1	#000000	#313130	Fail
span Manage consent prefe…	1.66:1	4.5:1	#000000	#323332	Fail
a Reject all	1.64:1	4.5:1	#000000	#333231	Fail
a Accept all	1.60:1	4.5:1	#000000	#313030	Fail
div We use cookies to op…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
div Strictly necessary c…	20.31:1	4.5:1	#000000	#FCFBF9	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.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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)

Alt Text Quality

All 59 images OK

PASS

All 59 images OK

6 image(s) with alt text over 125 characters

42 decorative image(s) correctly marked

11 image(s) with good alt text

59 images 11 good alt text 42 decorative

Issue	Count
too long	6 image(s)

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
pref_1	checkbox		none
pref_2	checkbox		none
pref_4	checkbox		none
#CartDrawer-Note	textarea	Sending a gift? Add a gift message below	for/id
#Search-In-Modal	search	Search	for/id
#first_name_01M3YR9AF0K9V5WPX9CBB4PG07	text	First Name	for/id
#email_01M3YR9AF68A7N9E7FYQE58R94	email	Email	for/id
#email_01M1E04NE564AZK7SKGXMTNQZY	email	Email	aria-label

A+

Form Input Types

8 form control(s) checked, no type mismatches

PASS

8 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

8 form control(s) checked, no input-semantic issues

PASS

8 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

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -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.)

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

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

PASS

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

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 31 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
Made sustainably, always `div#findra-feature-mousetrap > div.feature > div.feature__text > a`

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.

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

●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

●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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○Uses ARIA roles only on compatible elements

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

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