Skip to content
https://bandcamp.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
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::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Heading Hierarchy
35 headings, 1 skip(s)
REVIEW
35 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 We care about your privacy
  • H1 Fans have paid artists $1.71 billion using Bandcamp, and yesterday alone bought 73,003 records.
  • H5 Struktur skipped
  • H5 Funky Q Nice
  • H5 Jah Ragga - The Great Prophet
  • H5 Oops... All Breaks! Vol 2 - More Baltimore Club Loops for the Discerning DJ
  • H5 Oops... All Breaks! Vol 1 - Baltimore Club Loops for the Discerning DJ
  • H5 Individual Thought Patterns (Reissue)
  • H5 disinteGration
  • H5 House FM (Extended version)
  • H5 Purpose
  • H5 Road of the Lonely Ones
  • H5 Bend Ya Back
  • H5 Struktur
  • H5 Funky Q Nice
  • H5 Jah Ragga - The Great Prophet
  • H5 Oops... All Breaks! Vol 2 - More Baltimore Club Loops for the Discerning DJ
  • H5 Oops... All Breaks! Vol 1 - Baltimore Club Loops for the Discerning DJ
  • H5 Individual Thought Patterns (Reissue)
  • H5 disinteGration
  • H5 House FM (Extended version)
  • H5 Purpose
  • H5 Road of the Lonely Ones
  • H5 Bend Ya Back
  • H5 (empty)
  • H2 Bandcamp Daily
  • H2 Bandcamp Radio
  • H2 New and Notable
  • H2 Album of the Day
  • H2 Get the best of Bandcamp Daily
  • H2 Discover music by genre and location
  • H2 Discover merch
  • H2 Listening Parties & Live Streams
  • H3 Bandcamp Dailyyour guide to the world of Bandcamp
  • H3 On Bandcamp Radio

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

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

B
Alt Text Quality
1 of 53 images have issues
REVIEW
1 of 53 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
30 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
53 images 22 good alt text 30 decorative 1 missing
IssueCount
missing1 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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Bandcamp ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA 13 pass AA only
title Bandcamp
3.17:1
#000000
on
#5B5D5D
needs 4.5:1 (normal text)
16px · top of page (header area)
p Bandcamp uses cookies to make the site w…
3.17:1
#000000
on
#5B5D5D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Read our
1.75:1
#000000
on
#193B45
needs 4.5:1 (normal text)
16px · top of page (header area)
a Privacy Policy
2.47:1
#000000
on
#414F53
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span to learn more about how Bandcamp uses co…
3.17:1
#000000
on
#5B5D5D
needs 4.5:1 (normal text)
16px · above the fold
p You can update your cookie settings at a…
3.17:1
#000000
on
#5B5D5D
needs 4.5:1 (normal text)
16px · above the fold
button Accept all
3.17:1
#000000
on
#5B5D5D
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
h1 Fans have paid artis…3.17:13.0:1
#000000
#5B5D5D
Pass
h1 using Bandcamp, and …3.17:13.0:1
#000000
#5B5D5D
Pass
h1 records.3.17:13.0:1
#000000
#5B5D5D
Pass
h2 We care about your p…3.17:13.0:1
#000000
#5B5D5D
Pass
h2 Bandcamp Daily3.17:13.0:1
#000000
#5B5D5D
Pass
h2 Bandcamp Radio3.17:13.0:1
#000000
#5B5D5D
Pass
h2 New and Notable3.17:13.0:1
#000000
#5B5D5D
Pass
h2 Album of the Day3.17:13.0:1
#000000
#5B5D5D
Pass
h2 Get the best of Band…3.17:13.0:1
#000000
#5B5D5D
Pass
h2 Discover music by ge…3.17:13.0:1
#000000
#5B5D5D
Pass
h2 Discover merch3.17:13.0:1
#000000
#5B5D5D
Pass
h2 Listening Parties & …3.17:13.0:1
#000000
#5B5D5D
Pass
h3 On Bandcamp Radio3.17:13.0:1
#000000
#5B5D5D
Pass
title Bandcamp3.17:14.5:1
#000000
#5B5D5D
Fail
p Bandcamp uses cookie…3.17:14.5:1
#000000
#5B5D5D
Fail
span Read our1.75:14.5:1
#000000
#193B45
Fail
a Privacy Policy2.47:14.5:1
#000000
#414F53
Fail
span to learn more about …3.17:14.5:1
#000000
#5B5D5D
Fail
p You can update your …3.17:14.5:1
#000000
#5B5D5D
Fail
button Accept all3.17:14.5:1
#000000
#5B5D5D
Fail

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
22 landmarks
PASS
22 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Bandcamp" 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

A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#g-input-uid2searchSearch for artist, album or track (optional)for/id
#g-input-uid1emailEmail addressfor/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 30 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
●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
●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
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○`<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
○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.
○`<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.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○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