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 7 REVIEW 8 FIX

Link & Button Quality

Action

8 issue(s) across 492 links and 40 buttons

FIX

8 issue(s) across 492 links and 40 buttons

1 link(s) with no accessible text

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

Got: /blogs/news/drake-s-radio-ep-27-soundtrack-to-a-road-trip

6 link(s) with generic text

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

Got: /pages/returns ("here"); /blogs/news/the-autumn-collection-part-two ("READ MORE"); /blogs/news/at-the-table-dean-s ("READ MORE"); /blogs/news/at-the-scale-of-living-with-clare-goodwin ("READ MORE"); /blogs/news/drake-s-radio-ep-27-soundtrack-to-a-road-trip (""); /account/login#recover ("Click Here")

4 link(s) open in new tab without warning

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

Got: https://www.drakes.com/pages/delivery; https://www.drakes.com/pages/returns; https://www.drakes.com/pages/eu-withdrawal-form; https://www.drakes.com/pages/returns

1 button(s) with no accessible text

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

Got: button.go-cart-mini-cart__close (#2517 on page)

481 link(s) with descriptive text

492 links

1 empty

6 generic text

4 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/pages/returns	here	generic text	Replace with descriptive text
Before: here Suggested: Returns
https://www.drakes.com/pages/delivery	delivery page	new tab	Add '(opens in new tab)' to text
https://www.drakes.com/pages/returns	returns portal	new tab	Add '(opens in new tab)' to text
https://www.drakes.com/pages/eu-withdraw…	Withdrawal Form.	new tab	Add '(opens in new tab)' to text
https://www.drakes.com/pages/returns	Returns Portal	new tab	Add '(opens in new tab)' to text
/blogs/news/the-autumn-collection-part-t…	READ MORE	generic text	Replace with descriptive text
Before: READ MORE Suggested: The Autumn Collection Part Two
/blogs/news/at-the-table-dean-s	READ MORE	generic text	Replace with descriptive text
Before: READ MORE Suggested: At The Table Dean S
/blogs/news/at-the-scale-of-living-with-…	READ MORE	generic text	Replace with descriptive text
Before: READ MORE Suggested: At The Scale Of Living With Clare Goodwin
/blogs/news/drake-s-radio-ep-27-soundtra…	link	generic text	Replace with descriptive text
Before: link Suggested: Drake S Radio Ep 27 Soundtrack To A Road Trip
/blogs/news/drake-s-radio-ep-27-soundtra…	(empty)	empty	Add link text or aria-label
/account/login#recover	Click Here	generic text	Replace with descriptive text
Before: Click Here Suggested: Login#Recover
<button>	(empty)	empty	Add button text or aria-label

520 links and buttons have descriptive text

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

/blogs/news/drake-s-radio-ep-27-soundtrack-to-a-road-trip

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.

/pages/returns ("here"); /blogs/news/the-autumn-collection-part-two ("READ MORE"); /blogs/news/at-the-table-dean-s ("READ MORE"); /blogs/news/at-the-scale-of-living-with-clare-goodwin ("READ MORE"); /blogs/news/drake-s-radio-ep-27-soundtrack-to-a-road-trip (""); /account/login#recover ("Click Here")

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.drakes.com/pages/delivery; https://www.drakes.com/pages/returns; https://www.drakes.com/pages/eu-withdrawal-form; https://www.drakes.com/pages/returns

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.go-cart-mini-cart__close (#2517 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

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

FIX

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

5 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">, <input type="search" name="q">, <input type="email" name="customer[email]" id="LoginEmail">, <input type="email" name="customer[email]" id="RegisterEmail">, <input type="email" name="email" id="email_01M0FB4YDFM6P1FHVS1BHJ76XA">

404 Error Page

Action

HTTP 404, custom page

FIX

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

Got: #000000

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

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.

Heading Hierarchy

36 headings, 1 skip(s)

REVIEW

36 headings, 1 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

1 empty heading(s)

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

H1 .logo-svg svg { width: 100%; max-width: 100px; } @media (max-width: 64rem) { .logo-svg svg {
H3 Your Cart skipped
H2 Your Cart
H3 Why not add:
H2 Returns
H2 Delivery Options
H2 Dispatch Information
H2 FAQ's
H3 Do I need an account to place an order?
H3 When will my order be dispatched?
H3 I can't find my size online. Will it be restocked?
H3 What is your returns policy?
H3 How do I exercise my right of withdrawal?
H3 Can I cancel my order?
H3 Can I return an item purchased online at one of your shops?
H3 Do bundle offers qualify for extra discounts?
H3 I can't access my account online. What should I do?
H3 Is your website accessible to all users?
H2 The Autumn Collection: Part Two
H2 At The Table: Gray’s Papaya
H2 At Home with Leonard Baby
H2 Product in Focus
H2 Radio
H1 Drake’s Radio 29: Raife Burchell duplicate H1
H2 Instagram
H2 Log In / Register Register / Log In
H2 Not Signed Up?
H2 Already Have An Account?
H2 Shop Look
H2 Relaxed Elegance since 1977
H3 Sign up to email newsletter
H3 About
H3 Customer
H3 Legal
H3 Follow
H2 (empty)

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

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

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

Alt Text Quality

Action

17 of 25 images have issues

REVIEW

17 of 25 images have issues

16 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with generic alt text

8 image(s) with good alt text

25 images 8 good alt text 1 generic 16 missing

Issue	Count
missing	16 image(s)
generic	1 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

Form Accessibility

2 of 11 controls have issues

REVIEW

2 of 11 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="search" name="q">; <input type="search" name="q">

9 control(s) properly labeled

11 controls

9 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#LoginEmail	email	Email Address*	for/id
#LoginPassword	password	Password*	for/id
#FirstName	text	First Name*	for/id
#LastName	text	Last Name*	for/id
#RegisterEmail	email	Email Address*	for/id
#DrawerCreatePassword	password	Password*	for/id
#email_01M0FB4YDFM6P1FHVS1BHJ76XA	email	Email Address*	aria-label
#Accepts%20Marketing__3__6	checkbox	By subscribing to our newsletter, you agree to receive promotional content from Drake's in accordance with our Privacy Policy	aria-label
input	input	ftr-tmp-input	aria-label
q	search	(What are you looking for?)	placeholder only
q	search	(What are you looking for?)	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

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

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

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

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

Iframe Accessibility

3/4 iframe(s) missing title; 0 placeholder(s)

REVIEW

3/4 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.

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

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

REVIEW

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

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

Lighthouse Accessibility Audits

Score 85/100 — 4 failing, 25 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.

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
VIEW PLAYLIST `div.flex@md > div.width-100% > div.image-text__content > a.position-relative`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.crt-EmptyCollection_Media > div.crt-EmptyCollection_Image > div.rsp-Image > img.rsp-Image_Image `div.crt-EmptyCollection_Media > div.crt-EmptyCollection_Image > div.rsp-Image > img.rsp-Image_Image`
div.crt-EmptyCollection_Media > div.crt-EmptyCollection_Image > div.rsp-Image > img.rsp-Image_Image `div.crt-EmptyCollection_Media > div.crt-EmptyCollection_Image > div.rsp-Image > img.rsp-Image_Image`
div.crt-EmptyCollection_Media > div.crt-EmptyCollection_Image > div.rsp-Image > img.rsp-Image_Image `div.crt-EmptyCollection_Media > div.crt-EmptyCollection_Image > div.rsp-Image > img.rsp-Image_Image`
div.crt-EmptyCollection_Media > div.crt-EmptyCollection_Image > div.rsp-Image > img.rsp-Image_Image `div.crt-EmptyCollection_Media > div.crt-EmptyCollection_Image > div.rsp-Image > img.rsp-Image_Image`
div.position-absolute > div.block > div.rsp-Image > img.rsp-Image_Image `div.position-absolute > div.block > div.rsp-Image > img.rsp-Image_Image`
div.banner-column > div.banner-column-image > div.rsp-Image > img.rsp-Image_Image `div.banner-column > div.banner-column-image > div.rsp-Image > img.rsp-Image_Image`
div.banner-column > div.banner-column-image > div.rsp-Image > img.rsp-Image_Image `div.banner-column > div.banner-column-image > div.rsp-Image > img.rsp-Image_Image`
div.flex@md > div.width-100% > div.rsp-Image > img.rsp-Image_Image `div.flex@md > div.width-100% > div.rsp-Image > img.rsp-Image_Image`
div.banner-column > div.banner-column-image > div.rsp-Image > img.rsp-Image_Image `div.banner-column > div.banner-column-image > div.rsp-Image > img.rsp-Image_Image`
div.banner-column > div.banner-column-image > div.rsp-Image > img.rsp-Image_Image `div.banner-column > div.banner-column-image > div.rsp-Image > img.rsp-Image_Image`
div.flex@md > div.width-100% > div.rsp-Image > img.rsp-Image_Image `div.flex@md > div.width-100% > div.rsp-Image > img.rsp-Image_Image`
div.featured-products-media > div.featured-products-media__media > div.rsp-Image > img.rsp-Image_Image `div.featured-products-media > div.featured-products-media__media > div.rsp-Image > img.rsp-Image_Image`
div.flex@md > div.width-100% > div.rsp-Image > img.rsp-Image_Image `div.flex@md > div.width-100% > div.rsp-Image > img.rsp-Image_Image`

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
ul.crt-Empty_CollectionsList > li.crt-Empty_CollectionsItem > div.crt-EmptyCollection > a.crt-EmptyCollection_Link `ul.crt-Empty_CollectionsList > li.crt-Empty_CollectionsItem > div.crt-EmptyCollection > a.crt-EmptyCollection_Link`
ul.crt-Empty_CollectionsList > li.crt-Empty_CollectionsItem > div.crt-EmptyCollection > a.crt-EmptyCollection_Link `ul.crt-Empty_CollectionsList > li.crt-Empty_CollectionsItem > div.crt-EmptyCollection > a.crt-EmptyCollection_Link`
ul.crt-Empty_CollectionsList > li.crt-Empty_CollectionsItem > div.crt-EmptyCollection > a.crt-EmptyCollection_Link `ul.crt-Empty_CollectionsList > li.crt-Empty_CollectionsItem > div.crt-EmptyCollection > a.crt-EmptyCollection_Link`
ul.crt-Empty_CollectionsList > li.crt-Empty_CollectionsItem > div.crt-EmptyCollection > a.crt-EmptyCollection_Link `ul.crt-Empty_CollectionsList > li.crt-Empty_CollectionsItem > div.crt-EmptyCollection > a.crt-EmptyCollection_Link`
div.col > div.width-100% > div > a.btn--link `div.col > div.width-100% > div > a.btn--link`

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
div.col > div.width-100% > div > a.btn--link `div.col > div.width-100% > div > a.btn--link`
VIEW PLAYLIST `div.flex@md > div.width-100% > div.image-text__content > a.position-relative`

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

●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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

1 <nav> landmark(s) found

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 Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H1: 183 chars

Got: 1 >120-char heading(s)

A+

Form Input Types

11 form control(s) checked, no type mismatches

PASS

11 form control(s) checked, no type mismatches

No input-type mismatches detected

Form Input Quality

1 input-semantic issue(s) across 11 form control(s)

PASS

1 input-semantic issue(s) across 11 form control(s)

2 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="customer[password]">, <input type="password" name="customer[password]">.

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Mobile-Readable Font Sizes

No visible text nodes measured on the page

PASS

No visible text nodes measured on the page

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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Drake’s Radio 29: …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your Cart	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Returns	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Delivery Options	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Dispatch Information	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 FAQ's	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The Autumn Collectio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 At The Table: Gray�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 At Home with Leonard…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Product in Focus	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Radio	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Instagram	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Not Signed Up?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Already Have An Acco…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop Look	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Relaxed Elegance sin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Your Cart	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Why not add:	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sign up to email new…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About	21.00:1	3.0: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.

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