Skip to content
https://Undotrump.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
D
Mobile-Readable Font Sizes
Action
59% of visible text renders at >= 12 CSS px (85 below threshold)
FIX
59% of visible text renders at >= 12 CSS px (85 below threshold)
Warning::
85 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: <div> 11.0px ("★ \u00a0 ★ \u00a0 ★"); <a> 11.0px ("Active"); <a> 11.0px ("In Courts"); <a> 11.0px ("Partially Undone"); <a> 11.0px ("Undone").
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: #1b2a4a
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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
qtext(Search the record — executive orders, climate, immigration, tariffs…)placeholder only
selectselect(none)none

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

<select>

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="text" name="q">

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
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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404 Not Found Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA
title UndoTrump.com
1.25:1
#000000
on
#111D33
needs 4.5:1 (normal text)
16px · top of page (header area)
span ESTABLISHED 2024
1.38:1
#000000
on
#172541
needs 4.5:1 (normal text)
16px · top of page (header area)
span A CIVIC RECORD OF ACTIONS TAKEN AGAINST …
1.48:1
#000000
on
#1B2A4A
needs 4.5:1 (normal text)
16px · top of page (header area)
strong May 10, 2026
1.48:1
#000000
on
#1B2A4A
needs 3.0:1 (large text)
16px · top of page (header area)
div A nonpartisan civic restoration project
1.48:1
#000000
on
#1B2A4A
needs 4.5:1 (normal text)
16px · above the fold
span Undo
1.48:1
#000000
on
#1B2A4A
needs 4.5:1 (normal text)
16px · above the fold
span Trump
1.48:1
#000000
on
#1B2A4A
needs 4.5:1 (normal text)
16px · above the fold
span com
1.48:1
#000000
on
#1B2A4A
needs 4.5:1 (normal text)
16px · above the fold
div ★   ★   ★
1.48:1
#000000
on
#1B2A4A
needs 4.5:1 (normal text)
16px · above the fold
p Tracking every rollback, reversal, and o…
1.48:1
#000000
on
#1B2A4A
needs 4.5:1 (normal text)
16px · above the fold
div 1,032
4.40:1
#000000
on
#6D737E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div 475
4.40:1
#000000
on
#6D737E
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
div Days Tracking
1.48:1
#000000
on
#1B2A4A
needs 4.5:1 (normal text)
16px · mid-page
a All Actions
1.25:1
#000000
on
#111D33
needs 4.5:1 (normal text)
16px · mid-page

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
h2 The Record18.35:13.0:1
#000000
#F4EFE7
Pass
title UndoTrump.com1.25:14.5:1
#000000
#111D33
Fail
span ESTABLISHED 20241.38:14.5:1
#000000
#172541
Fail
span A CIVIC RECORD OF AC…1.48:14.5:1
#000000
#1B2A4A
Fail
strong May 10, 20261.48:13.0:1
#000000
#1B2A4A
Fail
div A nonpartisan civic …1.48:14.5:1
#000000
#1B2A4A
Fail
span Undo1.48:14.5:1
#000000
#1B2A4A
Fail
span Trump1.48:14.5:1
#000000
#1B2A4A
Fail
span com1.48:14.5:1
#000000
#1B2A4A
Fail
div ★   ★   ★1.48:14.5:1
#000000
#1B2A4A
Fail
p Tracking every rollb…1.48:14.5:1
#000000
#1B2A4A
Fail
div 1,0324.40:14.5:1
#000000
#6D737E
Fail
div Actions Tracked15.97:14.5:1
#000000
#E8E0CC
Pass
div 79815.97:14.5:1
#000000
#E8E0CC
Pass
div Still Active15.97:14.5:1
#000000
#E8E0CC
Pass
div In the Courts15.97:14.5:1
#000000
#E8E0CC
Pass
div Restored15.97:14.5:1
#000000
#E8E0CC
Pass
div 4754.40:14.5:1
#000000
#6D737E
Fail
div Days Tracking1.48:14.5:1
#000000
#1B2A4A
Fail
a All Actions1.25:14.5:1
#000000
#111D33
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 2 failing, 12 passed
REVIEW
83

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
ACTIONS TRACKED div.container > div.stat-strip-inner > div.stat-item > div.stat-label
STILL ACTIVE div.container > div.stat-strip-inner > div.stat-item > div.stat-label
IN THE COURTS div.container > div.stat-strip-inner > div.stat-item > div.stat-label
RESTORED div.container > div.stat-strip-inner > div.stat-item > div.stat-label
475 div.container > div.stat-strip-inner > div.stat-item > div.stat-number
DAYS TRACKING div.container > div.stat-strip-inner > div.stat-item > div.stat-label
🌍 ENVIRONMENT nav.nav-bar > div.container > div.nav-inner > a.nav-item
🏥 HEALTHCARE nav.nav-bar > div.container > div.nav-inner > a.nav-item
FILTER: div.search-bar > div.container > div.filter-pills > span
ACTIVE main > article.action-card > div.card-meta > span.status-badge
CORRUPTION main > article.action-card > div.card-tags > a.card-tag
ETHICS OVERSIGHT main > article.action-card > div.card-tags > a.card-tag
EXECUTIVE_POWER main > article.action-card > div.card-tags > a.card-tag
GOVERNMENT_ACCOUNTABILITY main > article.action-card > div.card-tags > a.card-tag
PARDONS main > article.action-card > div.card-tags > a.card-tag
WATCHDOG ELIMINATION main > article.action-card > div.card-tags > a.card-tag
Tracked 2 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 3 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 4 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 5 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 5 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 5 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 5 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 6 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 8 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Tracked 8 days  ·  🤖 AI-categorized main > article.action-card > div.card-footer > span.card-tracking
Environment  ·  May 9, 2026 div.sidebar-widget > div.activity-feed > div.activity-item > div.activity-meta
Immigration  ·  May 9, 2026 div.sidebar-widget > div.activity-feed > div.activity-item > div.activity-meta
Foreign Policy  ·  May 9, 2026 div.sidebar-widget > div.activity-feed > div.activity-item > div.activity-meta
A nonpartisan civic record of actions taken against American institutions, valu… div.container > div.footer-inner > div > p.footer-tagline
Admin ↗ div.footer-inner > div > div.footer-links > a.footer-link
© 2026 UNDOTRUMP.COM  ·  NONPARTISAN CIVIC TRACKER  ·  DATA IS NOT PARTISAN — I… footer.site-footer > div.container > div.footer-bottom > span.footer-copy
Restoring America, one record at a time. footer.site-footer > div.container > div.footer-bottom > span.footer-pledge

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
⚡ All Actions (1,032) 🌍 Environment (65) 🏥 Healthcare (75) 🗽 Immigration (96) ✊… aside.sidebar > div.sidebar-widget > div.cat-mobile-select > select.cat-select

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.

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>`
Buttons have an accessible name
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
Links have a discernible name
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
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.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
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 ASIDE CONTENTINFO footer

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

A+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 UndoTrump.com
  • H2 The Record
  • H3 Trump Pardons Public Corruption Convicts While Dismantling Watchdog Office
  • H3 Second Circuit Rejects Trump No-Bond Immigration Detention Policy
  • H3 US Cancels Visas for Costa Rican Newspaper Board Members
  • H3 Federal Court Restricts Mifepristone Access via Telehealth
  • H3 FDA Authorizes Fruit-Flavored Vapes for Adults
  • H3 DHS Closes Immigration Detention Watchdog Office
  • H3 Education Department Launches Title IX Investigation into Smith College
  • H3 Trump Administration Tightens Green Card Rules on Political Speech
  • H3 U.S. Fast-Tracks $8.6 Billion Arms Deals to Mideast Partners
  • H3 Judge Blocks Trump Administration from Deporting Yemeni Refugees
A+
Heading Text Quality
All 12 heading(s) have substantive, well-formed text
PASS
All 12 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback