Skip to content
https://healthdata.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
D
Heading Hierarchy
Action
23 headings, 4 skip(s)
FIX
23 headings, 4 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Main navigation
  • H1 All people living long lives in full health
  • H2 Featured stories
  • H4 Childhood cancer is a substantial contributor to global childhood mortality and global cancer burden skipped
  • H4 Global maternal deaths fell to 240,000 in 2023, but more than 100 countries still fall short of the global maternal mortality target as progress slows worldwide
  • H4 The Lancet Oncology: Breast cancer remains the most common cancer among women worldwide, with annual cases expected to reach over 3.5 million by 2050
  • H4 U.S. Medical Care is Improving, but Cost and Health Differ Depending on Disease
  • H2 Recent publications
  • H4 Measuring antenatal care timing and content: a systematic analysis of trends from 1995 to 2023 across 131 low-income and middle-income countries skipped
  • H4 Global burden of metabolic dysfunction-associated steatotic liver disease, 1990–2023, and projections to 2050: a systematic analysis for the Global Burden of Disease Study 2023
  • H4 Implications of changes in WHO haemoglobin elevation adjustment guidelines on global, regional, and national anaemia burden, 1990–2023: a population-based modelling study
  • H4 Burden of cancer attributable to occupational asbestos exposure in the Americas, 1990–2023: an analysis using the Global Burden of Disease Study 2023
  • H2 Hear from experts
  • H4 Launch of Brazil subnational capstone: An analysis of estimates from the GBD 2023 study skipped
  • H4 The average age of death from ischemic heart disease varies by nearly 30 years globally. New findings show which countries perform best.
  • H4 Delivering scientific evidence through the NUS-IHME Global Burden of Disease Research Centre
  • H4 Career advice from IHME female faculty members
  • H2 Popular pages and tools
  • H4 Global Burden of Disease (GBD) skipped
  • H4 Health by location
  • H4 Data sources
  • H4 Interactive data visuals
  • H2 Subscribe to our newsletter

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

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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #0f7c95
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 ModePartial Dark Mode
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::
5 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="edit-submit">; <input type="submit" name="op" id="mailchimp-signup-subscribe-block-subscribe-to-our-newsletter-form-wrapper-edit-submit">
Info::
2 control(s) properly labeled
4 controls
2 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#edit-search-inputtextSearcharia-label
#edit-mergevars-emailemailEmail Addressfor/id
#edit-submitsubmit(none)none
#mailchimp-signup-subscribe-block-subscribe-to-our-newsletter-form-wrapper-edit-submitsubmit(none)none

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

<input type="submit" name="op" id="edit-submit">; <input type="submit" name="op" id="mailchimp-signup-subscribe-block-subscribe-to-our-newsletter-form-wrapper-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

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::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title IHME logo white Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) 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::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name 192×192 icon 512×512 icon Start URL Display Mode standalone
Display Mode standalone Theme Color #0f7c95 Background Color #0f7c95 Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
title Homepage | Institute for Health Metrics …
1.32:1
#000000
on
#02262E
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 All people living lo…20.83:13.0:1
#000000
#FFFEFC
Pass
h2 Main navigation10.78:13.0:1
#000000
#B5BE97
Pass
h2 Featured stories20.83:13.0:1
#000000
#FFFEFC
Pass
h2 Recent publications20.83:13.0:1
#000000
#FFFEFC
Pass
h2 Hear from experts20.83:13.0:1
#000000
#FFFEFC
Pass
h2 Popular pages and to…20.83:13.0:1
#000000
#FFFEFC
Pass
h2 Subscribe to our new…20.83:13.0:1
#000000
#FFFEFC
Pass
title Homepage | Institute…1.32:14.5:1
#000000
#02262E
Fail
a Skip to main content20.83:14.5:1
#000000
#FFFEFC
Pass
div Institute for Health…20.83:14.5:1
#000000
#FFFEFC
Pass
a Contact us20.83:14.5:1
#000000
#FFFEFC
Pass
a Research library12.63:14.5:1
#000000
#FFB8A2
Pass
a Data catalog10.09:14.5:1
#000000
#84C28F
Pass
a Give now10.09:14.5:1
#000000
#84C28F
Pass
button Research and analysi…11.82:14.5:1
#000000
#83D3A4
Pass
span Close13.19:14.5:1
#000000
#84DFB3
Pass
mark Research and analysi…13.19:14.5:1
#000000
#84DFB3
Pass
button Health topics15.88:14.5:1
#000000
#B5ECD1
Pass
mark Air pollution18.63:14.5:1
#000000
#DFF7EA
Pass
mark Alcohol use17.08:14.5:1
#000000
#C8F1DD
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.

A+
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Utility" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
8 image(s) with good alt text
9 images 8 good alt text
IssueCount
too long1 image(s)
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 25 passed
PASS
95

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
A child's hand, with an IV attached, holds an adult hand div.c-node-feed__inner > article.c-card > div.c-card__teaser-image > a
Black and white image of hands on a pregnant belly div.c-node-feed__inner > article.c-card > div.c-card__teaser-image > a
Image of a mammogram div.c-node-feed__inner > article.c-card > div.c-card__teaser-image > a
AI-generated graphic representing coins and bars, with dollar signs div.c-node-feed__inner > article.c-card > div.c-card__teaser-image > a
Image of webinar speakers Luisa Caldeira Brant (UFMG), Renato A. Texeira (UFMG)… div.c-editorial-grid__featured > article.c-card > div.c-card__teaser-image > a
Healthcare, patient and doctor with blood pressure test, health and wellness c… div.c-editorial-grid__feed > article.c-card > div.c-card__teaser-image > a
Illustration of women in different roles div.c-editorial-grid__feed > article.c-card > div.c-card__teaser-image > a

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.

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
Childhood cancer is a substantial contributor to global childhood mortality and… div.c-node-feed > div.c-node-feed__inner > article.c-card > h4.c-card__title
Measuring antenatal care timing and content: a systematic analysis of trends fr… div.c-node-feed > div.c-node-feed__inner > article.c-card > h4.c-card__title
Launch of Brazil subnational capstone: An analysis of estimates from the GBD 20… div.l-grid > div.c-editorial-grid__featured > article.c-card > h4.c-card__title
Global Burden of Disease (GBD) div.layout__region > div.c-node-card > article.c-card > h4.c-card__title

These are opportunities to improve keyboard navigation in your application.

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
Buttons have an accessible name
Image elements have `[alt]` attributes
Input buttons have discernible text.
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
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 have a discernible name
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.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
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 type="image">` elements have `[alt]` text
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.
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.
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.
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