Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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.

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 ✗

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title AllMusic | Music Search, Recommendations, Videos and Reviews ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 32 passed

PASS

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
Learn more `div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label`

These are opportunities to improve the legibility of your content.

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
Submit search `div#searchNavContainer > div.searchContainer > form.site-search > input.siteSearchButton`
ZAYN `div.newReleaseItem > div.nrMeta > div.artist > a`
Konnakol `div.newReleaseItem > div.nrMeta > div.title > a`
They Might Be Giants `div.newReleaseItem > div.nrMeta > div.artist > a`
The World Is to Dig `div.newReleaseItem > div.nrMeta > div.title > a`
Snocaps `div.newReleaseItem > div.nrMeta > div.artist > a`
Snocaps `div.newReleaseItem > div.nrMeta > div.title > a`
Yaya Bey `div.newReleaseItem > div.nrMeta > div.artist > a`
Fidelity `div.newReleaseItem > div.nrMeta > div.title > a`
Julia `div.newReleaseItem > div.nrMeta > div.title > a`
Penny Arcade `div.newReleaseItem > div.nrMeta > div.artist > a`
Double Exposure `div.newReleaseItem > div.nrMeta > div.title > a`
Fellow Mortals `div.newReleaseItem > div.nrMeta > div.artist > a`
Stella's Birth-Day `div.newReleaseItem > div.nrMeta > div.title > a`
John Coltrane `div.newReleaseItem > div.nrMeta > div.artist > a`
Jessie Ware `div.moreReleasesItem > div.moreReleasesMeta > div.artist > a`
Superbloom `div.moreReleasesItem > div.moreReleasesMeta > div.title > a`
Adrian Younge `div.moreReleasesItem > div.moreReleasesMeta > div.artist > a`
Younge `div.moreReleasesItem > div.moreReleasesMeta > div.title > a`
Bitches' Blues `div.moreReleasesItem > div.moreReleasesMeta > div.title > a`
Winston Hightower `div.moreReleasesItem > div.moreReleasesMeta > div.artist > a`
100 Acre Wood `div.moreReleasesItem > div.moreReleasesMeta > div.title > a`
The Zombies `div.moreReleasesItem > div.moreReleasesMeta > div.artist > a`
Begin Here `div.moreReleasesItem > div.moreReleasesMeta > div.title > a`
Tiga `div.moreReleasesItem > div.moreReleasesMeta > div.artist > a`
Hotlife `div.moreReleasesItem > div.moreReleasesMeta > div.title > a`
Tirakat `div.homeECItem > div.homeECMeta > div.title > a`
Kim Gordon `div.homeECItem > div.homeECMeta > div.artist > a`
Play Me `div.homeECItem > div.homeECMeta > div.title > a`
Prostitute `div.homeECItem > div.homeECMeta > div.artist > a`
Sunya `div.homeECItem > div.homeECMeta > div.title > a`
Lotus Bridge `div.homeECItem > div.homeECMeta > div.title > a`
Jane Wiedlin `div.homeStaffPick > div.staffPickMeta > div.artist > a`
Jane Wiedlin `div.homeStaffPick > div.staffPickMeta > div.title > a`

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-*]` 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

●Input buttons have discernible text.

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

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○`[lang]` attributes have a valid value

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

○Identical links have the same purpose.

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