Accessibility

F

Heading Hierarchy

Action

49 headings, 8 skip(s)

FIX

49 headings, 8 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

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: H2 → H4 (missing H3)

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

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: H2 → H4 (missing H3)

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

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: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

H1 The music platform empowering artists.
H3 Unlock all music for unlimited streaming skipped
H2 TRENDING SONGS
H4 BNXN & Sarz skipped
H4 Plutomania & Shallipopi
H4 Muyeez, Zerrydl, Ayo Maff, Famous Pluto
H4 King Promise, Mr Eazi
H4 Modola, Bhadboi OML
H2 TRENDING ALBUMS
H4 King Promise skipped
H4 Wizkid & Asake
H4 Aquafaba
H4 Danny Brown
H4 Seyi Vibez
H2 TOP AUDIOMACK PLAYLISTS
H4 Verified: Hip-Hop skipped
H4 Verified: Afrosounds
H4 Verified: R&B
H4 Verified: Pop
H4 Verified: Electronic
H2 TOP SONGS IN nl
H4 Evado skipped
H4 Wizkid & Asake
H4 Asake & DJ Snake
H4 Muyeez, Zerrydl, Ayo Maff, Famous Pluto
H4 BNXN & Sarz
H2 TOP ALBUMS IN nl
H4 Evado skipped
H4 Wizkid & Asake
H4 Seyi Vibez
H4 Black Sherif
H4 Asake
H2 AUDIOMACK WORLD
H4 Watch BigXthaPlug & 600 Ent. Perform Live for ‘Fine Tuned’ skipped
H4 You Need To Hear: Trim
H2 RECENTLY ADDED
H4 BHADBOI JNR skipped
H4 Will Kill
H4 XXXRAZAPHA
H4 T1HUNNXD
H4 Wasiu kayode sideeq babanwaka
H2 Do Not Sell or Share My Personal Data
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H5 Functional Cookies
H4 Opt Out of Sale of Sharing/Targeted Advertising
H5 Performance Cookies
H5 Targeting Cookies
H3 Cookie List

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-emee85

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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

7 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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

15 landmarks

REVIEW

15 landmarks

<main> landmark present

7 <nav> landmark(s) found

7 of 7 <nav> elements are unlabeled

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

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

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

Link & Button Quality

Action

11 issue(s) across 132 links and 34 buttons

REVIEW

11 issue(s) across 132 links and 34 buttons

23 link(s) open in new tab without warning

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

Got: https://guide.audiomack.com; https://audiomack.studio/; https://creators.audiomack.com/upload; https://twitter.com/audiomack; https://www.facebook.com/audiomack; https://www.instagram.com/audiomack; https://www.youtube.com/@audiomackworld; https://www.tiktok.com/@audiomack?lang=en; https://twitch.tv/audiomack; /about (+13 more)

11 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button[data-testid="sidebar-opener"]; button[data-testid="sidebar-close-icon-btn"]; button.Carousel-button (#355 on page); button.Carousel-button (#425 on page); button.Carousel-button (#483 on page); button.Carousel-button (#552 on page); button.Carousel-button (#627 on page); button.Carousel-button (#652 on page); button.Carousel-button (#721 on page); button (#958 on page) (+1 more)

109 link(s) with descriptive text

132 links

0 empty

0 generic text

23 new tab

11 empty buttons

Element	Text	Issue	Suggested Fix
https://guide.audiomack.com	Artist Guide	new tab	Add '(opens in new tab)' to text
https://audiomack.studio/	Audiomack Studios	new tab	Add '(opens in new tab)' to text
https://creators.audiomack.com/upload	Upload	new tab	Add '(opens in new tab)' to text
https://twitter.com/audiomack	Follow us on twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/audiomack	Follow us on facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/audiomack	Follow us on instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@audiomackworld	Follow us on youtube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@audiomack?lang=e…	Follow us on tiktok	new tab	Add '(opens in new tab)' to text
https://twitch.tv/audiomack	Follow us on twitch	new tab	Add '(opens in new tab)' to text
/about	About	new tab	Add '(opens in new tab)' to text
https://audiomack.zendesk.com/	Help	new tab	Add '(opens in new tab)' to text
https://creators.audiomack.com/contact-u…	Business inquiries	new tab	Add '(opens in new tab)' to text
https://styleguide.audiomack.com/	Styleguide	new tab	Add '(opens in new tab)' to text
https://creators.audiomack.com/creator-a…	Creator App	new tab	Add '(opens in new tab)' to text
https://amack.it/creator-app-embed	Download mobile app	new tab	Add '(opens in new tab)' to text
https://audiomack.com	Download mobile app	new tab	Add '(opens in new tab)' to text
https://creators.audiomack.com/about/leg…	Legal & DMCA	new tab	Add '(opens in new tab)' to text
/about/privacy-policy	Privacy Policy	new tab	Add '(opens in new tab)' to text
/about/terms-of-service	Terms of Service	new tab	Add '(opens in new tab)' to text
https://creators.audiomack.com/responsib…	Report a Vulnerability	new tab	Add '(opens in new tab)' to text
/about/privacy-policy#accessing-updating	Do not sell my info	new tab	Add '(opens in new tab)' to text
https://cookiepedia.co.uk/giving-consent…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

132 links and buttons have descriptive text

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

https://guide.audiomack.com; https://audiomack.studio/; https://creators.audiomack.com/upload; https://twitter.com/audiomack; https://www.facebook.com/audiomack; https://www.instagram.com/audiomack; https://www.youtube.com/@audiomackworld; https://www.tiktok.com/@audiomack?lang=en; https://twitch.tv/audiomack; /about (+13 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button[data-testid="sidebar-opener"]; button[data-testid="sidebar-close-icon-btn"]; button.Carousel-button (#355 on page); button.Carousel-button (#425 on page); button.Carousel-button (#483 on page); button.Carousel-button (#552 on page); button.Carousel-button (#627 on page); button.Carousel-button (#652 on page); button.Carousel-button (#721 on page); button (#958 on page) (+1 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

B

Favicon & Branding

7 icon(s) detected

REVIEW

7 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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA

h2 TRENDING SONGS

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 TRENDING ALBUMS

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 TOP AUDIOMACK PLAYLISTS

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 TOP SONGS IN nl

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 TOP ALBUMS IN nl

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AUDIOMACK WORLD

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 RECENTLY ADDED

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Do Not Sell or Share My Personal Data

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Unlock all music for unlimited streaming

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Manage Consent Preferences

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cookie List

1.36:1

#000000

on

#1F252D

needs 3.0:1 (large text)

19px · bottom of viewport

title Audiomack - Music platform empowering ar…

1.27:1

#000000

on

#191F27

needs 4.5:1 (normal text)

16px · top of page (header area)

a Get Plus

1.27:1

#000000

on

#191F27

needs 4.5:1 (normal text)

16px · top of page (header area)

a Discover

1.27:1

#000000

on

#191F27

needs 4.5:1 (normal text)

16px · top of page (header area)

a Trending Songs

1.27:1

#000000

on

#191F27

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The music platform	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 TRENDING SONGS	1.36:1	3.0:1	#000000	#1F252D	Fail
h2 TRENDING ALBUMS	1.36:1	3.0:1	#000000	#1F252D	Fail
h2 TOP AUDIOMACK PLAYLI…	1.36:1	3.0:1	#000000	#1F252D	Fail
h2 TOP SONGS IN nl	1.36:1	3.0:1	#000000	#1F252D	Fail
h2 TOP ALBUMS IN nl	1.36:1	3.0:1	#000000	#1F252D	Fail
h2 AUDIOMACK WORLD	1.36:1	3.0:1	#000000	#1F252D	Fail
h2 RECENTLY ADDED	1.36:1	3.0:1	#000000	#1F252D	Fail
h2 Do Not Sell or Share…	1.36:1	3.0:1	#000000	#1F252D	Fail
h3 Unlock all music for…	1.36:1	3.0:1	#000000	#1F252D	Fail
h3 Manage Consent Prefe…	1.36:1	3.0:1	#000000	#1F252D	Fail
h3 Cookie List	1.36:1	3.0:1	#000000	#1F252D	Fail
title Audiomack - Music pl…	1.27:1	4.5:1	#000000	#191F27	Fail
a Get Plus	1.27:1	4.5:1	#000000	#191F27	Fail
a Discover	1.27:1	4.5:1	#000000	#191F27	Fail
a Trending Songs	1.27:1	4.5:1	#000000	#191F27	Fail
a Trending Albums	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Top Songs	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Top Albums	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Recently Added	21.00:1	4.5: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.

B

Lighthouse Accessibility Audits

Score 85/100 — 5 failing, 24 passed

REVIEW

85

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.rootLayout > div.web-to-app_WebToAppContainer__uagRx > div.web-to-app_WebToAppModule__7_Mg1 > button.web-to-app_WebToAppModule__Close__ybsLy `div.rootLayout > div.web-to-app_WebToAppContainer__uagRx > div.web-to-app_WebToAppModule__7_Mg1 > button.web-to-app_WebToAppModule__Close__ybsLy`
body.__variable_4d0e85 > div.rootLayout > div.LayoutWithSidebar > button.Sidebar-btnOpen `body.__variable_4d0e85 > div.rootLayout > div.LayoutWithSidebar > button.Sidebar-btnOpen`
aside.Sidebar > div.Sidebar-absolute > div.Sidebar-btnClose-icon-container > button.Sidebar-btnClose-icon `aside.Sidebar > div.Sidebar-absolute > div.Sidebar-btnClose-icon-container > button.Sidebar-btnClose-icon`

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.

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
It’s better in the app `div.rootLayout > div.web-to-app_WebToAppContainer__uagRx > div.web-to-app_WebToAppModule__7_Mg1 > h4.heading_Heading__L5e_i`
Unlock all music for unlimited streaming `div.Sidebar-absolute > div.SidebarAd > div.SidebarAd-content > h3.SidebarAd-text-bold`
BNXN & Sarz `div.Carousel > div.Carousel-container > article.MusicCard > h4.MusicCard-artist`
King Promise `div.Carousel > div.Carousel-container > article.MusicCard > h4.MusicCard-artist`
Verified: Hip-Hop `div.Carousel > div.Carousel-container > article.PlaylistCard > h4.PlaylistCard-title`
Evado `div.Carousel > div.Carousel-container > article.MusicCard > h4.MusicCard-artist`
Evado `div.Carousel > div.Carousel-container > article.MusicCard > h4.MusicCard-artist`
Watch BigXthaPlug & 600 Ent. Perform Live for ‘Fine Tuned’ `div.Carousel > div.Carousel-container > div.ArticleCard > h4.ArticleCard-title`
BHADBOI JNR `div.Carousel > div.Carousel-container > article.MusicCard > h4.MusicCard-artist`

These are opportunities to improve keyboard navigation in your application.

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`

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
Still Hungry `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-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
Back Outside `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
420 `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
See What We've Done `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
REAL, Vol. 1 `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
By Now `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
Jogodo `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
Promise land `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
REAL, Vol. 1 `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
Movie(intro) `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
Still Hungry `div.Carousel-container > article.MusicCard > div.MusicCard-title > a.MusicCard-title-link`
Cookies Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`

○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

●Image elements have `[alt]` attributes

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Form elements have associated labels

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

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

Alt Text Quality

All 36 images OK

PASS

All 36 images OK

36 image(s) with good alt text

36 images 36 good alt text

All images have appropriate alt text.

A

Form Accessibility

1 of 7 controls have issues

PASS

1 of 7 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text">

6 control(s) properly labeled

7 controls

6 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-OSSTA_BG	checkbox	Opt Out of Sale of Sharing/Targeted Advertising	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
input	text	(Search for artists, songs, albums!)	placeholder only

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

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Audiomack

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Audiomack ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Audiomack Display Mode standalone Theme Color #0D0D0D Background Color #0D0D0D Icons 2 icon(s)