Skip to content
https://nber.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title NBER: National Bureau of Economic Research ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA 8 pass AA only
title National Bureau of Economic Research | N…
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · top of page (header area)
a Subscribe
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · top of page (header area)
a Media
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · top of page (header area)
a Open Calls
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · above the fold
span Login
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · above the fold
span Login
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · above the fold
label Search
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · above the fold
button Research
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · above the fold
a EXPLORE Research
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · above the fold
span Findings
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · above the fold
a Working Papers
4.41:1
#000000
on
#4470C9
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 National Bureau of E…4.41:13.0:1
#000000
#4570C9
Pass
h2 Research Projects4.41:13.0:1
#000000
#4570C9
Pass
h2 Conferences4.41:13.0:1
#000000
#4570C9
Pass
h2 Books & Chapters4.41:13.0:1
#000000
#4570C9
Pass
h2 Videos4.41:13.0:1
#000000
#4570C9
Pass
h3 Latest from the NBER4.41:13.0:1
#000000
#4570C9
Pass
h3 Featured Working Pap…4.41:13.0:1
#000000
#4570C9
Pass
h3 In the News4.41:13.0:1
#000000
#4570C9
Pass
title National Bureau of E…4.41:14.5:1
#000000
#4470C9
Fail
a Skip to main content4.41:14.5:1
#000000
#4470C9
Fail
a Subscribe4.41:14.5:1
#000000
#4470C9
Fail
a Media4.41:14.5:1
#000000
#4470C9
Fail
a Open Calls4.41:14.5:1
#000000
#4470C9
Fail
span Login4.41:14.5:1
#000000
#4470C9
Fail
span Login4.41:14.5:1
#000000
#4470C9
Fail
label Search4.41:14.5:1
#000000
#4470C9
Fail
button Research4.41:14.5:1
#000000
#4470C9
Fail
a EXPLORE Research4.41:14.5:1
#000000
#4470C9
Fail
span Findings4.41:14.5:1
#000000
#4470C9
Fail
a Working Papers4.41:14.5:1
#000000
#4470C9
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
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
1 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Utility Navigation" MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A
Heading Hierarchy
17 headings, 1 skip(s)
PASS
17 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 National Bureau of Economic Research
  • H3 Latest from the NBER skipped
  • H4 A research summary from the monthly NBER Digest
  • H4 The Impact of Expanding Paternity Leave
  • H4 American Economic Association Names Distinguished Fellows for 2026
  • H4 From the NBER Reporter: Research, program, and conference summaries
  • H4 Program Report: Development Economics
  • H4 From the NBER Bulletin on Entrepreneurship
  • H4 Capital Gains Taxation and Startup Founders
  • H4 From the NBER Bulletin on Health
  • H4 Immunotherapy Increases the Cost of Cancer Care but Reduces Mortality
  • H3 Featured Working Papers
  • H3 In the News
  • H2 Research Projects
  • H2 Conferences
  • H2 Books & Chapters
  • H2 Videos

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

A+
Alt Text Quality
1 of 10 images have issues
PASS
1 of 10 images have issues
Warning::
1 image(s) with filename as alt text
Info::
9 image(s) with good alt text
10 images 9 good alt text 1 generic
IssueCount
filename1 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-bar__field--mobiletextSearchfor/id
#search-bar__field--desktoptextSearchfor/id
A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 21 passed
PASS
90

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.

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 from the NBER div.promo-grid__promos > div.promo-grid__multi-promo > div.page-subtitle > h3.page-subtitle__title

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
Economic Measurement Research Institute PROJECT Coordinating Center on the Econ… section.promo-grid > div.promo-grid__promos > div.book-list > ul.book-list__list
2025, 17th Annual Feldstein Lecture, N. Gregory Mankiw," The Fiscal Future" FEL… section.promo-grid > div.promo-grid__promos > div.book-list > ul.book-list__list

These are opportunities to improve the experience of reading tabular or list data using 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
617-868-3900 div#block-footercontact > div.footer__contact-address > p > a
info@nber.org div#block-footercontact > div.footer__contact-address > p > a
webaccessibility@nber.org div#block-footercontact > div.footer__contact-address > p > a
Accessibility Policy nav.footer-legal > ul > li > a
Diversity Policy nav.footer-legal > ul > li > a
Privacy Policy nav.footer-legal > ul > li > a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read the research here div > div.digest-card > div.digest-card__summary > a
Read the research here div > div.digest-card > div.digest-card__summary > a
Read the research here div > div.digest-card > div.digest-card__summary > a
Read the research here div > div.digest-card > div.digest-card__summary > a
Read the research here div > div.digest-card > div.digest-card__summary > a
○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
●Buttons have an accessible name
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<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.
●Image elements do not have `[alt]` attributes that are redundant text.
●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 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
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback