Skip to content
https://worldhistory.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 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-vldiik
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
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Gravitec SDK
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name Gravitec SDK ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
Name Gravitec SDK
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: #293744
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
3 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 3 <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
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 ASIDE 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

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

C
Alt Text Quality
Action
2 of 35 images have issues
REVIEW
2 of 35 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
33 image(s) with good alt text
35 images 33 good alt text 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

C
Form Accessibility
Action
3 of 8 controls have issues
REVIEW
3 of 8 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="subscribe" id="mc-embedded-subscribe">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="email" name="EMAIL" id="mce-EMAIL">
Info::
5 control(s) properly labeled
8 controls
5 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#tag-historyenthusiastradioHistory Enthusiastfor/id
#tag-teacherradioTeacherfor/id
#tag-studentradioStudentfor/id
#tag-librarianradioLibrarianfor/id
#tag-scholarradioScholarfor/id
#mce-EMAILemail(Email address...)placeholder only
qtext(Search or ask question...)placeholder only
#mc-embedded-subscribesubmit(none)none

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

<input type="submit" name="subscribe" id="mc-embedded-subscribe">

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="text" name="q">; <input type="email" name="EMAIL" id="mce-EMAIL">

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

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 25 passed
REVIEW
83

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.

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
Manage Your Privacy div#cmpboxcontent > div.cmpboxtxtdiv > h1#cmpboxheadline1 > span
Accept All div.cmpboxbtns > span#cmpwelcomebtnyes > a.cmpboxbtn > span#cmpbntyestxt

These are opportunities to improve the legibility of your content.

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
Ancient Rome a#1-68 > div.ci_preview_content > div.ci_header > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > img.metricoolPixel body.home > img.metricoolPixel
aside.right_1_column > div.about-awards > a > img aside.right_1_column > div.about-awards > a > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#mc-embedded-subscribe-form > div#mc_embed_signup_scroll > div > input form#mc-embedded-subscribe-form > div#mc_embed_signup_scroll > div > input

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
body.home > header#header_wrapper > div#header > a#logo_link body.home > header#header_wrapper > div#header > a#logo_link
header#header_wrapper > nav#meanmenu > div.mean-bar > a.meanmenu-reveal header#header_wrapper > nav#meanmenu > div.mean-bar > a.meanmenu-reveal
div#content > aside.right_1_column > div.media_library > a div#content > aside.right_1_column > div.media_library > a
div#content > aside.right_1_column > div.about-awards > a div#content > aside.right_1_column > div.about-awards > a

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.

○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
●Input buttons have discernible text.
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○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
○Buttons have an accessible name
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<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.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Heading Hierarchy
25 headings, 1 skip(s)
PASS
25 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 World History Encyclopedia
  • H3 Ancient Rome skipped
  • H3 The Amphitheater of Caesarea Maritima
  • H2 Free for the World, Supported by You
  • H3 Code of Ur-Nammu - The Oldest Law Code in the World
  • H3 Ur-Nammu - Founder of the Sumerian Renaissance
  • H3 Battle of Omdurman - Britain's Vengeance for the Death of General Gordon
  • H3 Mesopotamian Warfare - Early Development of Armed Conflict
  • H3 Charles-Maurice de Talleyrand-Périgord - Napoleon's Treacherous Foreign Minister
  • H3 The Hymn to Ninkasi, Goddess of Beer - A Praise Song and Ancient Beer Recipe
  • H3 Caratacus - The Catuvellauni Chieftain Who Defied Rome
  • H3 Siege of Khartoum - Last Stand of General Gordon
  • H3 Beer - The Drink Which Makes One's Heart Feel Light
  • H3 Louis XIV of France - The Sun King
  • H3 Mahdist War - Holy War in Sudan, 1881-99
  • H3 Burial in Ancient Mesopotamia - Respect for the Living, Honoring the Dead
  • H3 Maria Theresa - The Great Habsburg Empress
  • H3 A History of Vaccination - Taming the World's Deadliest Diseases
  • H3 Love, Sex, & Marriage in Ancient Mesopotamia - Relationships in the Ancient World
  • H3 Matabeleland (Kingdom) - The Ndebele Empire in Southern Africa
  • H2 About Us
  • H2 Media Library
  • H2 Awards
  • H2 Newsletter
  • H2 Statistics

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+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /template/css/exclude/print.css?v=1776170372
Print Stylesheet ✓ Print Optimized
Print stylesheet /template/css/exclude/print.css?v=1776170372 ✓Inline @media print Not detected ✗
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 World History Encycl…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Free for the World, …18.26:13.0:1
#000000
#EFEFEF
Pass
h2 About Us18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Media Library18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Awards18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Newsletter18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Statistics18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Ancient Rome18.26:13.0:1
#000000
#EFEFEF
Pass
h3 The Amphitheater of …18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Code of Ur-Nammu18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Ur-Nammu18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Battle of Omdurman18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Mesopotamian Warfare18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Charles-Maurice de T…18.26:13.0:1
#000000
#EFEFEF
Pass
h3 The Hymn to Ninkasi,…18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Caratacus18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Siege of Khartoum18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Beer18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Louis XIV of France18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Mahdist War18.26:13.0:1
#000000
#EFEFEF
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