Chevroletchevrolet.com
Accessibility Score
Issues Found
Issues Found
CriticalElements must only use supported ARIA attributes7 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.
Failing Elements
<li data-id="electric" class="gb-tab-button default-tab stat-tab-link active" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Electric </div> </div> </li>
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="true"
<li data-id="suvs" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> SUVs </div> </div> </li>
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="true"
<li data-id="trucks" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Trucks </div> </div> </li>
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="true"
<li data-id="performance" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Performance </div> </div> </li>
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="true"
<li data-id="equinox" class="gb-tab-button default-tab default-expander stat-tab-link active" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Equinox LT FWD </div> </div> </li>
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="true"
<li data-id="colorado" class="gb-tab-button stat-tab-link" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Colorado Custom 2WD </div> </div> </li>
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="true"
<li data-id="equinox-2" class="gb-tab-button stat-tab-link" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Equinox EV LT 2 </div> </div> </li>
Fix all of the following:
- ARIA attribute is not allowed: aria-selected="true"
CriticalButtons must have discernible text4 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.
Failing Elements
<button class="indicator active" data-slide-num="0" style="flex-basis: 33.3333%;"> <div class="indicator-label"></div> <div class="indicator-bar"> <div class="gb-mccb-progress-bar" data-interval="7000" style="width: 111.9%;"></div> </div> </button>
Fix any of the following:
- Element does not have inner 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
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="indicator" data-slide-num="1" style="flex-basis: 33.3333%;"> <div class="indicator-label"></div> <div class="indicator-bar"> <div class="gb-mccb-progress-bar" data-interval="7000" style="width: 0%;"></div> </div> </button>
Fix any of the following:
- Element does not have inner 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
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="indicator" data-slide-num="2" style="flex-basis: 33.3333%;"> <div class="indicator-label"></div> <div class="indicator-bar"> <div class="gb-mccb-progress-bar" data-interval="7000" style="width: 0%;"></div> </div> </button>
Fix any of the following:
- Element does not have inner 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
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
<button class="play-pause-toggle"></button>
Fix any of the following:
- Element does not have inner 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
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
SeriousInteractive controls must not be nested16 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.
Failing Elements
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/chevy-trucks/master">
Fix any of the following:
- Element has focusable descendants
<gb-disclosure data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-1500-rst-2/master" role="button" class="gb-disclosure">
Fix any of the following:
- Element has focusable descendants
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/26-1500-rst/master">
Fix any of the following:
- Element has focusable descendants
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-eev-rs/master" target="_self">
Fix any of the following:
- Element has focusable descendants
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
Fix any of the following:
- Element has focusable descendants
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/msrp/master" target="_self">
Fix any of the following:
- Element has focusable descendants
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
Fix any of the following:
- Element has focusable descendants
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/rotator-msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(7)</sup></gb-disclosure>
Fix any of the following:
- Element has focusable descendants
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
Fix any of the following:
- Element has focusable descendants
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/rotator-msrp/master" target="_self">
Fix any of the following:
- Element has focusable descendants
Showing first 10 of 16 failing elements.
SeriousElements must meet minimum color contrast ratio thresholds8 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
<a class="gb-tertiary-button stat-button-link no-padding small-list gb-small-button gb-none-margin " href="/request-test-drive" data-link-type="internal" target="_self" title="Schedule a test drive" data-dtm="find it together">
Fix any of the following:
- Element has insufficient color contrast of 3.62 (foreground color: #0077d9, background color: #e6e6e6, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a class="gb-tertiary-button ..." href="https://accessories...." data-link-type="external" target="_blank" title="See accessories for ..." data-dtm="find it together">
Fix any of the following:
- Element has insufficient color contrast of 3.62 (foreground color: #0077d9, background color: #e6e6e6, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a class="gb-tertiary-button stat-button-link no-padding small-list gb-small-button gb-none-margin " href="/electric/lineup" data-link-type="internal" target="_self" title="Show me the Chevy EV lineup" data-dtm="find it together">
Fix any of the following:
- Element has insufficient color contrast of 3.62 (foreground color: #0077d9, background color: #e6e6e6, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a class="gb-tertiary-button stat-button-link no-padding small-list gb-small-button gb-none-margin " href="/trucks/trailering-and-towing-guide" data-link-type="internal" target="_self" title="What is my towing capacity?" ...>
Fix any of the following:
- Element has insufficient color contrast of 3.62 (foreground color: #0077d9, background color: #e6e6e6, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a class="gb-tertiary-button stat-button-link no-padding small-list gb-small-button gb-none-margin " href="/electric/ev-charging" data-link-type="internal" target="_self" title="How do I learn about EV charging?" data-dtm="find it together">
Fix any of the following:
- Element has insufficient color contrast of 3.62 (foreground color: #0077d9, background color: #e6e6e6, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a class="gb-tertiary-button stat-button-link no-padding small-list gb-small-button gb-none-margin " href="/trade-in-appraisal" data-link-type="internal" target="_self" title="Find out my trade-in value" data-dtm="find it together">
Fix any of the following:
- Element has insufficient color contrast of 3.62 (foreground color: #0077d9, background color: #e6e6e6, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a class="gb-tertiary-button-i..." href="/content/chevrolet/n..." data-link-type="internal" target="_self" title="Search" data-dtm="footer">
Fix any of the following:
- Element has insufficient color contrast of 4.04 (foreground color: #0077d9, background color: #f2f2f2, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<p>
Fix any of the following:
- Element has insufficient color contrast of 3 (foreground color: #8c8c8c, background color: #f2f2f2, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
SeriousFrames must have an accessible name1 element
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Failing Elements
<iframe width="100%" id="targetLeadForm" scrolling="no" src="/request-quote" style="border: 0px; display: block; margin-bottom: 30px; height: 0px;"></iframe>
Fix any of the following:
- Element has no title attribute
- 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's default semantics were not overridden with role="none" or role="presentation"
SeriousForm 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.
Failing Elements
<input title="Search" class="autocomplete gb-search-input stat-search-input" type="text" required="" id="autocomplete" name="q" placeholder="Search" data-dtm="find it together">
Fix all of the following:
- Only title used to generate label for form element
SeriousLinks must have discernible text7 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.
Failing Elements
<a href="https://accessories...." class="gb-primary-wrapper ..." data-link-type="external" target="_blank" data-dtm="teaser" data-dtm2="accessories - get 20...">
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
<a href="/electric/bolt-ev" class="gb-primary-wrapper ..." data-link-type="internal" target="_self" data-dtm="teaser" data-dtm2="americas number1 ful...">
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
<a href="/trucks/trail-boss-f..." class="gb-primary-wrapper ..." data-link-type="internal" target="_self" data-dtm="teaser" data-dtm2="trail boss family - ...">
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
<a href="https://accessories...." class="gb-primary-wrapper ..." data-link-type="external" target="_blank" data-dtm="teaser" data-dtm2="ev chargers - get 10...">
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
<a href="https://www.chevrole..." class="gb-primary-wrapper ..." data-link-type="internal" target="_self" data-dtm="teaser" data-dtm2="trusted care starts ...">
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
<a href="/electric/bolt-ev" class="gb-primary-wrapper ..." data-link-type="internal" target="_self" data-dtm="teaser" data-dtm2="2027 bolt - the fun ...">
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
<a class="external stat-text-link" href="http://www.gm.com/copyright-trademark?evar25=ch_footer" data-dtm="footer" target="_self" rel="noopener noreferrer"> </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
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
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
<gb-global-nav enable-language-selector="true" lang-country-context="-" show-scroll-height="150" role="navigation" data-auth-content-active="show-unauth-users"> </gb-global-nav>
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModeratePage 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.
Failing Elements
<html dir="ltr" lang="en-US" style="" class=" js no-touch csscolumns">
Fix all of the following:
- Page must have a level-one heading
ModerateAll page content should be contained by landmarks1 element
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="gb-disclaimer-footer">
Fix any of the following:
- Some page content is not contained by landmarks
MinorAlternative text of images should not be repeated as text1 element
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.
Failing Elements
<img class="icon-normal" src="/content/dam/chevrolet/na/us/english/portable-nav/search-icon.svg" alt="Search">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
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 dir="ltr" lang="en-US" style="" class=" js no-touch csscolumns">
<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 dir="ltr" lang="en-US" style="" class=" js no-touch csscolumns">
<li> elements must be contained in a <ul> or <ol>10 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 data-id="electric" class="gb-tab-button default-tab stat-tab-link active" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Electric </div> </div> </li>
<li data-id="suvs" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> SUVs </div> </div> </li>
<li data-id="trucks" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Trucks </div> </div> </li>
<li data-id="performance" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Performance </div> </div> </li>
<li data-id="equinox" class="gb-tab-button default-tab default-expander stat-tab-link active" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Equinox LT FWD </div> </div> </li>
<li data-id="colorado" class="gb-tab-button stat-tab-link" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Colorado Custom 2WD </div> </div> </li>
<li data-id="equinox-2" class="gb-tab-button stat-tab-link" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Equinox EV LT 2 </div> </div> </li>
<li>Ultra-low mileage lease example for qualified lessees with a current eligible lease</li>
<li>36 months, $2,879 due at signing after all offers</li>
<li>$0 Acquisition fee ($695 value)</li>
<ul> and <ol> must only directly contain <li>, <script> or <template> elements4 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul class="gb-tab-button-list " data-tab="">
<ul class="gb-tab-button-list " data-tab="">
<ul> <li>Ultra-low mileage lease example for qualified lessees with a current eligible lease</li> <li>36 months, $2,879 due at signing after all offers</li> <li>$0 Acquisition fee ($695 value)</li> </ul>
<ul class="gb-suggest-items-container no-bullet"></ul>
All page content should be contained by landmarks1089 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
<gb-geo-ip-notification>
<gb-global-nav enable-language-selector="true" lang-country-context="-" show-scroll-height="150" role="navigation" data-auth-content-active="show-unauth-users"> </gb-global-nav>
<div class="gn-extras"> <button class="gb-visually-hide-show gb-skip-to-main-content gb-body1 stat-button-link" data-dtm="global nav"> Skip to Main Content </button> </div>
<button class="gb-visually-hide-show gb-skip-to-main-content gb-body1 stat-button-link" data-dtm="global nav"> Skip to Main Content </button>
<div class="gn-aria-label"> </div>
<div class="gn-logo-container"> <a href="/" class="stat-logo" title="Chevrolet" data-dtm="global nav"> <img class="gn-logo gn-nav-logo-image" src="/content/dam/chevrolet/na/us/english/portable-nav/chevrolet-bowtie-120.svg" alt="Chevrolet" title="Chevrolet"> </a> </div>
<a href="/" class="stat-logo" title="Chevrolet" data-dtm="global nav"> <img class="gn-logo gn-nav-logo-image" src="/content/dam/chevrolet/na/us/english/portable-nav/chevrolet-bowtie-120.svg" alt="Chevrolet" title="Chevrolet"> </a>
<img class="gn-logo gn-nav-logo-image" src="/content/dam/chevrolet/na/us/english/portable-nav/chevrolet-bowtie-120.svg" alt="Chevrolet" title="Chevrolet">
<nav class="gn-main-nav">
<button class="gn-main-button ..." href="/content/chevrolet/n..." flyout="primary-0" data-dtm="global nav" data-hamburger-menu="true" data-flyout-pagetitl...="hamburger-menu">
Showing first 10 of 1089 audited elements.
Alternative text of images should not be repeated as text23 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 class="gn-logo gn-nav-logo-image" src="/content/dam/chevrolet/na/us/english/portable-nav/chevrolet-bowtie-120.svg" alt="Chevrolet" title="Chevrolet">
<img class="gn-icon-svg
" src="/content/dam/chevrolet/na/us/english/primary-navigation-icons/hamburger.svg" alt="Additional Products and Services"><img src="/content/dam/chevrolet/na/us/english/portable-nav/account.svg" alt="profile">
<img alt="2026 Chevy Trucks" height="1000" width="2250" src="/content/dam/chevrolet/na/us/english/retail/march-2026/phase-1/hp/v2/truck-pack-hp-mast-desktop-v1.png?imwidth=1200" class="gb-rectangle-image-responsive gb-image">
<img alt="2026 Chevy Silverado 1500 RST 5.3L" height="1000" width="2250" src="/content/dam/chevrolet/na/us/english/retail/march-2026/phase-1/hp/v2/silverado-1500-26-hp-mast-desktop.png?imwidth=1200" class="gb-rectangle-image-responsive gb-image">
<img alt="2026 EQUINOX EV" height="1000" width="2250" src="/content/dam/chevrolet/na/us/english/retail/february-2026/phase-1/hp/equinox-ev-26-hp-mast-desktop.png?imwidth=1200" class="gb-rectangle-image-responsive gb-image">
<img srcset="/content/dam/chevrol..." alt="Chevrolet Bolt" src="/content/dam/chevrol..." height="900" width="1600" fetchpriority="high">
<img srcset="/content/dam/chevrol..." alt="Chevrolet Equinox EV" src="/content/dam/chevrol..." height="900" width="1600" fetchpriority="high">
<img srcset="/content/dam/chevrol..." alt="Chevrolet Blazer EV" src="/content/dam/chevrol..." height="900" width="1600" fetchpriority="high">
<img srcset="/content/dam/chevrol..." alt="Chevrolet Silverado ..." src="/content/dam/chevrol..." height="900" width="1600" fetchpriority="high">
Showing first 10 of 23 audited elements.
ARIA attributes must be used as specified for the element's role29 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 aria-haspopup="dialog">Truck*</button>
<button aria-haspopup="dialog">Value*</button>
<button aria-haspopup="dialog">Incentive*</button>
<button aria-haspopup="dialog">MSRP*</button>
<li data-id="electric" class="gb-tab-button default-tab stat-tab-link active" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Electric </div> </div> </li>
<li data-id="suvs" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> SUVs </div> </div> </li>
<li data-id="trucks" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Trucks </div> </div> </li>
<li data-id="performance" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Performance </div> </div> </li>
<div class="gb-expander-content" aria-hidden="false">
<button class="scrl-btn scrl-prev stat-arrow-prev scrl-disabled" aria-label="Previous Slide"></button>
Showing first 10 of 29 audited elements.
ARIA attributes must conform to valid names29 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 aria-haspopup="dialog">Truck*</button>
<button aria-haspopup="dialog">Value*</button>
<button aria-haspopup="dialog">Incentive*</button>
<button aria-haspopup="dialog">MSRP*</button>
<li data-id="electric" class="gb-tab-button default-tab stat-tab-link active" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Electric </div> </div> </li>
<li data-id="suvs" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> SUVs </div> </div> </li>
<li data-id="trucks" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Trucks </div> </div> </li>
<li data-id="performance" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Performance </div> </div> </li>
<div class="gb-expander-content" aria-hidden="false">
<button class="scrl-btn scrl-prev stat-arrow-prev scrl-disabled" aria-label="Previous Slide"></button>
Showing first 10 of 29 audited elements.
ARIA attributes must conform to valid values29 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 aria-haspopup="dialog">Truck*</button>
<button aria-haspopup="dialog">Value*</button>
<button aria-haspopup="dialog">Incentive*</button>
<button aria-haspopup="dialog">MSRP*</button>
<li data-id="electric" class="gb-tab-button default-tab stat-tab-link active" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Electric </div> </div> </li>
<li data-id="suvs" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> SUVs </div> </div> </li>
<li data-id="trucks" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Trucks </div> </div> </li>
<li data-id="performance" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Performance </div> </div> </li>
<div class="gb-expander-content" aria-hidden="false">
<button class="scrl-btn scrl-prev stat-arrow-prev scrl-disabled" aria-label="Previous Slide"></button>
Showing first 10 of 29 audited elements.
ARIA commands must have an accessible name16 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
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/chevy-trucks/master">
<gb-disclosure data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-1500-rst-2/master" role="button" class="gb-disclosure">
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/26-1500-rst/master">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-eev-rs/master" target="_self">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/msrp/master" target="_self">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/rotator-msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(7)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/rotator-msrp/master" target="_self">
Showing first 10 of 16 audited elements.
ARIA hidden element must not be focusable or contain focusable elements10 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
<iframe src="https://generalmotor..." sandbox="allow-same-origin al..." scrolling="no" frameborder="0" title="MPEL Storage" aria-hidden="true" style="height: 0px; width: ...">
<gb-flyout role="menuitem" aria-hidden="true" aria-label="submenu" flyout-id="more-flyout" close-button-label="Close Flyout" class="stacked-flyout">
<gb-flyout data-hamburger-menu="true" role="menuitem" aria-hidden="true" aria-label="submenu" flyout-id="primary-0" close-button-label="Close Flyout">
<gb-flyout role="menuitem" aria-hidden="true" aria-label="submenu" flyout-id="primary-1" close-button-label="Close Flyout">
<gb-flyout role="menuitem" aria-hidden="true" aria-label="submenu" flyout-id="primary-2" close-button-label="Close Flyout">
<div class="gb-expander-content" aria-hidden="true">
<div class="gb-expander-content" aria-hidden="true">
<div class="gb-expander-content" aria-hidden="true">
<div class="gb-expander-content" aria-hidden="true">
<div class="gb-expander-content" aria-hidden="true">
ARIA role should be appropriate for the element146 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
<div class="gb-print-header" role="banner">
<gb-global-nav enable-language-selector="true" lang-country-context="-" show-scroll-height="150" role="navigation" data-auth-content-active="show-unauth-users"> </gb-global-nav>
<gb-flyout role="menuitem" aria-hidden="true" aria-label="submenu" flyout-id="more-flyout" close-button-label="Close Flyout" class="stacked-flyout">
<div class="gb-flyouts-container" role="none">
<gb-flyout data-hamburger-menu="true" role="menuitem" aria-hidden="true" aria-label="submenu" flyout-id="primary-0" close-button-label="Close Flyout">
<gb-flyout role="menuitem" aria-hidden="true" aria-label="submenu" flyout-id="primary-1" close-button-label="Close Flyout">
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button></gb-disclosure>
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button></gb-disclosure>
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button></gb-disclosure>
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button></gb-disclosure>
Showing first 10 of 146 audited elements.
ARIA roles used must conform to valid values19 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
<gb-global-nav enable-language-selector="true" lang-country-context="-" show-scroll-height="150" role="navigation" data-auth-content-active="show-unauth-users"> </gb-global-nav>
<div class="gb-flyouts-container" role="none">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/chevy-trucks/master">
<gb-disclosure data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-1500-rst-2/master" role="button" class="gb-disclosure">
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/26-1500-rst/master">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-eev-rs/master" target="_self">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/msrp/master" target="_self">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/rotator-msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(7)</sup></gb-disclosure>
Showing first 10 of 19 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 data-image-lazy-load-enabled="true" class="generic_template_page base page basicpage disclosures-loaded" id="generic_template_page-ba428b42cc" data-cmp-link-accessibility-enabled="" data-cmp-link-accessibility-text="opens in a new tab" data-auth-content-active="show-unauth-users">
Buttons must have discernible text26 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="gb-visually-hide-show gb-skip-to-main-content gb-body1 stat-button-link" data-dtm="global nav"> Skip to Main Content </button>
<button class="gn-main-button ..." href="/content/chevrolet/n..." flyout="primary-0" data-dtm="global nav" data-hamburger-menu="true" data-flyout-pagetitl...="hamburger-menu">
<button class="gn-main-button ..." href="/content/chevrolet/n..." flyout="primary-1" title="Vehicles" data-dtm="global nav" data-dtm2="Vehicles" data-flyout-pagetitl...="vehicles">
<button class="gn-main-button stat-text-link " href="/content/chevrolet/na/us/en/portablenavigation/simplified-nav/primarynavigation/shop.html" flyout="primary-2" title="Shop" data-dtm="global nav" data-dtm2="Shop" data-flyout-pagetitle="shop">
<button class="gf-main-button stat-text-link" data-dtm="global nav">
<button aria-haspopup="dialog">Truck*</button>
<button aria-haspopup="dialog">Value*</button>
<button aria-haspopup="dialog">Incentive*</button>
<button aria-haspopup="dialog">MSRP*</button>
<button class="scrl-btn scrl-prev stat-arrow-prev scrl-disabled" aria-label="Previous Slide"></button>
Showing first 10 of 26 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
<gb-global-footer role="contentinfo" lang-country-context="-"> </gb-global-footer>
Deprecated ARIA roles must not be used19 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
<gb-global-nav enable-language-selector="true" lang-country-context="-" show-scroll-height="150" role="navigation" data-auth-content-active="show-unauth-users"> </gb-global-nav>
<div class="gb-flyouts-container" role="none">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/chevy-trucks/master">
<gb-disclosure data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-1500-rst-2/master" role="button" class="gb-disclosure">
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/26-1500-rst/master">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-eev-rs/master" target="_self">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/msrp/master" target="_self">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/rotator-msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(7)</sup></gb-disclosure>
Showing first 10 of 19 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 dir="ltr" lang="en-US" style="" class=" js no-touch csscolumns">
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
<gb-global-footer role="contentinfo" lang-country-context="-"> </gb-global-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 id="gb-main-content" tabindex="-1">
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 dir="ltr" lang="en-US" style="" class=" js no-touch csscolumns">
Elements must meet minimum color contrast ratio thresholds102 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
<select class="gb-geo-ip-notification-dropdown stat-dropdown" name="geoipDropdown">
<button class="gn-main-button ..." href="/content/chevrolet/n..." flyout="primary-1" title="Vehicles" data-dtm="global nav" data-dtm2="Vehicles" data-flyout-pagetitl...="vehicles">
<button class="gn-main-button stat-text-link " href="/content/chevrolet/na/us/en/portablenavigation/simplified-nav/primarynavigation/shop.html" flyout="primary-2" title="Shop" data-dtm="global nav" data-dtm2="Shop" data-flyout-pagetitle="shop">
<a class="gb-primary-button ..." href="https://www.costcoau..." data-link-type="external" target="_blank" title="Costco Member Offer" data-dtm="masthead:2026 silver...">
<a class="gb-primary-button ..." href="https://www.chevrole..." data-link-type="internal" target="_self" title="Current Offers" data-dtm="masthead:2026 equino...">
<h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Build<br>
& Price
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Current<br>
Offers
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Search<br>
Inventory
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Find a <br>
Dealer
</h2><h2 class="gb-headline
gb-none-margin gb-headline2-black text-center">
EVERY DRIVE STARTS HERE
</h2>Showing first 10 of 102 audited elements.
Elements must only use permitted ARIA attributes29 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 aria-haspopup="dialog">Truck*</button>
<button aria-haspopup="dialog">Value*</button>
<button aria-haspopup="dialog">Incentive*</button>
<button aria-haspopup="dialog">MSRP*</button>
<li data-id="electric" class="gb-tab-button default-tab stat-tab-link active" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Electric </div> </div> </li>
<li data-id="suvs" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> SUVs </div> </div> </li>
<li data-id="trucks" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Trucks </div> </div> </li>
<li data-id="performance" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Performance </div> </div> </li>
<div class="gb-expander-content" aria-hidden="false">
<button class="scrl-btn scrl-prev stat-arrow-prev scrl-disabled" aria-label="Previous Slide"></button>
Showing first 10 of 29 audited elements.
Elements must only use supported ARIA attributes22 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 aria-haspopup="dialog">Truck*</button>
<button aria-haspopup="dialog">Value*</button>
<button aria-haspopup="dialog">Incentive*</button>
<button aria-haspopup="dialog">MSRP*</button>
<div class="gb-expander-content" aria-hidden="false">
<button class="scrl-btn scrl-prev stat-arrow-prev scrl-disabled" aria-label="Previous Slide"></button>
<button aria-haspopup="dialog">*</button>
<button aria-haspopup="dialog">*</button>
<button aria-haspopup="dialog">*</button>
<button aria-haspopup="dialog">*</button>
Showing first 10 of 22 audited elements.
Elements should not have tabindex greater than zero9 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<div tabindex="-1" class="gb-main-content"></div>
<main id="gb-main-content" tabindex="-1">
<li data-id="electric" class="gb-tab-button default-tab stat-tab-link active" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Electric </div> </div> </li>
<li data-id="suvs" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> SUVs </div> </div> </li>
<li data-id="trucks" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Trucks </div> </div> </li>
<li data-id="performance" class="gb-tab-button stat-tab-link" data-dtm="vehicles" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> Performance </div> </div> </li>
<li data-id="equinox" class="gb-tab-button default-tab default-expander stat-tab-link active" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Equinox LT FWD </div> </div> </li>
<li data-id="colorado" class="gb-tab-button stat-tab-link" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Colorado Custom 2WD </div> </div> </li>
<li data-id="equinox-2" class="gb-tab-button stat-tab-link" data-dtm="offers" aria-selected="true" tabindex="0"> <div class="gb-tab-icon-title-container"> <div class="gb-tab-title"> 2026 Equinox EV LT 2 </div> </div> </li>
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 title="Search" class="autocomplete gb-search-input stat-search-input" type="text" required="" id="autocomplete" name="q" placeholder="Search" data-dtm="find it together">
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 title="Search" class="autocomplete gb-search-input stat-search-input" type="text" required="" id="autocomplete" name="q" placeholder="Search" data-dtm="find it together">
Heading levels should only increase by one18 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
<h2 class="gb-headline
gb-small-margin gb-body1 invert "><h2 class="gb-headline
gb-small-margin gb-body1 invert ">
<span class="gb-headline1-black invert">$10,000</span> Total Cash Allowance
</h2><h2 class="gb-headline
gb-none-margin gb-body1 invert "><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Build<br>
& Price
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Current<br>
Offers
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Search<br>
Inventory
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Find a <br>
Dealer
</h2><h2 class="gb-headline
gb-none-margin gb-headline2-black text-center">
EVERY DRIVE STARTS HERE
</h2><h2 class="gb-headline
gb-none-margin gb-headline4 ">
Bolt
</h2><h2 class="gb-headline
gb-none-margin gb-headline4 ">
Equinox EV
</h2>Showing first 10 of 18 audited elements.
Headings should not be empty18 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
<h2 class="gb-headline
gb-small-margin gb-body1 invert "><h2 class="gb-headline
gb-small-margin gb-body1 invert ">
<span class="gb-headline1-black invert">$10,000</span> Total Cash Allowance
</h2><h2 class="gb-headline
gb-none-margin gb-body1 invert "><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Build<br>
& Price
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Current<br>
Offers
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Search<br>
Inventory
</h2><h2 class="gb-headline
gb-medium-margin gb-headline4 ">
Find a <br>
Dealer
</h2><h2 class="gb-headline
gb-none-margin gb-headline2-black text-center">
EVERY DRIVE STARTS HERE
</h2><h2 class="gb-headline
gb-none-margin gb-headline4 ">
Bolt
</h2><h2 class="gb-headline
gb-none-margin gb-headline4 ">
Equinox EV
</h2>Showing first 10 of 18 audited elements.
Images must have alternative text24 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 class="gn-logo gn-nav-logo-image" src="/content/dam/chevrolet/na/us/english/portable-nav/chevrolet-bowtie-120.svg" alt="Chevrolet" title="Chevrolet">
<img class="gn-icon-svg
" src="/content/dam/chevrolet/na/us/english/primary-navigation-icons/hamburger.svg" alt="Additional Products and Services"><img src="/content/dam/chevrolet/na/us/english/portable-nav/account.svg" alt="profile">
<img alt="2026 Chevy Trucks" height="1000" width="2250" src="/content/dam/chevrolet/na/us/english/retail/march-2026/phase-1/hp/v2/truck-pack-hp-mast-desktop-v1.png?imwidth=1200" class="gb-rectangle-image-responsive gb-image">
<img alt="2026 Chevy Silverado 1500 RST 5.3L" height="1000" width="2250" src="/content/dam/chevrolet/na/us/english/retail/march-2026/phase-1/hp/v2/silverado-1500-26-hp-mast-desktop.png?imwidth=1200" class="gb-rectangle-image-responsive gb-image">
<img alt="2026 EQUINOX EV" height="1000" width="2250" src="/content/dam/chevrolet/na/us/english/retail/february-2026/phase-1/hp/equinox-ev-26-hp-mast-desktop.png?imwidth=1200" class="gb-rectangle-image-responsive gb-image">
<img srcset="/content/dam/chevrol..." alt="Chevrolet Bolt" src="/content/dam/chevrol..." height="900" width="1600" fetchpriority="high">
<img srcset="/content/dam/chevrol..." alt="Chevrolet Equinox EV" src="/content/dam/chevrol..." height="900" width="1600" fetchpriority="high">
<img srcset="/content/dam/chevrol..." alt="Chevrolet Blazer EV" src="/content/dam/chevrol..." height="900" width="1600" fetchpriority="high">
<img srcset="/content/dam/chevrol..." alt="Chevrolet Silverado ..." src="/content/dam/chevrol..." height="900" width="1600" fetchpriority="high">
Showing first 10 of 24 audited elements.
Inline text spacing must be adjustable with custom stylesheets24 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
<html dir="ltr" lang="en-US" style="" class=" js no-touch csscolumns">
<button class="indicator active" data-slide-num="0" style="flex-basis: 33.3333%;"> <div class="indicator-label"></div> <div class="indicator-bar"> <div class="gb-mccb-progress-bar" data-interval="7000" style="width: 111.9%;"></div> </div> </button>
<div class="gb-mccb-progress-bar" data-interval="7000" style="width: 111.9%;"></div>
<button class="indicator" data-slide-num="1" style="flex-basis: 33.3333%;"> <div class="indicator-label"></div> <div class="indicator-bar"> <div class="gb-mccb-progress-bar" data-interval="7000" style="width: 0%;"></div> </div> </button>
<button class="indicator" data-slide-num="2" style="flex-basis: 33.3333%;"> <div class="indicator-label"></div> <div class="indicator-bar"> <div class="gb-mccb-progress-bar" data-interval="7000" style="width: 0%;"></div> </div> </button>
<div style="height: 48px; width: 48px;" class="gb-universal-image gb-vector-image gb-rectangle-image gb-none-margin">
<div style="height: 48px; width: 99px;" class="gb-universal-image gb-vector-image gb-rectangle-image gb-none-margin">
<div style="height: 48px; width: 48px;" class="gb-universal-image gb-vector-image gb-rectangle-image gb-none-margin">
<div style="height: 48px; width: 99px;" class="gb-universal-image gb-vector-image gb-rectangle-image gb-none-margin">
<div style="height: 48px; width: 48px;" class="gb-universal-image gb-vector-image gb-rectangle-image gb-none-margin">
Showing first 10 of 24 audited elements.
Interactive controls must not be nested54 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="gb-visually-hide-show gb-skip-to-main-content gb-body1 stat-button-link" data-dtm="global nav"> Skip to Main Content </button>
<img class="gn-logo gn-nav-logo-image" src="/content/dam/chevrolet/na/us/english/portable-nav/chevrolet-bowtie-120.svg" alt="Chevrolet" title="Chevrolet">
<button class="gn-main-button ..." href="/content/chevrolet/n..." flyout="primary-0" data-dtm="global nav" data-hamburger-menu="true" data-flyout-pagetitl...="hamburger-menu">
<img class="gn-icon-svg
" src="/content/dam/chevrolet/na/us/english/primary-navigation-icons/hamburger.svg" alt="Additional Products and Services"><button class="gn-main-button ..." href="/content/chevrolet/n..." flyout="primary-1" title="Vehicles" data-dtm="global nav" data-dtm2="Vehicles" data-flyout-pagetitl...="vehicles">
<button class="gn-main-button stat-text-link " href="/content/chevrolet/na/us/en/portablenavigation/simplified-nav/primarynavigation/shop.html" flyout="primary-2" title="Shop" data-dtm="global nav" data-dtm2="Shop" data-flyout-pagetitle="shop">
<button class="gf-main-button stat-text-link" data-dtm="global nav">
<img src="/content/dam/chevrolet/na/us/english/portable-nav/account.svg" alt="profile">
<button aria-haspopup="dialog">Truck*</button>
<img alt="2026 Chevy Trucks" height="1000" width="2250" src="/content/dam/chevrolet/na/us/english/retail/march-2026/phase-1/hp/v2/truck-pack-hp-mast-desktop-v1.png?imwidth=1200" class="gb-rectangle-image-responsive gb-image">
Showing first 10 of 54 audited elements.
Landmarks 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.
Audit Elements
<main id="gb-main-content" tabindex="-1">
<gb-global-footer role="contentinfo" lang-country-context="-"> </gb-global-footer>
Links must be distinguishable without relying on color2 elements
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a class="internal stat-text-link auth-internal" href="/destination-freight-charges" data-dtm="footer" target="_self" rel="noopener noreferrer">destination freight charge</a>
<a class="internal stat-text-link auth-internal" href="/destination-freight-charges" data-dtm="footer" target="_self" rel="noopener noreferrer">destination freight charges</a>
Links must have discernible text83 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a href="/" class="stat-logo" title="Chevrolet" data-dtm="global nav"> <img class="gn-logo gn-nav-logo-image" src="/content/dam/chevrolet/na/us/english/portable-nav/chevrolet-bowtie-120.svg" alt="Chevrolet" title="Chevrolet"> </a>
<a class="gb-primary-button ..." href="https://www.costcoau..." data-link-type="external" target="_blank" title="Costco Member Offer" data-dtm="masthead:2026 chevy ...">
<a class="gb-secondary-button ..." href="https://www.chevrole..." data-link-type="internal" target="_self" title="Search Inventory" data-dtm="masthead:2026 chevy ...">
<a class="gb-primary-button ..." href="https://www.costcoau..." data-link-type="external" target="_blank" title="Costco Member Offer" data-dtm="masthead:2026 silver...">
<a class="gb-secondary-button ..." href="https://www.chevrole..." data-link-type="external" target="_self" title="Search Inventory" data-dtm="masthead:2026 silver...">
<a class="gb-primary-button ..." href="https://www.chevrole..." data-link-type="internal" target="_self" title="Current Offers" data-dtm="masthead:2026 equino...">
<a class="gb-secondary-button ..." href="https://www.chevrole..." data-link-type="external" target="_self" title="Search Inventory" data-dtm="masthead:2026 equino...">
<a href="https://www.chevrole..." class="gb-primary-wrapper ..." data-link-type="external" target="_self" data-dtm="next steps" data-dtm2="build and buy">
<a href="/current-offers" class="gb-primary-wrapper ..." data-link-type="internal" target="_self" data-dtm="next steps" data-dtm2="current offers">
<a href="https://www.chevrole..." class="gb-primary-wrapper ..." data-link-type="external" target="_self" data-dtm="next steps" data-dtm2="search inventory">
Showing first 10 of 83 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 id="gb-main-content" tabindex="-1">
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 dir="ltr" lang="en-US" style="" class=" js no-touch csscolumns">
Required ARIA attributes must be provided19 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
<gb-global-nav enable-language-selector="true" lang-country-context="-" show-scroll-height="150" role="navigation" data-auth-content-active="show-unauth-users"> </gb-global-nav>
<div class="gb-flyouts-container" role="none">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/chevy-trucks/master">
<gb-disclosure data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-1500-rst-2/master" role="button" class="gb-disclosure">
<gb-disclosure class="gb-disclosure" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/march_2026/phase_1/hp/26-1500-rst/master">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/retail/april_2026/phase_1/hp/26-eev-rs/master" target="_self">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/msrp/master" target="_self">
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/common-disclosures-library/msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(5)</sup></gb-disclosure>
<gb-disclosure class="gb-disclosure auth-internal" role="button" data-disclosure-id="/content/experience-fragments/chevrolet/na/us/en/index/index-sub-content/disclosures/rotator-msrp/master"><button aria-haspopup="dialog">*</button><sup class="q-disclosure-print-number">(7)</sup></gb-disclosure>
Showing first 10 of 19 audited elements.
Scrollable region must have keyboard access3 elements
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<adv-slides>
<adv-slides>
<adv-slides>
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">