Skip to content
https://house.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ PNG Icons Present
✗ 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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Form Accessibility
Action
4 of 10 controls have issues
REVIEW
4 of 10 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="search" id="header-site-search-mobile">; <input type="submit" name="Enter">; <input type="submit" id="homepage-representatives-submit">; <input type="submit" id="homepage-findrep-submit">
Info::
6 control(s) properly labeled
10 controls
6 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#searchtextSearch:none
#header-find-rep-zip-codetextEnter your zip code:none
#search-formatselectSearch Sourcefor/id
#billsearchfieldtextSearch Textfor/id
#goToRepresentativeselectVisit Your Representative's Website:for/id
#ZIPtextEnter your zip codefor/id
#header-site-search-mobiletext(none)none
#homepage-representatives-submitsubmit(none)none
Entersubmit(none)none
#homepage-findrep-submitsubmit(none)none

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

<input type="text" name="search" id="header-site-search-mobile">; <input type="submit" name="Enter">; <input type="submit" id="homepage-representatives-submit">; <input type="submit" id="homepage-findrep-submit">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
title Homepage | house.gov
1.28:1
#000000
on
#021E46
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.65:1
#000000
on
#013363
needs 4.5:1 (normal text)
16px · top of page (header area)
a house.gov
1.59:1
#000000
on
#01305E
needs 4.5:1 (normal text)
16px · top of page (header area)
label Search:
1.55:1
#000000
on
#452143
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
button Search
2.58:1
#000000
on
#A40101
needs 4.5:1 (normal text)
16px · above the fold
div Find Your Representative
1.87:1
#000000
on
#133B6D
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 Legislative Activity21.00:13.0:1
#000000
#FFFFFF
Pass
h1 House Overview21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Most Recent Votes21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Search Congress.gov21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Representatives21.00:13.0:1
#000000
#FFFFFF
Pass
h2 View Representatives…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Leadership21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Republican Leadershi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Democratic Leadershi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Committees21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Officers and Organiz…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Congressional Partne…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Public Disclosure21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Life at the House21.00:13.0:1
#000000
#FFFFFF
Pass
title Homepage | house.gov1.28:14.5:1
#000000
#021E46
Fail
a Skip to main content1.65:14.5:1
#000000
#013363
Fail
a house.gov1.59:14.5:1
#000000
#01305E
Fail
label Search:1.55:14.5:1
#000000
#452143
Fail
button Search2.58:14.5:1
#000000
#A40101
Fail
div Find Your Representa…1.87:14.5:1
#000000
#133B6D
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.

A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
1 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "block-mainnavigation-menu" 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

A
Heading Hierarchy
56 headings
PASS
56 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Legislative Activity
  • H2 Most Recent Votes
  • H2 Search Congress.gov
  • H1 House Overview duplicate H1
  • H2 Representatives
  • H2 View Representatives by State
  • H2 Leadership
  • H2 Speaker of the House: Rep. Mike Johnson(link is external)
  • H2 Republican Leadership
  • H3 Majority Leader(link is external)
  • H4 Rep. Steve Scalise
  • H3 Majority Whip(link is external)
  • H4 Rep. Tom Emmer
  • H3 Republican Conference Chairman(link is external)
  • H4 Rep. Lisa McClain
  • H3 Republican Policy Committee Chairman(link is external)
  • H4 Rep. Jay Obernolte
  • H2 Democratic Leadership
  • H3 Democratic Leader(link is external)
  • H4 Rep. Hakeem Jeffries
  • H3 Democratic Whip(link is external)
  • H4 Rep. Katherine Clark
  • H3 Democratic Caucus Chairman(link is external)
  • H4 Rep. Pete Aguilar
  • H3 Democratic Caucus Vice Chair(link is external)
  • H4 Rep. Ted Lieu
  • H3 Assistant Democratic Leader(link is external)
  • H4 Rep. Joe Neguse
  • H2 Committees
  • H2 Officers and Organizations
  • H2 Chaplain of the House(link is external)
  • H2 Chief Administrative Officer(link is external)
  • H2 Clerk of the House(link is external)
  • H2 Sergeant at Arms
  • H2 General Counsel(link is external)
  • H2 Historian of the House(link is external)
  • H2 Inspector General
  • H2 Office of Congressional Conduct(link is external)
  • H2 Parliamentarian of the House
  • H2 Legislative Counsel(link is external)
  • H2 Congressional Partners
  • H2 Architect of the Capitol(link is external)
  • H2 Capitol Police(link is external)
  • H2 Congressional Budget Office(link is external)
  • H2 Government Accountability Office(link is external)
  • H2 Government Printing Office(link is external)
  • H2 Library of Congress(link is external)
  • H2 National Archives(link is external)
  • H2 United States Senate(link is external)
  • H2 Public Disclosure
  • H2 Financial Disclosure Reports(link is external)
  • H2 Foreign Travel Reports(link is external)
  • H2 Gift Travel Filings(link is external)
  • H2 Legal Expense Fund Disclosures(link is external)
  • H2 Statement of Disbursements
  • H2 Life at the House

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

A+
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
17 image(s) with good alt text
17 images 17 good alt text
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 34 passed
PASS
97

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.

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
Accessibility section#block-footer-menu > ul.menu > li.expanded > a
Contact Webmaster section#block-footer-menu > ul.menu > li.expanded > a
Feature Stories section#block-footer-menu > ul.menu > li.expanded > a
Privacy Policy section#block-footer-menu > ul.menu > li.expanded > a
Site Map section#block-footer-menu > ul.menu > li.expanded > a
Site Tools section#block-footer-menu > ul.menu > li.expanded > a
Terms of Use section#block-footer-menu > ul.menu > li.expanded > a
Watch live.house.gov section#block-footer-menu > ul.menu > li.expanded > a

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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●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
●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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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.
○`[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 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 type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○`<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
○Identical links have the same purpose.
○`<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