Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 REVIEW 6 FIX

Landmark Structure

Action

3 landmarks

FIX

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

No contentinfo (footer) landmark

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Link & Button Quality

Action

19 issue(s) across 201 links and 0 buttons

FIX

19 issue(s) across 201 links and 0 buttons

18 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a.centerer (#100 on page); a.button--play (#637 on page); a.button--actions (#638 on page); #; http://blog.reverbnation.com; http://facebook.com/reverbnation; http://twitter.com/reverbnation; http://www.youtube.com/user/ReverbNationVideos; http://instagram.com/reverbnation; http://www.pinterest.com/reverbnation/ (+8 more)

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: ("here")

4 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: http://blog.reverbnation.com/; https://bandlabtechnologies.com/careers/; http://blog.reverbnation.com/; https://bandlabtechnologies.com/careers/

178 link(s) with descriptive text

201 links

18 empty

1 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
http://blog.reverbnation.com	(empty)	empty	Add link text or aria-label
http://facebook.com/reverbnation	(empty)	empty	Add link text or aria-label
http://twitter.com/reverbnation	(empty)	empty	Add link text or aria-label
http://www.youtube.com/user/ReverbNation…	(empty)	empty	Add link text or aria-label
http://instagram.com/reverbnation	(empty)	empty	Add link text or aria-label
http://www.pinterest.com/reverbnation/	(empty)	empty	Add link text or aria-label
http://blog.reverbnation.com/	Blog	new tab	Add '(opens in new tab)' to text
https://bandlabtechnologies.com/careers/	Careers	new tab	Add '(opens in new tab)' to text
http://blog.reverbnation.com/	Blog	new tab	Add '(opens in new tab)' to text
https://bandlabtechnologies.com/careers/	Careers	new tab	Add '(opens in new tab)' to text
	here	generic text	Replace with descriptive text
Before: here Suggested: Home page
#	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label

178 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a.centerer (#100 on page); a.button--play (#637 on page); a.button--actions (#638 on page); #; http://blog.reverbnation.com; http://facebook.com/reverbnation; http://twitter.com/reverbnation; http://www.youtube.com/user/ReverbNationVideos; http://instagram.com/reverbnation; http://www.pinterest.com/reverbnation/ (+8 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

("here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

http://blog.reverbnation.com/; https://bandlabtechnologies.com/careers/; http://blog.reverbnation.com/; https://bandlabtechnologies.com/careers/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #0d0d0e

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Lighthouse Accessibility Audits

Action

Score 55/100 — 9 failing, 12 passed

FIX

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
Join For Free `section.hero-lp > div.page-width > div.hero-lp--button > a.pricing-button-secondary`
Release Music `div.page-width > div.distro-cta--content > div.distro-cta--button > a.pricing-button-secondary`
Start Today `div.sullivan > section.start-selling-your-songs > div.start-selling-your-songs-container > a.pricing-button-secondary`
Artists `div.small-12 > ul.inline-list > li > a`
Industry `div.small-12 > ul.inline-list > li > a`
Fans `div.small-12 > ul.inline-list > li > a`
Venues `div.small-12 > ul.inline-list > li > a`

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ReverbNation Artist Membership Artist Development Artist Tools Policies `div.small-12 > div.row > div.small-12 > dl.accordion`

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Join For Free Log In Home Features Discover Crowd Picks Charts Opportunities Di… `div.ng-scope > aside.left > div.submenu-container > ul.side-nav--mobile`
Notifications All Notifications Messages All Messages `div.contain-to-grid > div.ng-scope > nav.right > ul.dropdown`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `span.submenu > span.ng-scope > span > li.menu-item`
Features `span.submenu > span.ng-scope > span > li.menu-item`
Discover `span.submenu > span.ng-scope > span > li.menu-item`
Crowd Picks `span.submenu > span.ng-scope > span > li.menu-item`
Charts `span.submenu > span.ng-scope > span > li.menu-item`
Opportunities `span.submenu > span.ng-scope > span > li.menu-item`
Distribution `span.submenu > span.ng-scope > span > li.menu-item`
Pricing `span.submenu > span.ng-scope > span > li.menu-item`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
ReverbNation `dl.accordion > dd.accordion-navigation > a.accordion--footer-links__header > h6.text-sullivanBlue`

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.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`
div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope `div.ng-scope > div.community-trending-chart-item > div.chart-item-card > img.ng-scope`

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.row > div.small-2 > div.left > a.centerer `div.row > div.small-2 > div.left > a.centerer`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play `div.community-trending-chart-item > div.chart-item-card > div.chart-item-card-buttons > a.button--play`
div.row > div.small-12 > div.mb0 > a.social-links__link `div.row > div.small-12 > div.mb0 > a.social-links__link`
div.row > div.small-12 > div.mb0 > a.social-links__link `div.row > div.small-12 > div.mb0 > a.social-links__link`
div.row > div.small-12 > div.mb0 > a.social-links__link `div.row > div.small-12 > div.mb0 > a.social-links__link`
div.row > div.small-12 > div.mb0 > a.social-links__link `div.row > div.small-12 > div.mb0 > a.social-links__link`
div.row > div.small-12 > div.mb0 > a.social-links__link `div.row > div.small-12 > div.mb0 > a.social-links__link`
div.row > div.small-12 > div.mb0 > a.social-links__link `div.row > div.small-12 > div.mb0 > a.social-links__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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Form elements have associated labels

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○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

○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.

○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.

○Image elements do not have `[alt]` attributes that are redundant text.

○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.

Heading Hierarchy

Action

24 headings, 2 skip(s)

REVIEW

24 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 Your music careeris serious business
H2 Distribute your music worldwide
H2 It's music distribution that works
H3 With ReverbNation, you get:
H2 Exclusive Opportunities
H2 Powerful Services
H2 Innovative A&R
H4 Sponsored Artists skipped
H6 I_o_S-A skipped
H6 ReverbNation
H6 Artist Membership
H6 Artist Development
H6 Artist Tools
H6 Policies
H6 ReverbNation
H6 Artist Membership
H6 Artist Development
H6 Artist Tools
H6 Policies
H2 ReverbNation Channels
H3 Select a Music Channel to Get Started
H2 Select Genres
H3 (empty)
H4 (empty)

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

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 ▾

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

Alt Text Quality

Action

2 of 28 images have issues

REVIEW

2 of 28 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

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

26 image(s) with good alt text

28 images 26 good alt text 2 missing

Issue	Count
missing	2 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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

1 control(s) without accessible label

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

Got: <select name="reverb_radio[genres][]" id="reverb_radio_genres_player_select">

1 control(s) rely on placeholder only

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

Got: <input type="text" id="mobile-search-input">

2 controls

0 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#mobile-search-input	text	(Search ReverbNation)	placeholder only
#reverb_radio_genres_player_select	select	(none)	none

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

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.

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: ReverbNation

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ReverbNation ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name ReverbNation Display Mode standalone Theme Color #0d0d0e Background Color #0d0d0e Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only

h1 Your music career

1.16:1

#000000

#141619

needs 3.0:1 (large text)

32px · mid-page · over background image/gradient

h1 is serious business

1.36:1

#000000

#212529

needs 3.0:1 (large text)

32px · mid-page

h2 Distribute your music

1.36:1

#000000

#212529

needs 3.0:1 (large text)

24px · bottom of viewport

h2 It's music distribution that

1.36:1

#000000

#212529

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Exclusive Opportunities

1.36:1

#000000

#212529

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Powerful Services

1.36:1

#000000

#212529

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Innovative A&R

1.36:1

#000000

#212529

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ReverbNation Channels

1.36:1

#000000

#212529

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Select Genres

1.36:1

#000000

#212529

needs 3.0:1 (large text)

24px · bottom of viewport

h3 With

1.36:1

#000000

#212529

needs 3.0:1 (large text)

19px · bottom of viewport

h3 , you get:

1.36:1

#000000

#212529

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Select a Music Channel to Get Started

1.36:1

#000000

#212529

needs 3.0:1 (large text)

19px · bottom of viewport

title ReverbNation : Artists First

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Join

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Join For Free

1.12:1

#000000

#0F1311

needs 4.5:1 (normal text)

16px · top of page (header area)

a Log In

3.43:1

#000000

#516663

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Features

1.30:1

#000000

#1C221E

needs 4.5:1 (normal text)

16px · above the fold

span Discover

1.48:1

#000000

#252D28

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Crowd Picks

3.25:1

#000000

#526259

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

4 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)

Element	Ratio	Required	FG	BG	Result
h1 Your music career	1.16:1	3.0:1	#000000	#141619	Fail
h1 is serious business	1.36:1	3.0:1	#000000	#212529	Fail
h2 Distribute your musi…	1.36:1	3.0:1	#000000	#212529	Fail
h2 It's music distribut…	1.36:1	3.0:1	#000000	#212529	Fail
h2 Exclusive Opportunit…	1.36:1	3.0:1	#000000	#212529	Fail
h2 Powerful Services	1.36:1	3.0:1	#000000	#212529	Fail
h2 Innovative A&R	1.36:1	3.0:1	#000000	#212529	Fail
h2 ReverbNation Channel…	1.36:1	3.0:1	#000000	#212529	Fail
h2 Select Genres	1.36:1	3.0:1	#000000	#212529	Fail
h3 With	1.36:1	3.0:1	#000000	#212529	Fail
h3 , you get:	1.36:1	3.0:1	#000000	#212529	Fail
h3 Select a Music Chann…	1.36:1	3.0:1	#000000	#212529	Fail
title ReverbNation : Artis…	1.00:1	4.5:1	#000000	#000000	Fail
a Join	1.00:1	4.5:1	#000000	#000000	Fail
a Join For Free	1.12:1	4.5:1	#000000	#0F1311	Fail
a Log In	3.43:1	4.5:1	#000000	#516663	Fail
span Home	5.04:1	4.5:1	#000000	#6A817C	Pass
span Features	1.30:1	4.5:1	#000000	#1C221E	Fail
span Discover	1.48:1	4.5:1	#000000	#252D28	Fail
span Crowd Picks	3.25:1	4.5:1	#000000	#526259	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.