Skip to content
https://www.marywyattlondon.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
8
REVIEW
2
PASS
14
INFO
0
Checks
24
14 PASS 2 REVIEW 8 FIX
D
Mobile-Readable Font Sizes
Action
15% of visible text renders at >= 12 CSS px (55 below threshold)
FIX
15% of visible text renders at >= 12 CSS px (55 below threshold)
Warning::
55 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: <p> 11.0px ("We and our partners, including Shopify, ..."); <a> 11.0px ("Privacy Policy"); <span> 11.0px ("Manage preferences"); <button> 11.0px ("Accept"); <button> 11.0px ("Decline").
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
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.
B
Tabindex Anti-Patterns
0 positive, 5 -1-on-focusable
REVIEW
0 positive, 5 -1-on-focusable
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h2 Cookie consent
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · top of page (header area)
title Mary Wyatt London
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
p We and our partners, including Shopify, …
1.90:1
#000000
on
#3C3C3B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Privacy Policy
1.16:1
#000000
on
#151615
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Manage preferences
1.02:1
#000000
on
#030403
needs 4.5:1 (normal text)
16px · above the fold
button Accept
1.01:1
#000000
on
#020201
needs 4.5:1 (normal text)
16px · above the fold
button Decline
1.05:1
#000000
on
#080909
needs 4.5:1 (normal text)
16px · above the fold
a Skip to content
1.46:1
#000000
on
#2A2A29
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Mary Wyatt London
1.07:1
#000000
on
#0B0B0B
needs 4.5:1 (normal text)
16px · above the fold
span Navigation menu
1.01:1
#000000
on
#010201
needs 4.5:1 (normal text)
16px · above the fold
summary SHOP
1.01:1
#000000
on
#010201
needs 4.5:1 (normal text)
16px · above the fold
a SHOP ALL
1.26:1
#000000
on
#1E1E1D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a TOPS
1.04:1
#000000
on
#060705
needs 4.5:1 (normal text)
16px · above the fold
a BOTTOMS
1.09:1
#000000
on
#0D0E0C
needs 4.5:1 (normal text)
16px · mid-page
a DRESSES
1.09:1
#000000
on
#0F0E0C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a SWEATS
1.33:1
#000000
on
#24231E
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a OUTERWEAR
1.31:1
#000000
on
#23211D
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

7 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)
ElementRatioRequiredFGBGResult
h2 Cookie consent1.00:13.0:1
#000000
#000000
Fail
h2 NEW ARRIVALS18.93:13.0:1
#000000
#F3F3F3
Pass
h2 SHOP BACK IN STOCK18.93:13.0:1
#000000
#F3F3F3
Pass
title Mary Wyatt London1.00:14.5:1
#000000
#000000
Fail
p We and our partners,…1.90:14.5:1
#000000
#3C3C3B
Fail
a Privacy Policy1.16:14.5:1
#000000
#151615
Fail
span Manage preferences1.02:14.5:1
#000000
#030403
Fail
button Accept1.01:14.5:1
#000000
#020201
Fail
button Decline1.05:14.5:1
#000000
#080909
Fail
a Skip to content1.46:14.5:1
#000000
#2A2A29
Fail
span Mary Wyatt London1.07:14.5:1
#000000
#0B0B0B
Fail
span Navigation menu1.01:14.5:1
#000000
#010201
Fail
summary SHOP1.01:14.5:1
#000000
#010201
Fail
a SHOP ALL1.26:14.5:1
#000000
#1E1E1D
Fail
a TOPS1.04:14.5:1
#000000
#060705
Fail
a BOTTOMS1.09:14.5:1
#000000
#0D0E0C
Fail
a DRESSES1.09:14.5:1
#000000
#0F0E0C
Fail
a SWEATS1.33:14.5:1
#000000
#24231E
Fail
a OUTERWEAR1.31:14.5:1
#000000
#23211D
Fail
a ACCESSORIES17.94:14.5:1
#000000
#EDEDED
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
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
5 headings
PASS
5 headings
Info::
Single H1 present
  • H2 Cookie consent
  • H1 Mary Wyatt London
  • H2 NEW ARRIVALS
  • H2 SHOP BACK IN STOCK
  • H2 MW X TYPE O NEGATIVE LIMITED EDITION COLLECTION
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 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: 3 all-caps heading(s)
A
Alt Text Quality
All 175 images OK
PASS
All 175 images OK
Info::
27 image(s) with alt text over 125 characters
Info::
33 decorative image(s) correctly marked
Info::
115 image(s) with good alt text
175 images 115 good alt text 33 decorative
IssueCount
too long27 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchSearcharia-label
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 30 passed
PASS
97

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.

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
main#main > section#shopify-section-template--27280028467573__slideshow_y8QKw3 > slideshow-carousel#carousel-template--27280028467573__slideshow_y8QKw3 > a.slideshow__slide main#main > section#shopify-section-template--27280028467573__slideshow_y8QKw3 > slideshow-carousel#carousel-template--27280028467573__slideshow_y8QKw3 > a.slideshow__slide
main#main > section#shopify-section-template--27280028467573__slideshow_inLEct > slideshow-carousel#carousel-template--27280028467573__slideshow_inLEct > a.slideshow__slide main#main > section#shopify-section-template--27280028467573__slideshow_inLEct > slideshow-carousel#carousel-template--27280028467573__slideshow_inLEct > a.slideshow__slide

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SPAIN (EUR €) div.footer__aside > div.localization-selectors > div.relative > button.localization-toggle
○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
●`[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
●`<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
●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
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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
○`[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
○Form elements have associated labels
○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.
○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.

Send Feedback