Skip to content
https://tsa.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
5
REVIEW
1
PASS
7
INFO
0
Checks
13
7 PASS 1 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 3 <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.
B
Heading Hierarchy
30 headings, 1 skip(s)
REVIEW
30 headings, 1 skip(s)
Warning::
Multiple H1 headings (13 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.
  • H3 notice
  • H3 Travel
  • H3 Media
  • H3 About
  • H3 For Industry
  • H3 Contact
  • H1 Serve with Honor, Travel with Ease
  • H1 TSA successfully rolls out TSA ConfirmID duplicate H1
  • H1 TSA ConfirmID: Don’t have a REAL ID or acceptable form of ID? duplicate H1
  • H1 TSA Introduces New $45 Fee Option for Travelers Without REAL ID duplicate H1
  • H1 Families on the Fly duplicate H1
  • H1 DHS Ends ‘Shoes-Off’ Travel Policy duplicate H1
  • H1 Serve with Honor, Travel with Ease duplicate H1
  • H1 TSA successfully rolls out TSA ConfirmID duplicate H1
  • H1 TSA ConfirmID: Don’t have a REAL ID or acceptable form of ID? duplicate H1
  • H1 TSA Introduces New $45 Fee Option for Travelers Without REAL ID duplicate H1
  • H1 Families on the Fly duplicate H1
  • H1 DHS Ends ‘Shoes-Off’ Travel Policy duplicate H1
  • H1 Serve with Honor, Travel with Ease duplicate H1
  • H3 TSA ConfirmID Alert skipped
  • H2 REAL ID
  • H2 TSA Cares
  • H2 Customer Service
  • H2 TSA PreCheck®
  • H2 What Can I Bring?
  • H3 Travel Tips
  • H2 TSA Strategy
  • H2 Latest News
  • H2 Identification
  • H2 Passenger Support

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

A+
Landmark Structure
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" SEARCH MAIN ASIDE CONTENTINFO footer
A
Alt Text Quality
2 of 28 images have issues
PASS
2 of 28 images have issues
Warning::
2 image(s) with generic alt text
Info::
26 image(s) with good alt text
28 images 26 good alt text 2 generic
IssueCount
generic2 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="query">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
querysearch(Enter your search terms)placeholder only

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

<input type="search" name="query">

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

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Lock ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /profiles/tsad8_gov/themes/custom/tsa_uswds/assets/css/print.css?tduu13
Print Stylesheet ✓ Print Optimized
Print stylesheet /profiles/tsad8_gov/themes/custom/tsa_uswds/assets/css/print.css?tduu13 ✓Inline @media print Not detected ✗
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)
ElementRatioRequiredFGBGResult
h1 Serve with Honor, Tr…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 TSA successfully rol…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 TSA ConfirmID: Don…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 TSA Introduces New $…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Families on the Fly21.00:13.0:1
#000000
#FFFFFF
Pass
h1 DHS Ends ‘Shoes-Of…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Serve with Honor, Tr…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 TSA successfully rol…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 TSA ConfirmID: Don…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 TSA Introduces New $…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Families on the Fly21.00:13.0:1
#000000
#FFFFFF
Pass
h1 DHS Ends ‘Shoes-Of…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Serve with Honor, Tr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 REAL ID21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TSA Cares21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Customer Service21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TSA PreCheck®21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What Can I Bring?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TSA Strategy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest News21.00:13.0: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+
Lighthouse Accessibility Audits
Score 99/100 — 1 failing, 30 passed
PASS
99

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.

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
TSA ConfirmID Alert div.grid-row > div.paragraph > div.usa-alert__body > h3.usa-alert__heading

These are opportunities to improve keyboard navigation in your application.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[accesskey]` values are unique
●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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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