Delta Air Linesdelta.com
Accessibility Score
Issues Found
Issues Found
CriticalARIA attributes must conform to valid values1 element
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.
Failing Elements
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
Fix all of the following:
- Invalid ARIA attribute value: aria-controls="tab-1"
ModerateAside should not be contained in another landmark1 element
Screen reader users can skip over complementary content like <aside> elements when they appear at the top level. Embedding asides within other landmarks may disable this navigation feature, forcing users to wade through ancillary content they want to skip.
Failing Elements
<aside class="bg-button-primary flex items-center justify-center rounded-full h-[4px] mt-[10px]"></aside>
Fix any of the following:
- The null landmark is contained in another landmark.
ModerateAll page content should be contained by landmarks14 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 _ngcontent-ng-c740051916="" class="relative w-full">
Fix any of the following:
- Some page content is not contained by landmarks
<div _ngcontent-ng-c740051916="" class="hidden tablet:block">
Fix any of the following:
- Some page content is not contained by landmarks
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> About Delta </h3>
Fix any of the following:
- Some page content is not contained by landmarks
<ul class="tablet:flex hidden flex-col items-start p-0 gap-16 w-full laptop:w-[220px] tablet:w-[167px] list-none">
Fix any of the following:
- Some page content is not contained by landmarks
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Customer Service </h3>
Fix any of the following:
- Some page content is not contained by landmarks
<ul class="tablet:flex hidden flex-col items-start p-0 gap-16 w-full laptop:w-[220px] tablet:w-[167px] list-none">
Fix any of the following:
- Some page content is not contained by landmarks
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Site Support </h3>
Fix any of the following:
- Some page content is not contained by landmarks
<ul class="tablet:flex hidden flex-col items-start p-0 gap-16 w-full laptop:w-[220px] tablet:w-[167px] list-none">
Fix any of the following:
- Some page content is not contained by landmarks
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Policies </h3>
Fix any of the following:
- Some page content is not contained by landmarks
<ul class="tablet:flex hidden flex-col items-start p-0 gap-16 w-full laptop:w-[220px] tablet:w-[167px] list-none">
Fix any of the following:
- Some page content is not contained by landmarks
Showing first 10 of 14 failing elements.
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">
<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">
<li> elements must be contained in a <ul> or <ol>26 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 _ngcontent-ng-c740051916="">
<li _ngcontent-ng-c740051916="">
<li _ngcontent-ng-c740051916=""><a _ngcontent-ng-c740051916="" class="text-label-md-semibold text-inverse hover:underline" href="/redeem-ecredit/" target="_blank" data-acdl-page-section="footer:popular topics" data-acdl-name="eCredits" data-acdl-action="footer:popular topics:"> eCredits </a></li>
<li class="w-full laptop:w-[220px] tablet:w-[167px] h-auto">
<li class="w-full laptop:w-[220px] tablet:w-[167px] h-auto">
<li class="w-full laptop:w-[220px] tablet:w-[167px] h-auto">
<li class="w-full laptop:w-[220px] tablet:w-[167px] h-auto">
<li class="w-full laptop:w-[220px] tablet:w-[167px] h-auto">
<li class="w-full laptop:w-[220px] tablet:w-[167px] h-auto">
<li class="w-full laptop:w-[220px] tablet:w-[167px] h-auto">
Showing first 10 of 26 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements5 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 _ngcontent-ng-c740051916="" class="flex list-none pl-0 gap-24">
<ul class="tablet:flex hidden flex-col items-start p-0 gap-16 w-full laptop:w-[220px] tablet:w-[167px] list-none">
<ul class="tablet:flex hidden flex-col items-start p-0 gap-16 w-full laptop:w-[220px] tablet:w-[167px] list-none">
<ul class="tablet:flex hidden flex-col items-start p-0 gap-16 w-full laptop:w-[220px] tablet:w-[167px] list-none">
<ul class="tablet:flex hidden flex-col items-start p-0 gap-16 w-full laptop:w-[220px] tablet:w-[167px] list-none">
All page content should be contained by landmarks470 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
<idp-root _nghost-ng-c3284182398="" ng-version="18.2.9">
<idp-header _ngcontent-ng-c3284182398="">
<idp-unsupported-browser _nghost-ng-c2289240993=""><!----></idp-unsupported-browser>
<idp-alert-advisories-container data-acdl-page-section="header:alerts and advisories" _nghost-ng-c613831991=""><!----></idp-alert-advisories-container>
<idp-skip-navigation-wrapper _nghost-ng-c1532468115="">
<div _ngcontent-ng-c1532468115="" class="absolute top-0 focus-within:z-[10000]">
<idp-skip-navigation _ngcontent-ng-c1532468115="" _nghost-ng-c2958126702="">
<button _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<nav idpheaderposition="" idpinspirationsubnavcontainer="" idpclickoutside="" id="mach-core-header-nav" idptaborderfocus="" data-design-system="" class="header header--container px-0 min-h-[209px] tablet:min-h-[195px] laptop:min-h-[214px] bg-[linear-gradient(180deg,#001932_0%,#001122_100%)]">
<div class="header__top top-0 left-0 right-0 flex justify-center items-center h-[52px] laptop:h-[auto] laptop:py-[16px] bg-[linear-gradient(180deg,#001932_0%,#001122_100%)] z-[1030]" style="position: fixed; top: 0px; z-index: 1040;">
Showing first 10 of 470 audited elements.
Alternative text of images should not be repeated as text14 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 _ngcontent-ng-c1143333985="" width="119" height="19" alt="Delta Air Lines" src="/content/dam/delta_homepage_redesign/Logo/Delta-Logo.svg">
<img _ngcontent-ng-c1143333985="" width="24" height="24" class="min-w-[24px]" alt="Skyteam" src="/content/dam/delta_homepage_redesign/Logo/Sky Team.svg">
<img _ngcontent-ng-c14261...="" src="/content/dam/delta-a..." role="button" tabindex="0" data-acdl-action="widget:refundable fa..." data-acdl-page-secti...="header:search widget" class="grayscale-effect" aria-label="Refundable Only Help...">
<img src="/content/dam/delta-com/external-link-images/external-icon.svg" alt="External Link Icon" class="inline-block ml-1">
<img class="inspirational-image" src="/content/dam/delta-tnt/homepage/hero/2026/summer-refresh/wf-4488023-gold-1600x624.webp" alt="Summer inspiration">
<img class="logo-cardArt-Span" src="/content/dam/delta-tnt/homepage/card-art/amex-gold-refresh-384x244.png" alt="Gold American Express Card" fetchpriority="high">
<img class="card-image-content object-cover tablet:block hidden" src="/content/dam/delta-tnt/homepage/btf/wf-4509973-960x720.webp" alt="Unlock 15% Off Award Travel">
<img class="card-image-content object-cover tablet:block hidden" src="/content/dam/delta-tnt/homepage/btf/wf-3383622-01-1050x600.webp" alt="Discover Travel Products">
<img class="card-image-content object-cover tablet:block hidden" src="/content/dam/delta-tnt/homepage/card-cd/brycecanyon-ut-slc-945.webp" alt="Ready For Adventure?" width="945" height="600">
<img class="card-image-content object-cover tablet:block hidden" src="/content/dam/delta-tnt/homepage/card-cd/premium-cabin-deals-945.webp" alt="Elevate Your Flight Experience">
Showing first 10 of 14 audited elements.
ARIA attributes must be used as specified for the element's role50 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
<button _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab3" tabindex="-1"> Need Help? </a>
<button class="button button-primary button-sm whitespace-nowrap !h-[28px]" tabindex="0" role="button" aria-label="Sign Up" data-acdl-action="header:sign up" data-acdl-name="sign up">Sign Up</button>
Showing first 10 of 50 audited elements.
ARIA attributes must conform to valid names50 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
<button _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab3" tabindex="-1"> Need Help? </a>
<button class="button button-primary button-sm whitespace-nowrap !h-[28px]" tabindex="0" role="button" aria-label="Sign Up" data-acdl-action="header:sign up" data-acdl-name="sign up">Sign Up</button>
Showing first 10 of 50 audited elements.
ARIA attributes must conform to valid values49 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
<button _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab3" tabindex="-1"> Need Help? </a>
<button class="button button-primary button-sm whitespace-nowrap !h-[28px]" tabindex="0" role="button" aria-label="Sign Up" data-acdl-action="header:sign up" data-acdl-name="sign up">Sign Up</button>
<button id="login-trigger" tabindex="0" role="button" data-acdl-action="header:log in" data-acdl-name="log in" data-acdl-page-section="header:log in" class="button button-primary button-sm whitespace-nowrap !h-[28px]" aria-label="Log in, opens in new popup"> Log in </button>
Showing first 10 of 49 audited elements.
ARIA commands must have an accessible name1 element
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<a _ngcontent-ng-c1426168160="" role="button" tabindex="0" class="link link-sm self-start flex-shrink-0">
ARIA dialog and alertdialog nodes should have an accessible name1 element
Screen reader users cannot identify the purpose of role="dialog" or role="alertdialog" elements without an accessible name. This leaves users confused about what dialog they've encountered and what it contains.
Audit Elements
<div class="ot-sdk-container" role="dialog" aria-label="Privacy">
ARIA hidden element must not be focusable or contain focusable elements45 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
<div _ngcontent-ng-c2722801603="" aria-hidden="true" id="mach-core-notification-counter" class="feed-counter absolute top-0 right-0 tablet:right-[-3px] ultrawide:right-[-3px] box-content w-[15px] h-[15px] ml-[12px] rounded-[10px] bg-icon-alert">
<div class="dropdown__placeholder--icon" aria-hidden="true" style="--icon-mask: url('/content/dam/delta-applications/sitewide/capability/flight-shop/images/trip-icon.svg');"></div><div class="dropdown__list-item-icon" aria-hidden="true" style="--item-icon: url('/content/dam/delta-applications/sitewide/capability/flight-shop/images/trip-icon.svg');"></div><div class="dropdown__list-item-icon" aria-hidden="true" style="--item-icon: url('/content/dam/delta-applications/sitewide/capability/flight-shop/images/one-way.svg');"></div><div class="dropdown__list-item-icon" aria-hidden="true" style="--item-icon: url('/content/dam/delta-applications/sitewide/capability/flight-shop/images/multi-trip-icon.svg');"></div><button class="date-button placeholder" disabled="" aria-hidden="true" tabindex="-1" style="pointer-events: none;"></button>
<button class="date-button placeholder" disabled="" aria-hidden="true" tabindex="-1" style="pointer-events: none;"></button>
<button class="date-button placeholder" disabled="" aria-hidden="true" tabindex="-1" style="pointer-events: none;"></button>
<button class="date-button placeholder" disabled="" aria-hidden="true" tabindex="-1" style="pointer-events: none;"></button>
<button class="date-button placeholder" disabled="" aria-hidden="true" tabindex="-1" style="pointer-events: none;"></button>
Showing first 10 of 45 audited elements.
ARIA role should be appropriate for the element361 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
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<ul id="mach-core-header-nav-primary-list" itemscope="" role="tablist" class="navbar-container-links--list flex whitespace-nowrap pt-[8px] laptop:min-h-[47px] laptop:gap-[35px] ultrawide:gap-[199px]">
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-0">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-1">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-2">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-3">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
Showing first 10 of 361 audited elements.
ARIA roles used must conform to valid values38 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
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<ul id="mach-core-header-nav-primary-list" itemscope="" role="tablist" class="navbar-container-links--list flex whitespace-nowrap pt-[8px] laptop:min-h-[47px] laptop:gap-[35px] ultrawide:gap-[199px]">
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-0">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-1">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-2">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-3">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
Showing first 10 of 38 audited elements.
ARIA tooltip nodes must have an accessible name1 element
Screen reader users cannot understand the purpose of role="tooltip" elements without an accessible name. The name provides the essential context or help text that the tooltip is meant to convey.
Audit Elements
<div id="red-signup-tooltip-popup" role="tooltip" aria-live="polite" style="top: 61px; left: 841px; opacity: 1;">
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 data-design-system="delta-mach-1-light" style="">
Buttons must have discernible text21 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 _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<button class="button button-primary button-sm whitespace-nowrap !h-[28px]" tabindex="0" role="button" aria-label="Sign Up" data-acdl-action="header:sign up" data-acdl-name="sign up">Sign Up</button>
<button id="login-trigger" tabindex="0" role="button" data-acdl-action="header:log in" data-acdl-name="log in" data-acdl-page-section="header:log in" class="button button-primary button-sm whitespace-nowrap !h-[28px]" aria-label="Log in, opens in new popup"> Log in </button>
<button _ngcontent-ng-c27228...="" tabindex="0" data-acdl-action="header:notification ..." data-acdl-name="notification bell" data-acdl-page-secti...="header:notification ..." id="mach-core-notificati..." class="bell-icon__container..." aria-label="notification, 3 unre...">
<button id="mach-core-header-search-button" data-acdl-action="header:search" data-acdl-name="search" data-acdl-page-section="header:search" aria-label="Search" class="header-search__icon text-icon-inverse w-8 h-8">
<button class="tab-item tab-active active" type="button" role="tab" aria-selected="true" id="flights" tabindex="0" data-value="Flights" data-id="flights">
<button class="tab-item" type="button" role="tab" aria-selected="false" id="stays" tabindex="-1" data-value="Stays" data-id="stays"><div class="tab-item-icon"><svg class="item-icon-hotel"></svg></div><div class="tab-item-content"><span class="item-label-text">Stays</span></div></button>
<button class="tab-item" type="button" role="tab" aria-selected="false" id="cars" tabindex="-1" data-value="Cars" data-id="cars"><div class="tab-item-icon"><svg class="item-icon-car"></svg></div><div class="tab-item-content"><span class="item-label-text">Cars</span></div></button>
<button class="tab-item" type="button" role="tab" aria-selected="false" id="vacations" tabindex="-1" data-value="Vacations" data-id="vacations">
<button class="tab-item" type="button" role="tab" aria-selected="false" id="cruises" tabindex="-1" data-value="Cruises" data-id="cruises" aria-label="Cruises Opens in new tab">
Showing first 10 of 21 audited elements.
Certain ARIA roles must be contained by particular parents12 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
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab3" tabindex="-1"> Need Help? </a>
<button class="tab-item tab-active active" type="button" role="tab" aria-selected="true" id="flights" tabindex="0" data-value="Flights" data-id="flights">
<button class="tab-item" type="button" role="tab" aria-selected="false" id="stays" tabindex="-1" data-value="Stays" data-id="stays"><div class="tab-item-icon"><svg class="item-icon-hotel"></svg></div><div class="tab-item-content"><span class="item-label-text">Stays</span></div></button>
<button class="tab-item" type="button" role="tab" aria-selected="false" id="cars" tabindex="-1" data-value="Cars" data-id="cars"><div class="tab-item-icon"><svg class="item-icon-car"></svg></div><div class="tab-item-content"><span class="item-label-text">Cars</span></div></button>
Showing first 10 of 12 audited elements.
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
<ul id="mach-core-header-nav-primary-list" itemscope="" role="tablist" class="navbar-container-links--list flex whitespace-nowrap pt-[8px] laptop:min-h-[47px] laptop:gap-[35px] ultrawide:gap-[199px]">
<div class="tabs-list" role="tablist" aria-orientation="horizontal">
Deprecated ARIA roles must not be used38 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
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<ul id="mach-core-header-nav-primary-list" itemscope="" role="tablist" class="navbar-container-links--list flex whitespace-nowrap pt-[8px] laptop:min-h-[47px] laptop:gap-[35px] ultrawide:gap-[199px]">
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-0">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-1">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-2">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-3">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
Showing first 10 of 38 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">
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
<div id="content-body-mach-core" role="main" data-acdl-page="homepage">
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">
Elements marked as presentational should be consistently ignored7 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-0">
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-1">
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-2">
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-3">
<li role="none" dropdown="" class="navbar-item text-label-xs-medium py-[4px] max-[1280px]:!text-[11px] first-static-link" id="mach-core-header-nav-secondary-0">
<li role="none" dropdown="" class="navbar-item text-label-xs-medium py-[4px] max-[1280px]:!text-[11px]" id="mach-core-header-nav-secondary-1">
<li role="none" dropdown="" class="navbar-item text-label-xs-medium py-[4px] max-[1280px]:!text-[11px] last-static-link" id="mach-core-header-nav-secondary-2">
Elements must meet minimum color contrast ratio thresholds48 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
<button class="button button-primary button-sm whitespace-nowrap !h-[28px]" tabindex="0" role="button" aria-label="Sign Up" data-acdl-action="header:sign up" data-acdl-name="sign up">Sign Up</button>
<div _ngcontent-ng-c2722801603="" class="feed-counter-text text-center text-[10px] font-['Whitney'] leading-[15px] text-inverse font-[375]"> 3 </div>
<span class="item-label-text">Flights</span>
<span class="item-label-text">Stays</span>
<span class="item-label-text">Cars</span>
<span class="item-label-text">Vacations</span>
<span class="item-label-text">Cruises</span>
<span class="external-links__text text-inverse mr-[4px] whitespace-nowrap"> Delta AMEX Cards </span>
<span class="external-links__text text-inverse whitespace-nowrap"> Gift Cards </span>
<span class="external-links__text text-inverse whitespace-nowrap"> Updated Bags & Travel Fees </span>
Showing first 10 of 48 audited elements.
Elements must only use permitted ARIA attributes49 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
<button _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab3" tabindex="-1"> Need Help? </a>
<button class="button button-primary button-sm whitespace-nowrap !h-[28px]" tabindex="0" role="button" aria-label="Sign Up" data-acdl-action="header:sign up" data-acdl-name="sign up">Sign Up</button>
Showing first 10 of 49 audited elements.
Elements must only use supported ARIA attributes50 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
<button _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab3" tabindex="-1"> Need Help? </a>
<button class="button button-primary button-sm whitespace-nowrap !h-[28px]" tabindex="0" role="button" aria-label="Sign Up" data-acdl-action="header:sign up" data-acdl-name="sign up">Sign Up</button>
Showing first 10 of 50 audited elements.
Elements should not have tabindex greater than zero30 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
<button _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab3" tabindex="-1"> Need Help? </a>
<button class="button button-primary button-sm whitespace-nowrap !h-[28px]" tabindex="0" role="button" aria-label="Sign Up" data-acdl-action="header:sign up" data-acdl-name="sign up">Sign Up</button>
Showing first 10 of 30 audited elements.
Form elements must have labels5 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 _ngcontent-ng-c1426168160="" type="checkbox" id="shopWithMiles" class="checkbox" aria-label="Shop with Miles">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="flexibleDate" class="checkbox" aria-label="My Dates are Flexible">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="basicFaresField" class="checkbox" aria-label="Include Basic">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="showExtraFareOnly" class="checkbox" aria-label="Refundable Only">
<input _ngcontent-ng-c74005...="" type="text" data-acdl-action="footer:search for a ..." data-acdl-name="search for a topic" data-acdl-page-secti...="footer:search for a ..." id="mach-homepage-footer..." name="mach-homepage-footer..." placeholder=" " class="single-line-input pe...">
Form elements should have a visible label5 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 _ngcontent-ng-c1426168160="" type="checkbox" id="shopWithMiles" class="checkbox" aria-label="Shop with Miles">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="flexibleDate" class="checkbox" aria-label="My Dates are Flexible">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="basicFaresField" class="checkbox" aria-label="Include Basic">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="showExtraFareOnly" class="checkbox" aria-label="Refundable Only">
<input _ngcontent-ng-c74005...="" type="text" data-acdl-action="footer:search for a ..." data-acdl-name="search for a topic" data-acdl-page-secti...="footer:search for a ..." id="mach-homepage-footer..." name="mach-homepage-footer..." placeholder=" " class="single-line-input pe...">
Form field must not have multiple label elements5 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 _ngcontent-ng-c1426168160="" type="checkbox" id="shopWithMiles" class="checkbox" aria-label="Shop with Miles">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="flexibleDate" class="checkbox" aria-label="My Dates are Flexible">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="basicFaresField" class="checkbox" aria-label="Include Basic">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="showExtraFareOnly" class="checkbox" aria-label="Refundable Only">
<input _ngcontent-ng-c74005...="" type="text" data-acdl-action="footer:search for a ..." data-acdl-name="search for a topic" data-acdl-page-secti...="footer:search for a ..." id="mach-homepage-footer..." name="mach-homepage-footer..." placeholder=" " class="single-line-input pe...">
Heading levels should only increase by one5 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
<h3 _ngcontent-ng-c740051916="" class="text-label-md-semibold text-navigation"> Popular Topics: </h3>
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> About Delta </h3>
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Customer Service </h3>
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Site Support </h3>
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Policies </h3>
Headings should not be empty5 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
<h3 _ngcontent-ng-c740051916="" class="text-label-md-semibold text-navigation"> Popular Topics: </h3>
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> About Delta </h3>
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Customer Service </h3>
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Site Support </h3>
<h3 class="tablet:flex hidden w-auto h-5 text-label-md-semibold text-navigation"> Policies </h3>
IDs used in ARIA and labels must be unique33 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
<li class="dropdown__list-item" id="select-r5ys2ys7dps-option-0" role="option" data-value="ROUND_TRIP" data-index="0" aria-selected="true">
<div id="grid-help-date-picker-9q75d4zibco" class="sr-only">Use arrow keys to navigate. Up and down arrows move by week, left and right arrows move by day.</div>
<li class="dropdown__list-item" id="select-2o9lvbtymzu-option-0" role="option" data-value="1" data-index="0" aria-selected="true">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="shopWithMiles" class="checkbox" aria-label="Shop with Miles">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="flexibleDate" class="checkbox" aria-label="My Dates are Flexible">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="basicFaresField" class="checkbox" aria-label="Include Basic">
<input _ngcontent-ng-c1426168160="" type="checkbox" id="showExtraFareOnly" class="checkbox" aria-label="Refundable Only">
<input _ngcontent-ng-c74005...="" type="text" data-acdl-action="footer:search for a ..." data-acdl-name="search for a topic" data-acdl-page-secti...="footer:search for a ..." id="mach-homepage-footer..." name="mach-homepage-footer..." placeholder=" " class="single-line-input pe...">
<span _ngcontent-ng-c639582066="" id="lang-selector-label" class="sr-only"> Link to change the language </span>
<header class="ensTitle" id="ensTitle">Privacy Settings</header>
Showing first 10 of 33 audited elements.
Images must have alternative text14 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 _ngcontent-ng-c1143333985="" width="119" height="19" alt="Delta Air Lines" src="/content/dam/delta_homepage_redesign/Logo/Delta-Logo.svg">
<img _ngcontent-ng-c1143333985="" width="24" height="24" class="min-w-[24px]" alt="Skyteam" src="/content/dam/delta_homepage_redesign/Logo/Sky Team.svg">
<img _ngcontent-ng-c14261...="" src="/content/dam/delta-a..." role="button" tabindex="0" data-acdl-action="widget:refundable fa..." data-acdl-page-secti...="header:search widget" class="grayscale-effect" aria-label="Refundable Only Help...">
<img src="/content/dam/delta-com/external-link-images/external-icon.svg" alt="External Link Icon" class="inline-block ml-1">
<img class="inspirational-image" src="/content/dam/delta-tnt/homepage/hero/2026/summer-refresh/wf-4488023-gold-1600x624.webp" alt="Summer inspiration">
<img class="logo-cardArt-Span" src="/content/dam/delta-tnt/homepage/card-art/amex-gold-refresh-384x244.png" alt="Gold American Express Card" fetchpriority="high">
<img class="card-image-content object-cover tablet:block hidden" src="/content/dam/delta-tnt/homepage/btf/wf-4509973-960x720.webp" alt="Unlock 15% Off Award Travel">
<img class="card-image-content object-cover tablet:block hidden" src="/content/dam/delta-tnt/homepage/btf/wf-3383622-01-1050x600.webp" alt="Discover Travel Products">
<img class="card-image-content object-cover tablet:block hidden" src="/content/dam/delta-tnt/homepage/card-cd/brycecanyon-ut-slc-945.webp" alt="Ready For Adventure?" width="945" height="600">
<img class="card-image-content object-cover tablet:block hidden" src="/content/dam/delta-tnt/homepage/card-cd/premium-cabin-deals-945.webp" alt="Elevate Your Flight Experience">
Showing first 10 of 14 audited elements.
Inline text spacing must be adjustable with custom stylesheets38 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
<body data-design-system="delta-mach-1-light" style="">
<div class="header__top top-0 left-0 right-0 flex justify-center items-center h-[52px] laptop:h-[auto] laptop:py-[16px] bg-[linear-gradient(180deg,#001932_0%,#001122_100%)] z-[1030]" style="position: fixed; top: 0px; z-index: 1040;">
<div class="[-ms-overflow-style:none] [scrollbar-width:none] bg-surface-navigation header__booking items-center justify-center mobile:flex overflow-x-auto tablet:justify-center tablet:max-w-none w-[100%]" style="position: sticky; top: 80px; margin-top: 79px; left: 0px; right: 0px; z-index: 12;">
<div id="mach-core-header-widgets" class="header__widgets flex items-center rounded-b-[8px] laptop:p-[24px] tablet:p-16 bg-surface-02 justify-center" style="z-index: 12; position: sticky; left: 0px; right: 0px; top: 124px; margin-top: 0px;">
<label class="from-and-to__button-label" style="--container-width: 120px;">From</label>
<label class="from-and-to__button-label" style="--container-width: 120px;">To</label>
<div class="bg-surface-navigation tablet:h-[22.1875rem] laptop:h-[24.8125rem] ultrawide:h-[36rem] relative isolate mx-auto h-[16.875rem] w-full laptop:mb-16" style="overflow: visible; background: linear-gradient(to right, #E3DCD2, #FFEBB7);">
<p style="text-align: center;">THE DELTA CUSTOMER EXPERIENCE</p>
<p style="text-align: center;"><span class="tablet:text-heading-sm text-label-xl-semibold">Supporting You Through Your Travel Journey</span></p>
<button _ngcontent-ng-c74005...="" id="homepage-footer-sear..." data-acdl-action="footer:search consol..." data-acdl-name="search for a topic:c..." data-acdl-page-secti...="footer:search for a ..." data-search-type="footer:search for a ..." class="header-search__icon ..." aria-label="Search" ...>
Showing first 10 of 38 audited elements.
Interactive controls must not be nested52 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
<button _ngcontent-ng-c2958126702="" tabindex="0" aria-label="Skip to main content" class="absolute left-[-9999px] button button-primary button-xs focus:left-0 focus:z-[10000]"> Skip to Main Content </button>
<img _ngcontent-ng-c1143333985="" width="119" height="19" alt="Delta Air Lines" src="/content/dam/delta_homepage_redesign/Logo/Delta-Logo.svg">
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<img _ngcontent-ng-c1143333985="" width="24" height="24" class="min-w-[24px]" alt="Skyteam" src="/content/dam/delta_homepage_redesign/Logo/Sky Team.svg">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
Showing first 10 of 52 audited elements.
Interactive elements must have a visible focus indicator2 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<button id="onetrust-accept-btn-handler">
<button class="rs-tooltip-close" aria-label="Dismiss tooltip">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination3 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
<nav idpheaderposition="" idpinspirationsubnavcontainer="" idpclickoutside="" id="mach-core-header-nav" idptaborderfocus="" data-design-system="" class="header header--container px-0 min-h-[209px] tablet:min-h-[195px] laptop:min-h-[214px] bg-[linear-gradient(180deg,#001932_0%,#001122_100%)]">
<section role="region" aria-label="Booking tabs and external links" id="mach-core-widget-tabs-section" class="widget-tabs max-[429px]:w-[343px] min-[430px]:w-auto tablet:w-auto ultrawide:w-[1152px] tablet:justify-center flex laptop:justify-between laptop:gap-[34px] ultrawide:gap-[202px]">
<div id="content-body-mach-core" role="main" data-acdl-page="homepage">
Links must have discernible text50 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 _ngcontent-ng-c1143333985="" id="header-first-focusable" data-acdl-action="header:delta logo" data-acdl-name="delta logo" data-acdl-page-section="header:delta logo" href="/" target="_self">
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab1" tabindex="-1"> Travel Info </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab2" tabindex="-1"> SkyMiles </a>
<a role="tab" href="javascript:void(0);" class="navbar-item--link !text-inverse text-label-xs-medium max-[1280px]:!text-[11px]" aria-selected="false" id="headSectab3" tabindex="-1"> Need Help? </a>
<a href="javascript:void(0)" role="button" tabindex="0" id="mach-core-widget-del..." class="external-links__delt..." data-acdl-action="widget:delta amex ca..." data-acdl-name="delta amex cards" data-acdl-page-secti...="header:book:delta am..." aria-label="Delta AMEX CardsThis...">
Showing first 10 of 50 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
<div id="content-body-mach-core" role="main" data-acdl-page="homepage">
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">
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">
Required ARIA attributes must be provided38 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
<a _ngcontent-ng-c1143333985="" role="button" tabindex="0" data-acdl-action="header:sub logo" data-acdl-name="sub logo" data-acdl-page-section="header:sub logo" aria-haspopup="true" href="javascript:void(0);" id="mach-core-header-sublogo-link" class="mr-0" aria-label="Skyteam">
<ul id="mach-core-header-nav-primary-list" itemscope="" role="tablist" class="navbar-container-links--list flex whitespace-nowrap pt-[8px] laptop:min-h-[47px] laptop:gap-[35px] ultrawide:gap-[199px]">
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-0">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="true" id="headPrimary1" aria-controls="tab-1" tabindex="0"> Book </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-1">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary2" aria-controls="tab-2" tabindex="-1"> Check-in </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-2">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary3" aria-controls="tab-3" tabindex="-1"> My Trips </a>
<li role="none" itemprop="name" class="navbar-item text-label-xs-semibold py-[4px] max-[1280px]:!text-[12px]" id="mach-core-header-nav-primary-3">
<a role="tab" href="javascript:void(0);" itemprop="url" class="navbar-item !text-inverse text-label-xs-semibold no-underline max-[1280px]:!text-[12px]" aria-selected="false" id="headPrimary4" aria-controls="tab-4" tabindex="-1"> Flight Status </a>
Showing first 10 of 38 audited elements.
Users 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.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1">
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">