Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 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

2 icon(s) detected

FIX

2 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

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

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

Tap Target Adequacy

Action

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

REVIEW

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

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 7 pass AA only

a Accessories

3.18:1

#000000

#595E5C

needs 4.5:1 (normal text)

16px · mid-page

a New In

3.23:1

#000000

#615E51

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Best sellers	20.00:1	3.0:1	#000000	#FFF8F5	Pass
h2 What customers say	20.00:1	3.0:1	#000000	#FFF8F5	Pass
h2 Our looks	20.00:1	3.0:1	#000000	#FFF8F5	Pass
h2 Join our community	20.00:1	3.0:1	#000000	#FFF8F5	Pass
title Womenswear designed …	20.00:1	4.5:1	#000000	#FFF8F5	Pass
a Skip to content	20.00:1	4.5:1	#000000	#FFF8F5	Pass
span Kate Barton	6.17:1	4.5:1	#000000	#7E8F88	Pass
span Navigation menu	6.33:1	4.5:1	#000000	#7F918B	Pass
summary Shop	6.52:1	4.5:1	#000000	#83938C	Pass
a All Products AW26	6.69:1	4.5:1	#000000	#85958E	Pass
a Dresses & Skirts	6.96:1	4.5:1	#000000	#899890	Pass
a Dungarees & Jumpsuit…	7.07:1	4.5:1	#000000	#8C9990	Pass
a Shirts & Tops	8.37:1	4.5:1	#000000	#A2A598	Pass
a Trousers	9.02:1	4.5:1	#000000	#AEAA9B	Pass
a Knitwear	7.57:1	4.5:1	#000000	#9D9C8D	Pass
a Jackets & Waistcoats	4.53:1	4.5:1	#000000	#75756F	Pass
a Nightwear	5.88:1	4.5:1	#000000	#89887C	Pass
a Accessories	3.18:1	4.5:1	#000000	#595E5C	Fail
a New In	3.23:1	4.5:1	#000000	#615E51	Fail
span EUR €	7.52:1	4.5:1	#000000	#A09A90	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+

Landmark Structure

11 landmarks

PASS

11 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

A+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 Kate Barton
H2 AutumnWinter
H2 Best sellers
H2 What customers say
H2 Our looks
H2 Join our community

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 146 images OK

PASS

All 146 images OK

36 decorative image(s) correctly marked

110 image(s) with good alt text

146 images 110 good alt text 36 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	aria-label
#kb-newsletter-email-template--25150137172344__kb_newsletter_tbk4TF	email	E-mail	for/id

A+

Link & Button Quality

85 links, 158 buttons — all OK

PASS

85 links, 158 buttons — all OK

85 link(s) with descriptive text

85 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

243 links and buttons have descriptive text

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

10 explicit tabindex attribute(s) checked, no anti-patterns

PASS

10 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

Iframe Accessibility

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

PASS

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

A+

Mobile-Readable Font Sizes

All 67 visible text node(s) render at >= 12 CSS pixels

PASS

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

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.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 27 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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
Sale price €205,00 `div.v-stack > div.v-stack > price-list.price-list > sale-price.text-subdued`
Sale price €195,00 `div.v-stack > div.v-stack > price-list.price-list > sale-price.text-subdued`
Sale price €185,00 `div.v-stack > div.v-stack > price-list.price-list > sale-price.text-subdued`
Sale price €60,00 `div.v-stack > div.v-stack > price-list.price-list > sale-price.text-subdued`
★★★★★ Rated 4.7 on Trustpilot · 216 reviews `div.section-stack > div.section-header > div.prose > p.h6`
"It is so difficult to find dresses that fit my shape so well. I must admit I c… `testimonial-carousel#carousel-template--25150137172344__testimonials_39pd87 > div.testimonial-item > div.prose > p`
Sign up to our newsletter to be entered into a monthly draw to win a £200 Kate … `section#shopify-section-template--25150137172344__kb_newsletter_tbk4TF > div.kb-nl > div.kb-nl__body > p`
div.kb-nl > form#kb-newsletter-template--25150137172344__kb_newsletter_tbk4TF > div.kb-nl__row > input#kb-newsletter-email-template--25150137172344__kb_newsletter_tbk4TF `div.kb-nl > form#kb-newsletter-template--25150137172344__kb_newsletter_tbk4TF > div.kb-nl__row > input#kb-newsletter-email-template--25150137172344__kb_newsletter_tbk4TF`

These are opportunities to improve the legibility of your content.

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
Go to item 1 `div.kb-cl > div.container > carousel-navigation.page-dots > button.relative`
Go to item 2 `div.kb-cl > div.container > carousel-navigation.page-dots > button.relative`
Go to item 3 `div.kb-cl > div.container > carousel-navigation.page-dots > button.relative`
Go to item 4 `div.kb-cl > div.container > carousel-navigation.page-dots > button.relative`
Go to item 1 `div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area`
Go to item 2 `div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area`
Go to item 3 `div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area`

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Identical links have the same purpose.

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

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