Ford ford.com
Accessibility score
League position
6thof 9
Issues found
8
Audits passed
54
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousElements must meet minimum color contrast ratio thresholds16 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.
Failing Elements
<p class="cmp-grid__eyebrow fade fade-in">
JD Power Awards
</p>Fix any of the following:
- Element has insufficient color contrast of 1.32 (foreground color: #e0e0e0, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<p class="cmp-grid__heading fade fade-in">
Unmatched New-Vehicle Quality Among Mainstream Brands
</p>Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #cccccc, background color: #ffffff, font size: 36.0pt (48px), font weight: normal). Expected contrast ratio of 3:1
<p>Only One Can Rule the Dirt</p>
Fix any of the following:
- Element has insufficient color contrast of 1.13 (foreground color: #f0f0f0, background color: #ffffff, font size: 18.0pt (24px), font weight: normal). Expected contrast ratio of 3:1
<span class="cmp-button__text">Let's Go</span>
Fix any of the following:
- Element has insufficient color contrast of 1.4 (foreground color: #f0f0f0, background color: #cccccc, font size: 10.5pt (14px), font weight: bold). Expected contrast ratio of 4.5:1
<span class="disclosure_id" tabindex="-1" role="button" aria-label="Disclosure Important Details" data-listener-added="true" aria-hidden="true">Important Details</span>
Fix any of the following:
- Element has insufficient color contrast of 1.13 (foreground color: #f0f0f0, background color: #ffffff, font size: 8.3pt (11px), font weight: normal). Expected contrast ratio of 4.5:1
<p class="cmp-grid__eyebrow fade fade-in">
Models
</p>Fix any of the following:
- Element has insufficient color contrast of 1.54 (foreground color: #2e2e2e, background color: #000000, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<h2 class="cmp-grid__heading fade fade-in">
Find Your Ford
</h2>Fix any of the following:
- Element has insufficient color contrast of 1.66 (foreground color: #333333, background color: #000000, font size: 36.0pt (48px), font weight: normal). Expected contrast ratio of 3:1
<h2 class="cmp-grid__eyebrow fade fade-in">
Technology
</h2>Fix any of the following:
- Element has insufficient color contrast of 1.32 (foreground color: #e0e0e0, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<p class="cmp-grid__heading fade fade-in">
Create Your Perfect Drive
</p>Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #cccccc, background color: #ffffff, font size: 36.0pt (48px), font weight: normal). Expected contrast ratio of 3:1
<h2 class="cmp-grid__eyebrow fade fade-in">
Buying A Ford
</h2>Fix any of the following:
- Element has insufficient color contrast of 1.32 (foreground color: #e0e0e0, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
Showing first 10 of 16 failing elements.
SeriousElements must have their visible text as part of their accessible name20 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Failing Elements
<a type="link" class="cmp-button " href="https://www.ford.com/awards/?intcmp=hp-bb-awards" aria-label="Explore Ford awards" tabindex="0">
Fix any of the following:
- Text inside the element is not included in the accessible name
<a class="cmp-button " aria-label="Discover the offers ..." data-fof-context="{"nasapiModelName":"..." href="https://www.ford.com..." x-cq-linkchecker="skip" target="_self" tabindex="0">Fix any of the following:
- Text inside the element is not included in the accessible name
<a class="cmp-button " aria-label="Discover the offers ..." data-fof-context="{"nasapiModelName":"..." href="https://www.ford.com..." x-cq-linkchecker="skip" target="_self" tabindex="0">Fix any of the following:
- Text inside the element is not included in the accessible name
<a class="cmp-button " aria-label="Discover the offers ..." data-fof-context="{"nasapiModelName":"..." href="https://www.ford.com..." x-cq-linkchecker="skip" target="_self" tabindex="0">Fix any of the following:
- Text inside the element is not included in the accessible name
<a type="link" class="cmp-button " href="https://shop.ford.com/showroom/?intcmp=hp-cta-selp" aria-label="Discover the offers for all Ford Vehicles" target="_self">
Fix any of the following:
- Text inside the element is not included in the accessible name
<a type="link" class="cmp-button " href="/trucks/f150/2026?intcmp=hp-3up-jdp-vhp" aria-label="Discover the 2026 Ford F150®" tabindex="0">
Fix any of the following:
- Text inside the element is not included in the accessible name
<a type="link" class="cmp-button " href="/trucks/super-duty/2026?intcmp=hp-3up-jdp-vhp" aria-label="Discover the 2026 Ford Super Duty®" tabindex="0">
Fix any of the following:
- Text inside the element is not included in the accessible name
<a type="link" class="cmp-button " href="/cars/mustang/2026?intcmp=hp-3up-jdp-vhp" aria-label="Discover the 2026 Ford Mustang®" tabindex="0">
Fix any of the following:
- Text inside the element is not included in the accessible name
<a type="link" class="cmp-button " href="https://www.ford.com/suvs/?intcmp=hp-vehLineUp-veh-segment-suvs" aria-label="Learn more about Ford SUVs & Cars" target="_self">
Fix any of the following:
- Text inside the element is not included in the accessible name
<a type="link" class="cmp-button " aria-label="Sign up for 2027 Ford Mustang Mach-E® Trail Package updates" data-smartlink-href="##getupdates/$(make=Ford&model=Mache)" tabindex="0" role="button" style="cursor: pointer;">
Fix any of the following:
- Text inside the element is not included in the accessible name
Showing first 10 of 20 failing elements.
SeriousLinks must have discernible text1 element
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.
Failing Elements
<a class="footer-skinny__logo hide-on-mobile" href="https://www.ford.com">
<svg height="33" width="84">
<title></title>
<use href="#footer-skinny-logo"></use>
</svg>
</a>Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
Serious<ul> and <ol> must only directly contain <li>, <script> or <template> elements1 element
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.
Failing Elements
<ul class="navigation-menu__unordered-list">
Fix all of the following:
- List element has direct children that are not allowed: a
SeriousAll touch targets must be 24px large, or leave sufficient space2 elements
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Failing Elements
<a href="http://corporate.for..." data-ford-metrics-cl...="{"name":"referral-ex...">Fix any of the following:
- Target has insufficient size (154.4px by 15.7px, should be at least 24px by 24px)
- Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 16.2px instead of at least 24px.
<a href="//www.ford.com/content/na/ford/en_us/help/third-party-trademarks" target="_self" rel="noopener noreferrer">
Third-Party Trademarks
</a>Fix any of the following:
- Target has insufficient size (123.2px by 15.7px, should be at least 24px by 24px)
- Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 16.2px instead of at least 24px.
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination2 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.
Failing Elements
<form action="https://www.ford.com..." class="search-bar__form nav..." method="GET" novalidate="" role="search" data-search-click-ac...="{"name":"globalSearc..." data-search-input-na...="f:searchInputString">Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
<section id="carousel-e66d406791" class="cmp-carousel-slider background-white pad-top-56 pad-bottom-56 cmp-billboardCarousel" role="region" aria-roledescription="carousel" data-cmp-is="carousel" data-placeholder-text="false" data-target-component="carousel">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModerateAll page content should be contained by landmarks46 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="grid">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-left">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-details">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-footer">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-announcement">Ending Soon</div>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-left">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-details">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-footer">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-announcement">Ending Soon</div>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="cmp-offerCard__campaign-left">
Fix any of the following:
- Some page content is not contained by landmarks
Showing first 10 of 46 failing elements.
MinorARIA role should be appropriate for the element3 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.
Failing Elements
<section id="carousel-e66d406791" class="cmp-carousel-slider background-white pad-top-56 pad-bottom-56 cmp-billboardCarousel" role="region" aria-roledescription="carousel" data-cmp-is="carousel" data-placeholder-text="false" data-target-component="carousel">
Fix any of the following:
- ARIA role region is not allowed for given element
<section id="jd-power-carousel" class="cmp-carousel-slider gdux--lightTheme background-white pad-top-56 pad-bottom-56" role="region" aria-roledescription="carousel" data-cmp-is="carousel" data-placeholder-text="false" data-target-component="carousel">
Fix any of the following:
- ARIA role region is not allowed for given element
<section id="carousel-4dae6b3dde" class="cmp-carousel-slider gdux--rsfDark background-white pad-top-56 pad-bottom-56" role="region" aria-roledescription="carousel" data-cmp-is="carousel" data-placeholder-text="false" data-target-component="carousel">
Fix any of the following:
- ARIA role region is not allowed for given element
Passed audits54 across 1 page
<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="fgx-brand-Ford image-motion-js motion-js" dir="ltr" data-locale="en_us" translate="no">
<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="fgx-brand-Ford image-motion-js motion-js" dir="ltr" data-locale="en_us" translate="no">
<li> elements must be contained in a <ul> or <ol>99 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="navigation-menu__list-item ">
<li class="navigation-menu__list-item ">
<li class="navigation-menu__list-item ">
<li class="navigation-menu__list-item ">
<li class="navigation-menu__list-item search-bar" data-cmp-is="search-bar">
Showing first 5 of 99 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements13 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="navigation-menu__unordered-list navigation-menu__unordered-list--icons">
<ul class="cmp-carousel-slider-content " aria-atomic="false" aria-live="polite" style="transform: translateX(0px);">
<ul class="cmp-carousel-slider-pagination-crumbs" aria-label="carousel controls" data-pagination-label="Slide 1">
<ul class="cmp-carousel-slider-content " aria-atomic="false" aria-live="polite" style="transform: translateX(0px);">
<ul class="cmp-carousel-slider-content " aria-atomic="false" aria-live="polite" style="transform: translateX(0px);">
Showing first 5 of 13 audited elements.
All page content should be contained by landmarks1624 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
<main class="main-container">
</main><div class="promobanner promoBanner"> </div>
<header class="header header--theme-transparent-on-dark" data-cmp-is="header" style="opacity: 1;">
<div class="header__scrim"></div>
<nav class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
Showing first 5 of 1624 audited elements.
All touch targets must be 24px large, or leave sufficient space170 elements
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Audit Elements
<a aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
Skip to content
</a><a class="navigation-menu__bra..." href="http://www.ford.com/" data-ford-metrics-cl...="{"name":"global-oncl..."><button class="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Support & Service" data-ford-metrics-cl...="{"name":"global-oncl..." type="button">Showing first 5 of 170 audited elements.
Alternative text of images should not be repeated as text31 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="Person loading horses into a horse trailer hitched to a 2026 Ford F-150® King Ranch® model" fetchpriority="high">
<img src="https://www.assets.f..." srcset="https://www.assets.f..." alt="Collage of people do..." fetchpriority="high">
<img alt="Campaign Image" src="https://www.ford.com/cxservices/incentives/CampaignImage?imageType=global&initiativeID=333194&imageName=349707v1.png&provinceOrRegion=F48B&make=Ford&model=F-150 F-150&year=2026&language=EN&authId=258103172®ionCode=USA" height="160" width="252" loading="lazy">
<img alt="Campaign Image" src="https://www.ford.com/cxservices/incentives/CampaignImage?imageType=global&initiativeID=333200&imageName=349711v1.png&provinceOrRegion=F48B&make=Ford&model=SuperDuty&year=2026&language=EN&authId=258103172®ionCode=USA" height="160" width="252" loading="lazy">
<img alt="Campaign Image" src="https://www.ford.com/cxservices/incentives/CampaignImage?imageType=global&initiativeID=333192&imageName=349706v1.png&provinceOrRegion=F48B&make=Ford&model=Explorer&year=2026&language=EN&authId=258103172®ionCode=USA" height="160" width="252" loading="lazy">
Showing first 5 of 31 audited elements.
ARIA attributes must be used as specified for the element's role148 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 class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<a aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
Skip to content
</a><svg aria-label="Ford Home Page" height="30" width="80">
<title>Ford Home Page</title>
<use href="#navigation-menu-ford-logo"></use>
</svg><button class="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button">Showing first 5 of 148 audited elements.
ARIA attributes must conform to valid names148 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 class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<a aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
Skip to content
</a><svg aria-label="Ford Home Page" height="30" width="80">
<title>Ford Home Page</title>
<use href="#navigation-menu-ford-logo"></use>
</svg><button class="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button">Showing first 5 of 148 audited elements.
ARIA attributes must conform to valid values145 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 class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<a aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
Skip to content
</a><svg aria-label="Ford Home Page" height="30" width="80">
<title>Ford Home Page</title>
<use href="#navigation-menu-ford-logo"></use>
</svg><button class="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button">Showing first 5 of 145 audited elements.
ARIA commands must have an accessible name39 elements
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
<span class="disclosure_id" tabindex="0" role="button" aria-label="Disclosure Important Details" data-listener-added="true">Important Details</span>
<span class="disclosure_id" tabindex="0" role="button" aria-label="Disclosure 7" data-listener-added="true">7</span>
<span class="disclosure_id" tabindex="0" role="button" aria-label="Offer Details" data-listener-added="true">Offer Details</span>
<span class="disclosure_id" tabindex="0" role="button" aria-label="Disclosure 8" data-listener-added="true">8</span>
<span class="disclosure_id" tabindex="0" role="button" aria-label="Offer Details" data-listener-added="true">Offer Details</span>
Showing first 5 of 39 audited elements.
ARIA hidden element must not be focusable or contain focusable elements184 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 aria-label="Close" aria-hidden="true" height="24" width="24">
<use href="#close"></use>
</svg><svg aria-hidden="true" height="24" width="24">
<use href="#close"></use>
</svg><span aria-hidden="true" class="mobile-navigation__toggle-lines"></span>
<div aria-hidden="true" class="mobile-navigation__toggle-label mobile-navigation__toggle-label--close visually-hidden">
close menu
</div><span class="fgx-icon locate-dealer-icon icon-location-v2" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none">
<use href="#locate-dealer-icon"></use>
</svg>
</span>Showing first 5 of 184 audited elements.
ARIA role should be appropriate for the element267 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
<iframe src="about:blank" title="" role="presentation" loading="eager" style="width: 0px; height: 0px; border: 0px; display: none;"></iframe>
<div class="zipcode-overlay__content" role="dialog" tabindex="-1">
<button type="button" role="button" aria-label="Close" class="icon icon-close zipcode-toggle-popup">
<div class="cmp-location-verification-modal__overlay" role="dialog" aria-modal="true" aria-labelledby="loc-verify-title" tabindex="-1" style="display:none;">
<div id="loc-verify-error" class="cmp-location-verification-modal__error" role="alert" aria-live="assertive" style="display:none;">
Please enter a valid ZIP code
</div>Showing first 5 of 267 audited elements.
ARIA roles used must conform to valid values75 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 class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<div class="navigation-menu__container" data-role-cfg="{"mbl": "list", "dsk": "presentation"}" role="presentation"><form action="https://www.ford.com..." class="search-bar__form nav..." method="GET" novalidate="" role="search" data-search-click-ac...="{"name":"globalSearc..." data-search-input-na...="f:searchInputString"><section id="carousel-e66d406791" class="cmp-carousel-slider background-white pad-top-56 pad-bottom-56 cmp-billboardCarousel" role="region" aria-roledescription="carousel" data-cmp-is="carousel" data-placeholder-text="false" data-target-component="carousel">
<span class="disclosure_id" tabindex="0" role="button" aria-label="Disclosure Important Details" data-listener-added="true">Important Details</span>
Showing first 5 of 75 audited elements.
ARIA tab nodes must have an accessible name6 elements
Ensure every ARIA tab node has an accessible name
Audit Elements
<li role="tab" id="tabs-27bc08990d-item-13e5e3a802-tab" class="cmp-tabs__tab cmp-tabs__tab--active dropdown-item" aria-selected="true" tabindex="0">
<h3>
SUVs & Cars
</h3>
</li><li role="tab" id="tabs-27bc08990d-item-9435c5ae58-tab" class="cmp-tabs__tab dropdown-item" aria-selected="false" tabindex="-1">
<h3>
Trucks & Vans
</h3>
</li><li role="tab" id="tabs-27bc08990d-item-69887fb79f-tab" class="cmp-tabs__tab dropdown-item" aria-selected="false" tabindex="-1">
<h3>
Electric & Hybrid
</h3>
</li><div class="itemTitle" role="tab" data-accordion-item="0" id="ford-mobile-service-tab" tabindex="0" aria-controls="ford-mobile-service-tabpanel" aria-selected="true"><h3>Ford Mobile Service</h3> </div>
<div class="itemTitle" role="tab" data-accordion-item="1" id="ford-pickup-&-delivery-tab" tabindex="-1" aria-controls="ford-pickup-&-delivery-tabpanel" aria-selected="false"><h3>Ford Pickup & Delivery</h3> </div>
Showing first 5 of 6 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="fgx-brand-css bri-nav-transparent-onDrk gdux--lightTheme back-to-top-enabled">
autocomplete attribute must be used correctly1 element
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 aria-label="Search" autocapitalize="none" autocomplete="off" autocorrect="off" class="footer-nav__input" name="f:searchInputString" placeholder="Search" type="search">
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="header header--theme-transparent-on-dark" data-cmp-is="header" style="opacity: 1;">
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="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Support & Service" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="For Business" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button aria-label="Search Submit" class="search-bar__button search-bar__submit" type="submit">
<svg aria-label="Search Submit" height="16" width="16">
<title>Search Submit</title>
<use href="#navigation-menu-search"></use>
</svg>
</button>Showing first 5 of 30 audited elements.
Certain ARIA roles must be contained by particular parents9 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
<li role="tab" id="tabs-27bc08990d-item-13e5e3a802-tab" class="cmp-tabs__tab cmp-tabs__tab--active dropdown-item" aria-selected="true" tabindex="0">
<h3>
SUVs & Cars
</h3>
</li><li role="tab" id="tabs-27bc08990d-item-9435c5ae58-tab" class="cmp-tabs__tab dropdown-item" aria-selected="false" tabindex="-1">
<h3>
Trucks & Vans
</h3>
</li><li role="tab" id="tabs-27bc08990d-item-69887fb79f-tab" class="cmp-tabs__tab dropdown-item" aria-selected="false" tabindex="-1">
<h3>
Electric & Hybrid
</h3>
</li><button class="cmp-tabbedCarousel__item active" data-tabitem="0" id="1-tab" tabindex="0" role="tab" aria-controls="1-tabpanel" aria-selected="true">
<div class="item-title" style="height: 24px;"><h3>BlueCruise<sup>™</sup></h3>
</div>
</button><button class="cmp-tabbedCarousel__item " data-tabitem="1" id="2-tab" tabindex="-1" role="tab" aria-controls="2-tabpanel" aria-selected="false">
<div class="item-title" style="height: 24px;"><p>In-Vehicle Wi-Fi</p>
</div>
</button>Showing first 5 of 9 audited elements.
Certain ARIA roles must contain particular children5 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
<ol role="tablist" class="cmp-tabs__tabBar initTabFocus dropdown-menu-wrapper" aria-multiselectable="false" data-comp-init="true">
<div class="cmp-tabbedCarousel__tablist containerTransform blockTransform" role="tablist" aria-labelledby="tabbedCarousel" aria-owns="1-tab 2-tab 3-tab" style="--maxTab: 24px;">
<div role="tablist">
<div class="itemTitle" role="tab" data-accordion-item="0" id="ford-mobile-service-tab" tabindex="0" aria-controls="ford-mobile-service-tabpanel" aria-selected="true"><h3>Ford Mobile Service</h3>
</div>
</div><div role="tablist">
<div class="itemTitle" role="tab" data-accordion-item="1" id="ford-pickup-&-delivery-tab" tabindex="-1" aria-controls="ford-pickup-&-delivery-tabpanel" aria-selected="false"><h3>Ford Pickup & Delivery</h3>
</div>
</div><div role="tablist">
<div class="itemTitle" role="tab" data-accordion-item="2" id="fordpass-rewards-tab" tabindex="-1" aria-controls="fordpass-rewards-tabpanel" aria-selected="false"><h3>Ford Rewards</h3>
</div>
</div>Content must reflow without two-dimensional scrolling13 elements
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Audit Elements
<div class="navigation-menu__container" data-role-cfg="{"mbl": "list", "dsk"..." role="presentation"><div class="cmp-vehicleLineup__vehicleItem cmp-carousel-slider...">
<div class="cmp-vehicleLineup__vehicleItem cmp-carousel-slider...">
<div class="cmp-vehicleLineup__vehicleItem cmp-carousel-slider...">
<div class="cmp-vehicleLineup__vehicleItem cmp-carousel-slider...">
Showing first 5 of 13 audited elements.
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 data-cmp-is="footer" aria-label="Footer" class="footer">
Deprecated ARIA roles must not be used75 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 class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<div class="navigation-menu__container" data-role-cfg="{"mbl": "list", "dsk": "presentation"}" role="presentation"><form action="https://www.ford.com..." class="search-bar__form nav..." method="GET" novalidate="" role="search" data-search-click-ac...="{"name":"globalSearc..." data-search-input-na...="f:searchInputString"><section id="carousel-e66d406791" class="cmp-carousel-slider background-white pad-top-56 pad-bottom-56 cmp-billboardCarousel" role="region" aria-roledescription="carousel" data-cmp-is="carousel" data-placeholder-text="false" data-target-component="carousel">
<span class="disclosure_id" tabindex="0" role="button" aria-label="Disclosure Important Details" data-listener-added="true">Important Details</span>
Showing first 5 of 75 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="fgx-brand-Ford image-motion-js motion-js" dir="ltr" data-locale="en_us" translate="no">
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="header header--theme-transparent-on-dark" data-cmp-is="header" style="opacity: 1;">
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 data-cmp-is="footer" aria-label="Footer" class="footer">
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 class="main-container">
</main>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="fgx-brand-Ford image-motion-js motion-js" dir="ltr" data-locale="en_us" translate="no">
Elements must have their visible text as part of their accessible name36 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Audit Elements
<button class="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Support & Service" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="For Business" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><a class="utility-item locate-..." href="//www.ford.com/conte..." id="brand-nav-lad-deskto..." aria-label="Locate Dealer" data-ford-metrics-cl...="{"name":"global-oncl...">Showing first 5 of 36 audited elements.
Elements must meet minimum color contrast ratio thresholds177 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
<input type="text" class="zipcode-overlay__input" aria-label="ZIP code" maxlength="5">
<input type="text" id="loc-verify-input" class="cmp-location-verification-modal__input" aria-label="ZIP code" aria-describedby="loc-verify-error" autocomplete="postal-code">
<input aria-label="Type your search" autocapitalize="none" autocomplete="off" autocorrect="off" class="search-bar__input" maxlength="{55}" name="f:searchInputString" placeholder="Search" type="search"><input aria-label="Type your search" autocapitalize="none" autocomplete="off" autocorrect="off" class="search-bar__input" maxlength="{55}" name="f:searchInputString" placeholder="Search" type="search"><span class="cmp-button__text">Explore Awards</span>
Showing first 5 of 177 audited elements.
Elements must only use permitted ARIA attributes144 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 class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<a aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
Skip to content
</a><svg aria-label="Ford Home Page" height="30" width="80">
<title>Ford Home Page</title>
<use href="#navigation-menu-ford-logo"></use>
</svg><button class="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button">Showing first 5 of 144 audited elements.
Elements must only use supported ARIA attributes148 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 class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<a aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
Skip to content
</a><svg aria-label="Ford Home Page" height="30" width="80">
<title>Ford Home Page</title>
<use href="#navigation-menu-ford-logo"></use>
</svg><button class="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button">Showing first 5 of 148 audited elements.
Elements should not have tabindex greater than zero77 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 class="header__content-end" id="header__content-end" tabindex="-1"></div>
<button class="carousel-slider-button prev-button " aria-label="Previous Slide" tabindex="0">
<svg height="24" width="24" aria-label="Previous Slide">
<use href="#keyboard_arrow_left"></use>
</svg>
</button><span class="disclosure_id" tabindex="0" role="button" aria-label="Disclosure Important Details" data-listener-added="true">Important Details</span>
<a type="link" class="cmp-button " href="https://www.ford.com/awards/?intcmp=hp-bb-awards" aria-label="Explore Ford awards" tabindex="0">
<button class="carousel-slider-button next-button " aria-label="Next Slide" tabindex="0">
<svg height="24" width="24" aria-label="Next Slide">
<use href="#keyboard_arrow_right"></use>
</svg>
</button>Showing first 5 of 77 audited elements.
Focused elements must not be entirely hidden by author-created content50 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
<a class="navigation-menu__brand" href="http://www.ford.com/" data-ford-metrics-click="{"name":"global-onclick","..."><button class="navigation-menu__list-item-button" aria-label="Vehicles" data-ford-metrics-click="{"name":"global-onclick","..." type="button"><button class="navigation-menu__list-item-button" aria-label="Shop" data-ford-metrics-click="{"name":"global-onclick","..." type="button"><button class="navigation-menu__list-item-button" aria-label="Support & Service" data-ford-metrics-click="{"name":"global-onclick","..." type="button">Showing first 5 of 50 audited elements.
Form elements must have labels1 element
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 aria-label="Search" autocapitalize="none" autocomplete="off" autocorrect="off" class="footer-nav__input" name="f:searchInputString" placeholder="Search" type="search">
Form elements should have a visible label1 element
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 aria-label="Search" autocapitalize="none" autocomplete="off" autocorrect="off" class="footer-nav__input" name="f:searchInputString" placeholder="Search" type="search">
Form field must not have multiple label elements1 element
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 aria-label="Search" autocapitalize="none" autocomplete="off" autocorrect="off" class="footer-nav__input" name="f:searchInputString" placeholder="Search" type="search">
Heading levels should only increase by one26 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>
<h2 class="cmp-grid__heading fade " style="opacity: 1;">
Featured Offers
</h2><h3 class="cmp-offerCard__campaign-title"><b><div style="font-size:14pt">2026 Ford F-150</div> <div style="font-size:12pt">XLT 2.7L 4X4 Black Appearance Package</div></b></h3>
<h3 class="cmp-offerCard__campaign-title"><b><div style="font-size:14pt">2026 Ford Super Duty</div> <div style="font-size:12pt">XL Super Cab Pickup with STX package</div></b></h3>
<h3 class="cmp-offerCard__campaign-title"><b><div style="font-size:14pt">2026 Ford Explorer</div> <div style="font-size:12pt">Active with Comfort Package 4WD</div></b></h3>
Showing first 5 of 26 audited elements.
Headings should not be empty26 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>
<h2 class="cmp-grid__heading fade " style="opacity: 1;">
Featured Offers
</h2><h3 class="cmp-offerCard__campaign-title"><b><div style="font-size:14pt">2026 Ford F-150</div> <div style="font-size:12pt">XLT 2.7L 4X4 Black Appearance Package</div></b></h3>
<h3 class="cmp-offerCard__campaign-title"><b><div style="font-size:14pt">2026 Ford Super Duty</div> <div style="font-size:12pt">XL Super Cab Pickup with STX package</div></b></h3>
<h3 class="cmp-offerCard__campaign-title"><b><div style="font-size:14pt">2026 Ford Explorer</div> <div style="font-size:12pt">Active with Comfort Package 4WD</div></b></h3>
Showing first 5 of 26 audited elements.
IDs used in ARIA and labels must be unique32 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
<h2 id="loc-verify-title" class="cmp-location-verification-modal__title">
Find local incentives
</h2><input type="text" id="loc-verify-input" class="cmp-location-verification-modal__input" aria-label="ZIP code" aria-describedby="loc-verify-error" autocomplete="postal-code">
<div id="loc-verify-error" class="cmp-location-verification-modal__error" role="alert" aria-live="assertive" style="display:none;">
Please enter a valid ZIP code
</div><div class="navigation-menu" data-cmp-is="navigation-menu" id="navigation-menu">
<h2 class="modal-headline" id="externalHeading">
You are now leaving www.ford.com.
</h2>Showing first 5 of 32 audited elements.
Images must have alternative text31 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="Person loading horses into a horse trailer hitched to a 2026 Ford F-150® King Ranch® model" fetchpriority="high">
<img src="https://www.assets.f..." srcset="https://www.assets.f..." alt="Collage of people do..." fetchpriority="high">
<img alt="Campaign Image" src="https://www.ford.com/cxservices/incentives/CampaignImage?imageType=global&initiativeID=333194&imageName=349707v1.png&provinceOrRegion=F48B&make=Ford&model=F-150 F-150&year=2026&language=EN&authId=258103172®ionCode=USA" height="160" width="252" loading="lazy">
<img alt="Campaign Image" src="https://www.ford.com/cxservices/incentives/CampaignImage?imageType=global&initiativeID=333200&imageName=349711v1.png&provinceOrRegion=F48B&make=Ford&model=SuperDuty&year=2026&language=EN&authId=258103172®ionCode=USA" height="160" width="252" loading="lazy">
<img alt="Campaign Image" src="https://www.ford.com/cxservices/incentives/CampaignImage?imageType=global&initiativeID=333192&imageName=349706v1.png&provinceOrRegion=F48B&make=Ford&model=Explorer&year=2026&language=EN&authId=258103172®ionCode=USA" height="160" width="252" loading="lazy">
Showing first 5 of 31 audited elements.
Inline text spacing must be adjustable with custom stylesheets74 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
<header class="header header--theme-transparent-on-dark" data-cmp-is="header" style="opacity: 1;">
<ul class="cmp-carousel-slider-content " aria-atomic="false" aria-live="polite" style="transform: translateX(0px);">
<div data-motion-stagger="" class="
cmp-billboard__section
shorterBillboard
overlap-nav
" style="
--desktopBillboard: 16/9;
--tabletBillboard: 8/9;
--mobileBillboard: 9/16;"><div data-motion-stagger="" class="
cmp-billboard__section
shorterBillboard
overlap-nav
" style="
--desktopBillboard: 16/9;
--tabletBillboard: 8/9;
--mobileBillboard: 9/16;"><h2 class="cmp-grid__heading fade " style="opacity: 1;">
Featured Offers
</h2>Showing first 5 of 74 audited elements.
Interactive controls must not be nested104 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 class="navigation-menu__lis..." aria-label="Vehicles" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Shop" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="Support & Service" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button class="navigation-menu__lis..." aria-label="For Business" data-ford-metrics-cl...="{"name":"global-oncl..." type="button"><button aria-label="Search Submit" class="search-bar__button search-bar__submit" type="submit">
<svg aria-label="Search Submit" height="16" width="16">
<title>Search Submit</title>
<use href="#navigation-menu-search"></use>
</svg>
</button>Showing first 5 of 104 audited elements.
Interactive elements must have a visible focus indicator50 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
<a aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
<a class="navigation-menu__brand" href="http://www.ford.com/" data-ford-metrics-click="{"name":"global-onclick","..."><button class="navigation-menu__list-item-button" aria-label="Vehicles" data-ford-metrics-click="{"name":"global-onclick","..." type="button"><button class="navigation-menu__list-item-button" aria-label="Shop" data-ford-metrics-click="{"name":"global-onclick","..." type="button"><button class="navigation-menu__list-item-button" aria-label="Support & Service" data-ford-metrics-click="{"name":"global-onclick","..." type="button">Showing first 5 of 50 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination10 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
<main class="main-container">
</main><header class="header header--theme-transparent-on-dark" data-cmp-is="header" style="opacity: 1;">
<nav class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<footer data-cmp-is="footer" aria-label="Footer" class="footer">
<nav class="footer-nav">
Showing first 5 of 10 audited elements.
Links must have discernible text114 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 aria-label="Skip to content" class="header__skip-content visually-hidden" href="#header__content-end">
Skip to content
</a><a class="navigation-menu__bra..." href="http://www.ford.com/" data-ford-metrics-cl...="{"name":"global-oncl..."><a class="utility-item locate-..." href="//www.ford.com/conte..." id="brand-nav-lad-deskto..." aria-label="Locate Dealer" data-ford-metrics-cl...="{"name":"global-oncl..."><a type="link" class="cmp-button " href="https://www.ford.com/awards/?intcmp=hp-bb-awards" aria-label="Explore Ford awards" tabindex="0">
<a class="zipcode-text" href="javascript:void(0)" role="button" data-keypress="true" aria-label="Zipcode 48120">48120</a>
Showing first 5 of 114 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 class="main-container">
</main>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="fgx-brand-Ford image-motion-js motion-js" dir="ltr" data-locale="en_us" translate="no">
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="fgx-brand-Ford image-motion-js motion-js" dir="ltr" data-locale="en_us" translate="no">
Required ARIA attributes must be provided75 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 class="header__navbar" id="header__navbar" role="navigation" aria-label="Main Navigation">
<div class="navigation-menu__container" data-role-cfg="{"mbl": "list", "dsk": "presentation"}" role="presentation"><form action="https://www.ford.com..." class="search-bar__form nav..." method="GET" novalidate="" role="search" data-search-click-ac...="{"name":"globalSearc..." data-search-input-na...="f:searchInputString"><section id="carousel-e66d406791" class="cmp-carousel-slider background-white pad-top-56 pad-bottom-56 cmp-billboardCarousel" role="region" aria-roledescription="carousel" data-cmp-is="carousel" data-placeholder-text="false" data-target-component="carousel">
<span class="disclosure_id" tabindex="0" role="button" aria-label="Disclosure Important Details" data-listener-added="true">Important Details</span>
Showing first 5 of 75 audited elements.
Text must remain readable when spacing is increased0 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
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.0">
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.0">
How does your site stack up against Ford?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Automotive