Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 4 REVIEW 3 FIX

Alt Text Quality

Action

11 of 11 images have issues

FIX

11 of 11 images have issues

11 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

11 image-in-link without alt text

An image inside a link with no alt creates an empty link.

11 images 11 missing

Issue	Count
missing	11 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

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #9b2347

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Link & Button Quality

Action

12 issue(s) across 90 links and 7 buttons

REVIEW

12 issue(s) across 90 links and 7 buttons

11 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /congress/votes/119-2026/h131; /congress/votes/119-2026/h129; /congress/votes/119-2026/h128; /congress/votes/119-2026/h127; /congress/votes/119-2026/h126; /congress/bills/119/hr6956; /congress/bills/119/hr5366; /congress/bills/119/hr227; /congress/bills/119/hr7971; /congress/bills/119/hr6495 (+1 more)

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /congress/bills/ ("More")

78 link(s) with descriptive text

90 links

11 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/congress/bills/	More	generic text	Replace with descriptive text
Before: More Suggested: Bills
/congress/votes/119-2026/h131	(empty)	empty	Add link text or aria-label
/congress/votes/119-2026/h129	(empty)	empty	Add link text or aria-label
/congress/votes/119-2026/h128	(empty)	empty	Add link text or aria-label
/congress/votes/119-2026/h127	(empty)	empty	Add link text or aria-label
/congress/votes/119-2026/h126	(empty)	empty	Add link text or aria-label
/congress/bills/119/hr6956	(empty)	empty	Add link text or aria-label
/congress/bills/119/hr5366	(empty)	empty	Add link text or aria-label
/congress/bills/119/hr227	(empty)	empty	Add link text or aria-label
/congress/bills/119/hr7971	(empty)	empty	Add link text or aria-label
/congress/bills/119/hr6495	(empty)	empty	Add link text or aria-label
/congress/bills/119/hr6506	(empty)	empty	Add link text or aria-label

85 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/congress/votes/119-2026/h131; /congress/votes/119-2026/h129; /congress/votes/119-2026/h128; /congress/votes/119-2026/h127; /congress/votes/119-2026/h126; /congress/bills/119/hr6956; /congress/bills/119/hr5366; /congress/bills/119/hr227; /congress/bills/119/hr7971; /congress/bills/119/hr6495 (+1 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/congress/bills/ ("More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Breadcrumb navigation detected

Got: aria-label

Skip navigation link detected

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs aria-label navigation

Skip Link Skip link detected

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

4 <nav> landmark(s) found

1 of 4 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

23 headings

PASS

23 headings

Single H1 present

H1 We’re tracking the activities of the United States Congress and the White House to make a more open and accountable government.
H2 Legislative Preview for April 20, 2026
H2 FISA Section 702 Reauthorization
H2 Find your representative and senators:
H2 Find legislation that affects you:
H3 H.Res. 1189: Providing for consideration of the bill (H.R. 4690) to amend the Energy Conservation and Production Act to repeal certain Federal building energy efficiency performance standards, and for
H3 S. 1020: A bill to require the Federal Energy Regulatory Commission to extend the time period during which licensees are required to commence construction of certain hydropower projects.
H3 H.R. 2493: Improving Care in Rural America Reauthorization Act of 2025
H3 H.R. 5201: Kari’s Law Reporting Act
H3 H.R. 5200: Emergency Reporting Act
H3 H.R. 6956: BARCODE Efficiency Act
H3 H.R. 5366: Doug LaMalfa Federal Disaster Tax Relief Certainty Act
H3 H.R. 227: Clergy Act
H3 H.R. 7971: Taxpayer Experience Improvement Act
H3 H.R. 6495: Taxpayer Notification and Privacy Act
H3 H.R. 6506: Taxpayer Due Process Enhancement Act
H3 H.R. 8250: Parents Decide Act
H3 H.R. 1897: ESA Amendments Act of 2025
H3 Roll Call Votes
H3 H.J.Res. 140: Providing for congressional disapproval under chapter 8 of title 5, United States Code, of the rule submitted by the Bureau of Land ...
H3 H.Res. 1155: Impeaching Donald J. Trump, President of the United States, for high crimes and misdemeanors.
H3 H.R. 8230: NO TOD Act
H2 [error message]

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#master_search_q	search	Search	aria-label
#address	text	Find your representative and senators: Enter your home address:	for/id
#bill-subject-area	select	Find legislation that affects you: Select a subject area to search and get alerts:	for/id

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found -- GovTrack.us ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 We’re tracking the…	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h1 and the	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h1 to make a more	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h1 and	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h1 government.	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h2 Legislative Preview …	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h2 FISA Section 702 Rea…	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h2 Find your representa…	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h2 Find legislation tha…	17.96:1	3.0:1	#000000	#F0EDE6	Pass
h2 [error message]	17.96:1	3.0:1	#000000	#F0EDE6	Pass
title GovTrack.us: Trackin…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Hide The Ads ▶	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Log In ▶	13.35:1	4.5:1	#000000	#C6CFDB	Pass
button Your Account	13.60:1	4.5:1	#000000	#CED0D4	Pass
a Your Subscriptions &…	14.04:1	4.5:1	#000000	#D2D3D7	Pass
a Your Positions	14.46:1	4.5:1	#000000	#D5D6DA	Pass
a Your Docket	14.90:1	4.5:1	#000000	#D9D9DB	Pass
a Account Settings	16.03:1	4.5:1	#000000	#E0E1E1	Pass
a Log Out	14.23:1	4.5:1	#000000	#D1D5D9	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+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 27 passed

PASS

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.