Skip to content
https://metal-archives.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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

F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
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
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
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
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

C
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="searchString" id="searchQueryBox">; <select name="type">; <input type="text" name="loginUsername">; <input type="password" name="loginPassword">
4 controls
0 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#searchQueryBoxtext(none)none
typeselect(none)none
loginUsernametext(none)none
loginPasswordpassword(none)none

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

<input type="text" name="searchString" id="searchQueryBox">; <select name="type">; <input type="text" name="loginUsername">; <input type="password" name="loginPassword">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
title Home - Encyclopaedia Metallum: The Metal…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Metal Archives
2.25:1
#000000
on
#623D3C
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div loading...
2.31:1
#000000
on
#5A433F
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
label Search:
1.61:1
#000000
on
#4F2422
needs 4.5:1 (normal text)
16px · top of page (header area)
option Band name
1.06:1
#000000
on
#120807
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Music genre
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
option Themes
2.18:1
#000000
on
#484442
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Album title
3.89:1
#000000
on
#766764
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Song title
1.55:1
#000000
on
#302E2C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Label
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
option Artist
2.89:1
#000000
on
#5A5653
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option User profile
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
option Google
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Advanced search
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
button Submit
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Help
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Rules
1.08:1
#000000
on
#0D0D0C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Store
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Forum
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a FAQ
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page

8 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
title Home - Encyclopaedia…1.00:14.5:1
#000000
#000000
Fail
a Metal Archives2.25:14.5:1
#000000
#623D3C
Fail
div loading...2.31:14.5:1
#000000
#5A433F
Fail
label Search:1.61:14.5:1
#000000
#4F2422
Fail
option Band name1.06:14.5:1
#000000
#120807
Fail
option Music genre1.00:14.5:1
#000000
#000000
Fail
option Themes2.18:14.5:1
#000000
#484442
Fail
option Album title3.89:14.5:1
#000000
#766764
Fail
option Song title1.55:14.5:1
#000000
#302E2C
Fail
option Label1.00:14.5:1
#000000
#000000
Fail
option Artist2.89:14.5:1
#000000
#5A5653
Fail
option User profile1.00:14.5:1
#000000
#000000
Fail
option Google1.00:14.5:1
#000000
#000000
Fail
a Advanced search1.00:14.5:1
#000000
#000000
Fail
button Submit1.00:14.5:1
#000000
#000000
Fail
a Help1.00:14.5:1
#000000
#000000
Fail
a Rules1.08:14.5:1
#000000
#0D0D0C
Fail
a Store1.00:14.5:1
#000000
#000000
Fail
a Forum1.00:14.5:1
#000000
#000000
Fail
a FAQ1.00:14.5:1
#000000
#000000
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.

C
Lighthouse Accessibility Audits
Action
Score 73/100 — 9 failing, 24 passed
REVIEW
73

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
Latest additions: div#content_wrapper > div#latest > div#lastAdded > span.header
Latest updates: div#content_wrapper > div#latest > div#lastUpdated > span.header
Latest reviews: div#content_wrapper > div#latest > div#lastReviews > span.header
Upcoming albums div#content_wrapper > div#latest > div#upcomingAlbums > span.header

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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#news > div.motd > p.body > img div#news > div.motd > p.body > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search_box > form#search_form > div > input#searchQueryBox div#search_box > form#search_form > div > input#searchQueryBox
div#member_box > form#login_form > div > input div#member_box > form#login_form > div > input
div#member_box > form#login_form > div > input div#member_box > form#login_form > div > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Band name Music genre Themes Album title Song title Label Artist User profile G… div#search_box > form#search_form > div > select

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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search_box > form#search_form > div > input#searchQueryBox div#search_box > form#search_form > div > input#searchQueryBox
Band name Music genre Themes Album title Song title Label Artist User profile G… div#search_box > form#search_form > div > select
Advanced search div#search_box > form#search_form > div > a.float_left
Submit div#search_box > form#search_form > div > button.btn_submit

These are opportunities to improve keyboard navigation in your application.

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
alphabetical li > ul > li > a
country li > ul > li > a
genre li > ul > li > a
alphabetical li > ul > li > a
country li > ul > li > a
R.I.P. div#left_menu_box > ul.menu_style_3 > li > a
Random Band div#left_menu_box > ul.menu_style_3 > li > a
User rankings div#left_menu_box > ul.menu_style_3 > li > a
News archive div#left_menu_box > ul.menu_style_3 > li > a
Reports div#left_menu_box > ul.menu_style_3 > li > a
Wotans Macht tr > td > span.forceBreak > a
Ⱂⱆⱍⰵ Ⰿⱁⰼ tr > td > span.forceBreak > a
Profanomancer tr > td > span.forceBreak > a
Hurmos tr > td > span.forceBreak > a
H. Mortiz tr > td > span.forceBreak > a
Irrational Exuberants tr > td > span.forceBreak > a
Dragged into Obliteration tr > td > span.forceBreak > a
Doomantra tr > td > span.forceBreak > a
Cornucopia tr > td > span.forceBreak > a
Fuck White God tr > td > span.forceBreak > a
Vasodilator tr > td > span.forceBreak > a
Ganid tr > td > span.forceBreak > a
Indignance tr > td > span.forceBreak > a
Contaminate tr > td > span.forceBreak > a
Ghost Bath tbody > tr > td > a
Shot to Hell tbody > tr > td > a
Ghost Bath tr > td > span.forceBreak > a
Moonlover tbody > tr > td > a
At the Gates tr > td > span.forceBreak > a
With Fear I Kiss... tbody > tr > td > a
Warside tr > td > span.forceBreak > a
Cognitive Extinction tbody > tr > td > a
Oromet tr > td > span.forceBreak > a
The Sinking Isle tbody > tr > td > a
Necrony tr > td > span.forceBreak > a
Promo Tape '93-'94 tbody > tr > td > a
Коммунизм 2077 tr > td > span.forceBreak > a
Дестрой tbody > tr > td > a
Hail the Void tr > td > span.forceBreak > a
Memento Mori tbody > tr > td > a
Immortal tr > td > span.forceBreak > a
Battles in the North tbody > tr > td > a
Dead Again tbody > tr > td > a
Immortal tr > td > span.forceBreak > a
Diabolical... tbody > tr > td > a
Sawed Apart tr > td > span.forceBreak > a
Bone Harvester tbody > tr > td > a
Συντριμμια tr > td > span.forceBreak > a
Repulsive... tbody > tr > td > a
Doedsvangr tr > td > span.forceBreak > a
Within the Flesh tbody > tr > td > a
Black Abyss tr > td > span.forceBreak > a
The Overflowing... tbody > tr > td > a
Survive/Yourself tbody > tr > td > a
Dead Void tr > td > span.forceBreak > a
Volatile Forms tbody > tr > td > a
Hellripper tr > td > span.forceBreak > a
Coronach tbody > tr > td > a
Between Live and... tbody > tr > td > a
A Grotesque... tbody > tr > td > a
I Don't Care tbody > tr > td > a
Cardiomyotomy tr > td > span.forceBreak > a
Beautifying... tbody > tr > td > a
Deadzone tr > td > span.forceBreak > a
Deliberate tbody > tr > td > a
Extinction A.D. tr > td > span.forceBreak > a
Truth or... tbody > tr > td > a
Hans & Valter tr > td > span.forceBreak > a
The Prophecy tbody > tr > td > a
Without Dreams tr > td > span.forceBreak > a
Mana Diagram tr > td > span.forceBreak > a
Where Victims Lie tr > td > span.forceBreak > a
Coven of the Swamp tr > td > span.forceBreak > a
The Veil tbody > tr > td > a
A Figment of... tbody > tr > td > a
Falling Leaves tbody > tr > td > a
Ural tr > td > span.forceBreak > a
Anthropic Genetic... tbody > tr > td > a
Rahvira tr > td > span.forceBreak > a
In the Darkness... tbody > tr > td > a
Seum tr > td > span.forceBreak > a
Parking Life tbody > tr > td > a
Hagane tr > td > span.forceBreak > a
We Are the Knight tbody > tr > td > a
Bloody Falls tr > td > span.forceBreak > a
Mother, Your Son... tbody > tr > td > a
Vomit Forth tr > td > span.forceBreak > a
In the Name of... tbody > tr > td > a

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 html

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ghost Bath Ghost Bath Apr 22nd Black Label Society Shot to Hell Apr 22nd Gh… div.tabs > div.block > div.ui-tabs-panel-content > table
Inhale Blue Moment April 22nd Concerto Moon Between Live and... April 22nd … div.tabs > div.block > div.ui-tabs-panel-content > table
○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
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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
○Heading elements appear in a sequentially-descending order
○`<html>` element has a valid value for its `[lang]` attribute
○`<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
○Skip links are focusable.
○`<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.
A
Alt Text Quality
1 of 2 images have issues
PASS
1 of 2 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 image(s) with good alt text
2 images 1 good alt text 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

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

Send Feedback