Skip to content
https://worldpopulationreview.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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!) NAV MAIN (missing!) ASIDE 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

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

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

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::
2 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 2 <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.
C
Form Accessibility
Action
3 of 13 controls have issues
REVIEW
3 of 13 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="format">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" id="53291fa6-8a43-4d81-a142-3c9ffdfdb714-search-mobile">; <input type="search" id="53291fa6-8a43-4d81-a142-3c9ffdfdb714-search-desktop">
Info::
10 control(s) properly labeled
13 controls
10 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
querysearchSearcharia-label
querysearchSearcharia-label
#53291fa6-8a43-4d81-a142-3c9ffdfdb714-email-form-emailemailEmail Addressfor/id
#53291fa6-8a43-4d81-a142-3c9ffdfdb714-email-form-consentcheckboxI agree to receive emails from World Population Reviewfor/id
#b732f460-3ffe-4c93-bcde-7370df751b31-email-form-emailemailEmail Addressfor/id
#b732f460-3ffe-4c93-bcde-7370df751b31-email-form-consentcheckboxI agree to receive emails from World Population Reviewfor/id
#b9be73eb-8405-41ab-b406-fa1aa1c8476b-email-form-emailemailEmail Addressfor/id
#b9be73eb-8405-41ab-b406-fa1aa1c8476b-email-form-consentcheckboxI agree to receive emails from World Population Reviewfor/id
#ad67d5df-fa85-4619-8284-fb683e958fbb-email-form-emailemailEmail Addressfor/id
#ad67d5df-fa85-4619-8284-fb683e958fbb-email-form-consentcheckboxI agree to receive emails from World Population Reviewfor/id
#53291fa6-8a43-4d81-a142-3c9ffdfdb714-search-mobilesearch(Search)placeholder only
#53291fa6-8a43-4d81-a142-3c9ffdfdb714-search-desktopsearch(Search)placeholder only
formatselect(none)none

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

<select name="format">

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="search" id="53291fa6-8a43-4d81-a142-3c9ffdfdb714-search-mobile">; <input type="search" id="53291fa6-8a43-4d81-a142-3c9ffdfdb714-search-desktop">

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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - File Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: World Population Review
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name World Population Review ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name World Population Review Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Lighthouse Accessibility Audits
Action
Score 77/100 — 8 failing, 24 passed
REVIEW
77

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.raptive-player-position > div.adthrive-player-without-wrapper-text > div.adthrive-player-ad-controls > button.adthrive-player-icon div.raptive-player-position > div.adthrive-player-without-wrapper-text > div.adthrive-player-ad-controls > button.adthrive-player-icon
div.flex > div.order-1 > div.control > button.pl-2 div.flex > div.order-1 > div.control > button.pl-2
div.order-1 > div > div.flex > button#53291fa6-8a43-4d81-a142-3c9ffdfdb714-download-btn div.order-1 > div > div.flex > button#53291fa6-8a43-4d81-a142-3c9ffdfdb714-download-btn
div.flex > div.outer > div.bg-wpr-ui_bg > button.display-btn div.flex > div.outer > div.bg-wpr-ui_bg > button.display-btn
div.flex > div.outer > div.bg-wpr-ui_bg > button.display-btn div.flex > div.outer > div.bg-wpr-ui_bg > button.display-btn
div.flex > div.outer > div.bg-wpr-ui_bg > button.display-btn div.flex > div.outer > div.bg-wpr-ui_bg > button.display-btn
div.flex > div.outer > div.bg-wpr-ui_bg > button.display-btn div.flex > div.outer > div.bg-wpr-ui_bg > button.display-btn

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
Agriculture div.carousel-container > div.carousel-item > div.group > a.z-0
Crime/Safety div.carousel-container > div.carousel-item > div.group > a.z-0
Culture div.carousel-container > div.carousel-item > div.group > a.z-0
Economics div.carousel-container > div.carousel-item > div.group > a.z-0
Education div.carousel-container > div.carousel-item > div.group > a.z-0
Environment div.carousel-container > div.carousel-item > div.group > a.z-0
Facts/Trivia div.carousel-container > div.carousel-item > div.group > a.z-0
Flags div.carousel-container > div.carousel-item > div.group > a.z-0
Geography div.carousel-container > div.carousel-item > div.group > a.z-0
Health div.carousel-container > div.carousel-item > div.group > a.z-0
History div.carousel-container > div.carousel-item > div.group > a.z-0
Infrastructure/Energy div.carousel-container > div.carousel-item > div.group > a.z-0
Law div.carousel-container > div.carousel-item > div.group > a.z-0
Manufacturing/Mining div.carousel-container > div.carousel-item > div.group > a.z-0
Military div.carousel-container > div.carousel-item > div.group > a.z-0
Politics/Government div.carousel-container > div.carousel-item > div.group > a.z-0
Population div.carousel-container > div.carousel-item > div.group > a.z-0
Sports div.carousel-container > div.carousel-item > div.group > a.z-0
Tech/Business div.carousel-container > div.carousel-item > div.group > a.z-0
Travel div.carousel-container > div.carousel-item > div.group > a.z-0

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
Hong Kong div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
China div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Puerto Rico div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
USA div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Greenland div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Denmark div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Taiwan div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
China div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Western Sahara div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Morocco div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Kosovo div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Macau div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
China div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Gibraltar div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
UK div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Monaco div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
San Marino div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Andorra div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Isle of Man div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
UK div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
India div.p-6 > div.mb-8 > p > a
China div.p-6 > div.mb-8 > p > a
Russia div.p-6 > div.mb-8 > p > a
Japan div.p-6 > div.mb-8 > p > a
DR Congo div.p-6 > div.mb-8 > p > a
Vietnam div.p-6 > div.mb-8 > p > a
2024 World Population Prospects report div#countries-by-size > div.p-6 > p > a
fertility rates div#countries-by-size > div.p-6 > p > a
birth rates div#countries-by-size > div.p-6 > p > a
infant mortality div#countries-by-size > div.p-6 > p > a
malnutrition div#countries-by-size > div.p-6 > p > a
death rate div#countries-by-size > div.p-6 > p > a
deliberately low div#countries-by-size > div.p-6 > p > a
population decline div#countries-by-size > div.p-6 > p > a
World Population Clock div#countries-by-size > div.p-6 > p > a
still developing div > div.content > p > a
least-developed div > div.content > p > a
developed countries div > div.content > p > a
quality of life div > div.content > p > a
human development index div > div.content > p > a
level of education div > div.content > p > a
per-capita health expenditure div > div.content > p > a
life expectancy div > div.content > p > a
infant mortality rates div > div.content > p > a
All div.flex > div.not-prose > div#worldHistoryGraph-buttons > button.timebtn
World Population Prospects (2024 Revision) div.border-wpr-table_border > ol.m-0 > li.text-sm > a
Historical Estimates of World Population div.border-wpr-table_border > ol.m-0 > li.text-sm > a
Privacy Policy footer.px-5 > div.flex > div.flex > a
Terms footer.px-5 > div.flex > div.flex > a
Contact footer.px-5 > div.flex > div.flex > a
About footer.px-5 > div.flex > div.flex > a
Methodology footer.px-5 > div.flex > div.flex > a
Cite div.ml-2 > div#cite-page-button > button.btn > span
Information from your device can be used to personalize your ad experience. Do… body.adthrive-device-phone > div.adthrive-comscore > div#adthrive-ccpa-link
Do not sell or share my personal information. body.adthrive-device-phone > div.adthrive-comscore > div#adthrive-ccpa-link > a#ccpaTag
Terms of Content Use body.adthrive-device-phone > div.adthrive-comscore > div.raptive-content-terms-footer > a.raptive-content-terms-footer-link

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Hong Kong div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
China div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Puerto Rico div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
USA div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Greenland div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Denmark div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Taiwan div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
China div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Western Sahara div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Morocco div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Kosovo div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Macau div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
China div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Gibraltar div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
UK div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Monaco div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
San Marino div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Andorra div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
Isle of Man div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
UK div.text-wpr-body_text > ul.ml-5 > li.mb-1.5 > a
India div.p-6 > div.mb-8 > p > a
China div.p-6 > div.mb-8 > p > a
Russia div.p-6 > div.mb-8 > p > a
Japan div.p-6 > div.mb-8 > p > a
DR Congo div.p-6 > div.mb-8 > p > a
Vietnam div.p-6 > div.mb-8 > p > a
fertility rates div#countries-by-size > div.p-6 > p > a
birth rates div#countries-by-size > div.p-6 > p > a
infant mortality div#countries-by-size > div.p-6 > p > a
malnutrition div#countries-by-size > div.p-6 > p > a
death rate div#countries-by-size > div.p-6 > p > a
deliberately low div#countries-by-size > div.p-6 > p > a
population decline div#countries-by-size > div.p-6 > p > a
still developing div > div.content > p > a
least-developed div > div.content > p > a
developed countries div > div.content > p > a
quality of life div > div.content > p > a
human development index div > div.content > p > a
level of education div > div.content > p > a
life expectancy div > div.content > p > a
infant mortality rates div > div.content > p > a

These are opportunities to improve the legibility of your content.

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 html

These are opportunities to improve the interpretation of your content by users in different locales.

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
Do not sell or share my personal information. body.adthrive-device-phone > div.adthrive-comscore > div#adthrive-ccpa-link > a#ccpaTag
Terms of Content Use body.adthrive-device-phone > div.adthrive-comscore > div.raptive-content-terms-footer > a.raptive-content-terms-footer-link

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 html

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
COUNTRY 2026 POP. ↓ RANK AREA (KM²) DENSITY ANNUAL CHANGE % GLOBA… div.relative > div.border-wpr-table_border > div#53291fa6-8a43-4d81-a142-3c9ffdfdb714-scroll-container > table#53291fa6-8a43-4d81-a142-3c9ffdfdb714
COUNTRY 2026 POP. 2050 POP. GROWTH ↓ India 1,476,630,000 1,679,590,0… div.relative > div.border-wpr-table_border > div#b9be73eb-8405-41ab-b406-fa1aa1c8476b-scroll-container > table#b9be73eb-8405-41ab-b406-fa1aa1c8476b
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○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
○`<html>` element has a valid value for its `[lang]` attribute
○`<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.
○`[lang]` attributes have a valid value
○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.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
A
Heading Hierarchy
27 headings, 1 skip(s)
PASS
27 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.
  • H4 Data by Location
  • H4 Ranking & Comparison
  • H4 Tools
  • H2 Contents
  • H1 Current World Population
  • H3 Request Data skipped
  • H2 Countries by Size
  • H3 Countries with 1B+ people
  • H3 Countries with 100M+ people
  • H3 Least Populous Countries
  • H3 Population Ranges of Countries
  • H3 Rates of population growth around the world
  • H3 Life expectancy and its impact on world population
  • H3 Challenges inherent in population estimates
  • H2 World Population Projections
  • H3 Population
  • H3 Request Data
  • H3 Top 10 Countries Whose Populations Will Grow the Most by 2050:
  • H3 Request Data
  • H3 The rise, peak, and decline of population growth
  • H3 World Population History (5000 B.C. - 2020 A.D.)
  • H3 Population History: Visualized
  • H3 Request Data
  • H3 Sources
  • H2 Related Pages
  • H2 Related Articles
  • H3 Cite This Page:

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
All 292 images OK
PASS
All 292 images OK
Info::
292 image(s) with good alt text
292 images 292 good alt text
All images have appropriate alt text.
A
Favicon & Branding
6 icon(s) detected
PASS
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Color Contrast (Screenshot)
20 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.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Current World Popula…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Contents21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Countries by Size21.00:13.0:1
#000000
#FFFFFF
Pass
h2 World Population Pro…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Related Pages21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Related Articles21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Request Data21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Countries with 1B+ p…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Countries with 100M+…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Least Populous Count…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Population Ranges of…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Rates of population …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Life expectancy and …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Challenges inherent …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Population21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Request Data21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Top 10 Countries Who…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Request Data21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The rise, peak, and …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 World Population His…21.00:13.0: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