Skip to content
https://iii.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
33
GRADE
F
FIX
9
REVIEW
4
PASS
0
INFO
0
Checks
13
4 REVIEW 9 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 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
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 (missing!) CONTENTINFO footer

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
13 of 13 images have issues
FIX
13 of 13 images have issues
Critical::
13 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
13 image-in-link without alt text
An image inside a link with no alt creates an empty link.
13 images 13 missing
IssueCount
missing13 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-g987h0
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.

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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://iii.org/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://iii.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.

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.
C
Heading Hierarchy
Action
18 headings, 2 skip(s)
REVIEW
18 headings, 2 skip(s)
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Main
  • H3 Insurance: The Basics
  • H3 Research + Data
  • H3 Resource Center
  • H5 MEMBERSHIP skipped
  • H5 AMPLIFY
  • H5 EN ESPAÑOL
  • H5 Connect With Us
  • H5 Popular Media
  • H2 Our Promise
  • H1 New and Trending
  • H1 Insight + Analysis duplicate H1
  • H3 I.I.I. Glossary skipped
  • H1 Thought Leadership duplicate H1
  • H1 I.I.I. News Wire duplicate H1
  • H1 Events Calendar duplicate H1
  • H2 Sign In
  • H3 Don't Have an Account?Register Now

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

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

C
Form Accessibility
Action
3 of 5 controls have issues
REVIEW
3 of 5 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit" name="op" id="edit-submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="keys" id="keyword">
Info::
2 control(s) properly labeled
5 controls
2 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#edit-nametextEmail Address *for/id
#edit-passpasswordPassword *for/id
#keywordtext(Type to Search iii.org)placeholder only
#g-recaptcha-responsetextarea(none)none
#edit-submitsubmit(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit" name="op" id="edit-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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="keys" id="keyword">

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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only
h1 New and Trending
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Insight + Analysis
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Thought Leadership
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
32px · bottom of viewport
h1 I.I.I. News Wire
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Events Calendar
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Our Promise
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sign In
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
24px · bottom of viewport
h3 I.I.I. Glossary
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Don't Have an Account?
1.02:1
#000000
on
#020301
needs 3.0:1 (large text)
19px · bottom of viewport
title III | We are the trusted source of uniqu…
2.38:1
#000000
on
#1A4D79
needs 4.5:1 (normal text)
16px · top of page (header area)
div Home
2.38:1
#000000
on
#1A4D79
needs 4.5:1 (normal text)
16px · top of page (header area)
a Sign In
1.95:1
#000000
on
#054260
needs 4.5:1 (normal text)
16px · top of page (header area)
label Search iii.org
2.02:1
#000000
on
#054465
needs 4.5:1 (normal text)
16px · top of page (header area)
a Insurance: The Basics
1.95:1
#000000
on
#054260
needs 4.5:1 (normal text)
16px · above the fold
a About the Industry
2.02:1
#000000
on
#054464
needs 4.5:1 (normal text)
16px · above the fold
a Auto Insurance
2.02:1
#000000
on
#054464
needs 4.5:1 (normal text)
16px · above the fold
a Homeowners + Renters Insurance
1.95:1
#000000
on
#054260
needs 4.5:1 (normal text)
16px · above the fold
a Life Insurance
3.44:1
#000000
on
#64606F
needs 4.5:1 (normal text)
16px · above the fold
a Business Insurance
4.35:1
#000000
on
#727178
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 New and Trending1.02:13.0:1
#000000
#020301
Fail
h1 Insight + Analysis1.02:13.0:1
#000000
#020301
Fail
h1 Thought Leadership1.02:13.0:1
#000000
#020301
Fail
h1 I.I.I. News Wire1.02:13.0:1
#000000
#020301
Fail
h1 Events Calendar1.02:13.0:1
#000000
#020301
Fail
h2 Our Promise1.02:13.0:1
#000000
#020301
Fail
h2 Sign In1.02:13.0:1
#000000
#020301
Fail
h3 I.I.I. Glossary1.02:13.0:1
#000000
#020301
Fail
h3 Don't Have an Accoun…1.02:13.0:1
#000000
#020301
Fail
title III | We are the tru…2.38:14.5:1
#000000
#1A4D79
Fail
div Home2.38:14.5:1
#000000
#1A4D79
Fail
a Sign In1.95:14.5:1
#000000
#054260
Fail
label Search iii.org2.02:14.5:1
#000000
#054465
Fail
a Insurance: The Basic…1.95:14.5:1
#000000
#054260
Fail
a About the Industry2.02:14.5:1
#000000
#054464
Fail
a Auto Insurance2.02:14.5:1
#000000
#054464
Fail
a Homeowners + Renters…1.95:14.5:1
#000000
#054260
Fail
a Life Insurance3.44:14.5:1
#000000
#64606F
Fail
a Financial Planning5.09:14.5:1
#000000
#847C6F
Pass
a Business Insurance4.35:14.5:1
#000000
#727178
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 78/100 — 6 failing, 18 passed
REVIEW
78

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.hero-column > div.story > div.content > a.btn
HOMEOWNERS div.column > div.article > div.content > a.tag
AUTO div.column > div.article > div.content > a.tag
CRIME + FRAUD div.column > div.article > div.content > a.tag
DISASTERS + PREPAREDNESS div.column > div.article > div.content > a.tag
LIFE INSURANCE div.column > div.article > div.content > a.tag
ABOUT THE INDUSTRY div.column > div.article > div.content > a.tag
ABOUT THE INDUSTRY div.column > div.article > div.content > a.tag
INSURANCE INDUSTRY div.column > div.article > div.content > a.tag
SEE FULL GLOSSARY div.grid-wrapper > div.grid > div#widget-glossary > a.btn
Most Shared div.grid > div#widget-stats > div.main-tabs-nav > a
SEE MORE NEWS RELEASES div.wrapper > div.grid > div.content > a.btn
SEE MORE EVENTS div.wrapper > div.grid > div.content > a.btn

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
I.I.I. Glossary div.grid-wrapper > div.grid > div#widget-glossary > h3

These are opportunities to improve keyboard navigation in your application.

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.js html.js

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.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.column > div.article > a > img div.column > div.article > a > img
div.grid-wrapper > div.grid > a > img div.grid-wrapper > div.grid > a > img
div.grid-wrapper > div.grid > a > img div.grid-wrapper > div.grid > a > img
div.grid-wrapper > div.grid > a > img div.grid-wrapper > div.grid > a > img

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.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.wrapper > div.column > div.article > a div.wrapper > div.column > div.article > a
div.grid > div#widget-smedia > div.main-tabs-nav > a.active div.grid > div#widget-smedia > div.main-tabs-nav > a.active
div.wrapper > div.grid-wrapper > div.grid > a div.wrapper > div.grid-wrapper > div.grid > a
div.wrapper > div.grid-wrapper > div.grid > a div.wrapper > div.grid-wrapper > div.grid > a
div.wrapper > div.grid-wrapper > div.grid > a div.wrapper > div.grid-wrapper > div.grid > a
div.wrapper-962 > div.grid-wrapper > div.grid-962 > a#logo-footer div.wrapper-962 > div.grid-wrapper > div.grid-962 > a#logo-footer
div.menu-smedia > ul > li.smedia_tw > a div.menu-smedia > ul > li.smedia_tw > a
div.menu-smedia > ul > li.smedia_linkedin > a div.menu-smedia > ul > li.smedia_linkedin > a
div.menu-smedia > ul > li.smedia_fb > a div.menu-smedia > ul > li.smedia_fb > a
div.menu-smedia > ul > li.smedia_youtube > a div.menu-smedia > ul > li.smedia_youtube > 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

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.js html.js

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[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
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●Touch targets have sufficient size and spacing.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback