Skip to content
https://democracynow.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
35
GRADE
F
FIX
11
REVIEW
2
PASS
0
INFO
0
Checks
13
2 REVIEW 11 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 (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

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

F
Heading Hierarchy
Action
59 headings, 8 skip(s)
FIX
59 headings, 8 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 You turn to us for voices you won't hear anywhere else.
  • H5 Menu skipped
  • H5 Menu
  • H5 Editions
  • H5 Follow
  • H5 Democracy Now!
  • H4 Daily Show
  • H5 Tuesday, April 21, 2026
  • H4 Daily Show
  • H5 Tuesday, April 21, 2026
  • H5 Media Options
  • H5 Headlines
  • H5 Speaking Events
  • H5 The Daily News Digest
  • H5 30th Anniversary Event
  • H3 Watch: Celebrating 30 Years of Independent Global News with Democracy Now!
  • H5 Featured Coverage skipped
  • H3 Yanar Mohammed, Iraqi Feminist Leader Assassinated in Baghdad
  • H5 Gift Catalog skipped
  • H3 Official Democracy Now! Gift Catalog
  • H4 Top News
  • H3 Deaths in ICE Custody Skyrocket: 2026 Toll Reaches 17, on Average One a Week
  • H3 Caught in the Crackdown: Cases Against Arrested Anti-ICE Protesters Keep Falling Apart
  • H3 Animal Rights Activists Target Wisconsin Facility Accused of Breeding Dogs for Medical Experiments
  • H3 “Gulf of Trust” Between Iran & U.S. as End of Ceasefire Nears, Peace Talks Uncertain
  • H3 Who Is Breaking International Law in the Strait of Hormuz? It’s Not Iran, Says Scholar
  • H3 Shepard Fairey on Art, Activism & Resisting Fascism: “It Can Happen Here, and It Is”
  • H3 Forest Firings: Trump Admin Aims to “Break the Forest Service,” Nearly 200 Million Acres at Stake
  • H3 As Iran Reopens Strait of Hormuz, Are U.S. & Iran Near Deal or Renewed Fighting?
  • H3 Report from Beirut: Israel-Lebanon Ceasefire Met with “Cautious Optimism”
  • H3 Rami Khouri: U.S. & Israel Were “Forced into Two Ceasefires” as Regional Balance of Power Shifts
  • H3 Aliya Rahman v. DHS: Disabled Woman Dragged from Car Files Claim over Violent Arrest in Minneapolis
  • H3 Hormuz Crisis “Only Going to Get More Horrific Before It Gets Any Better”: Prof. Laleh Khalili
  • H3 “Depths of Hell”: Sudan Enters Fourth Year of Devastating Civil War Amid Growing Energy Crisis
  • H5 Headlines skipped
  • H5 Most popular
  • H5 Speaking Events
  • H5 The Daily News Digest
  • H5 30th Anniversary Event
  • H3 Watch: Celebrating 30 Years of Independent Global News with Democracy Now!
  • H5 Featured Coverage skipped
  • H3 Yanar Mohammed, Iraqi Feminist Leader Assassinated in Baghdad
  • H5 Gift Catalog skipped
  • H3 Official Democracy Now! Gift Catalog
  • H5 Most popular skipped
  • H5 More news
  • H3 “Into the Wood Chipper”: Whistleblower’s Inside Story of DOGE Shredding USAID, 14 Million May Die
  • H3 Israel’s War & Demands “Could Throw Lebanon Back into a Civil War”: Ex-Israeli Negotiator Daniel Levy
  • H3 “Scorched-Earth Campaign”: Israel Uses “Gaza Playbook” to Turn Southern Lebanon into Rubble
  • H3 Reps. Swalwell & Gonzales Resign over Alleged Sexual Misconduct; Will Congress Take More Action?
  • H3 “The Future Is Peace”: Maoz Inon & Aziz Abu Sarah on Israelis and Palestinians Working Together
  • H3 Exclusive: Former U.S. Envoy & Iranian Nuclear Negotiator Discuss Ceasefire Talks, How War Could End
  • H2 Non-commercial news needs your support
  • H5 independent global news skipped
  • H5 News
  • H5 Democracy Now!
  • H5 Editions
  • H5 Follow
  • H5 Get Email Updates

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

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

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

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

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

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

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

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

F
Alt Text Quality
Action
115 of 115 images have issues
FIX
115 of 115 images have issues
Critical::
115 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
61 image-in-link without alt text
An image inside a link with no alt creates an empty link.
115 images 115 missing
IssueCount
missing115 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
Form Accessibility
Action
14 of 16 controls have issues
FIX
14 of 16 controls have issues
Critical::
10 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="hobby">; <input type="submit" name="commit" id="daily_digest_modal_submit">; <textarea>; <textarea>; <input type="text" name="hobby">; <input type="submit" name="commit">; <input type="text" name="hobby">; <input type="submit" name="commit">; <input type="text" name="hobby">; <input type="submit" name="commit">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="subscriber[email]">; <input type="email" name="subscriber[email]">; <input type="email" name="subscriber[email]">; <input type="email" name="subscriber[email]">
Info::
2 control(s) properly labeled
16 controls
2 labeled
4 placeholder only
10 unlabeled
ControlTypeLabelMethod
#querytextnone
#mobile_querytextnone
subscriber[email]email(Email)placeholder only
subscriber[email]email(Email)placeholder only
subscriber[email]email(Email)placeholder only
subscriber[email]email(Email)placeholder only
textareatextarea(none)none
hobbytext(none)none
hobbytext(none)none
commitsubmit(none)none
#daily_digest_modal_submitsubmit(none)none
hobbytext(none)none
commitsubmit(none)none
textareatextarea(none)none
hobbytext(none)none
commitsubmit(none)none

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

<input type="text" name="hobby">; <input type="submit" name="commit" id="daily_digest_modal_submit">; <textarea>; <textarea>; <input type="text" name="hobby">; <input type="submit" name="commit">; <input type="text" name="hobby">; <input type="submit" name="commit">; <input type="text" name="hobby">; <input type="submit" name="commit">

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="email" name="subscriber[email]">; <input type="email" name="subscriber[email]">; <input type="email" name="subscriber[email]">; <input type="email" name="subscriber[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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
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.
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
Info::
2 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 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.
D
Lighthouse Accessibility Audits
Action
Score 67/100 — 6 failing, 12 passed
FIX
67

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.visible-xs > ul > li > button#hamburger_button div.visible-xs > ul > li > button#hamburger_button

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.daily_digest_modal_wrapper > div.daily_digest_modal_content > a#continue_to_site > img div.daily_digest_modal_wrapper > div.daily_digest_modal_content > a#continue_to_site > img
div.hidden-lg > div.container-fluid > a.logo > img div.hidden-lg > div.container-fluid > a.logo > img
ul > li > button#hamburger_button > img ul > li > button#hamburger_button > img
div.latest_show > div.cover_container > div.player_button > img div.latest_show > div.cover_container > div.player_button > img
div.news_item > a.media > picture > img.modern div.news_item > a.media > picture > img.modern
div.news_item > div.content > div.news_label > img.play div.news_item > div.content > div.news_label > img.play
div.news_item > a.media > picture > img.modern div.news_item > a.media > picture > img.modern
div.news_item > div.content > div.news_label > img.play div.news_item > div.content > div.news_label > img.play
div.news_item > a.media > picture > img.modern div.news_item > a.media > picture > img.modern
div.news_item > div.content > div.news_label > img.play div.news_item > div.content > div.news_label > img.play
div.news_item > a.media > picture > img.modern div.news_item > a.media > picture > img.modern
div.news_item > div.content > div.news_label > img.play div.news_item > div.content > div.news_label > img.play
div#highlighted_stories > div.news_item > div.news_label > img.play div#highlighted_stories > div.news_item > div.news_label > img.play
div#highlighted_stories > div.news_item > div.news_label > img.play div#highlighted_stories > div.news_item > div.news_label > img.play
div#highlighted_stories > div.news_item > div.news_label > img.play div#highlighted_stories > div.news_item > div.news_label > img.play
div#highlighted_stories > div.news_item > div.news_label > img.play div#highlighted_stories > div.news_item > div.news_label > img.play
div#highlighted_stories > div.news_item > div.news_label > img.play div#highlighted_stories > div.news_item > div.news_label > img.play
div.news_item > div.content > div.news_label > img.play div.news_item > div.content > div.news_label > img.play
div.news_item > div.content > div.news_label > img.play div.news_item > div.content > div.news_label > img.play
div.news_item > div.content > div.news_label > img.play div.news_item > div.content > div.news_label > img.play
div.news_item > div.content > div.news_label > img.play div.news_item > div.content > div.news_label > img.play
div.col-xs-12 > div.widget > div.digest_container > img div.col-xs-12 > div.widget > div.digest_container > img
div.col-xs-12 > div.widget > a > img div.col-xs-12 > div.widget > a > img
div.col-xs-12 > div.widget > a > img div.col-xs-12 > div.widget > a > img
div.col-xs-12 > div.widget > a > img div.col-xs-12 > div.widget > a > img
div.col-sm-6 > div.news_item > div.news_label > img.play div.col-sm-6 > div.news_item > div.news_label > img.play
div.col-sm-6 > div.news_item > div.news_label > img.play div.col-sm-6 > div.news_item > div.news_label > img.play
div.col-sm-6 > div.news_item > div.news_label > img.play div.col-sm-6 > div.news_item > div.news_label > img.play
div.col-sm-6 > div.news_item > div.news_label > img.play div.col-sm-6 > div.news_item > div.news_label > img.play
div.col-sm-6 > div.news_item > div.news_label > img.play div.col-sm-6 > div.news_item > div.news_label > img.play
div.col-sm-6 > div.news_item > div.news_label > img.play div.col-sm-6 > div.news_item > div.news_label > img.play
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > a > img
ul > li > a > img ul > li > 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#daily_digest_modal > div.daily_digest_modal_wrapper > div.daily_digest_modal_content > a#continue_to_site div#daily_digest_modal > div.daily_digest_modal_wrapper > div.daily_digest_modal_content > a#continue_to_site
header > div.hidden-lg > div.container-fluid > a.logo header > div.hidden-lg > div.container-fluid > a.logo
div.row > div.col-lg-6 > div.news_item > a.media div.row > div.col-lg-6 > div.news_item > a.media
div.row > div.col-lg-6 > div.news_item > a.media div.row > div.col-lg-6 > div.news_item > a.media
div.row > div.col-lg-6 > div.news_item > a.media div.row > div.col-lg-6 > div.news_item > a.media
div.row > div.col-lg-6 > div.news_item > a.media div.row > div.col-lg-6 > div.news_item > a.media
div.row > div.col-xs-12 > div.widget > a div.row > div.col-xs-12 > div.widget > a
div.row > div.col-xs-12 > div.widget > a div.row > div.col-xs-12 > div.widget > a
div.row > div.col-xs-12 > div.widget > a div.row > div.col-xs-12 > div.widget > a
div.col-lg-6 > ul > li > a div.col-lg-6 > ul > li > a
div.col-lg-6 > ul > li > a div.col-lg-6 > ul > li > a
div.col-lg-6 > ul > li > a div.col-lg-6 > ul > li > a
div.col-lg-6 > ul > li > a div.col-lg-6 > ul > li > a
div.col-lg-6 > ul > li > a div.col-lg-6 > ul > li > a
div.col-lg-6 > ul > li > a div.col-lg-6 > ul > li > 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
You turn to us for voices you won't hear anywhere else. div.daily_digest_modal_wrapper > div.daily_digest_modal_content > div > h1
DONATE div.nav_container > div.container-fluid > nav.secondary_nav > a.donate_mobile
Listen div.visible-xs > div.audio_cover > div.controls > div.listen
Media Options div.audio_cover > div.controls > div.show_modal > span.hidden-sm
APR 21, 2026 div.news_item > div.content > div.news_label > span.date
APR 21, 2026 div.news_item > div.content > div.news_label > span.date
APR 21, 2026 div.news_item > div.content > div.news_label > span.date
APR 20, 2026 div.news_item > div.content > div.news_label > span.date
APR 20, 2026 div#highlighted_stories > div.news_item > div.news_label > span.date
APR 20, 2026 div#highlighted_stories > div.news_item > div.news_label > span.date
APR 20, 2026 div#highlighted_stories > div.news_item > div.news_label > span.date
APR 17, 2026 div#highlighted_stories > div.news_item > div.news_label > span.date
APR 17, 2026 div#highlighted_stories > div.news_item > div.news_label > span.date
DONATE div.row > div#highlighted_stories > div.donate_banner > a.donate
APR 17, 2026 div.news_item > div.content > div.news_label > span.date
APR 17, 2026 div.news_item > div.content > div.news_label > span.date
APR 16, 2026 div.news_item > div.content > div.news_label > span.date
APR 16, 2026 div.news_item > div.content > div.news_label > span.date
APR ul > li > div.calendar > div.month
21 ul > li > div.calendar > div.day
APR ul > li > div.calendar > div.month
21 ul > li > div.calendar > div.day
APR ul > li > div.calendar > div.month
23 ul > li > div.calendar > div.day
THE DAILY NEWS DIGEST div.col-xs-12 > div.widget > div.digest_container > h5
APR 16, 2026 div.col-sm-6 > div.news_item > div.news_label > span.date
APR 15, 2026 div.col-sm-6 > div.news_item > div.news_label > span.date
APR 15, 2026 div.col-sm-6 > div.news_item > div.news_label > span.date
APR 15, 2026 div.col-sm-6 > div.news_item > div.news_label > span.date
APR 15, 2026 div.col-sm-6 > div.news_item > div.news_label > span.date
APR 14, 2026 div.col-sm-6 > div.news_item > div.news_label > span.date
NON-COMMERCIAL NEWS NEEDS YOUR SUPPORT div.body_wrapper > div#appeal > div.container-fluid > h2
We rely on contributions from our viewers and listeners to do our work. Please … div.body_wrapper > div#appeal > div.container-fluid > div.text
div.row > div.col-lg-5 > form#footer_subscribe > input.button_blue div.row > div.col-lg-5 > form#footer_subscribe > input.button_blue
Democracy Now! is a 501(c)3 non-profit news organization. We do not accept fund… div.container-fluid > div.row > div.col-xs-12 > div.about
MAKE A DONATION div.container-fluid > div.row > div.col-xs-12 > a.donate

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
Daily Show div.visible-xs > div.latest_show > div.cover_container > h4
MOST POPULAR div.most_popular > div.container-fluid > div.row > h5
Featured Coverage div.row > div.col-xs-12 > div.widget > h5
Gift Catalog div.row > div.col-xs-12 > div.widget > h5
NEWS div.row > div.col-sm-6 > div.news > h5

These are opportunities to improve keyboard navigation in your application.

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>`
Input buttons have discernible text.
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.
Document has a `<title>` element
`<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
Touch targets have sufficient size and spacing.
ARIA IDs are unique
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
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
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.
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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404 Error Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA 1 pass AA only
h1 You turn to us for voices you won't hear…
2.71:1
#000000
on
#0F5975
needs 3.0:1 (large text)
32px · top of page (header area) · over background image/gradient
span Sign up for Democracy Now!'s Daily Diges…
1.26:1
#000000
on
#191F24
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
1.50:1
#000000
on
#561318
needs 4.5:1 (normal text)
16px · above the fold
a Daily Digest
1.27:1
#000000
on
#2E1822
needs 4.5:1 (normal text)
16px · above the fold
a Events
1.29:1
#000000
on
#2C1B23
needs 4.5:1 (normal text)
16px · above the fold
a Stations
1.27:1
#000000
on
#281B26
needs 4.5:1 (normal text)
16px · above the fold
a Español
1.26:1
#000000
on
#231C25
needs 4.5:1 (normal text)
16px · above the fold
a Donate
1.24:1
#000000
on
#1E1B24
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)
ElementRatioRequiredFGBGResult
h1 You turn to us for v…2.71:13.0:1
#000000
#0F5975
Fail
h2 Non-commercial news …8.38:13.0:1
#000000
#01AFEF
Pass
title Democracy Now! | Dem…8.38:14.5:1
#000000
#01AFEF
Pass
span Sign up for Democrac…1.26:14.5:1
#000000
#191F24
Fail
p to get our latest he…21.00:14.5:1
#000000
#FFFFFF
Pass
span Independent Global N…21.00:14.5:1
#000000
#FFFFFF
Pass
a About1.50:14.5:1
#000000
#561318
Fail
a Daily Digest1.27:14.5:1
#000000
#2E1822
Fail
a Events1.29:14.5:1
#000000
#2C1B23
Fail
a Stations1.27:14.5:1
#000000
#281B26
Fail
a Español1.26:14.5:1
#000000
#231C25
Fail
a Donate1.24:14.5:1
#000000
#1E1B24
Fail
a Daily Shows4.66:14.5:1
#000000
#77767A
Pass
a Tuesday,21.00:14.5:1
#000000
#FFFFFF
Pass
a April 21, 202614.48:14.5:1
#000000
#9EE0F9
Pass
a Monday,8.38:14.5:1
#000000
#01AFEF
Pass
a April 20, 20268.38:14.5:1
#000000
#01AFEF
Pass
a Friday,8.38:14.5:1
#000000
#01AFEF
Pass
a April 17, 20268.38:14.5:1
#000000
#01AFEF
Pass
a Thursday,8.38:14.5:1
#000000
#01AFEF
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