Volkswagen vw.com
Accessibility score
League position
2ndof 9
Issues found
1
Audits passed
49
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
Serious<dt> and <dd> elements must be contained by a <dl>8 elements
Definition list items must follow a specific hierarchy: dl as parent, with alternating dt (term) and dd (description) children. Without this proper structure, the list becomes invalid and screen readers cannot inform users they're listening to a list or convey the relationships between terms and their definitions.
Failing Elements
<dt class="sc-fqkvVR huepRD">1.</dt>
Fix any of the following:
- Description list item does not have a <dl> parent element
<dd class="sc-fqkvVR huepRD">
Fix any of the following:
- Description list item does not have a <dl> parent element
<dt class="sc-fqkvVR huepRD">3.</dt>
Fix any of the following:
- Description list item does not have a <dl> parent element
<dd class="sc-fqkvVR huepRD">
Fix any of the following:
- Description list item does not have a <dl> parent element
<dt class="sc-fqkvVR behOnt"></dt>
Fix any of the following:
- Description list item does not have a <dl> parent element
<dd class="sc-fqkvVR behOnt">
Fix any of the following:
- Description list item does not have a <dl> parent element
<dt class="sc-fqkvVR behOnt"></dt>
Fix any of the following:
- Description list item does not have a <dl> parent element
<dd class="sc-fqkvVR behOnt">
Fix any of the following:
- Description list item does not have a <dl> parent element
Passed audits49 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" dir="ltr" class="js-enabled" style="--100vh: 800px;">
<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" dir="ltr" class="js-enabled" style="--100vh: 800px;">
<li> elements must be contained in a <ul> or <ol>49 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="sc-flBipw kuCZZS"><button data-testid="topbar-nav-primary-menu-flyout" aria-controls="navigation-flyout" aria-expanded="false" class="sc-dhKdcB cRrNlP"><span class="sc-gsFSXq jNKHXW">Menu</span></button></li>
<li class="sc-flBipw kuCZZS"><a href="/en/offers.html" class="CmsPlainLink__StyledPlainLink-sc-26ade311-0 eAcYOo">Offers</a></li>
<li class="sc-flBipw kuCZZS"><a href="/en/dealer-search.html" class="CmsPlainLink__StyledPlainLink-sc-26ade311-0 eAcYOo">Find a Dealer</a></li>
<li class="sc-flBipw kuCZZS"><a href="/en/inventory.html" class="CmsPlainLink__StyledPlainLink-sc-26ade311-0 eAcYOo">Search Inventory</a></li>
<li></li>
Showing first 5 of 49 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements7 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 data-testid="topbar-nav-primary-menu" class="sc-jNwOwP zkgin">
<ul data-testid="topbar-nav-primary-quick-actions" class="sc-cpgxJx cmyyXn">
<ol data-component="disclaimer" class="sc-dAbbOL fWodKI">
<ul class="expand-collapse-module__StyledList-sc-dd384e3f-1 dCSqMB">
<ol data-component="disclaimer" class="sc-dAbbOL fWodKI">
Showing first 5 of 7 audited elements.
All page content should be contained by landmarks997 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div id="cookiemgmt">
<section>
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<div id="ensBannerDescription">
<p>
Showing first 5 of 997 audited elements.
Alternative text of images should not be repeated as text10 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="sc-bbSZdi LCeKu" src="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 9' />" alt="A Jetta shown in Kings Red Metallic is parked at a college campus while a student walks toward the Jetta.">
<img class="sc-bbSZdi LCeKu lazyloading" src="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 9' />" alt="Front view of an Tiguan in Platinum Gray Metallic parked in front of house with the front gate and driveway in the background.">
<img class="sc-bbSZdi LCeKu lazyloaded" src="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 9' />" alt="A 3/4 profile view of a Atlas shown in Avocado Green Metallic parked in a lot with a shed and bushes in the background.">
<img class="sc-bbSZdi LCeKu lazy..." src="data:image/gif;base6..." data-src="https://assets.volks..." data-srcset="https://assets.volks..." data-sizes="(min-width: 560px) 5..." alt="Profile view of an A..." data-srcset-webp="https://assets.volks...">
<img class="sc-bbSZdi LCeKu lazy..." src="data:image/gif;base6..." data-src="https://assets.volks..." data-srcset="https://assets.volks..." data-sizes="(min-width: 560px) 5..." alt="Close up profile rea..." data-srcset-webp="https://assets.volks...">
Showing first 5 of 10 audited elements.
ARIA attributes must be used as specified for the element's role32 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<button id="ensAcceptAll" aria-label="Accept All" class="button raised blue">Accept All</button>
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">Required Only</button>
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">Settings</button>
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
Showing first 5 of 32 audited elements.
ARIA attributes must conform to valid names32 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<button id="ensAcceptAll" aria-label="Accept All" class="button raised blue">Accept All</button>
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">Required Only</button>
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">Settings</button>
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
Showing first 5 of 32 audited elements.
ARIA attributes must conform to valid values32 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<button id="ensAcceptAll" aria-label="Accept All" class="button raised blue">Accept All</button>
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">Required Only</button>
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">Settings</button>
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
Showing first 5 of 32 audited elements.
ARIA dialog and alertdialog nodes should have an accessible name1 element
Screen reader users cannot identify the purpose of role="dialog" or role="alertdialog" elements without an accessible name. This leaves users confused about what dialog they've encountered and what it contains.
Audit Elements
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
ARIA hidden element must not be focusable or contain focusable elements14 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 xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true">
<svg width="24px" height="24px" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" fill="currentColor" role="img" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true">
<nav role="navigation" aria-hidden="true" class="SSRNavigation__StyledNav-sc-eafc8b2e-0 iaRRTc">
<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M6.835 4.5h1.33v15h-1.33zM15.835 4.5h1.33v15h-1.33z"></path></svg>
Showing first 5 of 14 audited elements.
ARIA role should be appropriate for the element43 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 id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" tabindex="-1">
<div class="description" id="defaultdescription" role="definition"><p></p></div>
<div class="description" id="Targetingdescription" role="definition"><p></p></div>
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
Showing first 5 of 43 audited elements.
ARIA roles used must conform to valid values24 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
<header data-testid="topbar-nav-header" role="banner" class="sc-bYHUQc hJNLqf">
<div aria-label="Carousel" role="region" data-testid="stage-slide-wrapper" class="sc-bTcWjT bysZkS" style="--slideHeight: 810px;">
<div aria-label="Slides of the media gallery" role="tablist" class="sc-idPYgo hYlMri">
Showing first 5 of 24 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="js-personalization-show-default">
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 data-testid="topbar-nav-header" role="banner" class="sc-bYHUQc hJNLqf">
Buttons must have discernible text15 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 id="ensAcceptAll" aria-label="Accept All" class="button raised blue">Accept All</button>
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">Required Only</button>
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">Settings</button>
<button data-testid="topbar-nav-primary-menu-flyout" aria-controls="navigation-flyout" aria-expanded="false" class="sc-dhKdcB cRrNlP"><span class="sc-gsFSXq jNKHXW">Menu</span></button>
<button aria-label="Search" class="sc-fiCwlc iIoQmf">
Showing first 5 of 15 audited elements.
Certain ARIA roles must be contained by particular parents13 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Audit Elements
<button role="tab" id="stage-slide-bullet-0" aria-controls="stage-slide-panel-0" aria-selected="true" aria-label="Slide 3" tabindex="0" class="sc-fhvnAp laruZe"></button>
<button role="tab" id="stage-slide-bullet-1" aria-controls="stage-slide-panel-1" aria-selected="false" aria-label="Slide 3" tabindex="-1" class="sc-fhvnAp kswRUm"></button>
<button role="tab" id="stage-slide-bullet-2" aria-controls="stage-slide-panel-2" aria-selected="false" aria-label="Feels big inside, drives big outside. That’s versatility." tabindex="-1" class="sc-fhvnAp kswRUm"></button>
<button role="tab" id="stage-slide-bullet-3" aria-controls="stage-slide-panel-3" aria-selected="false" aria-label="Welcome to you, in the 2026 Tiguan" tabindex="-1" class="sc-fhvnAp kswRUm"></button>
<li role="listitem" class="bottom-nav__StyledBottomNavChild-sc-a31a4d40-5 jLaizA"><span class="sc-fqkvVR UzoRZ"><a href="/en/privacy.html#cookies-and-tracking" class="sc-dhKdcB gGbSEM"><span class="sc-gsFSXq jNKHXW">AdChoices</span></a></span></li>
Showing first 5 of 13 audited elements.
Certain ARIA roles must contain particular children6 elements
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Audit Elements
<div aria-label="Slides of the media gallery" role="tablist" class="sc-idPYgo hYlMri">
<ul role="list" class="sc-eeDRCY ipnfdy">
<ul role="list" class="sc-eeDRCY ipnfdy">
<ul role="list" class="sc-eeDRCY ipnfdy">
<ul role="list" class="sc-eeDRCY ipnfdy">
Showing first 5 of 6 audited elements.
Content must reflow without two-dimensional scrolling3 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="sc-kTYlsj gtnACJ" style="transform: translate3d(-16.6667%, 0px, 0px);">
<div class="sc-hfAwGc culLkH" style="transform: translateX(0%);">
<div class="sc-hfAwGc culLkH" style="transform: translateX(0%);">
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 class="footer__StyledFooter-sc-35f581e8-4 ecmLVr">
Deprecated ARIA roles must not be used24 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
<header data-testid="topbar-nav-header" role="banner" class="sc-bYHUQc hJNLqf">
<div aria-label="Carousel" role="region" data-testid="stage-slide-wrapper" class="sc-bTcWjT bysZkS" style="--slideHeight: 810px;">
<div aria-label="Slides of the media gallery" role="tablist" class="sc-idPYgo hYlMri">
Showing first 5 of 24 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" dir="ltr" class="js-enabled" style="--100vh: 800px;">
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 data-testid="topbar-nav-header" role="banner" class="sc-bYHUQc hJNLqf">
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 class="footer__StyledFooter-sc-35f581e8-4 ecmLVr">
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="sc-czLspv eJLzdT">
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" dir="ltr" class="js-enabled" style="--100vh: 800px;">
Elements marked as presentational should be consistently ignored1 element
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img class="sc-bbSZdi LCeKu lazyload " src="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 9' />" alt="">
Elements must meet minimum color contrast ratio thresholds163 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
<a href="https://www.vw.com/privacy/">Privacy Statement</a>
<button id="ensAcceptAll" aria-label="Accept All" class="button raised blue">Accept All</button>
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">Required Only</button>
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">Settings</button>
<span class="sc-fqkvVR kzIVHZ">Search Inventory</span>
Showing first 5 of 163 audited elements.
Elements must only use permitted ARIA attributes31 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<button id="ensAcceptAll" aria-label="Accept All" class="button raised blue">Accept All</button>
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">Required Only</button>
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">Settings</button>
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
Showing first 5 of 31 audited elements.
Elements must only use supported ARIA attributes32 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<button id="ensAcceptAll" aria-label="Accept All" class="button raised blue">Accept All</button>
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">Required Only</button>
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">Settings</button>
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
Showing first 5 of 32 audited elements.
Elements should not have tabindex greater than zero26 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 id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<div id="back-to-Top" tabindex="-1" class="AnchorTarget__StyledAnchorTarget-sc-7886fa1d-1 lmpyzx"></div>
<button role="tab" id="stage-slide-bullet-0" aria-controls="stage-slide-panel-0" aria-selected="true" aria-label="Slide 3" tabindex="0" class="sc-fhvnAp laruZe"></button>
<button role="tab" id="stage-slide-bullet-1" aria-controls="stage-slide-panel-1" aria-selected="false" aria-label="Slide 3" tabindex="-1" class="sc-fhvnAp kswRUm"></button>
<button role="tab" id="stage-slide-bullet-2" aria-controls="stage-slide-panel-2" aria-selected="false" aria-label="Feels big inside, drives big outside. That’s versatility." tabindex="-1" class="sc-fhvnAp kswRUm"></button>
Showing first 5 of 26 audited elements.
Focused elements must not be entirely hidden by author-created content5 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<a href="https://www.vw.com/privacy/">
<button id="ensAcceptAll" aria-label="Accept All" class="button raised blue">
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">
Heading levels should only increase by one19 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="sc-fqkvVR lbFxon" id="heading"><span class="sc-cwHptR bWghLP">Today’s the day—and your ride is the Jetta</span></h1>
<h2 class="sc-fqkvVR iuFcvW"><span class="sc-cwHptR bWghLP"><b>Offers</b></span></h2>
<h3 class="sc-fqkvVR jwYGlj"><span class="sc-cwHptR hcVzmQ"><b><sub>2026 Tiguan Models</sub><br> $3,000 Customer Bonus on <br><span class="TextWithNonBreakingSafewords__StyledSafeWord-sc-a153e0f-0 cTSiyk">select</span> trims**<br> </b></span></h3>
<h3 class="sc-fqkvVR jwYGlj">
<h2 class="sc-fqkvVR iuFcvW"><span class="sc-cwHptR bWghLP"><b><span class="TextWithNonBreakingSafewords__StyledSafeWord-sc-a153e0f-0 cTSiyk">Volkswagen</span> innovation never stops. So let’s go.</b></span></h2>
Showing first 5 of 19 audited elements.
Headings should not be empty19 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="sc-fqkvVR lbFxon" id="heading"><span class="sc-cwHptR bWghLP">Today’s the day—and your ride is the Jetta</span></h1>
<h2 class="sc-fqkvVR iuFcvW"><span class="sc-cwHptR bWghLP"><b>Offers</b></span></h2>
<h3 class="sc-fqkvVR jwYGlj"><span class="sc-cwHptR hcVzmQ"><b><sub>2026 Tiguan Models</sub><br> $3,000 Customer Bonus on <br><span class="TextWithNonBreakingSafewords__StyledSafeWord-sc-a153e0f-0 cTSiyk">select</span> trims**<br> </b></span></h3>
<h3 class="sc-fqkvVR jwYGlj">
<h2 class="sc-fqkvVR iuFcvW"><span class="sc-cwHptR bWghLP"><b><span class="TextWithNonBreakingSafewords__StyledSafeWord-sc-a153e0f-0 cTSiyk">Volkswagen</span> innovation never stops. So let’s go.</b></span></h2>
Showing first 5 of 19 audited elements.
IDs used in ARIA and labels must be unique13 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
<div id="ensBannerDescription">
<header class="ensTitle" id="ensTitle"><h3>Cookie and Tracking Technology Preferences</h3></header>
<div class="consentDescription" id="ensDescription">
<input class="ensCheckbox" aria-describedby="defaultdescription" id="defaultSlide" type="checkbox" name="defaultSlide" checked="" disabled="">
<div class="description" id="defaultdescription" role="definition"><p></p></div>
Showing first 5 of 13 audited elements.
Images must have alternative text10 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="sc-bbSZdi LCeKu" src="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 9' />" alt="A Jetta shown in Kings Red Metallic is parked at a college campus while a student walks toward the Jetta.">
<img class="sc-bbSZdi LCeKu lazyloading" src="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 9' />" alt="Front view of an Tiguan in Platinum Gray Metallic parked in front of house with the front gate and driveway in the background.">
<img class="sc-bbSZdi LCeKu lazyloaded" src="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 9' />" alt="A 3/4 profile view of a Atlas shown in Avocado Green Metallic parked in a lot with a shed and bushes in the background.">
<img class="sc-bbSZdi LCeKu lazy..." src="data:image/gif;base6..." data-src="https://assets.volks..." data-srcset="https://assets.volks..." data-sizes="(min-width: 560px) 5..." alt="Profile view of an A..." data-srcset-webp="https://assets.volks...">
<img class="sc-bbSZdi LCeKu lazy..." src="data:image/gif;base6..." data-src="https://assets.volks..." data-srcset="https://assets.volks..." data-sizes="(min-width: 560px) 5..." alt="Close up profile rea..." data-srcset-webp="https://assets.volks...">
Showing first 5 of 10 audited elements.
Inline text spacing must be adjustable with custom stylesheets6 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 lang="en" dir="ltr" class="js-enabled" style="--100vh: 800px;">
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<div aria-label="Carousel" role="region" data-testid="stage-slide-wrapper" class="sc-bTcWjT bysZkS" style="--slideHeight: 810px;">
<div data-testid="sticky-wrapper" class="sc-jDGquE jJwWte" style="--mediaHeight: 720px;">
<div data-testid="nav-wrapper" class="sc-mkoLC KcaMq" style="--mediaHeight: 720px;">
Showing first 5 of 6 audited elements.
Interactive controls must not be nested24 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 id="ensAcceptAll" aria-label="Accept All" class="button raised blue">Accept All</button>
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">Required Only</button>
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">Settings</button>
<button data-testid="topbar-nav-primary-menu-flyout" aria-controls="navigation-flyout" aria-expanded="false" class="sc-dhKdcB cRrNlP"><span class="sc-gsFSXq jNKHXW">Menu</span></button>
<button aria-label="Search" class="sc-fiCwlc iIoQmf">
Showing first 5 of 24 audited elements.
Interactive elements must have a visible focus indicator5 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<a href="https://www.vw.com/privacy/">
<button id="ensAcceptAll" aria-label="Accept All" class="button raised blue">
<button id="ensRejectAll" aria-label="Required Only" class="button raised blue">
<button id="ensOpenModal" aria-label="Settings" class="button raised blue">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination12 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
<header data-testid="topbar-nav-header" role="banner" class="sc-bYHUQc hJNLqf">
<nav data-testid="topbar-nav-primary" aria-label="Primary" class="sc-gObJpS gTQDtM">
<main class="sc-czLspv eJLzdT">
<div aria-label="Carousel" role="region" data-testid="stage-slide-wrapper" class="sc-bTcWjT bysZkS" style="--slideHeight: 810px;">
Showing first 5 of 12 audited elements.
lang attribute must have a valid value2 elements
Screen readers use language-specific pronunciation libraries that must match the content's language. Invalid language declarations cause screen readers to use the wrong pronunciation library, making content sound confusing or unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<a lang="en" href="/en.html" class="sc-dhKdcB gGbSEM"><span class="sc-gsFSXq jNKHXW">English</span></a>
<a lang="es" href="/es.html" class="sc-dhKdcB gGbSEM"><span class="sc-gsFSXq jNKHXW">Español</span></a>
Links must be distinguishable without relying on color1 element
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 href="https://www.vw.com/privacy/">Privacy Statement</a>
Links must have discernible text67 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="https://www.vw.com/privacy/">Privacy Statement</a>
<a href="#" class="sc-jXbUNg gJWeRx"><span class="sc-fqkvVR kzIVHZ">Skip to main content</span></a>
<a href="#" class="sc-jXbUNg gJWeRx"><span class="sc-fqkvVR kzIVHZ">Skip to footer</span></a>
<a href="/en.html" aria-label="Volkswagen" class="CmsPlainLink__StyledPlainLink-sc-26ade311-0 eAcYOo">
<a href="/en/offers.html" class="CmsPlainLink__StyledPlainLink-sc-26ade311-0 eAcYOo">Offers</a>
Showing first 5 of 67 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="sc-czLspv eJLzdT">
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" dir="ltr" class="js-enabled" style="--100vh: 800px;">
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" dir="ltr" class="js-enabled" style="--100vh: 800px;">
Required ARIA attributes must be provided24 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
<div id="ensNotifyBanner" class="ensNotifyBanner" role="dialog" aria-label="Consent Banner" aria-describedby="ensBannerDescription" data-nosnippet="true" tabindex="0" style="display: block; left: 0px;">
<nav role="navigation" aria-label="Accessibility Links" class="sc-bdlOLf itfjpM">
<header data-testid="topbar-nav-header" role="banner" class="sc-bYHUQc hJNLqf">
<div aria-label="Carousel" role="region" data-testid="stage-slide-wrapper" class="sc-bTcWjT bysZkS" style="--slideHeight: 810px;">
<div aria-label="Slides of the media gallery" role="tablist" class="sc-idPYgo hYlMri">
Showing first 5 of 24 audited elements.
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta data-react-helmet="true" name="viewport" content="width=device-width">
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 data-react-helmet="true" name="viewport" content="width=device-width">
How does your site stack up against Volkswagen?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Automotive