Skip to content
https://winamp.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No contentinfo (footer) landmark
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 MAIN CONTENTINFO (missing!)

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
6 headings, 1 skip(s)
REVIEW
6 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.
  • H3 Winamp
  • H2 Winamp builds tools that empower artists to manage their music and revenue, while delivering a player that offers a seamless listening experience.
  • H3 Winamp Player
  • H3 Winampfor Creators
  • H6 Learn more about the music industry skipped
  • H6 Have question for the llamas or some feedback

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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 87/100 — 5 failing, 23 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.

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
OK! div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_acceptAll
Llama Group div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text
For Creators div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text
Learn div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text
Press div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text
Jobs div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text
Contact div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text
Legal Notice div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text
Privacy Policy div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text
General Terms of Use div.framer-E1snn > div.framer-i08v4m > p.framer-text > a.framer-text

These are opportunities to improve the legibility of your content.

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
Winamp div.framer-o9em2x > div.framer-1oq2iow > div.framer-xmpct0 > h3.framer-text
Learn more about the music industry div.framer-5rvl7t-container > a.framer-Qe1R9 > div.framer-1ayopk6 > h6.framer-text

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.framer-jlglih > div.framer-1uhkces > div.framer-cb3o2v-container > a.framer-LtIjF div.framer-jlglih > div.framer-1uhkces > div.framer-cb3o2v-container > a.framer-LtIjF
div.ssr-variant > div.framer-orz7o5-container > div.framer-rjFAI > a.framer-1heytf6 div.ssr-variant > div.framer-orz7o5-container > div.framer-rjFAI > a.framer-1heytf6
div.ssr-variant > div.framer-trks2g-container > div.framer-rjFAI > a.framer-ux8roz div.ssr-variant > div.framer-trks2g-container > div.framer-rjFAI > a.framer-ux8roz
div.ssr-variant > div.framer-1j3brgu-container > div.framer-rjFAI > a.framer-1mbg2q7 div.ssr-variant > div.framer-1j3brgu-container > div.framer-rjFAI > a.framer-1mbg2q7
div.ssr-variant > div.framer-1j3brgu-container > div.framer-rjFAI > a.framer-ckmvvb div.ssr-variant > div.framer-1j3brgu-container > div.framer-rjFAI > a.framer-ckmvvb
div.framer-1knlox0 > div.framer-1bowwdt > div.framer-drlte0-container > a.framer-gm5uf div.framer-1knlox0 > div.framer-1bowwdt > div.framer-drlte0-container > a.framer-gm5uf
div.framer-1knlox0 > div.framer-1bowwdt > div.framer-17af7i2-container > a.framer-gm5uf div.framer-1knlox0 > div.framer-1bowwdt > div.framer-17af7i2-container > a.framer-gm5uf
div.framer-1knlox0 > div.framer-1bowwdt > div.framer-2fzlcw-container > a.framer-gm5uf div.framer-1knlox0 > div.framer-1bowwdt > div.framer-2fzlcw-container > a.framer-gm5uf
div.framer-1knlox0 > div.framer-1bowwdt > div.framer-1deyjea-container > a.framer-gm5uf div.framer-1knlox0 > div.framer-1bowwdt > div.framer-1deyjea-container > a.framer-gm5uf
div.framer-1knlox0 > div.framer-1bowwdt > div.framer-yund75-container > a.framer-gm5uf div.framer-1knlox0 > div.framer-1bowwdt > div.framer-yund75-container > a.framer-gm5uf
div.framer-1knlox0 > div.framer-1bowwdt > div.framer-sml9pd-container > a.framer-gm5uf div.framer-1knlox0 > div.framer-1bowwdt > div.framer-sml9pd-container > a.framer-gm5uf
div.framer-1lm2bxp > div.framer-1va5a83-container > div.framer-rjFAI > a.framer-1heytf6 div.framer-1lm2bxp > div.framer-1va5a83-container > div.framer-rjFAI > a.framer-1heytf6
div.framer-1lm2bxp > div.framer-1t0vh9f-container > div.framer-rjFAI > a.framer-ux8roz div.framer-1lm2bxp > div.framer-1t0vh9f-container > div.framer-rjFAI > a.framer-ux8roz
div.framer-1lm2bxp > div.framer-1q6gvj9-container > div.framer-rjFAI > a.framer-1mbg2q7 div.framer-1lm2bxp > div.framer-1q6gvj9-container > div.framer-rjFAI > a.framer-1mbg2q7
div.framer-1lm2bxp > div.framer-1q6gvj9-container > div.framer-rjFAI > a.framer-ckmvvb div.framer-1lm2bxp > div.framer-1q6gvj9-container > div.framer-rjFAI > a.framer-ckmvvb

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
Data Sharing with Google div.sc-hBEYId > ul > li > a
Audience Measurement & Analytics div.sc-hBEYId > ul > li > a

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
No, thanks div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_dismiss
Let me choose div.sc-fHYyUA > div.sc-ezredP > div.sc-pGacB > button#axeptio_btn_configure
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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 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
○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.
○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
○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 11 images OK
PASS
All 11 images OK
Info::
11 decorative image(s) correctly marked
11 images 11 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Winamp builds tools …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 seamless listening e…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Winamp21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Winamp Player21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Winamp21.00:13.0:1
#000000
#FFFFFF
Pass
h3 for Creators21.00:13.0:1
#000000
#FFFFFF
Pass
title Winamp21.00:14.5:1
#000000
#FFFFFF
Pass
p Scroll21.00:14.5:1
#000000
#FFFFFF
Pass
p down21.00:14.5:1
#000000
#FFFFFF
Pass
p Winamp aggregates th…21.00:14.5:1
#000000
#FFFFFF
Pass
p Learn more21.00:14.5:1
#000000
#FFFFFF
Pass
p and for the nostalgi…21.00:14.5:1
#000000
#FFFFFF
Pass
p Winamp for Creators …21.00:14.5:1
#000000
#FFFFFF
Pass
p Get started21.00:14.5:1
#000000
#FFFFFF
Pass
p Learn more21.00:14.5:1
#000000
#FFFFFF
Pass
p © 2025 Winamp21.00:14.5:1
#000000
#FFFFFF
Pass
p Helpful links21.00:14.5:1
#000000
#FFFFFF
Pass
a Llama Group21.00:14.5:1
#000000
#FFFFFF
Pass
a For Creators21.00:14.5:1
#000000
#FFFFFF
Pass
a Learn21.00:14.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.

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

Send Feedback