Skip to content
https://qrz.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-otow0v
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
Theme color only
FIX
Theme color only
Info::
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: #99ccff
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 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.

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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
B
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV 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

B
Heading Hierarchy
36 headings
REVIEW
36 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H5 Ham Life with an Amateur
  • H2 Interview
  • H2 QRZ News
  • H2 QRZ News
  • H2 Video
  • H2 QRZ News
  • H2 Magazine
  • H2 QRZ News
  • H2 Interview
  • H2 QRZ News
  • H2 QRZ News
  • H2 Announcement
  • H2 Announcement
  • H2 QRZ News
  • H2 Special Event
  • H2 QRZ News
  • H2 QRZ News
  • H2 Video
  • H2 Video
  • H2 Special Event
  • H2 Video
  • H2 QRZ News
  • H2 Special Event
  • H2 QRZ News
  • H2 Magazine
  • H2 QRZ News
  • H2 QRZ News
  • H2 QRZ News
  • H2 QRZ News
  • H2 QRZ News
  • H2 Special Event
  • H2 QRZ News
  • H2 QRZ News
  • H2 Interview
  • H2 Announcement
  • H2 QRZ News

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="mode" id="mode">; <input type="submit" id="tsubmit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search">
3 controls
0 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
inputsearch(Search...)placeholder only
#modeselect(none)none
#tsubmitsubmit(none)none

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

<select name="mode" id="mode">; <input type="submit" id="tsubmit">

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.

<input type="search">

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

C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: QRZ.com Callsign Database
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name QRZ.com Callsign Database ✓192×192 icon ✗512×512 icon ✗Start URL /?utm=homescreen ✓Display Mode standalone ✓
Name QRZ.com Callsign Database Display Mode standalone Theme Color #99ccff Icons 3 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA 1 pass AA only
title Callsign Database - QRZ.com
1.55:1
#000000
on
#312E27
needs 4.5:1 (normal text)
16px · top of page (header area)
a help/register
2.94:1
#000000
on
#6B5433
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
option by County
1.38:1
#000000
on
#52040D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option by Grid
1.04:1
#000000
on
#110304
needs 4.5:1 (normal text)
16px · above the fold
li Database
3.71:1
#000000
on
#676767
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a QSL ListMaker
3.45:1
#000000
on
#626263
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Ham Club Database
2.89:1
#000000
on
#6D513D
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

5 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 Callsign Database - …1.55:14.5:1
#000000
#312E27
Fail
a login11.46:14.5:1
#000000
#DCBB80
Pass
a help/register2.94:14.5:1
#000000
#6B5433
Fail
li 23:37:12 UTC 22 Apr …18.93:14.5:1
#000000
#F3F3F3
Pass
div Recent Callsign Look…11.71:14.5:1
#000000
#95C6F8
Pass
div by Callsign17.14:14.5:1
#000000
#E8E8E8
Pass
option by Callsign21.00:14.5:1
#000000
#FFFFFF
Pass
option by Name/Addr21.00:14.5:1
#000000
#FFFFFF
Pass
option in Biography5.78:14.5:1
#000000
#928380
Pass
option by County1.38:14.5:1
#000000
#52040D
Fail
option by Grid1.04:14.5:1
#000000
#110304
Fail
li Database3.71:14.5:1
#000000
#676767
Fail
a Advanced Search21.00:14.5:1
#000000
#FFFFFF
Pass
b Current Hot Callsign…21.00:13.0:1
#000000
#FFFFFF
Pass
a XML Logbook Data19.26:14.5:1
#000000
#F5F5F5
Pass
a QSL ListMaker3.45:14.5:1
#000000
#626263
Fail
a DX Spotting Network14.41:14.5:1
#000000
#DFD5BF
Pass
a Ham Club Database2.89:14.5:1
#000000
#6D513D
Fail
a QSL Corner9.19:14.5:1
#000000
#B5B01A
Pass
a Top Web Contacts17.76:14.5:1
#000000
#ECECEB
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 84/100 — 5 failing, 23 passed
REVIEW
84

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
login nav.qrzMenuNav > ul.tray > li > a
help/register nav.qrzMenuNav > ul.tray > li > a
LU1DXM li.featured-ham > div.homepage-box-content > div.callsign-positioner > a.fb
Click here for story. div.contentNodeBlock > div.articleContent > p > a
Click here. div.contentNodeBlock > div.articleContent > p > a
Click Here And Tell Us Your Answer div.qrzmain > ul.newsgrid > li.homepage-box > div.trivia-answer

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
Ham Life with an Amateur div.block > div.contentNodeBlock > div.articleContent > h5

These are opportunities to improve keyboard navigation in your application.

Tables and lists

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
Featured Member LU1DXM Solar-Terrestrial Data Provided by N0NBH Interview Insi… body.show_ads > div.container-fluid > div.qrzmain > ul.newsgrid

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

Names and labels

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
by Callsign by Name/Addr in Biography by County by Grid form#topcall > div.magic > div.modeWrapper > select#mode

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
Provided by N0NBH li.homepage-box > div.homepage-box-content > div.solar-pane > a.link

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●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
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○Buttons have an accessible name
○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
○`<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
○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.
○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.
A+
Alt Text Quality
All 95 images OK
PASS
All 95 images OK
Info::
95 image(s) with good alt text
95 images 95 good alt text
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback