Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

9 PASS 8 REVIEW 7 FIX

Form Accessibility

Action

10 of 10 controls have issues

FIX

10 of 10 controls have issues

5 control(s) without accessible label

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

Got: <input type="submit" id="edit-submit">; <input type="submit" id="edit-submit">; <input type="submit" id="edit-submit">; <input type="submit" id="edit-submit">; <input type="submit" name="subscribe" id="mc-embedded-subscribe">

5 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="q" id="edit-keys">; <input type="search" name="q" id="edit-keys">; <input type="text" name="FNAME" id="mce-FNAME">; <input type="text" name="LNAME" id="mce-LNAME">; <input type="email" name="EMAIL" id="mce-EMAIL">

10 controls

0 labeled

5 placeholder only

5 unlabeled

Control	Type	Label	Method
#edit-keys	search	(What do you want to learn today?)	placeholder only
#edit-keys	search	(What do you want to learn today?)	placeholder only
#mce-FNAME	text	(First Name)	placeholder only
#mce-LNAME	text	(Last Name)	placeholder only
#mce-EMAIL	email	(Email Address)	placeholder only
#edit-submit	submit	(none)	none
#edit-submit	submit	(none)	none
#edit-submit	submit	(none)	none
#edit-submit	submit	(none)	none
#mc-embedded-subscribe	submit	(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

Placeholder text disappears on focus and is not a reliable label.

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

Mobile Keyboard & Autofill

Action

6/6 eligible field(s) missing autocomplete or inputmode

FIX

6/6 eligible field(s) missing autocomplete or inputmode

3 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: given-name, family-name, email.

Got: <input type="text" name="FNAME" id="mce-FNAME">, <input type="text" name="LNAME" id="mce-LNAME">, <input type="email" name="EMAIL" id="mce-EMAIL">

3 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.

Got: <input type="search" name="q" id="edit-keys">, <input type="search" name="q" id="edit-keys">, <input type="email" name="EMAIL" id="mce-EMAIL">

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 ✗

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 present

Skip link target(s) don't exist on page: #main-content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

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

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

Heading Hierarchy

15 headings

REVIEW

15 headings

No H1 heading found

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

H4 The World’s #1 Online Encyclopedia
H4 Picks of the week
H4 Look who's using encyclopedia.com
H5 Pandemic Flu
H5 Bacteriophages
H5 The Anglerfish
H3 income tax
H3 autism
H3 Pure Land Buddhism
H3 Boston Tea Party
H3 Hernan Cortes
H3 Pyrenees
H3 More topics
H2 Subscribe to our newsletter
H2 Footer menu

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

Link & Button Quality

Action

4 issue(s) across 40 links and 5 buttons

REVIEW

4 issue(s) across 40 links and 5 buttons

1 link(s) with no accessible text

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

Got: a#main-content

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /about ("Read more")

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: input[type="submit"]#edit-submit; input[type="submit"]#edit-submit

38 link(s) with descriptive text

40 links

1 empty

1 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
/about	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: About
<input>	(empty)	empty	Add button text or aria-label
<input>	(empty)	empty	Add button text or aria-label

41 links and buttons have descriptive text

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

a#main-content

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

Generic link text like 'click here' doesn't describe the destination.

/about ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Icon-only buttons need an aria-label so screen readers can announce them.

input[type="submit"]#edit-submit; input[type="submit"]#edit-submit

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Iframe Accessibility

2/2 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/2 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

Tap Target Adequacy

1 tap target(s) too small or too close together

REVIEW

1 tap target(s) too small or too close together

1 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

Action

81% of visible text renders at >= 12 CSS px (11 below threshold)

REVIEW

81% of visible text renders at >= 12 CSS px (11 below threshold)

11 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.5px ("EXPLORE"); <a> 0.0px ("view"); <a> 0.0px ("view"); <a> 11.3px ("Home"); <a> 11.3px ("About Us").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA

span EXPLORE

2.41:1

#000000

#574933

needs 4.5:1 (normal text)

16px · top of page (header area)

span EXPLORE

2.97:1

#000000

#595950

needs 4.5:1 (normal text)

16px · top of page (header area)

a Earth and Environment

1.56:1

#000000

#3A2C1D

needs 4.5:1 (normal text)

16px · above the fold

a History

1.15:1

#000000

#2D0902

needs 4.5:1 (normal text)

16px · above the fold

a Literature and the Arts

1.09:1

#000000

#1F0801

needs 4.5:1 (normal text)

16px · above the fold

a Medicine

1.08:1

#000000

#1A0802

needs 4.5:1 (normal text)

16px · above the fold

a People

1.13:1

#000000

#1B110D

needs 4.5:1 (normal text)

16px · above the fold

a Philosophy and Religion

1.13:1

#000000

#1E1007

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Places

1.01:1

#000000

#070100

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Subscribe to our new…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 income tax	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 autism	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pure Land Buddhism	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Boston Tea Party	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hernan Cortes	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pyrenees	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 More topics	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Encyclopedia.com \| F…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span EXPLORE	2.41:1	4.5:1	#000000	#574933	Fail
span EXPLORE	2.97:1	4.5:1	#000000	#595950	Fail
a Earth and Environmen…	1.56:1	4.5:1	#000000	#3A2C1D	Fail
a History	1.15:1	4.5:1	#000000	#2D0902	Fail
a Literature and the A…	1.09:1	4.5:1	#000000	#1F0801	Fail
a Medicine	1.08:1	4.5:1	#000000	#1A0802	Fail
a People	1.13:1	4.5:1	#000000	#1B110D	Fail
a Philosophy and Relig…	1.13:1	4.5:1	#000000	#1E1007	Fail
a Places	1.01:1	4.5:1	#000000	#070100	Fail

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.

Lighthouse Accessibility Audits

Score 82/100 — 5 failing, 24 passed

REVIEW

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
div.ency-hero-search > form > div#edit-actions > input#edit-submit `div.ency-hero-search > form > div#edit-actions > input#edit-submit`
Recently researched about `div.clear-both > div.whoslooking-slider > div.whoslooking-item > span`
Recently researched about `div.clear-both > div.whoslooking-slider > div.whoslooking-item > span`
Recently researched about `div.clear-both > div.whoslooking-slider > div.whoslooking-item > span`
SUBSCRIBE TO OUR NEWSLETTER `div#block-mailchimp > div > div#mc_embed_signup > h2`
Sign up with your email address to receive news and updates. `div#block-mailchimp > div > div#mc_embed_signup > p.secondary-text`
We respect your privacy. `div#block-mailchimp > div > div#mc_embed_signup > p.privacy-text`
HOME `nav#block-trustme-footer > ul > li > a.is-active`
ABOUT US `nav#block-trustme-footer > ul > li > a`
HELP `nav#block-trustme-footer > ul > li > a`
SITE FEEDBACK `nav#block-trustme-footer > ul > li > a`
PRIVACY & COOKIE POLICY `nav#block-trustme-footer > ul > li > a`
TERMS AND CONDITIONS `nav#block-trustme-footer > ul > li > a`
DAILY `nav#block-trustme-footer > ul > li > a`
© 2019 Encyclopedia.com \| All rights reserved. `div#block-trustme-copyright > div > p > span`
Information from your device can be used to personalize your ad experience. Do… `body.path-frontpage > div.adthrive-comscore > div#adthrive-ccpa-link`
A RAPTIVE PARTNER SITE `body.path-frontpage > div.adthrive-comscore > span`

These are opportunities to improve the legibility of your content.

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
div#tltpvid_21855 > div.tl-transparent > div.tl-adchoices > img.tl-edaa-icon `div#tltpvid_21855 > div.tl-transparent > div.tl-adchoices > img.tl-edaa-icon`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Sponsored By Nintendo `div.AdThrive_Footer_1_HDX_pbs2s_Mobile_textcontent > div.AdThrive_Footer_1_HDX_pbs2s_Mobile_textcontent_creative_copy > div.AdThrive_Footer_1_HDX_pbs2s_Mobile_sponsor > a.AdThrive_Footer_1_HDX_pbs2s_Mobile_sponsor_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.js `html.js`

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

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

●Input buttons have discernible text.

●Form elements have associated labels

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

○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 Text Quality

All 15 heading(s) have substantive, well-formed text

PASS

All 15 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

3 decorative image(s) correctly marked

4 image(s) with good alt text

7 images 4 good alt text 3 decorative

All images have appropriate alt text.

A+

Form Input Types

10 form control(s) checked, no type mismatches

PASS

10 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

10 form control(s) checked, no input-semantic issues

PASS

10 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | Encyclopedia.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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