Skip to content
https://goodeeworld.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
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 2 pass AA only
div You are eligible for free shipping!
3.66:1
#000000
on
#955722
needs 4.5:1 (normal text)
16px · above the fold
a Check out
3.49:1
#000000
on
#91541F
needs 4.5:1 (normal text)
16px · above the fold
div Your cart is empty
2.77:1
#000000
on
#814413
needs 4.5:1 (normal text)
16px · above the fold
a Start shopping
4.44:1
#000000
on
#99684C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p — nothing more for you to pay.
4.01:1
#000000
on
#7B6865
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)
ElementRatioRequiredFGBGResult
h2 Refreshed for Spring21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Allday Goods21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Niwaki – Back In21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Stock21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Arden Set by eco…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Alessi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Baan Boon21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bergs Potter21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What we care about21.00:13.0:1
#000000
#FFFFFF
Pass
title Where Design meets P…12.15:14.5:1
#000000
#F3BD3A
Pass
a Skip to content12.15:14.5:1
#000000
#F3BD3A
Pass
div Shopping cart21.00:14.5:1
#000000
#FFFFFF
Pass
div You are $175.00 away…7.86:14.5:1
#000000
#BD9777
Pass
div You are eligible for…3.66:14.5:1
#000000
#955722
Fail
a Check out3.49:14.5:1
#000000
#91541F
Fail
div Your cart is empty2.77:14.5:1
#000000
#814413
Fail
a Start shopping4.44:14.5:1
#000000
#99684C
Fail
strong US & Canada: Duties …3.74:13.0:1
#000000
#776361
Pass
p — nothing more for…4.01:14.5:1
#000000
#7B6865
Fail
strong Free Carbon-Offset S…4.24:13.0:1
#000000
#7F6C67
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 27 passed
REVIEW
88

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
div#shopify-section-template--16015619981452__slideshow_yHj8yd > div#section-id-template--16015619981452__slideshow_yHj8yd > div.slideshow > ul.slick-dots div#shopify-section-template--16015619981452__slideshow_yHj8yd > div#section-id-template--16015619981452__slideshow_yHj8yd > div.slideshow > ul.slick-dots

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
open post div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container
open post div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container
open post div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container
open post div.instafeed-new-layout-container > div.instafeed-new-layout-wrapper > div.instafeed-new-layout-item > div.instafeed-new-layout-item-container

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
VIEW ALL div.container > div.collection-slider > div.view-all > a.small-feature-link

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
div.logo-area > div.logo-area__right > div.logo-area__right__inner > a.swym-wishlist div.logo-area > div.logo-area__right > div.logo-area__right__inner > a.swym-wishlist
div.logo-area > div.logo-area__right > div.logo-area__right__inner > a.cart-link div.logo-area > div.logo-area__right > div.logo-area__right__inner > a.cart-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.

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
NEW div.block-inner > div.block-inner-inner > div.image-cont > a.product-link
○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
●`[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 input fields have accessible names
●ARIA toggle fields have accessible names
●Document has a `<title>` element
●`<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
●Skip links are focusable.
●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 `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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
○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.
○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.
○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
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
1 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN ASIDE "Language selected: English" CONTENTINFO (missing!)

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

A+
Heading Hierarchy
16 headings
PASS
16 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 Refreshed for Spring
  • H2 Allday Goods
  • H2 Niwaki – Back In Stock
  • H2 The Arden Set by ecoBirdy
  • H2 Alessi
  • H2 Left New Arrivals Right
  • H2 Baan Boon
  • H2 Gather well. Live warmly. Feel the season.
  • H2 Bergs Potter
  • H2 What we care about
  • H2 Good Stories
  • H3 Craft of Care
  • H3 Kashiwa Craft: Shaped by Hand, Guided by Nature
  • H3 Rooted in Craft, Connected by Purpose: A Collaboration with EarthSeed Farm
  • H2 Follow Us on Instagram

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

A+
Alt Text Quality
All 68 images OK
PASS
All 68 images OK
Info::
50 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
68 images 18 good alt text 50 decorative
All images have appropriate alt text.
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
qtextSearch Storearia-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback