Skip to content
https://britannica.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 MAIN CONTENTINFO footer

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
1 of 61 images have issues
REVIEW
1 of 61 images have issues
Critical::
1 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::
15 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
44 image(s) with good alt text
61 images 44 good alt text 1 decorative 1 missing
IssueCount
missing1 image(s)
too long15 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

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 Error | Britannica ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
title Encyclopedia Britannica | Britannica
1.21:1
#000000
on
#071C2E
needs 4.5:1 (normal text)
16px · top of page (header area)
span Explore
1.21:1
#000000
on
#071C2E
needs 4.5:1 (normal text)
16px · top of page (header area)
label Search Britannica
1.21:1
#000000
on
#071C2E
needs 4.5:1 (normal text)
16px · top of page (header area)
span Click here to search
1.21:1
#000000
on
#071C2D
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Featured Games21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trending Quizzes21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Videos21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Read More21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Elections in the New…21.00:13.0:1
#000000
#FFFFFF
Pass
title Encyclopedia Britann…1.21:14.5:1
#000000
#071C2E
Fail
span Explore1.21:14.5:1
#000000
#071C2E
Fail
label Search Britannica1.21:14.5:1
#000000
#071C2E
Fail
span Click here to search1.21:14.5:1
#000000
#071C2D
Fail
label Search Britannica7.92:14.5:1
#000000
#98A0A7
Pass
span Click here to search21.00:14.5:1
#000000
#FFFFFF
Pass
a SUBSCRIBE21.00:14.5:1
#000000
#FFFFFF
Pass
a SUBSCRIBE21.00:14.5:1
#000000
#FFFFFF
Pass
span Login21.00:14.5:1
#000000
#FFFFFF
Pass
div https://premium.brit…21.00:14.5:1
#000000
#FFFFFF
Pass
a SUBSCRIBE21.00:14.5:1
#000000
#FFFFFF
Pass
label Search Britannica21.00:14.5:1
#000000
#FFFFFF
Pass
span Click here to search21.00:14.5:1
#000000
#FFFFFF
Pass
a Ask the Chatbot21.00:14.5: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.

B
Lighthouse Accessibility Audits
Score 82/100 — 4 failing, 20 passed
REVIEW
82

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.global-nav-top-bar > div.grid > div.col-35 > button.js-toggle-user-dropdown div.global-nav-top-bar > div.grid > div.col-35 > button.js-toggle-user-dropdown

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
div.grid > div.col-sm-40 > a > img.col-70 div.grid > div.col-sm-40 > a > img.col-70

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.marketing-HOMEPAGE_BOTTOM_SUBSCRIBE2 > div.grid > div.col-sm-40 > a div.marketing-HOMEPAGE_BOTTOM_SUBSCRIBE2 > div.grid > div.col-sm-40 > 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.

Contrast

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
archaeologists div.cards3up > div.kic-title-container > div.font-serif > a.md-crosslink
ancient Egyptian div.cards3up > div.kic-title-container > div.font-serif > a.md-crosslink
divine kingship div.cards3up > div.kic-title-container > div.font-serif > a.md-crosslink
afterlife div.cards3up > div.kic-title-container > div.font-serif > a.md-crosslink
Canada div.feature-block > div.oyr-title-container > p.font-serif > a.md-crosslink
Liberal div.feature-block > div.oyr-title-container > p.font-serif > a.md-crosslink
Mark Carney div.feature-block > div.oyr-title-container > p.font-serif > a.md-crosslink
Benin div.feature-block > div.oyr-title-container > p.font-serif > a.md-crosslink
Hungary div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
Viktor Orbán div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
Péter Magyar div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
European Union div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
Peru div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
Alberto Fujimori div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
has secured a place in the June 7 runoff div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
Ismail Omar Guelleh div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
Since he first took office in 1999 div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink
strategic location div.kic-right-rail > div.feature-block > p.font-serif > a.md-crosslink

These are opportunities to improve the legibility of your content.

○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
●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
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
○`[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
○`<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.
○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.
○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.
A
Heading Hierarchy
18 headings
PASS
18 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Temples and Tombs
  • H3 Read More
  • H3 Elections in the News
  • H2 New on Britannica
  • H2 Popular ProCon Debate Topics
  • H2 Featured Games
  • H2 Trending Quizzes
  • H2 Featured Videos
  • H1 Britannica Premium Subscription
  • H1 Unlock Exclusive Content! duplicate H1
  • H2 Explore Britannica
  • H3 History & Society
  • H3 Science & Tech
  • H3 Biographies
  • H3 Animals & Nature
  • H3 Geography & Travel
  • H3 Arts & Culture
  • H2 Calculators

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#__fe87332f-ce0d-4187-b6a8-5ac2e25ac139inputSearch Britannicaaria-label
#global-nav-search-queryinputSearch Britannicaaria-label
#__e95f8fd6-0266-4a38-9335-b83b2a4461beinputSearch Britannicaaria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback