Skip to content
https://amtrak.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
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: #ffffff
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
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.
C
Heading Hierarchy
Action
52 headings, 2 skip(s)
REVIEW
52 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
Info::
1 hidden heading(s) (aria-hidden)
  • H2 Browse by Region
  • H2 Planning & Booking
  • H2 Onboard
  • H2 Deals & Promotions
  • H2 Everyday Discounts
  • H2 Vacations & Rail Tours
  • H2 Multi-Ride & Rail Passes
  • H2 Amtrak Guest Rewards
  • H2 Program Overview
  • H2 Our Credit Cards
  • H2 {{initials}}
  • H2 Hi, {{firstName}}
  • H2 Guest Rewards Account
  • H2 Program Overview
  • H2 Our Credit Cards
  • H4 FIND TRIP skipped
  • H1 Book Flex Fares & Travel With Ease
  • H2 Deals & Promotions
  • H3 Save up to 60% off small group travel with Share Fares.
  • H2 Earn 20,000 bonus points Must apply here for this offer. Offers vary elsewhere.^
  • H3 Seniors and students save on travel.
  • H3 Go together for less. Kids ride for 50% off.
  • H2 Onboard Experience
  • H3 Never Ride in the Middle Seat
  • H3 Relax in a First Class Private Room
  • H3 Enjoy Food and Beverages Onboard
  • H3 Bring Your Bags for Free
  • H2 Travel Tools
  • H2 Trip Planning Map
  • H3 Discover more of America with our trip planning map.
  • H2 Track Your Train
  • H3 Check train status and track your train's location.
  • H2 Travel Easier
  • H3 With the Amtrak app.
  • H2 Amtrak RideReserve for Multi-Ride Passes
  • H4 About Amtrak skipped
  • H4 Traveling with Us
  • H4 Site Tools
  • H4 social media icons
  • H2 Amtrak Guest Rewards Amtrak Guest Rewards Terms and Conditions Have Changed
  • H3 (empty)
  • H2 Forgot Password?
  • H3 Question 1 of 2
  • H3 Question 2 of 2
  • H3 Question 2 of 2
  • H2 Manage Cookie Preferences
  • H3 (empty)
  • H4 Strictly Necessary Cookies
  • H4 Targeting Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H3 Cookie List

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
Alt Text Quality
2 of 56 images have issues
REVIEW
2 of 56 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
42 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
56 images 12 good alt text 42 decorative 2 missing
IssueCount
missing2 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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | Amtrak ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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 Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
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)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h2 Planning & Booking
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Onboard
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Deals & Promotions
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Everyday Discounts
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Vacations & Rail Tours
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Multi-Ride & Rail Passes
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Amtrak Guest Rewards
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Program Overview
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Credit Cards
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hi, {{firstName}}
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Guest Rewards Account
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Program Overview
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Credit Cards
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Deals & Promotions
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Earn 20,000 bonus points Must apply here…
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Onboard Experience
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Travel Tools
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trip Planning Map
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Track Your Train
2.54:1
#000000
on
#00537E
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Browse by Region5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Planning & Booking2.54:13.0:1
#000000
#00537E
Fail
h2 Onboard2.54:13.0:1
#000000
#00537E
Fail
h2 Deals & Promotions2.54:13.0:1
#000000
#00537E
Fail
h2 Everyday Discounts2.54:13.0:1
#000000
#00537E
Fail
h2 Vacations & Rail Tou…2.54:13.0:1
#000000
#00537E
Fail
h2 Multi-Ride & Rail Pa…2.54:13.0:1
#000000
#00537E
Fail
h2 Amtrak Guest Rewards2.54:13.0:1
#000000
#00537E
Fail
h2 Program Overview2.54:13.0:1
#000000
#00537E
Fail
h2 Our Credit Cards2.54:13.0:1
#000000
#00537E
Fail
h2 Hi, {{firstName}}2.54:13.0:1
#000000
#00537E
Fail
h2 Guest Rewards Accoun…2.54:13.0:1
#000000
#00537E
Fail
h2 Program Overview2.54:13.0:1
#000000
#00537E
Fail
h2 Our Credit Cards2.54:13.0:1
#000000
#00537E
Fail
h2 Deals & Promotions2.54:13.0:1
#000000
#00537E
Fail
h2 Earn 20,000 bonus po…2.54:13.0:1
#000000
#00537E
Fail
h2 Onboard Experience2.54:13.0:1
#000000
#00537E
Fail
h2 Travel Tools2.54:13.0:1
#000000
#00537E
Fail
h2 Trip Planning Map2.54:13.0:1
#000000
#00537E
Fail
h2 Track Your Train2.54:13.0:1
#000000
#00537E
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 80/100 — 7 failing, 28 passed
REVIEW
80

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
One-Way div.ff-top-navbar > am-dropdown.dropdown_menu > div.ng-tns-c896518535-0 > div.ng-tns-c896518535-0
Rail Passes div#purchaseTicket > div.tab-container > div.ff-top-navbar > button.ff-top-navbar__button
Auto Train div#purchaseTicket > div.tab-container > div.ff-top-navbar > a.ff-top-navbar__button
div.d-flex > div.departs-container > am-form-field-new.ads-relative > input#am-form-field-control-4 div.d-flex > div.departs-container > am-form-field-new.ads-relative > input#am-form-field-control-4
1 Traveler app-traveler > am-dropdown.ng-tns-c896518535-2 > div.ng-tns-c896518535-2 > div.ng-tns-c896518535-2

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.am-container > div.nav-container > div.collapse > ul.navbar-nav div.am-container > div.nav-container > div.collapse > ul.navbar-nav
BOOK TRAIN STATUS MY TRIP nav#tabs-c3a2de9be6 > div.am-container > div.nav-container > ul.navbar-nav
One-Way Rail Passes Auto Train amt-md-farefinder > div.md-farefinder > div#purchaseTicket > div.tab-container

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Seating div.tabs > div#tabs-3e85a66cb4 > ol.cmp-tabs__tablist > li#tabs-3e85a66cb4-item-84ec762294-tab

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Use Points div.d-flex > div.redeemlabelfare-finder-options-apply-button > label.mb-2 > small#usepoints
From div.from-station > station-search > am-form-field-new#autocomplete-combox__0 > label#am-label-3
To div.to-station > station-search > am-form-field-new#autocomplete-combox__1 > label#am-label-4
Depart Date div.d-flex > div.departs-container > am-form-field-new.ads-relative > label#am-label-0
Return Date div.farefinder-datepickers > div.d-flex > div.align-self-center > button.d-block

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
About Amtrak div.footer-list > div.general-column1 > div.listitem > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.collapse > ul.navbar-nav > li.nav-item > a#guest-reward-desktop div.collapse > ul.navbar-nav > li.nav-item > a#guest-reward-desktop
div.collapse > ul.navbar-nav > li.nav-item > a#need-help-desktop div.collapse > ul.navbar-nav > li.nav-item > a#need-help-desktop

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●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.
●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
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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 `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
○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
○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.
○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.
A
Landmark Structure
12 landmarks
PASS
12 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.
Info::
Skip navigation link present
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

A
Form Accessibility
1 of 46 controls have issues
PASS
1 of 46 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
45 control(s) properly labeled
46 controls
45 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputStationRouteSearchtextPlease enter station name or codearia-label
#am-form-field-control-16textFrom stationaria-label
#am-form-field-control-18textTo stationaria-label
#am-form-field-control-20inputDeparture Date in MM/DD/YYYY formataria-label
#am-form-field-control-22inputDeparture Date in MM/DD/YYYY formataria-label
#am-form-field-control-24inputReturn Date in MM/DD/YYYY formataria-label
#askJulietextWhat can I help you with?for/id
#am-form-field-control-12textdeparture stationaria-label
#am-form-field-control-14textTo staionaria-label
#res-numberinputReservation/Ticket Numberaria-label
#am-form-field-control-0textFromaria-label
#am-form-field-control-2textToaria-label
#am-form-field-control-4inputDepart Datefor/id
#am-form-field-control-6inputDepart Datefor/id
#am-form-field-control-8inputReturn Datefor/id
carouselProgressBtnradionone
carouselProgressBtnradionone
carouselProgressBtnradionone
carouselProgressBtnradionone
#signin-radioradioSign Infor/id
usernameemailEmail or Guest Rewards #none
passwordpasswordPassword Passwords should be at least 10 characters long and include 1 uppercase and 1 lowercase alpha character, 1 number and 1 special character. Passwords are case sensitive.none
#signup-radioradioJoinfor/id
firstNameinputFirst Namenone
lastNameinputLast Namenone
passwordpasswordPassword Passwords should be at least 10 characters long and include 1 uppercase and 1 lowercase alpha character, 1 number and 1 special character. Passwords are case sensitive.none
confirmPasswordpasswordConfirm Passwordnone
emailAddressemailEmail Addressnone
_cmscountryselectCountrynone
emailCommunicationOptinradionone
emailCommunicationOptinradionone
_nameinputEmail or Member #none
questioninputForgot Password Stepnone
questioninputForgot Password Stepnone
questioninputForgot Password Stepnone
questioninputForgot Password Stepnone
newPasswordpasswordNew Password Please enter a password. Your password must be at least 8 characters long, include at least 1 alpha character, and include at least 1 number or special character (- ? . _ @ " $ # ,). Passwords are case sensitive.none
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

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

Send Feedback