United Airlinesunited.com
Accessibility Score
Issues Found
Issues Found
ModerateAll page content should be contained by landmarks3 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<div class="app-containers-AccesibilityManager-styles__visuallyHidden--cRUBK">Navigated to: United Airlines - Airline Tickets, Travel Deals and Flights</div>
Fix any of the following:
- Some page content is not contained by landmarks
<h1 class="visuallyHidden">Welcome to United.com</h1>
Fix any of the following:
- Some page content is not contained by landmarks
<img alt="ActivityTags" src="https://ad.doubleclick.net/ddm/activity/src=13275716;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=${GDPR};gdpr_consent=${GDPR_CONSENT_755};type=mphome;cat=homepage;ord=3214097585423499?" width="1" height="1" border="0">Fix any of the following:
- Some page content is not contained by landmarks
MinorUsers should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Failing Elements
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=4,user-scalable=yes">
Fix any of the following:
- <meta> tag limits zooming on mobile devices
Passed Audits
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en" class="notranslate" translate="no" data-react-helmet="lang">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en" class="notranslate" translate="no" data-react-helmet="lang">
<li> elements must be contained in a <ul> or <ol>20 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li class="app-components-GlobalHeader-NavbarItems-styles__navbarItem--cv13u">
<li class="app-components-GlobalHeader-NavbarItems-styles__navbarItem--cv13u">
<li class="app-components-GlobalHeader-NavbarItems-styles__navbarItem--cv13u">
<li class="app-components-GlobalHeader-NavbarItems-styles__navbarItem--cv13u">
<li class="app-components-GlobalHeader-NavbarItems-styles__navbarItem--cv13u">
<li class="app-components-GlobalHeader-NavbarItems-styles__navbarItem--cv13u">
<li class="app-components-GlobalHeader-UserMenu-styles__userMenuLocalizeButton--mbovF app-components-GlobalHeader-UserMenu-styles__userMenuContainerItem--y0x18">
<li class="app-components-GlobalHeader-UserMenu-styles__userMenuContainerItem--y0x18">
<li class="app-components-GlobalHeader-UserMenu-styles__userMenuContainerItem--y0x18">
<li class="">
Showing first 10 of 20 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements4 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul class="app-components-GlobalHeader-NavbarItems-styles__navbar--cfZxK">
<ul class="app-components-GlobalHeader-UserMenu-styles__userMenuContainer--q0loV">
<ul class="atm-c-radio-field__list">
<ul class="atm-u-margin-none atm-u-padding-none app-components-PopularFooter-styles__mptContainer--XccVs">
All page content should be contained by landmarks435 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div id="app">
<div>
<div>
<div>
<div><div><div><div></div></div></div></div>
<div><div><div></div></div></div>
<div><div></div></div>
<div></div>
<div tabindex="-1">
<div class="page app-containers-App-AppHeader-styles__normal--YuIZm">
Showing first 10 of 435 audited elements.
Alternative text of images should not be repeated as text3 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img alt="United logo link to homepage" data-test-id="mileage-plus-logo" src="/2500e4e62233fbfe8ac6.unitedLogoNew.svg">
<img alt="Banner: 100 years of United logo" src="/de03c2916e8b84cccdb6.u100-DesktopWeb.webp" class="app-components-GlobalFooter-united100Logo-styles__united100LogoImage--rkFF3 app-components-GlobalFooter-united100Logo-styles__united100LogoImageDesktop--o4XXW" loading="lazy" fetchpriority="low">
<img alt="ActivityTags" src="https://ad.doubleclick.net/ddm/activity/src=13275716;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=${GDPR};gdpr_consent=${GDPR_CONSENT_755};type=mphome;cat=homepage;ord=3214097585423499?" width="1" height="1" border="0">ARIA attributes must be used as specified for the element's role80 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<nav aria-label="primary" class="app-components-GlobalHeader-NavbarItems-styles__navbarContainer--Gq2zL app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarContainer--wfHRp">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_booking_3" aria-expanded="false" data-name="id_booking_3" type="button">
<button class="atm-c-btn app-compon..." id="" aria-controls="id_manage_my_trips_4" aria-expanded="false" data-name="id_manage_my_trips_4" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_travel_info_5" aria-expanded="false" data-name="id_travel_info_5" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_mileageplus_6" aria-expanded="false" data-name="id_mileageplus_6" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_deals_7" aria-expanded="false" data-name="id_deals_7" type="button">
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<button class="atm-c-btn app-contai..." aria-label="Currently in English..." type="button">
<a aria-label="Search, opens in a new tab" class="atm-c-text-link atm-c-text-link app-components-GlobalHeader-UserMenu-styles__userMenuLocalizeButtonSeach--grzAE" target="_blank" href="/en/us/website-search">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__loginButton--tbffq atm-c-btn--bare" aria-label="Sign in" id="loginButton" type="button">
Showing first 10 of 80 audited elements.
ARIA attributes must conform to valid names80 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<nav aria-label="primary" class="app-components-GlobalHeader-NavbarItems-styles__navbarContainer--Gq2zL app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarContainer--wfHRp">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_booking_3" aria-expanded="false" data-name="id_booking_3" type="button">
<button class="atm-c-btn app-compon..." id="" aria-controls="id_manage_my_trips_4" aria-expanded="false" data-name="id_manage_my_trips_4" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_travel_info_5" aria-expanded="false" data-name="id_travel_info_5" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_mileageplus_6" aria-expanded="false" data-name="id_mileageplus_6" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_deals_7" aria-expanded="false" data-name="id_deals_7" type="button">
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<button class="atm-c-btn app-contai..." aria-label="Currently in English..." type="button">
<a aria-label="Search, opens in a new tab" class="atm-c-text-link atm-c-text-link app-components-GlobalHeader-UserMenu-styles__userMenuLocalizeButtonSeach--grzAE" target="_blank" href="/en/us/website-search">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__loginButton--tbffq atm-c-btn--bare" aria-label="Sign in" id="loginButton" type="button">
Showing first 10 of 80 audited elements.
ARIA attributes must conform to valid values80 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<nav aria-label="primary" class="app-components-GlobalHeader-NavbarItems-styles__navbarContainer--Gq2zL app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarContainer--wfHRp">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_booking_3" aria-expanded="false" data-name="id_booking_3" type="button">
<button class="atm-c-btn app-compon..." id="" aria-controls="id_manage_my_trips_4" aria-expanded="false" data-name="id_manage_my_trips_4" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_travel_info_5" aria-expanded="false" data-name="id_travel_info_5" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_mileageplus_6" aria-expanded="false" data-name="id_mileageplus_6" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_deals_7" aria-expanded="false" data-name="id_deals_7" type="button">
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<button class="atm-c-btn app-contai..." aria-label="Currently in English..." type="button">
<a aria-label="Search, opens in a new tab" class="atm-c-text-link atm-c-text-link app-components-GlobalHeader-UserMenu-styles__userMenuLocalizeButtonSeach--grzAE" target="_blank" href="/en/us/website-search">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__loginButton--tbffq atm-c-btn--bare" aria-label="Sign in" id="loginButton" type="button">
Showing first 10 of 80 audited elements.
ARIA hidden element must not be focusable or contain focusable elements82 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-right" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon atm-c-icon__size-2" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#language" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#close" aria-hidden="true"></use></svg>
<svg class="atm-c-icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#search" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon atm-c-icon__size-1" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#traveler" aria-hidden="true"></use></svg>
Showing first 10 of 82 audited elements.
ARIA role should be appropriate for the element169 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-down" aria-hidden="true"></use></svg>
<svg class="atm-c-icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#caret-right" aria-hidden="true"></use></svg>
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<svg class="atm-c-icon atm-c-btn__icon atm-c-icon__size-2" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#language" aria-hidden="true"></use></svg>
<svg class="atm-c-icon atm-c-btn__icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#close" aria-hidden="true"></use></svg>
<svg class="atm-c-icon" focusable="false" role="presentation" aria-hidden="true"><use href="/8e83f6f0764fbd8580db.spritemap.svg#search" aria-hidden="true"></use></svg>
Showing first 10 of 169 audited elements.
ARIA roles used must conform to valid values43 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<div class="app-components-Announcements-announcements__visuallyhidden--qY1pM" role="status" aria-live="polite" aria-atomic="true"></div>
<main role="main" class="app-containers-HomePage-styles__marginTop--RFtzz">
<div class="app-components-Announcements-announcements__visuallyhidden--qY1pM" role="status" aria-live="polite" aria-atomic="true"></div>
<div role="tablist" class="app-components-BookTravel-bookTravel__travelNav--Qo_b2" aria-label="A tabs widget: Book, Flight status, Check-in, My trip; note, use arrow keys to navigate between tabs and enter/space key to activate and navigate through the tab content">
<button id="travelTab" tabindex="0" role="tab" aria-selected="true" aria-controls="travelTab-panel" name="travelTab" class="app-components-BookTravel-bookTravel__flightContent--E4baF" aria-label="Book a flight or trip package">
<button id="statusTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="statusTab-panel" name="statusTab" aria-label="Check flight status">
<button id="checkInTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="checkInTab-panel" aria-label="Check in a flight ">
<button id="tripsTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="tripsTab-panel" aria-label="View and manage current trips ">
<section id="travelTab-panel" role="tabpanel" aria-hidden="false" aria-describedby="travelTab">
Showing first 10 of 43 audited elements.
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body class="body">
autocomplete attribute must be used correctly4 elements
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<input class="atm-c-text-input atm..." id="bookFlightOriginInpu..." type="text" placeholder="Origin" autocomplete="off" aria-invalid="false" autocapitalize="none" autocorrect="off" role="combobox" spellcheck="false" aria-autocomplete="both" aria-expanded="false" aria-activedescendan...="" ...>
<input class="atm-c-text-input atm..." id="bookFlightDestinatio..." type="text" placeholder="Destination" autocomplete="off" aria-invalid="false" autocapitalize="none" autocorrect="off" role="combobox" spellcheck="false" aria-autocomplete="both" aria-expanded="false" aria-activedescendan...="" ...>
<input type="text" class="atm-c-resizing-input atm-c-datepicker_input" required="" id="DepartDate" aria-labelledby="c7599571-6edb-4534-8574-b52f5b821863_label" aria-invalid="false" autocomplete="off" placeholder="Departure" value="Jun 26">
<input type="text" class="atm-c-resizing-input atm-c-datepicker_input" required="" id="ReturnDate" aria-labelledby="c7599571-6edb-4534-8574-b52f5b821863_label" aria-invalid="false" autocomplete="off" placeholder="Return" value="Jun 28">
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header class="app-containers-App-AppHeader-styles__floatingHeader--THurE">
Buttons must have discernible text30 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_booking_3" aria-expanded="false" data-name="id_booking_3" type="button">
<button class="atm-c-btn app-compon..." id="" aria-controls="id_manage_my_trips_4" aria-expanded="false" data-name="id_manage_my_trips_4" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_travel_info_5" aria-expanded="false" data-name="id_travel_info_5" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_mileageplus_6" aria-expanded="false" data-name="id_mileageplus_6" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_deals_7" aria-expanded="false" data-name="id_deals_7" type="button">
<button class="atm-c-btn app-contai..." aria-label="Currently in English..." type="button">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__loginButton--tbffq atm-c-btn--bare" aria-label="Sign in" id="loginButton" type="button">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__closeButtonTT--eLYpx atm-c-btn--bare" aria-label="Close button">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__signInButtonTT--XEYtE atm-c-btn--primary" type="button"><span class="atm-c-btn__text">Sign in</span></button>
<button class="atm-c-btn app-components-OmniCart-omniCart__btnCart--s8lp4 atm-c-btn--bare atm-c-btn--inverted-focus-state" aria-label="View Cart, click to view list of recently searched saved trips." type="button">
Showing first 10 of 30 audited elements.
Certain ARIA roles must be contained by particular parents8 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Audit Elements
<button id="travelTab" tabindex="0" role="tab" aria-selected="true" aria-controls="travelTab-panel" name="travelTab" class="app-components-BookTravel-bookTravel__flightContent--E4baF" aria-label="Book a flight or trip package">
<button id="statusTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="statusTab-panel" name="statusTab" aria-label="Check flight status">
<button id="checkInTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="checkInTab-panel" aria-label="Check in a flight ">
<button id="tripsTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="tripsTab-panel" aria-label="View and manage current trips ">
<button id="bookFlightTab" tabindex="0" role="tab" aria-selected="true" aria-controls="bookFlightTab-panel" class="" aria-label="Search and book a flight"><span>Flight</span></button>
<button id="bookPackageTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="bookPackageTab-panel" aria-label="Search and book a United vacation."><span>Packages</span></button>
<button id="bookHotelTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="bookHotelTab-panel" class="app-components-BookFlight-bookFlight__hotelButton--UvTiX" aria-label="Search and book a hotel"><span>Hotel</span></button>
<button id="bookCarTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="bookCarTab-panel" class="app-components-BookFlight-bookFlight__carButton--XTOKJ" aria-label="Search and reserve a car"><span>Car</span></button>
Certain ARIA roles must contain particular children2 elements
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Audit Elements
<div role="tablist" class="app-components-BookTravel-bookTravel__travelNav--Qo_b2" aria-label="A tabs widget: Book, Flight status, Check-in, My trip; note, use arrow keys to navigate between tabs and enter/space key to activate and navigate through the tab content">
<div role="tablist" class="app-components-BookF..." aria-label="Within the Book tab:...">
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer role="contentinfo">
Deprecated ARIA roles must not be used43 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<div class="app-components-Announcements-announcements__visuallyhidden--qY1pM" role="status" aria-live="polite" aria-atomic="true"></div>
<main role="main" class="app-containers-HomePage-styles__marginTop--RFtzz">
<div class="app-components-Announcements-announcements__visuallyhidden--qY1pM" role="status" aria-live="polite" aria-atomic="true"></div>
<div role="tablist" class="app-components-BookTravel-bookTravel__travelNav--Qo_b2" aria-label="A tabs widget: Book, Flight status, Check-in, My trip; note, use arrow keys to navigate between tabs and enter/space key to activate and navigate through the tab content">
<button id="travelTab" tabindex="0" role="tab" aria-selected="true" aria-controls="travelTab-panel" name="travelTab" class="app-components-BookTravel-bookTravel__flightContent--E4baF" aria-label="Book a flight or trip package">
<button id="statusTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="statusTab-panel" name="statusTab" aria-label="Check flight status">
<button id="checkInTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="checkInTab-panel" aria-label="Check in a flight ">
<button id="tripsTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="tripsTab-panel" aria-label="View and manage current trips ">
<section id="travelTab-panel" role="tabpanel" aria-hidden="false" aria-describedby="travelTab">
Showing first 10 of 43 audited elements.
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en" class="notranslate" translate="no" data-react-helmet="lang">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header class="app-containers-App-AppHeader-styles__floatingHeader--THurE">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer role="contentinfo">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main role="main" class="app-containers-HomePage-styles__marginTop--RFtzz">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en" class="notranslate" translate="no" data-react-helmet="lang">
Elements must meet minimum color contrast ratio thresholds66 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<h3 class="atm-c-heading app-components-Ciam-LoginButton-loginButton__tooltipHeading--F8a1c">Sign into your account</h3>
<span class="atm-c-btn__text">Sign in</span>
<span class="atm-c-btn__text">Join now</span>
<span class="app-components-BookTravel-bookTravel__bookTabLabel--Iz_sf">Book<div class="app-components-BookTravel-bookTravel__mobileTabArrow--kPPSq" tabindex="0"><i role="presentation" aria-hidden="true"></i></div></span>
<span class="app-components-BookTravel-bookTravel__bookTabLabel--Iz_sf">Flight status<div class="app-components-BookTravel-bookTravel__mobileTabArrow--kPPSq" tabindex="0"><i role="presentation" aria-hidden="true"></i></div></span>
<span class="app-components-BookTravel-bookTravel__bookTabLabel--Iz_sf">Check-in</span>
<span class="app-components-BookTravel-bookTravel__bookTabLabel--Iz_sf">My trips</span>
<span>Flight</span>
<span>Packages</span>
<span>Hotel</span>
Showing first 10 of 66 audited elements.
Elements must only use permitted ARIA attributes79 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<nav aria-label="primary" class="app-components-GlobalHeader-NavbarItems-styles__navbarContainer--Gq2zL app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarContainer--wfHRp">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_booking_3" aria-expanded="false" data-name="id_booking_3" type="button">
<button class="atm-c-btn app-compon..." id="" aria-controls="id_manage_my_trips_4" aria-expanded="false" data-name="id_manage_my_trips_4" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_travel_info_5" aria-expanded="false" data-name="id_travel_info_5" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_mileageplus_6" aria-expanded="false" data-name="id_mileageplus_6" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_deals_7" aria-expanded="false" data-name="id_deals_7" type="button">
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<button class="atm-c-btn app-contai..." aria-label="Currently in English..." type="button">
<a aria-label="Search, opens in a new tab" class="atm-c-text-link atm-c-text-link app-components-GlobalHeader-UserMenu-styles__userMenuLocalizeButtonSeach--grzAE" target="_blank" href="/en/us/website-search">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__loginButton--tbffq atm-c-btn--bare" aria-label="Sign in" id="loginButton" type="button">
Showing first 10 of 79 audited elements.
Elements must only use supported ARIA attributes80 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<nav aria-label="primary" class="app-components-GlobalHeader-NavbarItems-styles__navbarContainer--Gq2zL app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarContainer--wfHRp">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_booking_3" aria-expanded="false" data-name="id_booking_3" type="button">
<button class="atm-c-btn app-compon..." id="" aria-controls="id_manage_my_trips_4" aria-expanded="false" data-name="id_manage_my_trips_4" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_travel_info_5" aria-expanded="false" data-name="id_travel_info_5" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_mileageplus_6" aria-expanded="false" data-name="id_mileageplus_6" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_deals_7" aria-expanded="false" data-name="id_deals_7" type="button">
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<button class="atm-c-btn app-contai..." aria-label="Currently in English..." type="button">
<a aria-label="Search, opens in a new tab" class="atm-c-text-link atm-c-text-link app-components-GlobalHeader-UserMenu-styles__userMenuLocalizeButtonSeach--grzAE" target="_blank" href="/en/us/website-search">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__loginButton--tbffq atm-c-btn--bare" aria-label="Sign in" id="loginButton" type="button">
Showing first 10 of 80 audited elements.
Elements should not have tabindex greater than zero17 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<div tabindex="-1">
<div data-focus-guard="true" tabindex="-1" style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"></div>
<div data-focus-guard="true" tabindex="-1" style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"></div>
<div data-focus-guard="true" tabindex="-1" style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"></div>
<button id="travelTab" tabindex="0" role="tab" aria-selected="true" aria-controls="travelTab-panel" name="travelTab" class="app-components-BookTravel-bookTravel__flightContent--E4baF" aria-label="Book a flight or trip package">
<button id="statusTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="statusTab-panel" name="statusTab" aria-label="Check flight status">
<button id="checkInTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="checkInTab-panel" aria-label="Check in a flight ">
<button id="tripsTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="tripsTab-panel" aria-label="View and manage current trips ">
<button id="bookFlightTab" tabindex="0" role="tab" aria-selected="true" aria-controls="bookFlightTab-panel" class="" aria-label="Search and book a flight"><span>Flight</span></button>
<button id="bookPackageTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="bookPackageTab-panel" aria-label="Search and book a United vacation."><span>Packages</span></button>
Showing first 10 of 17 audited elements.
Form elements must have labels8 elements
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input id="radiofield-item-id-flightType-0" type="radio" name="flightType" class="atm-c-radio__input" aria-disabled="false" value="roundTrip" checked="">
<input id="radiofield-item-id-flightType-1" type="radio" name="flightType" class="atm-c-radio__input" aria-disabled="false" value="oneWay">
<input id="award" type="checkbox" name="AwardTravel" class="atm-c-checkbox__input" value="">
<input id="flexibleDates" type="checkbox" name="Flexible" class="atm-c-checkbox__input" value="">
<input class="atm-c-text-input atm..." id="bookFlightOriginInpu..." type="text" placeholder="Origin" autocomplete="off" aria-invalid="false" autocapitalize="none" autocorrect="off" role="combobox" spellcheck="false" aria-autocomplete="both" aria-expanded="false" aria-activedescendan...="" ...>
<input class="atm-c-text-input atm..." id="bookFlightDestinatio..." type="text" placeholder="Destination" autocomplete="off" aria-invalid="false" autocapitalize="none" autocorrect="off" role="combobox" spellcheck="false" aria-autocomplete="both" aria-expanded="false" aria-activedescendan...="" ...>
<input type="text" class="atm-c-resizing-input atm-c-datepicker_input" required="" id="DepartDate" aria-labelledby="c7599571-6edb-4534-8574-b52f5b821863_label" aria-invalid="false" autocomplete="off" placeholder="Departure" value="Jun 26">
<input type="text" class="atm-c-resizing-input atm-c-datepicker_input" required="" id="ReturnDate" aria-labelledby="c7599571-6edb-4534-8574-b52f5b821863_label" aria-invalid="false" autocomplete="off" placeholder="Return" value="Jun 28">
Form elements should have a visible label9 elements
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input id="radiofield-item-id-flightType-0" type="radio" name="flightType" class="atm-c-radio__input" aria-disabled="false" value="roundTrip" checked="">
<input id="radiofield-item-id-flightType-1" type="radio" name="flightType" class="atm-c-radio__input" aria-disabled="false" value="oneWay">
<input id="award" type="checkbox" name="AwardTravel" class="atm-c-checkbox__input" value="">
<input id="flexibleDates" type="checkbox" name="Flexible" class="atm-c-checkbox__input" value="">
<input class="atm-c-text-input atm..." id="bookFlightOriginInpu..." type="text" placeholder="Origin" autocomplete="off" aria-invalid="false" autocapitalize="none" autocorrect="off" role="combobox" spellcheck="false" aria-autocomplete="both" aria-expanded="false" aria-activedescendan...="" ...>
<input class="atm-c-text-input atm..." id="bookFlightDestinatio..." type="text" placeholder="Destination" autocomplete="off" aria-invalid="false" autocapitalize="none" autocorrect="off" role="combobox" spellcheck="false" aria-autocomplete="both" aria-expanded="false" aria-activedescendan...="" ...>
<input type="text" class="atm-c-resizing-input atm-c-datepicker_input" required="" id="DepartDate" aria-labelledby="c7599571-6edb-4534-8574-b52f5b821863_label" aria-invalid="false" autocomplete="off" placeholder="Departure" value="Jun 26">
<input type="text" class="atm-c-resizing-input atm-c-datepicker_input" required="" id="ReturnDate" aria-labelledby="c7599571-6edb-4534-8574-b52f5b821863_label" aria-invalid="false" autocomplete="off" placeholder="Return" value="Jun 28">
<select class="atm-c-select atm-c-select-field__control" id="cabinType" name="bookFlightModel.cabinType"><option class="" value="0">Economy</option><option class="" value="1">Premium economy</option><option class="" value="2">Business or First</option></select>
Form field must not have multiple label elements9 elements
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input id="radiofield-item-id-flightType-0" type="radio" name="flightType" class="atm-c-radio__input" aria-disabled="false" value="roundTrip" checked="">
<input id="radiofield-item-id-flightType-1" type="radio" name="flightType" class="atm-c-radio__input" aria-disabled="false" value="oneWay">
<input id="award" type="checkbox" name="AwardTravel" class="atm-c-checkbox__input" value="">
<input id="flexibleDates" type="checkbox" name="Flexible" class="atm-c-checkbox__input" value="">
<input class="atm-c-text-input atm..." id="bookFlightOriginInpu..." type="text" placeholder="Origin" autocomplete="off" aria-invalid="false" autocapitalize="none" autocorrect="off" role="combobox" spellcheck="false" aria-autocomplete="both" aria-expanded="false" aria-activedescendan...="" ...>
<input class="atm-c-text-input atm..." id="bookFlightDestinatio..." type="text" placeholder="Destination" autocomplete="off" aria-invalid="false" autocapitalize="none" autocorrect="off" role="combobox" spellcheck="false" aria-autocomplete="both" aria-expanded="false" aria-activedescendan...="" ...>
<input type="text" class="atm-c-resizing-input atm-c-datepicker_input" required="" id="DepartDate" aria-labelledby="c7599571-6edb-4534-8574-b52f5b821863_label" aria-invalid="false" autocomplete="off" placeholder="Departure" value="Jun 26">
<input type="text" class="atm-c-resizing-input atm-c-datepicker_input" required="" id="ReturnDate" aria-labelledby="c7599571-6edb-4534-8574-b52f5b821863_label" aria-invalid="false" autocomplete="off" placeholder="Return" value="Jun 28">
<select class="atm-c-select atm-c-select-field__control" id="cabinType" name="bookFlightModel.cabinType"><option class="" value="0">Economy</option><option class="" value="1">Premium economy</option><option class="" value="2">Business or First</option></select>
Heading levels should only increase by one2 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="visuallyHidden">Welcome to United.com</h1>
<h2 class="atm-c-heading app-components-PopularFooter-styles__popularFooterHeading--FZS_x atm-c-heading--size-2">Popular topics</h2>
Headings should not be empty3 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="visuallyHidden">Welcome to United.com</h1>
<h3 class="atm-c-heading app-components-Ciam-LoginButton-loginButton__tooltipHeading--F8a1c">Sign into your account</h3>
<h2 class="atm-c-heading app-components-PopularFooter-styles__popularFooterHeading--FZS_x atm-c-heading--size-2">Popular topics</h2>
IDs used in ARIA and labels must be unique35 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<button id="travelTab" tabindex="0" role="tab" aria-selected="true" aria-controls="travelTab-panel" name="travelTab" class="app-components-BookTravel-bookTravel__flightContent--E4baF" aria-label="Book a flight or trip package">
<button id="statusTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="statusTab-panel" name="statusTab" aria-label="Check flight status">
<button id="checkInTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="checkInTab-panel" aria-label="Check in a flight ">
<button id="tripsTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="tripsTab-panel" aria-label="View and manage current trips ">
<section id="travelTab-panel" role="tabpanel" aria-hidden="false" aria-describedby="travelTab">
<button id="bookFlightTab" tabindex="0" role="tab" aria-selected="true" aria-controls="bookFlightTab-panel" class="" aria-label="Search and book a flight"><span>Flight</span></button>
<button id="bookPackageTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="bookPackageTab-panel" aria-label="Search and book a United vacation."><span>Packages</span></button>
<button id="bookHotelTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="bookHotelTab-panel" class="app-components-BookFlight-bookFlight__hotelButton--UvTiX" aria-label="Search and book a hotel"><span>Hotel</span></button>
<button id="bookCarTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="bookCarTab-panel" class="app-components-BookFlight-bookFlight__carButton--XTOKJ" aria-label="Search and reserve a car"><span>Car</span></button>
<div id="bookFlightTab-panel" role="tabpanel" aria-hidden="false" aria-describedby="bookFlightTab">
Showing first 10 of 35 audited elements.
Images must have alternative text3 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img alt="United logo link to homepage" data-test-id="mileage-plus-logo" src="/2500e4e62233fbfe8ac6.unitedLogoNew.svg">
<img alt="Banner: 100 years of United logo" src="/de03c2916e8b84cccdb6.u100-DesktopWeb.webp" class="app-components-GlobalFooter-united100Logo-styles__united100LogoImage--rkFF3 app-components-GlobalFooter-united100Logo-styles__united100LogoImageDesktop--o4XXW" loading="lazy" fetchpriority="low">
<img alt="ActivityTags" src="https://ad.doubleclick.net/ddm/activity/src=13275716;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=${GDPR};gdpr_consent=${GDPR_CONSENT_755};type=mphome;cat=homepage;ord=3214097585423499?" width="1" height="1" border="0">Inline text spacing must be adjustable with custom stylesheets13 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<div data-focus-guard="true" tabindex="-1" style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"></div>
<div data-focus-guard="true" tabindex="-1" style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"></div>
<div data-focus-guard="true" tabindex="-1" style="width: 1px; height: 0px; padding: 0px; overflow: hidden; position: fixed; top: 1px; left: 1px;"></div>
<div class="app-components-CrossfadeImage-crossfadeimage__fader--aXX5X" role="presentation" style="background-image: url("/e12cc94d54b308001cb2.placeholder_desktop.webp");"></div>
<div class="app-components-LoadingIndicatorSpinner-LoadingIndicatorSpinner__loadingIndicatorSpinner--D5XN8" aria-label="Loading..." aria-busy="true" role="alert" style="height: 50px; width: 50px;">
<div style="height: 50px; width: 50px;"></div>
<div style="height: 50px; width: 50px;"></div>
<div style="height: 50px; width: 50px;"></div>
<div style="height: 50px; width: 50px;"></div>
<div style="height: 50px; width: 50px;"></div>
Showing first 10 of 13 audited elements.
Input buttons must have discernible text1 element
Screen reader users cannot understand an input type="button"'s purpose without an accessible name. Unnamed button images provide no description of their destination, purpose, or function, leaving users unable to make informed decisions about activating them.
Audit Elements
<input class="atm-c-text-input atm-c-textfield__input atm-c-text-input--hover" id="e5c0281e-aa35-4540-8309-841d358b4181" type="button" required="" aria-describedby="uaPaxSelectorMainButtonAriaDescription" aria-invalid="false" role="button" value="1 Adult">
Interactive controls must not be nested40 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<img alt="United logo link to homepage" data-test-id="mileage-plus-logo" src="/2500e4e62233fbfe8ac6.unitedLogoNew.svg">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_booking_3" aria-expanded="false" data-name="id_booking_3" type="button">
<button class="atm-c-btn app-compon..." id="" aria-controls="id_manage_my_trips_4" aria-expanded="false" data-name="id_manage_my_trips_4" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_travel_info_5" aria-expanded="false" data-name="id_travel_info_5" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_mileageplus_6" aria-expanded="false" data-name="id_mileageplus_6" type="button">
<button class="atm-c-btn app-components-GlobalHeader-NavbarItems-styles__navbarItemTitle--EqImp app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarItemTitle--RjIv2 atm-c-btn--bare" id="" aria-controls="id_deals_7" aria-expanded="false" data-name="id_deals_7" type="button">
<button class="atm-c-btn app-contai..." aria-label="Currently in English..." type="button">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__loginButton--tbffq atm-c-btn--bare" aria-label="Sign in" id="loginButton" type="button">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__closeButtonTT--eLYpx atm-c-btn--bare" aria-label="Close button">
<button class="atm-c-btn app-components-Ciam-LoginButton-loginButton__signInButtonTT--XEYtE atm-c-btn--primary" type="button"><span class="atm-c-btn__text">Sign in</span></button>
Showing first 10 of 40 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination6 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<header class="app-containers-App-AppHeader-styles__floatingHeader--THurE">
<nav aria-label="primary" class="app-components-GlobalHeader-NavbarItems-styles__navbarContainer--Gq2zL app-components-GlobalHeader-NavbarItems-styles__NewMenuNavbarContainer--wfHRp">
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<main role="main" class="app-containers-HomePage-styles__marginTop--RFtzz">
<footer role="contentinfo">
<div class="app-components-GlobalFooter-united100Logo-styles__united100LogoContainer--zbzZJ" role="region">
Links must have discernible text39 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a href="#travelTab" class="skipMenuNavigation atm-u-unstyled-link">Skip to book</a>
<a class="atm-c-text-link atm-c-text-link app-components-GlobalHeader-Logo-styles__headerLinkLogo--BcT2c" id="unitedLogo" href="/en/us/"><img alt="United logo link to homepage" data-test-id="mileage-plus-logo" src="/2500e4e62233fbfe8ac6.unitedLogoNew.svg"></a>
<a class="atm-c-text-link atm-c-text-link app-components-GlobalHeader-HelpLink-styles__navbarItemHelp--sFkoh app-components-GlobalHeader-styles__navbarItemHelpDesktop--te41s" href="/en/us/fly/help-center.html">
<a aria-label="Search, opens in a new tab" class="atm-c-text-link atm-c-text-link app-components-GlobalHeader-UserMenu-styles__userMenuLocalizeButtonSeach--grzAE" target="_blank" href="/en/us/website-search">
<a class="atm-c-btn app-components-Ciam-LoginButton-loginButton__joinNowTTlink--R3lNT atm-c-btn--link" href="https://www.united.com/en/US/account/join-now/about-me" aria-label="Create a MileagePlus account link, opens in new tab" data-test-id="enrollLink" target="_blank">
<a class="atm-c-btn app-compon..." href="http://cruises.unite..." aria-label="Search and book a Un..." aria-describedby="extDisclaimer" id="bookCruiseTab" target="_blank" rel="noopener">
<a class="atm-c-btn app-components-BookFlightForm-bookFlightForm__allSearchBtn--zoJ2K atm-c-btn--link atm-c-btn--link-with-icon" href="https://www.united.com/en-US/book-flight/united-reservations" title="Advanced search">
<a class="atm-c-btn atm-u-typography-preset-7 atm-c-btn--link" href="https://www.united.com/en/US/fly/baggage/checked-bags.html" title="Changed bag rules"><span class="atm-c-btn__text">Changed bag rules</span></a>
<a class="atm-c-btn atm-u-typography-preset-7 atm-c-btn--link" href="https://www.united.com/en/US/fly/products/upgrades-and-optional-service-charges.html" title="fees for optional services"><span class="atm-c-btn__text">fees for optional services</span></a>
<a aria-label="Wi-Fi, opens in a new tab" class="atm-c-text-link atm-c-text-link app-components-PopularFooter-styles__mptLink--mMJ0Z atm-c-text-link--inverted" target="_blank" href="/en/us/fly/travel-experience/inflight-wifi.html">
Showing first 10 of 39 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main role="main" class="app-containers-HomePage-styles__marginTop--RFtzz">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en" class="notranslate" translate="no" data-react-helmet="lang">
Page should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Audit Elements
<html lang="en" class="notranslate" translate="no" data-react-helmet="lang">
Required ARIA attributes must be provided43 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<nav role="navigation" class="app-components-GlobalHeader-UserMenu-styles__userMenu--pDsHJ" aria-label="secondary">
<div class="app-components-Announcements-announcements__visuallyhidden--qY1pM" role="status" aria-live="polite" aria-atomic="true"></div>
<main role="main" class="app-containers-HomePage-styles__marginTop--RFtzz">
<div class="app-components-Announcements-announcements__visuallyhidden--qY1pM" role="status" aria-live="polite" aria-atomic="true"></div>
<div role="tablist" class="app-components-BookTravel-bookTravel__travelNav--Qo_b2" aria-label="A tabs widget: Book, Flight status, Check-in, My trip; note, use arrow keys to navigate between tabs and enter/space key to activate and navigate through the tab content">
<button id="travelTab" tabindex="0" role="tab" aria-selected="true" aria-controls="travelTab-panel" name="travelTab" class="app-components-BookTravel-bookTravel__flightContent--E4baF" aria-label="Book a flight or trip package">
<button id="statusTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="statusTab-panel" name="statusTab" aria-label="Check flight status">
<button id="checkInTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="checkInTab-panel" aria-label="Check in a flight ">
<button id="tripsTab" tabindex="-1" role="tab" aria-selected="false" aria-controls="tripsTab-panel" aria-label="View and manage current trips ">
<section id="travelTab-panel" role="tabpanel" aria-hidden="false" aria-describedby="travelTab">
Showing first 10 of 43 audited elements.
Select element must have an accessible name1 element
Screen reader users cannot understand what information a select element requires without a proper label. Labels are essential for identifying form fields even when the purpose seems visually obvious, ensuring all users can complete forms successfully.
Audit Elements
<select class="atm-c-select atm-c-select-field__control" id="cabinType" name="bookFlightModel.cabinType"><option class="" value="0">Economy</option><option class="" value="1">Premium economy</option><option class="" value="2">Business or First</option></select>
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=4,user-scalable=yes">