Skip to content
https://carnegieendowment.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 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-492t7w
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
2 icon(s) detected
FIX
2 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
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::
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
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
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 2 pass AA only
h1 The Impact of Ending U.S. International …
2.23:1
#000000
on
#464647
needs 3.0:1 (large text)
32px · mid-page
a Experts
4.20:1
#000000
on
#796D68
needs 4.5:1 (normal text)
16px · above the fold
span More
4.27:1
#000000
on
#7B6E67
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Democracy
4.48:1
#000000
on
#856F6B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Iran
2.07:1
#000000
on
#464040
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Topics & Regions
3.47:1
#000000
on
#606366
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Donate
1.30:1
#000000
on
#261F20
needs 4.5:1 (normal text)
16px · above the fold · 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
h1 The United States Ha…3.58:13.0:1
#000000
#676463
Pass
h1 The Impact of Ending…2.23:13.0:1
#000000
#464647
Fail
h1 Africa’s Digital I…19.11:13.0:1
#000000
#F4F4F5
Pass
h2 We deliver unbiased …19.11:13.0:1
#000000
#F4F4F5
Pass
h2 We generate actionab…19.11:13.0:1
#000000
#F4F4F5
Pass
h2 We use data to guide…19.11:13.0:1
#000000
#F4F4F5
Pass
h2 We focus on cross-cu…19.11:13.0:1
#000000
#F4F4F5
Pass
h2 We host events world…19.11:13.0:1
#000000
#F4F4F5
Pass
h2 Carnegie Explainer V…19.11:13.0:1
#000000
#F4F4F5
Pass
title Carnegie Endowment f…21.00:14.5:1
#000000
#FFFFFF
Pass
span Global Locations21.00:14.5:1
#000000
#FFFFFF
Pass
a Research17.26:14.5:1
#000000
#F2E7DE
Pass
a Emissary12.76:14.5:1
#000000
#E4C4A8
Pass
a About6.36:14.5:1
#000000
#9D8A7C
Pass
a Experts4.20:14.5:1
#000000
#796D68
Fail
span More4.27:14.5:1
#000000
#7B6E67
Fail
a Democracy4.48:14.5:1
#000000
#856F6B
Fail
a Iran2.07:14.5:1
#000000
#464040
Fail
span Topics & Regions3.47:14.5:1
#000000
#606366
Fail
a Donate1.30:14.5:1
#000000
#261F20
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 3 failing, 20 passed
REVIEW
86

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > ul.flex > li.desktop:hidden > button#radix-_R_lb9fivb_-trigger-mobile-menu div > ul.flex > li.desktop:hidden > button#radix-_R_lb9fivb_-trigger-mobile-menu
main.flex > section.flex > div.absolute > button.border-1 main.flex > section.flex > div.absolute > button.border-1
main.flex > section.flex > div.absolute > button.border-1 main.flex > section.flex > div.absolute > button.border-1

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 > ul.flex > li.text-blueDark/[0.66] > a.search-toggle div > ul.flex > li.text-blueDark/[0.66] > a.search-toggle
div > div.flex > div.relative > a div > div.flex > div.relative > a
div.flex-1 > div.flex > div.aspect-video > a div.flex-1 > div.flex > div.aspect-video > a
div.flex-1 > div.flex > div.aspect-video > a div.flex-1 > div.flex > div.aspect-video > a
div.flex-1 > div.flex > div.aspect-video > a div.flex-1 > div.flex > div.aspect-video > a
div#69a17fdc8c9b1fad463ec54c > div.flex > div.aspect-video > a div#69a17fdc8c9b1fad463ec54c > div.flex > div.aspect-video > a
div#696fb7473302e3e38a280bca > div.flex > div.aspect-video > a div#696fb7473302e3e38a280bca > div.flex > div.aspect-video > a
div#696675e382918029cd13a27e > div.flex > div.aspect-video > a div#696675e382918029cd13a27e > div.flex > div.aspect-video > a
div.order-3 > div.flex > div.flex > a.group div.order-3 > div.flex > div.flex > a.group
div.order-3 > div.flex > div.flex > a.group div.order-3 > div.flex > div.flex > a.group
div.order-3 > div.flex > div.flex > a.group div.order-3 > div.flex > div.flex > a.group
div.order-3 > div.flex > div.flex > a.group div.order-3 > div.flex > div.flex > a.group
div.order-3 > div.flex > div.flex > a.group div.order-3 > div.flex > div.flex > a.group

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.

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
Andrew Leber, div.flex > div.min-w-0 > p.truncate > span
Sam Worby div.flex > div.min-w-0 > p.truncate > span
Nikita Smagin div.flex > div.min-w-0 > p.truncate > span
ARTICLE article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
Zeinab Shuker div.flex > div.min-w-0 > p.truncate > span
Raluca Csernatoni div.flex > div.min-w-0 > p.truncate > span
ARTICLE article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
Paul Staniland div.flex > div.min-w-0 > p.truncate > span
Leonardo Martinez-Diaz div.flex > div.min-w-0 > p.truncate > span
ABOUT THE CARNEGIE ENDOWMENT div.grid > div.col-span-12 > article.bg-blanc > p.relative
DONATE TO SUPPORT CARNEGIE div.grid > div.col-span-12 > div.flex > a.font-mono
TRENDING TOPICS AND REGIONS div.grid > div.col-span-12 > article.bg-blanc > p.relative
REPORT article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
Christopher S. Chivvis, div.flex > div.min-w-0 > p.truncate > span
Senkai Hsia div.flex > div.min-w-0 > p.truncate > span
ARTICLE article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
Ariel (Eli) Levite, div.flex > div.min-w-0 > p.truncate > span
Toby Dalton div.flex > div.min-w-0 > p.truncate > span
PAPER article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
PAPER article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
READ THE ARTICLE div.mx-auto > div.row-50 > div.flex > a.font-mono
10:00 AM - 11:00 AM EDT div.flex > article.flex > div.flex > span.text-offNoir/60
Michael J. Bustamante, div.flex > div.min-w-0 > p.truncate > span
Ricardo Zuniga, div.flex > div.min-w-0 > p.truncate > span
Aaron David Miller div.flex > div.min-w-0 > p.truncate > span
Heribert Webinar div.flex > div.min-w-0 > p.truncate > span
T.V. Paul div.flex > div.min-w-0 > p.truncate > span
SEE THE COLLECTION div.row-100 > div#66be504457fc6ea2466e4f82 > div.flex > a.font-mono
VIDEO article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
Darcie Draudt-Véjares div.flex > div.min-w-0 > p.truncate > span
VIDEO article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
Charles Hooper div.flex > div.min-w-0 > p.truncate > span
VIDEO article.flex > div.mb-[0.75rem] > div.flex-col > span.px-[0.8em]
Charles Hooper div.flex > div.min-w-0 > p.truncate > span
SUBSCRIBE div.flex > div.mx-auto > div > button.font-mono

These are opportunities to improve the legibility of your content.

○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
●`[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
●`<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
●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
●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
○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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV 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

A
Heading Hierarchy
9 headings
PASS
9 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 The United States Has an Internal Displacement Problem
  • H1 The Impact of Ending U.S. International Media Assistance duplicate H1
  • H1 Africa’s Digital Infrastructure Imperative duplicate H1
  • H2 We deliver unbiased research to decisionmakers who help set the global policy agenda
  • H2 We generate actionable policy ideas to help forge a safer world
  • H2 We use data to guide our understanding of complex issues
  • H2 We focus on cross-cutting policy issues and key regions
  • H2 We host events worldwide to unpack the most difficult global challenges
  • H2 Carnegie Explainer Videos

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

A
Alt Text Quality
All 44 images OK
PASS
All 44 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
26 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
44 images 15 good alt text 26 decorative
IssueCount
too long3 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 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-100000">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

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

Send Feedback