Skip to content
https://biography.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
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: #000000
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.

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::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 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 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

B
Heading Hierarchy
70 headings
REVIEW
70 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Who Was Richard Russell of #SkyKing? Why the Airline Worker Stole a Plane and Flew to His Death
  • H3 Everything We Know About Gilgo Beach Killer Rex Heuermann’s Life in Prison Today
  • H3 Get to Know ‘Michael’ Star Jafaar Jackson
  • H3 Katherine Jackson
  • H3 J Allen Hynek: The Man Who Made Us Watch the Skies
  • H3 Michael Barisone and the ‘Hawthorne Hill’ Shooting
  • H2 Notable Now
  • H3 Lucille Ball
  • H3 Miley Cyrus
  • H3 Meet Taylor Frankie Paul’s Exes
  • H3 What We Know About Dayton Webber’s Criminal Case
  • H2 True Crime
  • H3 Who Is Tanner Horner? All About the Former Delivery Driver Who Admitted to Athena Strand’s Murder
  • H3 Trial Delay for ‘American Idol’ Alum Caleb Flynn
  • H3 Lizzie Borden's Isolated Life After Her Murder Trial
  • H3 What We Know About Lynette Hooker’s Disappearance
  • H3 Where Is FLDS Prophet Warren Jeffs Now?
  • H3 Where Is Killer Rex Heuermann’s Family Now?
  • H3 Where Is Convicted Cult Leader Samuel Bateman Now?
  • H3 Where Are Samuel Bateman’s Wives Now?
  • H3 BTK Killer Sees ‘Clone’ in Gilgo Beach Suspect
  • H2 People You Should Know
  • H3 How These Famous Arab Americans Made History
  • H3 40 Famous Inventors Who Changed History
  • H3 15 Famous Veterans Who Served in the U.S. Military
  • H3 10 Comedians Who Never Made the ‘SNL’ Cast
  • H3 51 Inspiring Famous Women in History
  • H2 Athletes
  • H3 The True Story of Boxer Christy Martin
  • H3 Billie Jean King and the “Battle of the Sexes”
  • H3 Where Is Former NBA Star Lamar Odom Now?
  • H3 Serena Williams
  • H2 Musicians
  • H3 Lainey Wilson’s Relationship with Duck Hodges
  • H3 Michael Jackson
  • H3 How Phil Collins Wrote “In the Air Tonight”
  • H3 Megan Moroney
  • H2 Culture
  • H3 Plane Flown by 'Ace of Aces' Pilot Finally Found
  • H3 Amelia Earhart
  • H3 5 Powerful and Influential Native American Women
  • H3 An Old Radio Could Help Find Amelia Earhart's Plane
  • H2 Scientists
  • H3 8 Female Scientists Whose Discoveries Were Credited to Men
  • H3 Marie Curie
  • H3 Mae Jemison
  • H3 George Washington Carver
  • H2 Political Figures
  • H3 10 Shirley Chisholm Quotes That Show Her Determination and Fortitude
  • H3 11 Groundbreaking Women in U.S. Politics
  • H3 Ronald and Nancy Reagan's Timeless Love Story
  • H3 Archaeologists Found a Lost Site of Friendly Fire
  • H2 Activists
  • H3 10 Powerful Greta Thunberg Quotes
  • H3 The Women’s Rights Movement and the Women of Seneca Falls
  • H3 10 Inspiring Malala Yousafzai Quotes
  • H3 Sojourner Truth’s “Ain’t I a Woman” Speech May Not Have Contained That Famous Phrase
  • H2 The Latest
  • H3 Inside Rex Heuermann’s Life in Prison
  • H3 Get to Know ‘Michael’ Star Jafaar Jackson
  • H3 Katherine Jackson
  • H3 Taylor Frankie Paul and Her TV Controversies
  • H3 NASA’s Hidden Figures: The Unsung Women You Need to Know
  • H3 What to Know About Pope Leo XIV
  • H3 Sydney Sweeney
  • H3 The Real Name and Face of Jack the Ripper?
  • H3 All About Moriah Wilson’s Parents and Brother
  • H3 Olivia Rodrigo
  • H3 All About Moriah Wilson’s Friend Caitlin Cash
  • H3 Mo Wilson’s Family Opens Up About the Netflix Doc

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

B
Alt Text Quality
5 of 94 images have issues
REVIEW
5 of 94 images have issues
Warning::
5 image(s) with generic alt text
Info::
5 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
83 image(s) with good alt text
94 images 83 good alt text 1 decorative 5 generic
IssueCount
generic5 image(s)
too long5 image(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 1 pass AA only
title Biography: Historical and Celebrity Prof…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Search
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Newsletter
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a History - Culture
1.85:1
#000000
on
#3A3A3A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a BIO Buys
2.92:1
#000000
on
#784B4E
needs 4.5:1 (normal text)
16px · mid-page
a Privacy Notice
2.14:1
#000000
on
#5F393D
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

2 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)
ElementRatioRequiredFGBGResult
title Biography: Historica…1.00:14.5:1
#000000
#000000
Fail
span Search1.00:14.5:1
#000000
#000000
Fail
a Newsletter1.00:14.5:1
#000000
#000000
Fail
a History - Culture1.85:14.5:1
#000000
#3A3A3A
Fail
a Musicians13.18:14.5:1
#000000
#F9C387
Pass
a Athletes13.41:14.5:1
#000000
#FBC582
Pass
a Movies - TV13.00:14.5:1
#000000
#FBC177
Pass
a Artists13.75:14.5:1
#000000
#FEC878
Pass
a Power - Politics13.51:14.5:1
#000000
#FDC675
Pass
a Business12.39:14.5:1
#000000
#FABB6D
Pass
a Scientists16.49:14.5:1
#000000
#E5E5D4
Pass
a Scholars - Educators13.19:14.5:1
#000000
#F9C297
Pass
a Activists9.04:14.5:1
#000000
#F88F52
Pass
a True Crime5.21:14.5:1
#000000
#CD5E1A
Pass
a BIO Buys2.92:14.5:1
#000000
#784B4E
Fail
a Privacy Notice2.14:14.5:1
#000000
#5F393D
Fail
a Terms Of Use19.26:14.5:1
#000000
#F5F5F5
Pass
a Skip to Content19.26:14.5:1
#000000
#F5F5F5
Pass
label Search19.26:14.5:1
#000000
#F5F5F5
Pass
a History & Culture19.26:14.5:1
#000000
#F5F5F5
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.

A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#global-nav-search-input-inputtextSearchfor/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | Biography ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 26 passed
PASS
100

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.

○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
●Image elements have `[alt]` attributes
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback