Skip to content
https://arrl.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
41
GRADE
F
FIX
9
REVIEW
3
PASS
1
INFO
0
Checks
13
1 PASS 3 REVIEW 9 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
Alt Text Quality
Action
5 of 39 images have issues
FIX
5 of 39 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with filename as alt text
Info::
9 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
39 images 25 good alt text 9 decorative 1 generic 4 missing
IssueCount
missing4 image(s)
filename1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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-iiv6lr
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
Favicon & Branding
Action
5 icon(s) detected
FIX
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://arrl.org/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://arrl.org/manifest.json

Manifest contains invalid JSON.

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.

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.
D
Lighthouse Accessibility Audits
Action
Score 59/100 — 8 failing, 14 passed
FIX
59

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
Read All div#news > div.tabContent > p.more > a

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
LATEST NEWS div#ZONE-C > div#f-widget-294498 > div#news > h3.tab

These are opportunities to improve keyboard navigation in your application.

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#news2 > div.tabContent > div.section > img div#news2 > div.tabContent > div.section > img
div.tabContent > div.section > a > img div.tabContent > div.section > a > img
div#news2 > div.tabContent > div.section > img div#news2 > div.tabContent > div.section > img
div.section > center > a > img div.section > center > a > 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 > form#siteSearch > div > input#qq div#search > form#siteSearch > div > input#qq
div#search > form#fccSearch > div > input#qq2 div#search > form#fccSearch > div > input#qq2

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
Category Clubs Contests Exam Sessions Hamfest/Conventions Licensing Classes Mem… div#search > form#siteSearch > div > select#categ2

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#news2 > div.tabContent > div.section > a div#news2 > div.tabContent > div.section > a
div.tabContent > div.section > center > a div.tabContent > div.section > center > a
div#wrap2 > div#side2 > div.ad > a div#wrap2 > div#side2 > div.ad > a
div#wrap2 > div#side2 > div.ad > a div#wrap2 > div#side2 > div.ad > a
div#wrap2 > div#side2 > div.ad > a div#wrap2 > div#side2 > div.ad > a

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
Register Account cake:nocache > div#login > p > a.inline-dash
1 div.tabContent > div#f-gallery > p.nav > a#gallery-nav-1
2 div.tabContent > div#f-gallery > p.nav > a#gallery-nav-2
3 div.tabContent > div#f-gallery > p.nav > a#gallery-nav-3
4 div.tabContent > div#f-gallery > p.nav > a#gallery-nav-4
5 div.tabContent > div#f-gallery > p.nav > a#gallery-nav-5
News > tr.alt > td > strong > a
Hamfests & Conventions > tr.alt > td > strong > a
Media and Public Relations > tr.alt > td > strong > a
DXCC > tr.alt > td > strong > a
Contest Calendar > tr.alt > td > strong > a
Logbook of The World (LoTW) > tr.alt > td > strong > a
Award Programs > tr.alt > td > strong > a
Ham Radio > div.section > ul > li > a
Get Your License > div.section > ul > li > a
Practice Exams > div.section > ul > li > a
Find an Exam Site > div.section > ul > li > a
Resources for VEs > div.section > ul > li > a
Donate Now div.col > ul > li > a
Advertise With Us div.col > ul > li > a
Contact ARRL div.col > ul > li > a
Terms of Use / Privacy Policy div.col > ul > li > a
E-mail to a Friend div.col > ul > li > a
Sign Up for Our Newsletter div.col > ul > li > 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.

○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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●Input buttons have discernible text.
●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
●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.
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●All heading elements contain content.
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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>`.
○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.
○`<td>` elements in a large `<table>` have one or more table headers.
B
Heading Hierarchy
27 headings, 1 skip(s)
REVIEW
27 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 ARRL
  • H3 TI skipped
  • H3 ARRL Store
  • H3 Pass the Bill ARRL Grassroots Campaign
  • H3 Spectrum Defense 2026
  • H3 ARRL Dual-Band 2 m/70 cm Handheld Yagi Antenna
  • H3 TI
  • H3 ARRL Store
  • H3 LATEST NEWS
  • H2 (empty)
  • H2 th{text-align:left;}table{width:610px;margin-left:-10px;margin-top: -20px;margin-bottom: -20px;}td{line-height: 1.5;}td img{float: left;}td a{font-size: .85em;}
  • H3 MAGAZINES
  • H3 NEW TO ARRL
  • H3 MEMBER QUICK LINKS
  • H3 LICENSING LINKS
  • H3 IN THE ARRL STORE
  • H3 EXPLORE ARRL
  • H4 On The Air
  • H4 Licensing, Education & Training
  • H4 Membership
  • H4 Regulatory & Advocacy
  • H4 Public Service
  • H4 Technology
  • H4 Get Involved
  • H4 Publications & Online Store
  • H4 About ARRL
  • H1 ARRL duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
Form Accessibility
Action
5 of 5 controls have issues
REVIEW
5 of 5 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="data[Search][keywords]" id="qq">; <select name="data[Search][category]" id="categ2">; <input type="submit">; <input type="text" name="data[Search][terms]" id="qq2">; <input type="submit">
5 controls
0 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#qqtext(none)none
#categ2select(none)none
inputsubmit(none)none
#qq2text(none)none
inputsubmit(none)none

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

<input type="text" name="data[Search][keywords]" id="qq">; <select name="data[Search][category]" id="categ2">; <input type="submit">; <input type="text" name="data[Search][terms]" id="qq2">; <input type="submit">

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, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
title ARRL - Home
1.22:1
#000000
on
#001943
needs 4.5:1 (normal text)
16px · top of page (header area)
a ARRL
1.22:1
#000000
on
#001943
needs 4.5:1 (normal text)
16px · top of page (header area)
p Website Search
1.22:1
#000000
on
#001943
needs 4.5:1 (normal text)
16px · top of page (header area)
option Category
1.22:1
#000000
on
#001943
needs 4.5:1 (normal text)
16px · top of page (header area)
option Clubs
4.31:1
#000000
on
#63728B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Contests
2.18:1
#000000
on
#314567
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p Call Sign / Name Search
1.45:1
#000000
on
#21293D
needs 4.5:1 (normal text)
16px · mid-page
button Login
1.49:1
#000000
on
#232B40
needs 4.5:1 (normal text)
16px · mid-page

2 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
h3 ARRL Store21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pass the Bill ARRL G…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Spectrum Defense 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ARRL Dual-Band 2 m/7…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ARRL Store21.00:13.0:1
#000000
#FFFFFF
Pass
title ARRL - Home1.22:14.5:1
#000000
#001943
Fail
a ARRL1.22:14.5:1
#000000
#001943
Fail
p Website Search1.22:14.5:1
#000000
#001943
Fail
option Category1.22:14.5:1
#000000
#001943
Fail
option Clubs4.31:14.5:1
#000000
#63728B
Fail
option Contests2.18:14.5:1
#000000
#314567
Fail
option Exam Sessions7.96:14.5:1
#000000
#96A0B1
Pass
option Hamfest/Conventions21.00:14.5:1
#000000
#FFFFFF
Pass
option Licensing Classes17.02:14.5:1
#000000
#D8E9FF
Pass
option Member Directory19.26:14.5:1
#000000
#F3F5FB
Pass
option News17.93:14.5:1
#000000
#FBE9E9
Pass
option Special Events10.57:14.5:1
#000000
#D2B0AF
Pass
option ARECC Field Class/Ex…21.00:14.5:1
#000000
#FFFFFF
Pass
p Call Sign / Name Sea…1.45:14.5:1
#000000
#21293D
Fail
button Login1.49:14.5:1
#000000
#232B40
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.

A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /css/print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /css/print.css ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback