Skip to content
https://heritage.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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
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
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) 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!) MAIN CONTENTINFO footer

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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Lighthouse Accessibility Audits
Action
Score 76/100 — 7 failing, 27 passed
REVIEW
76

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.lbs-block-bottom-gap > div.slider-component__wrapper > ul.slick-dots > li#slick-slide03 div.lbs-block-bottom-gap > div.slider-component__wrapper > ul.slick-dots > li#slick-slide03

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.layout__region > div.lbs-block-bottom-gap > div.slider-component__wrapper > ul.slick-dots div.layout__region > div.lbs-block-bottom-gap > div.slider-component__wrapper > ul.slick-dots

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Parental Rights Initiative Robust families are key to restoring America. Ensur… div.lbs-block-bottom-gap > div.slider-component__wrapper > div.slick-list > div.slick-track

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main content div#main > main#content > section.section > a#main-content

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
ASSESS THE READINESS OF AMERICA’S MILITARY div.lbs-block-bottom-gap > div.title-link-img-desc__content > div.title-link-img-desc__link > a
READ MORE div.book-promo__inner > div.book-promo__content > div.book-promo__link > a
Charles Stimson div.layout__region > div.single-featured-component > div.single-featured-component__wrapper > div.single-featured-component__author
Victoria Coates div.layout__region > div.one-plus-two-featured-content > div.one-plus-two-featured-content__conntent-wrap > div.one-plus-two-featured-content__author
Simon Hankinson div.layout__region > div.one-plus-two-featured-content > div.one-plus-two-featured-content__conntent-wrap > div.one-plus-two-featured-content__author
Jonathan Butcher, Madison Marino Doan div.layout__region > div.one-plus-two-featured-content > div.one-plus-two-featured-content__conntent-wrap > div.one-plus-two-featured-content__author
Kevin D. Roberts, PhD div.card-commentary-report > a > div.card-commentary-report__commentary-wrapper > div.node-author-name
Roger Severino, Jay W. Richards, PhD, Emma Waters, Delano Squires, Rachel Sheff… div.card-commentary-report > a > div.card-commentary-report__reports-wrapper > div.node-author-name
LEARN MORE div.slider-component-wrapper > div.slider-component__content > div.slider-component__content-link-wrap > a
ALL EVENTS div.paragraph > div.card-component > div.card-component__content-link-wrap > a.card-component__content-link
ALL PODCASTS div.paragraph > div.card-component > div.card-component__content-link-wrap > a.card-component__content-link
APPLY BY JUNE 7TH div.paragraph > div.card-component > div.card-component__content-link-wrap > a.card-component__content-link
div.mktoFormRow > div.mktoFieldDescriptor > div.mktoFieldWrap > input#Email div.mktoFormRow > div.mktoFieldDescriptor > div.mktoFieldWrap > input#Email

These are opportunities to improve the legibility of your content.

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
body.path-frontpage > div.dialog-off-canvas-main-canvas > img body.path-frontpage > div.dialog-off-canvas-main-canvas > 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.lbs-block-bottom-gap-50desktop > div.highlight-cards__wrap > div.highlight-cards__content > a.highlight-cards__content-link div.lbs-block-bottom-gap-50desktop > div.highlight-cards__wrap > div.highlight-cards__content > a.highlight-cards__content-link
div.lbs-block-bottom-gap-50desktop > div.highlight-cards__wrap > div.highlight-cards__content > a.highlight-cards__content-link div.lbs-block-bottom-gap-50desktop > div.highlight-cards__wrap > div.highlight-cards__content > a.highlight-cards__content-link

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.

○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA toggle fields have accessible names
●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.
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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 `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
○`<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
○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
○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+
Heading Hierarchy
3 headings
PASS
3 headings
Info::
Single H1 present
  • H1 heritage.org
  • H2 Performing security verification
  • H2 Verification successful. Waiting for heritage.org to respond
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
10 text elements analyzed, 0 fail WCAG AA
PASS

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

10 pass
Show all checked elements (10)
ElementRatioRequiredFGBGResult
h1 heritage.org21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Performing security …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Verification success…21.00:13.0:1
#000000
#FFFFFF
Pass
title Just a moment...21.00:14.5:1
#000000
#FFFFFF
Pass
p This website uses a …21.00:14.5:1
#000000
#FFFFFF
Pass
div Ray ID:21.00:14.5:1
#000000
#FFFFFF
Pass
code 9effeacaf84aed8521.00:14.5:1
#000000
#FFFFFF
Pass
span Performance and Secu…21.00:14.5:1
#000000
#FFFFFF
Pass
a Cloudflare21.00:14.5:1
#000000
#FFFFFF
Pass
a Privacy21.00:14.5:1
#000000
#FFFFFF
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.

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

Send Feedback