Skip to content
https://goodfair.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
Theme color only
FIX
Theme color only
Info::
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: rgb(255, 255, 255)
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 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.

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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 4 <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.
B
Alt Text Quality
2 of 56 images have issues
REVIEW
2 of 56 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
8 decorative image(s) correctly marked
Info::
46 image(s) with good alt text
56 images 46 good alt text 8 decorative 2 missing
IssueCount
missing2 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

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 25 passed
REVIEW
86

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
Shop now div.spacing-style > div.group-block > div.group-block-content > a.size-style
$20 USD product-price.text-block > div > span.price > span.money
$20 USD product-price.text-block > div > span.price > span.money
$20 USD product-price.text-block > div > span.price > span.money
$20 USD product-price.text-block > div > span.price > span.money
$20 USD product-price.text-block > div > span.price > span.money
$20 USD product-price.text-block > div > span.price > span.money
$20 USD product-price.text-block > div > span.price > span.money
$20 USD product-price.text-block > div > span.price > span.money
Read More div.section > div.border-style > div.spacing-style > a.size-style
READ OUR STORY div.spacing-style > div.group-block > div.group-block-content > a.size-style
02/26/2025 div.stamped-carousel-scroll > div#stamped-carousel-scroll-wrapper > div.block > div.stamped-reviews-date
all the ones i got were so cute div.block > div.stamped-ratings-wrapper > div.stamped-reviews-message > div.stamped-reviews-message-block
Hannah div#stamped-carousel-scroll-wrapper > div.block > div.stamped-ratings-wrapper > div.stamped-reviews-author
OUR MISSION div.ai-mission-container-auuxqoehznk1ht1mwmaigenblockb336ac9k4xhcm > div.ai-mission-content-auuxqoehznk1ht1mwmaigenblockb336ac9k4xhcm > div.ai-mission-text-wrapper-auuxqoehznk1ht1mwmaigenblockb336ac9k4xhcm > div.ai-mission-eyebrow-auuxqoehznk1ht1mwmaigenblockb336ac9k4xhcm

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We used to sell thrift & mystery bundles. Now we curate sustainable everyday pr… div.group-block > div.group-block-content > div.spacing-style > h5

These are opportunities to improve keyboard navigation in your application.

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#Hero-template--20504138448953__hero_6M88Ej > div.hero__container > div.hero__media-wrapper > img.hero__image div#Hero-template--20504138448953__hero_6M88Ej > div.hero__container > div.hero__media-wrapper > img.hero__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
div.header__row > div.header__columns > div.header__column > a.size-style div.header__row > div.header__columns > div.header__column > a.size-style
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link
div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-link div.block > div.stamped-ratings-wrapper > div.stamped-reviews-title > a.stamped-reviews-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.

○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.
●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
●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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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
○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
○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
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN ASIDE CONTENTINFO footer

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
28 headings, 1 skip(s)
PASS
28 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Goodfair
  • H2 Country/Region
  • H2 Country/Region
  • H2 Account
  • H2 Account
  • H2 Your cart is empty
  • H5 We used to sell thrift & mystery bundles.Now we curate sustainable everyday products - same values, clearer impact. skipped
  • H3 Product title
  • H3 Product title
  • H3 Product title
  • H3 Product title
  • H3 Product title
  • H3 Product title
  • H3 Product title
  • H3 Product title
  • H3 Shop by Collection
  • H4 Our Mission
  • H3 Product title
  • H3 Product title
  • H3 Product title
  • H3 Product title
  • H3 No New Things
  • H4 The Benefits of Buying Used Flannel Shirts
  • H4 The history of thrift shopping: Exploring the origins and evolution of the thrift industry.
  • H4 How Thrifting Inspires Street Style
  • H2 Making sustainable fashion accessible to everyone
  • H2 Join our email list
  • H2 Search

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

A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#EmailInput-ASGp1ejU1RW5aTWl2S__email_signup_crihX7emailEmailfor/id
#cmdk-inputsearchSearchfor/id
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)
ElementRatioRequiredFGBGResult
h1 Goodfair21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Country/Region21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Country/Region21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Account21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Account21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your cart is empty21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Making sustainable f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join our email list21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Search21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Shop by Collection21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product title21.00:13.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.

Send Feedback