Skip to content
https://www.allbirds.eu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
F
Alt Text Quality
Action
16 of 76 images have issues
FIX
16 of 76 images have issues
Critical::
16 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
10 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
9 decorative image(s) correctly marked
Info::
51 image(s) with good alt text
76 images 51 good alt text 9 decorative 16 missing
IssueCount
missing16 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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
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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 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

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

C
Heading Hierarchy
Action
4 headings, 1 skip(s)
REVIEW
4 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Wir respektieren deine Privatsphäre
  • H3 WIR WOLLEN DIE DINGE ANDERS, ABER BESSER MACHEN
  • H6 Der beste Erfinder der Welt ist die Natur. Daher holen wir uns hier Inspiration für Schuhe, die unglaublich bequem sind und dir rundum ein gutes Gefühl geben. skipped
  • H3 Das sagen unsere Kunden über uns

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404 Nicht gefunden Custom Styling Navigation Homepage Link Search Form
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color #ffffff CSS indicators Detected

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA 3 pass AA only
title Nachhaltige Schuhe & Sneaker für Damen …
1.10:1
#000000
on
#101010
needs 4.5:1 (normal text)
16px · top of page (header area)
p Wir verwenden Cookies und andere Technol…
2.88:1
#000000
on
#585655
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Datenschutzerklärung.
1.19:1
#000000
on
#1C1815
needs 4.5:1 (normal text)
16px · top of page (header area)
span Einstellungen verwalten
1.50:1
#000000
on
#422418
needs 4.5:1 (normal text)
16px · above the fold
button Akzeptieren
1.41:1
#000000
on
#401E12
needs 4.5:1 (normal text)
16px · above the fold
button Ablehnen
1.38:1
#000000
on
#3B1E15
needs 4.5:1 (normal text)
16px · above the fold
a Zum Inhalt springen
1.21:1
#000000
on
#2D130D
needs 4.5:1 (normal text)
16px · above the fold
p VERSANDKOSTENFREI AB 50€
1.35:1
#000000
on
#391C15
needs 4.5:1 (normal text)
16px · above the fold
p SAMSTAGSZUSTELLUNG
1.32:1
#000000
on
#351C0E
needs 4.5:1 (normal text)
16px · above the fold
p GRATIS RÜCKVERSAND
1.15:1
#000000
on
#1A1311
needs 4.5:1 (normal text)
16px · above the fold
span Navigationsmenü öffnen
1.25:1
#000000
on
#291A15
needs 4.5:1 (normal text)
16px · above the fold
span Suche öffnen
1.71:1
#000000
on
#3B342C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
summary HERREN
2.22:1
#000000
on
#4B4540
needs 4.5:1 (normal text)
16px · mid-page
span Schuhe
3.74:1
#000000
on
#6A6765
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

3 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 Wir respektieren dei…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 WIR WOLLEN DIE DINGE…7.65:13.0:1
#000000
#9C9C9C
Pass
h3 Das sagen unsere Kun…7.65:13.0:1
#000000
#9C9C9C
Pass
title Nachhaltige Schuhe &…1.10:14.5:1
#000000
#101010
Fail
p Wir verwenden Cookie…2.88:14.5:1
#000000
#585655
Fail
a Datenschutzerklärun…1.19:14.5:1
#000000
#1C1815
Fail
span Einstellungen verwal…1.50:14.5:1
#000000
#422418
Fail
button Akzeptieren1.41:14.5:1
#000000
#401E12
Fail
button Ablehnen1.38:14.5:1
#000000
#3B1E15
Fail
a Zum Inhalt springen1.21:14.5:1
#000000
#2D130D
Fail
p VERSANDKOSTENFREI AB…1.35:14.5:1
#000000
#391C15
Fail
p SAMSTAGSZUSTELLUNG1.32:14.5:1
#000000
#351C0E
Fail
p GRATIS RÜCKVERSAND1.15:14.5:1
#000000
#1A1311
Fail
span Navigationsmenü öf…1.25:14.5:1
#000000
#291A15
Fail
span Suche öffnen1.71:14.5:1
#000000
#3B342C
Fail
summary HERREN2.22:14.5:1
#000000
#4B4540
Fail
span Schuhe3.74:14.5:1
#000000
#6A6765
Fail
span Sneaker5.24:14.5:1
#000000
#7F7F7F
Pass
span Sportschuhe5.24:14.5:1
#000000
#7F7F7F
Pass
span Wasserabweisende Sch…5.24:14.5:1
#000000
#7F7F7F
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 87/100 — 5 failing, 24 passed
REVIEW
87

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.

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
Der beste Erfinder der Welt ist die Natur. Daher holen wir uns hier Inspiration… div#slide-template--19445889171702__slideshow_CLzrkk-image_anFW6Q > div.content-over-media_content > div.prose > h6

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.content-over-media > video-media.sm:hidden > video.object-cover > img div.content-over-media > video-media.sm:hidden > video.object-cover > img
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.image
div.footer__block-content > div.footer__country-icons > a > img.image div.footer__block-content > div.footer__country-icons > a > img.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#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a
div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a div#block-country_links_frKQcD > div.footer__block-content > div.footer__country-icons > a

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.

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
4.41 / 5 div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-stars-link
(864 Bewertungen) div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-count-link

These items highlight common accessibility best practices.

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
4.41 / 5 div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-stars-link
(864 Bewertungen) div#block-socials_dhcdGf > div.footer__block-content > div.jdgm-widget > button.jdgm-footer-count-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
`[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.
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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
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
`<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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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+
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
qsearchSuchenaria-label
selectselectSort dropdownaria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback