Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 6 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

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

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

Heading Hierarchy

111 headings

REVIEW

111 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Featured Articles
H3 9 Best Places To Live In Kentucky In 2026
H3 6 Best Natural Wonders To Visit In California This Year
H3 Alligator
H3 How Far Did Alexander The Great Travel And Conquer?
H3 5 Snake-Filled Waters In New Zealand
H3 8 Prettiest Main Streetscapes In Washington
H3 9 Most Neighborly Towns In North Dakota
H3 11 Amazing New Mexico Day Trips That Are Worth The Drive
H2 Geography
H3 The Longest Rivers In Japan
H3 The 5 Most Dangerous Bodies Of Water In Wyoming
H3 6 Crystal-Clear Lakes in Wisconsin that You Have to See
H3 Matanuska-Susitna Valley
H3 What And Where Are Coastal Deserts?
H3 5 Snake-Filled Waters In Queensland
H3 Lakes With Islands That Contain Lakes
H3 Polar Deserts
H3 Popular In Geography
H3 How Many Countries Are There In Asia?
H3 What Are The Five Regions Of Asia?
H3 How Many Countries Are In Europe?
H3 How Many Oceans Are There In The World?
H3 How Many Countries Are In South America?
H3 Countries with Blue and White Flags
H3 Latin American Countries
H3 How Many Countries Are There In Africa?
H3 The Largest Countries In The World
H3 The Smallest Countries In The World
H3 How Many Countries Are There In The World?
H3 Countries
H2 Maps
H3 United States
H3 India
H3 China
H3 Reunion
H3 Burkina Faso
H3 Burundi
H3 Algeria
H3 Botswana
H3 Continents & Subcontinents
H2 North America
H2 Caribbean
H2 Central America
H2 South America
H2 Europe
H2 Africa
H2 Middle East
H2 Asia
H2 Oceania
H2 Arctic
H2 Antarctica
H3 World Administrative Divisions
H3 Florida
H3 Nova Scotia
H3 Nunavut
H3 Northwest Territories
H3 New Brunswick
H3 Manitoba
H3 British Columbia
H3 Alberta
H3 Virginia
H3 Pennsylvania
H3 Oregon
H3 Washington
H2 Flags Of The World
H3 United States
H3 India
H3 China
H3 Andorra
H3 United Arab Emirates
H3 Afghanistan
H3 Antigua and Barbuda
H3 Anguilla
H3 Albania
H3 Armenia
H3 Angola
H3 Argentina
H3 Austria
H3 Australia
H3 Aruba
H3 Azerbaijan
H3 Bosnia and Herzegovina
H3 Barbados
H2 History & Society
H3 The Longest Sieges in Ancient History
H3 Big Mac Index By Country
H3 The Rise Of Suleiman The Magnificent
H3 The Iran-Contra Affair
H3 Top 10 Steel Producing Countries In The World
H3 How Did Alexander The Great Defeat The Persian Empire?
H3 How Big Was Alexander The Great’s Empire At Its Peak?
H3 What Happened After Alexander The Great Died?
H2 Science & Nature
H3 What Causes Hail?
H3 How Many Types Of Cobras Are There?
H3 Is DDT Still Being Used?
H3 10 US States With the Most Tornadoes
H3 The Big Crunch
H3 Lemur
H3 Owl
H3 Fossa
H2 Places & Travel
H3 7 Main Streets Where New England Comes Alive
H3 7 Of The Friendliest Towns On The Atlantic Coast
H3 11 Serene Tennessee Towns For A Weekend Retreat
H3 10 Serene Towns in Texas for a Weekend Retreat
H3 5 Best Natural Wonders To Visit In Virginia This Year
H3 8 Most Welcoming Towns In Pacific Coast's Countryside
H3 9 Perfect Destinations for a Long Weekend in the Northern United States
H3 8 Of The Most Welcoming Towns In The Great Lakes Region

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Form Accessibility

2 of 8 controls have issues

REVIEW

2 of 8 controls have issues

2 control(s) without accessible label

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

Got: <input type="checkbox" id="nav_check_category_wrapper">; <input type="checkbox" id="nav_check_search">

6 control(s) properly labeled

8 controls

6 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#nav_check_continents	checkbox	Continents	for/id
#nav_check_maps	checkbox	Countries	for/id
#nav_check_world	checkbox	Geography	for/id
#nav_check_education	checkbox	Education	for/id
#nav_check_socialscience	checkbox	Social Science	for/id
#drawer_search_input	text	Search WorldAtlas	for/id
#nav_check_search	checkbox	(none)	none
#nav_check_category_wrapper	checkbox	(none)	none

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

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

Link & Button Quality

15 issue(s) across 281 links and 1 buttons

REVIEW

15 issue(s) across 281 links and 1 buttons

15 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a.continent (#551 on page); a.continent (#553 on page); a.continent (#555 on page); a.continent (#557 on page); a.continent (#559 on page); a.continent (#561 on page); a.continent (#563 on page); a.continent (#565 on page); a.continent (#567 on page); a.continent (#569 on page) (+5 more)

266 link(s) with descriptive text

281 links

15 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
/cities/8-prettiest-main-streetscapes-in…	(empty)	empty	Add link text or aria-label
/bodies-of-water/5-snake-filled-waters-i…	(empty)	empty	Add link text or aria-label
/ancient-world/how-did-alexander-the-gre…	(empty)	empty	Add link text or aria-label
/animals/lemur.html	(empty)	empty	Add link text or aria-label
/cities/8-most-welcoming-towns-in-pacifi…	(empty)	empty	Add link text or aria-label

267 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a.continent (#551 on page); a.continent (#553 on page); a.continent (#555 on page); a.continent (#557 on page); a.continent (#559 on page); a.continent (#561 on page); a.continent (#563 on page); a.continent (#565 on page); a.continent (#567 on page); a.continent (#569 on page) (+5 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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

h2 Geography

1.20:1

#000000

#181A1A

needs 3.0:1 (large text)

24px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Featured Articles	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Geography	1.20:1	3.0:1	#000000	#181A1A	Fail
h2 Maps	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 North America	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Caribbean	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Central America	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 South America	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Europe	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Africa	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Middle East	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Asia	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Oceania	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Arctic	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Antarctica	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Flags Of The World	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 History & Society	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Science & Nature	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Places & Travel	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Popular In Geography	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How Many Countries A…	21.00:1	3.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.

Alt Text Quality

All 83 images OK

PASS

All 83 images OK

13 image(s) with alt text over 125 characters

70 image(s) with good alt text

83 images 70 good alt text

Issue	Count
too long	13 image(s)

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 19 passed

PASS

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

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#feature_front > article.mod_bclip > div.bclip_info > a.bclip_container `div#feature_front > article.mod_bclip > div.bclip_info > a.bclip_container`
div#feature_frontgeography > article.mod_bclip > div.bclip_info > a.bclip_container `div#feature_frontgeography > article.mod_bclip > div.bclip_info > a.bclip_container`
div#feature_fronthistoryandsociety > article.mod_bclip > div.bclip_info > a.bclip_container `div#feature_fronthistoryandsociety > article.mod_bclip > div.bclip_info > a.bclip_container`
div#feature_frontscience > article.mod_bclip > div.bclip_info > a.bclip_container `div#feature_frontscience > article.mod_bclip > div.bclip_info > a.bclip_container`
div#feature_frontplacesandtravel > article.mod_bclip > div.bclip_info > a.bclip_container `div#feature_frontplacesandtravel > article.mod_bclip > div.bclip_info > a.bclip_container`

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.

Best practices

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.

○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

●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

●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

●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-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

○`[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

○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.

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