Skip to content
https://thinkprogress.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
3 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 3 <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.
B
Landmark Structure
48 landmarks
REVIEW
48 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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 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
39 headings, 1 skip(s)
REVIEW
39 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Think Progress Header Logo
  • H3 Topics Menu skipped
  • H3 More Menu
  • H2 CNN’s planning a 2020 LGBTQ forum. Here are some issues advocates say the candidates should address.
  • H2 It wasn’t a debate, but CNN’s 7-hour climate forum laid bare key differences among Democrats
  • H2 GOP candidate has a pretty hypocritical excuse for why he’s down in the polls
  • H2 To build Trump’s border wall, Pentagon will divert funds from military schools and day cares
  • H2 Trump describes Boris Johnson as someone who ‘knows how to win’ after historic Parliament defeats
  • H2 Trump’s Fox & Friends pals finally concede Mexico ain’t paying for that wall
  • H2 The Trump administration plans to gut food stamps, hitting red states hardest
  • H2 Kristen Stewart’s experience is emblematic of LGBTQ people’s struggles in Hollywood
  • H2 Boris Johnson’s Brexit plans have been derailed, thanks to members of his own party
  • H2 Dan Crenshaw is worried that universal background checks might keep him from arming his friends
  • H2 Texas congressman’s retirement points to a tough 2020 for House Republicans
  • H2 Alabama governor’s blackface scandal shows GOP’s hypocrisy
  • H2 House Democrats turn their attention to Donald Trump’s involvement in hush-money payments
  • H1 Climate duplicate H1
  • H2 Hurricane Dorian’s nightmarishly slow pace is linked to climate change
  • H2 Hurricane Dorian’s impacts could be resounding — here’s what to watch for
  • H2 Even Big Oil doesn’t like the EPA’s methane rollback
  • H2 Trump takes money from FEMA for border wall with Puerto Rico set for major storm
  • H2 Trump moves to allow logging in the world’s largest intact temperate rainforest
  • H2 Trump repeats relief funding lie as Tropical Storm Dorian approaches Puerto Rico
  • H2 Brazil rejects G7’s already minuscule aid package to help combat raging fires in the Amazon
  • H2 Trump skips G7 climate meeting as the Amazon burns
  • H2 The impact of Jay Inslee’s climate-focused 2020 candidacy
  • H2 Agriculture’s role in climate change draws scrutiny from 2020 Democrats
  • H2 Wealthy nations won’t be spared economic climate impacts, new study finds
  • H2 Tribe raises stakes in Dakota Access pipeline fight amid surge in Democratic 2020 support
  • H2 ‘Only you know if we did it’: Scientists write dire letter to the future about climate change
  • H2 House Democrats will consider bill to block HUD rule allowing anti-trans shelter discrimination
  • H2 How ‘Straight Pride’ parades like the one in Boston mask a far-right agenda
  • H2 Taylor Swift reminded us that the Equality Act would bolster LGBTQ rights
  • H2 NRA melts down over Walmart decision to reduce its ammo sales
  • H2 Mitch McConnell suggests Trump cannot be trusted to mean what he says on guns
  • H2 Native votes went missing in North Carolina. Tribal leaders vow that won’t happen again next week.
  • H2 Black kids in Missouri are being shot down in unspeakable numbers
  • H2 Exposed for 1967 blackface skit, Alabama governor issues written statement rather than face cameras
  • H2 Did Gillibrand’s push for Al Franken’s resignation doom her 2020 White House run?

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.4.6 / Google Search Central

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">; <input type="search" name="s">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
ssearch(Search)placeholder only
ssearch(Search)placeholder only

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

<input type="search" name="s">; <input type="search" name="s">

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

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
title ThinkProgress
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Contact Us
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Facebook
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Twitter
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Youtube
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Topics Menu21.00:13.0:1
#000000
#FFFFFF
Pass
h3 More Menu21.00:13.0:1
#000000
#FFFFFF
Pass
title ThinkProgress1.00:14.5:1
#000000
#000000
Fail
a Contact Us1.00:14.5:1
#000000
#000000
Fail
span Facebook1.00:14.5:1
#000000
#000000
Fail
span Twitter1.00:14.5:1
#000000
#000000
Fail
span Youtube1.00:14.5:1
#000000
#000000
Fail
span Instagram7.37:14.5:1
#000000
#999999
Pass
a Latest Stories21.00:14.5:1
#000000
#FFFFFF
Pass
span Facebook21.00:14.5:1
#000000
#FFFFFF
Pass
span Twitter21.00:14.5:1
#000000
#FFFFFF
Pass
span Youtube21.00:14.5:1
#000000
#FFFFFF
Pass
span Instagram21.00:14.5:1
#000000
#FFFFFF
Pass
a Video21.00:14.5:1
#000000
#FFFFFF
Pass
a ClimateProgress21.00:14.5:1
#000000
#FFFFFF
Pass
a Politics21.00:14.5:1
#000000
#FFFFFF
Pass
a Immigration21.00:14.5:1
#000000
#FFFFFF
Pass
a World21.00:14.5:1
#000000
#FFFFFF
Pass
a Health Care21.00:14.5:1
#000000
#FFFFFF
Pass
span Open More Menu21.00:14.5:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
15 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
24 images 8 good alt text 1 decorative
IssueCount
too long15 image(s)
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 21 passed
PASS
90

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
Advertisement div#primary > main#main > div.ad-wrapper > div.ad-label
SEP 4, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 4, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 4, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 4, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 4, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 3, 2019 header.post__header > div.post__meta > a > time.post__date
Advertisement div#primary > main#main > div.ad-wrapper > div.ad-label
AUG 26, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 22, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 21, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 20, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 19, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 18, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 3, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 31, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 27, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 3, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 3, 2019 header.post__header > div.post__meta > a > time.post__date
SEP 3, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 31, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 29, 2019 header.post__header > div.post__meta > a > time.post__date
AUG 29, 2019 header.post__header > div.post__meta > a > time.post__date
Information from your device can be used to personalize your ad experience. Do… body.home > div.adthrive-comscore > div#adthrive-ccpa-link

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
Topics Menu div.header-site__secondary-menus > div.header-site__secondary-menus-inner > div.header-site__topics-menu > h3.screen-reader-text

These are opportunities to improve keyboard navigation in your application.

Best practices

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
CASEY QUINLAN div.post__meta > span.post__byline > span.author > a.url
LUKE BARNES div.post__meta > span.post__byline > span.author > a.url
JOSH ISRAEL div.post__meta > span.post__byline > span.author > a.url
JOSH ISRAEL div.post__meta > span.post__byline > span.author > a.url
JOSH ISRAEL div.post__meta > span.post__byline > span.author > a.url
ADAM PECK div.post__meta > span.post__byline > span.author > a.url
E.A. CRUNDEN div.post__meta > span.post__byline > span.author > a.url
E.A. CRUNDEN div.post__meta > span.post__byline > span.author > a.url
E.A. CRUNDEN div.post__meta > span.post__byline > span.author > a.url
E.A. CRUNDEN div.post__meta > span.post__byline > span.author > a.url
E.A. CRUNDEN div.post__meta > span.post__byline > span.author > a.url
JOE ROMM div.post__meta > span.post__byline > span.author > a.url
JOSH ISRAEL div.post__meta > span.post__byline > span.author > a.url
JOSH ISRAEL div.post__meta > span.post__byline > span.author > a.url
DANIELLE MCLEAN div.post__meta > span.post__byline > span.author > a.url
KAY WICKER div.post__meta > span.post__byline > span.author > a.url
ALAN PYKE div.post__meta > span.post__byline > span.author > a.url
CASEY QUINLAN div.post__meta > span.post__byline > span.author > a.url

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
●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
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback