Skip to content
https://knightlab.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Alt Text Quality
Action
8 of 8 images have issues
FIX
8 of 8 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
8 images 8 missing
IssueCount
missing8 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

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-1jl7kx
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
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://knightlab.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://knightlab.com/manifest.json

Manifest contains invalid JSON.

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: #ffffff
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::
1 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 1 <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.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 5 failing, 11 passed
FIX
66

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
body > nav#navbar-product-top > div.nav-mobile-menu > button.button-plain body > nav#navbar-product-top > div.nav-mobile-menu > button.button-plain

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 > header.header-image > div.header-image-content > img.logo body > header.header-image > div.header-image-content > img.logo
div.grid > div.column-2 > a > img div.grid > div.column-2 > a > img
div.grid-size-2 > div.grid-item > a > img div.grid-size-2 > div.grid-item > a > img
div.grid-size-2 > div.grid-item > a > img div.grid-size-2 > div.grid-item > a > img

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.column-10 > div.cards > div.card > a div.column-10 > div.cards > div.card > a
div.column-10 > div.cards > div.card > a div.column-10 > div.cards > div.card > a
div.column-10 > div.cards > div.card > a div.column-10 > div.cards > div.card > a
div.container > div.grid > div.column-2 > a div.container > div.grid > div.column-2 > 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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest updates about our work, observations and experimentation in the Knight L… div.container > div.grid > div.column-10 > p.dek
LAB div.card > article > p.dateline > a
PROJECTS div.card > article > p.dateline > a
JUL 21, 2025 div.card > article > p.dateline > time
LAB div.card > article > p.dateline > a
PROJECTS div.card > article > p.dateline > a
OCT 6, 2023 div.card > article > p.dateline > time
by JOE GERMUSKA div.cards > div.card > article > p.byline
PEOPLE div.card > article > p.dateline > a
JAN 31, 2023 div.card > article > p.dateline > time
We build easy-to-use tools that can help you tell better stories. div.container > div.grid > div.column-10 > p.lead
Easy-to-make frame comparisons. div.card > a > article > p.product-tagline
Easy-to-make VR stories. div.card > a > article > p.product-tagline
Seamless inline audio. div.card > a > article > p.product-tagline
Tell the story behind the numbers. div.card > a > article > p.product-tagline
Maps that tell stories. div.card > a > article > p.product-tagline
Easy-to-make, beautiful timelines. div.card > a > article > p.product-tagline
Living documents and how-to guides developed by the Knight Lab community. div.container > div.grid > div.column-10 > p.lead
Live streaming is complicated but we can help. div.card > a > article > p.product-tagline
(847) 467-4971 div.grid > div.grid-item > address > span.tel
1845 SHERIDAN ROAD div.grid-item > address > span.address > span.street-address
FISK #109 & #111 div.grid-item > address > span.address > span.room-num
EVANSTON, address > span.address > div.address-group > span
IL address > span.address > div.address-group > span
60208 address > span.address > div.address-group > span
© COPYRIGHT 2017-2023 NORTHWESTERN UNIVERSITY div.container > div.grid > div.grid-item > span.copyright

These are opportunities to improve the legibility of your content.

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-hidden="true"]` is not present on the document `<body>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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.
●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
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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.
C
Landmark Structure
Action
15 landmarks
REVIEW
15 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) 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 NAV MAIN (missing!) CONTENTINFO footer

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

B
Heading Hierarchy
21 headings
REVIEW
21 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Latest News
  • H3 What if news avoiders are right, and you don’t need journalism?
  • H3 A Big Change That Will Probably Affect Your Storymaps
  • H3 Introducing AmyJo Brown, Knight Lab Professional Fellow
  • H2 Storytelling Tools
  • H3 Juxtapose JS
  • H3 Scene VR
  • H3 Soundcite JS
  • H3 Storyline JS
  • H3 StoryMap JS
  • H3 Timeline JS
  • H2 Studio
  • H2 Guides
  • H3 Live Streaming Guide for Journalists
  • H3 Social Media Guide for High School Journalists
  • H3 Design Resources
  • H2 Students and Community
  • H2 Local News Initiative
  • H2 Device Lab
  • H2 Research
  • H2 About

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
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
h2 Latest News
2.59:1
#000000
on
#4E5051
needs 3.0:1 (large text)
24px · above the fold
h3 What if news avoiders are right, and you…
1.42:1
#000000
on
#262829
needs 3.0:1 (large text)
19px · mid-page · over background image/gradient
h3 A Big Change That Will Probably Affect Y…
1.25:1
#000000
on
#1C1E1F
needs 3.0:1 (large text)
19px · mid-page

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)
ElementRatioRequiredFGBGResult
h2 Latest News2.59:13.0:1
#000000
#4E5051
Fail
h2 Storytelling Tools21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Studio21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Guides21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Students and Communi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Local News Initiativ…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Device Lab21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Research21.00:13.0:1
#000000
#FFFFFF
Pass
h2 About21.00:13.0:1
#000000
#FFFFFF
Pass
h3 What if news avoider…1.42:13.0:1
#000000
#262829
Fail
h3 A Big Change That Wi…1.25:13.0:1
#000000
#1C1E1F
Fail
h3 Introducing AmyJo Br…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Juxtapose21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Scene21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Soundcite21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Storyline21.00:13.0:1
#000000
#FFFFFF
Pass
h3 StoryMap21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Timeline21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Live Streaming Guide…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Social Media Guide f…21.00:13.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.

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback