Skip to content
https://allbirds.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Form Accessibility
Action
9 of 18 controls have issues
FIX
9 of 18 controls have issues
Critical::
8 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="radio" name="swatch-group-7266695741520" id="swatch-276782186576-featured-7266695741520">; <input type="radio" name="swatch-group-7205190795344" id="swatch-270335672400-featured-7205190795344">; <input type="radio" name="swatch-group-4870548979792" id="swatch-88217321541-featured-4870548979792">; <input type="radio" name="swatch-group-4638145937488" id="swatch-129542815824-featured-4638145937488">; <input type="radio" name="swatch-group-7205201248336" id="swatch-274419384400-featured-7205201248336">; <input type="radio" name="swatch-group-7205199478864" id="swatch-276437598288-featured-7205199478864">; <input type="radio" name="swatch-group-7205189779536" id="swatch-276388151376-featured-7205189779536">; <input type="radio" name="swatch-group-7217832656976" id="swatch-275774963792-featured-7217832656976">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="contact[email]" id="Email">
Info::
9 control(s) properly labeled
18 controls
9 labeled
1 placeholder only
8 unlabeled
ControlTypeLabelMethod
#country-selectorselectSelect countryaria-label
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#Emailemail(Email Address)placeholder only
#swatch-88217321541-featured-4870548979792radio(none)none
#swatch-129542815824-featured-4638145937488radio(none)none
#swatch-274419384400-featured-7205201248336radio(none)none
#swatch-276437598288-featured-7205199478864radio(none)none
#swatch-276388151376-featured-7205189779536radio(none)none
#swatch-275774963792-featured-7217832656976radio(none)none
#swatch-276782186576-featured-7266695741520radio(none)none
#swatch-270335672400-featured-7205190795344radio(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="radio" name="swatch-group-7266695741520" id="swatch-276782186576-featured-7266695741520">; <input type="radio" name="swatch-group-7205190795344" id="swatch-270335672400-featured-7205190795344">; <input type="radio" name="swatch-group-4870548979792" id="swatch-88217321541-featured-4870548979792">; <input type="radio" name="swatch-group-4638145937488" id="swatch-129542815824-featured-4638145937488">; <input type="radio" name="swatch-group-7205201248336" id="swatch-274419384400-featured-7205201248336">; <input type="radio" name="swatch-group-7205199478864" id="swatch-276437598288-featured-7205199478864">; <input type="radio" name="swatch-group-7205189779536" id="swatch-276388151376-featured-7205189779536">; <input type="radio" name="swatch-group-7217832656976" id="swatch-275774963792-featured-7217832656976">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="email" name="contact[email]" id="Email">

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

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: #ece9e2
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <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
Landmark Structure
9 landmarks
REVIEW
9 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.
Warning::
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
BANNER header NAV MAIN 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

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

B
Heading Hierarchy
70 headings, 1 skip(s)
REVIEW
70 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Men's Shoes
  • H3 Customer Favorites
  • H3 Apparel & Accessories
  • H3 Socks
  • H3 Men's Apparel
  • H3 Accessories
  • H3 Final Few
  • H3 Women's Shoes
  • H3 Popular Picks
  • H3 Apparel & Accessories
  • H3 Socks
  • H3 Apparel
  • H3 Accessories
  • H3 Final Few
  • H3 Men
  • H3 Women
  • H3 Featured
  • H3 Shoes
  • H3 Socks & Apparel
  • H3 Sale
  • H3 Customer Favorites
  • H3 Featured
  • H3 Shoes
  • H3 Socks & Apparel
  • H3 Sale
  • H3 All Sale
  • H2 Cart (0)
  • H2 Added to Cart
  • H3 You may also like
  • H2 30% Off Your Order When You Spend $130+
  • H3 Discount Automatically Applied at Checkout.
  • H1 Ready. Set. Take your time.
  • H1 Breathable By Nature duplicate H1
  • H2 New Arrivals
  • H2 Mens
  • H2 Womens
  • H2 Best Sellers
  • H3 Dasher NZ
  • H2 Your Easy, Breezy MVP
  • H2 Dasher NZ
  • H2 Varsity Collection
  • H2 Terralux™ Collection
  • H3 Follow The Flock
  • H2 Refund policy
  • H2 Privacy policy
  • H2 Terms of service
  • H1 Table of Contents duplicate H1
  • H3 1. Privacy skipped
  • H3 2. Registration
  • H3 3. Purchases
  • H3 4. General Restrictions on Use
  • H3 5. Content
  • H3 6. SMS Messaging
  • H3 7. Errors, Inaccuracies, and Omissions
  • H3 8. Disclaimers and Warranties
  • H3 9. Limitation of Liability
  • H3 10. Indemnity
  • H3 11. Links To Other Sites
  • H3 12. Digital Millennium Copyright Act – Copyright Infringement
  • H3 13. Dispute Resolution and Binding Arbitration
  • H3 14. Governing Law and Venue
  • H3 15. Miscellaneous
  • H3 Where are we shipping to?
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Allbirds ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Alt Text Quality
All 101 images OK
PASS
All 101 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
55 decorative image(s) correctly marked
Info::
45 image(s) with good alt text
101 images 45 good alt text 55 decorative
IssueCount
too long1 image(s)
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 Ready. Set. Take you…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Breathable By Nature21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cart (0)21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Added to Cart21.00:13.0:1
#000000
#FFFFFF
Pass
h2 New Arrivals21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mens21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Womens21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Best Sellers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Easy, Breezy MV…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dasher NZ21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Varsity Collection21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Terralux™ Collecti…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Refund policy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy policy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Terms of service21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Customer Favorites21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Apparel & Accessorie…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Accessories21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Final Few21.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.

A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 31 passed
PASS
100

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.

○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
●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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●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
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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