Audiaudi.com
Accessibility Score
Issues Found
Issues Found
SeriousElements must meet minimum color contrast ratio thresholds18 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
<h3 class="flex--title"> Formula 1® and Audi </h3>
Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #36393e, background color: #101319, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1
<p>Exploring the complex logistics behind Audi’s Formula 1 commitment<br></p>
Fix any of the following:
- Element has insufficient color contrast of 1.35 (foreground color: #2b2d33, background color: #101319, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="/en/articles/when-the-rear-wing-has-to-go-in-your-carry-on-a-look-into-the-different-worlds-of-logistics-at-audi-18029" class="up-can-clean">Learn more</a>
Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #36393e, background color: #101319, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<h3 class="flex--title"> Driving sustainability </h3>
Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #36393e, background color: #101319, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1
<p>Advancing electric mobility and embedding sustainability across the value chain</p>
Fix any of the following:
- Element has insufficient color contrast of 1.35 (foreground color: #2b2d33, background color: #101319, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="/en/sustainability-17137" class="up-can-clean">Learn more</a>
Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #36393e, background color: #101319, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<h3 class="flex--title"> Behind the scenes </h3>
Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #36393e, background color: #101319, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1
<p>How Audi is preparing for the era of the software-defined vehicle<br></p>
Fix any of the following:
- Element has insufficient color contrast of 1.35 (foreground color: #2b2d33, background color: #101319, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="/en/articles/the-future-is-created-in-the-pilot-hall-hardware-and-software-combined-with-passion-18098?node=40368" class="up-can-clean">Learn more</a>
Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #36393e, background color: #101319, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<h3 class="flex--title"> Key statements </h3>
Fix any of the following:
- Element has insufficient color contrast of 1.6 (foreground color: #36393e, background color: #101319, font size: 15.0pt (20px), font weight: normal). Expected contrast ratio of 4.5:1
Showing first 10 of 18 failing elements.
SeriousLinks must have discernible text1 element
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Failing Elements
<a class="header--title up-can-clean" href="/en"> <span class="brand-title"> <span class="brand-title--logo"></span> </span> </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
ModerateHeading levels should only increase by one2 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Failing Elements
<h4 class="main-stage-list-item--title" hyphenate="true"> Audi Nuvolari at Goodwood Festival of Speed </h4>
Fix any of the following:
- Heading order invalid
<h4 class="teaser-card--title" hyphenate="true"> <a href="/en/press-releases/the-right-car-for-any-situation-the-audi-q4-e-tron-takes-to-the-streets-18015" class="up-can-clean">The right car for any situation: the Audi Q4 <span class="nowrap">e-tron</span> takes to the streets</a> </h4>
Fix any of the following:
- Heading order invalid
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
<nav class="layout--breadcrumb-bar layout-breadcrumb-bar" up-hungry="true" up-id="breadcrumb">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
Passed Audits
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en" class="alpha-redesign privacy-increased-width privacy-en-DE privacy-v2" up-source="/en">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en" class="alpha-redesign privacy-increased-width privacy-en-DE privacy-v2" up-source="/en">
<li> elements must be contained in a <ul> or <ol>6 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> <a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/audi-at-a-glance-15904"><div class="topic-teaser-element--text"> Audi at a glance </div> </a></li>
<li> <a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/models-4"><div class="topic-teaser-element--text"> Models </div> </a></li>
<li> <a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/formula-1r-17158"><div class="topic-teaser-element--text"> Formula 1® </div> </a></li>
<li> <a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/investor-relations-17156"><div class="topic-teaser-element--text"> Investor Relations </div> </a></li>
<li> <a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/careers-at-audidriven-by-tech-driven-by-people-17124"><div class="topic-teaser-element--text"> Careers </div> </a></li>
<li> <a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/service-2305"><div class="topic-teaser-element--text"> Media </div> </a></li>
<ul> and <ol> must only directly contain <li>, <script> or <template> elements1 element
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul class="grid -topic-teaser" style="--topic-teaser-element-count: 6">
All page content should be contained by landmarks380 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 tracking-setup="true" up-data="{"trackingDomain":"//stats.audi-mediacenter.com","trackingId":5}"></div><div up-hungry="true" up-id="track-page-view">
<div track-page-view="true" ...>
<div class="layout--banner up-can-clean" up-fixed="top"> <div up-hungry="true" up-id="layout-banner-contents"></div> </div>
<div up-hungry="true" up-id="layout-banner-contents"></div>
<header class="layout--header up-can-clean" up-fixed="top">
<div class="header up-can-clean" style="--title-width: 69px; --menu-width: 0px;">
<a class="header--title up-can-clean" href="/en"> <span class="brand-title"> <span class="brand-title--logo"></span> </span> </a>
<span class="brand-title"> <span class="brand-title--logo"></span> </span>
<span class="brand-title--logo"></span>
Showing first 10 of 380 audited elements.
Alternative text of images should not be repeated as text15 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img alt="Audi Q6 e-tron Lifec..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="1438px">
<img alt="Audi Nuvolari at Goo..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi Q3 Sportback - ..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="179.34065934065933px">
<img alt="Audi RS 5 Avant - Au..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="153px">
<img alt="Audi A6 allroad - Au..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi Revolut F1 Team..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="All charged up: from..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Raphaela Fritz - Rap..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi presents its fi..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Team meeting at a co..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
Showing first 10 of 15 audited elements.
ARIA attributes must be used as specified for the element's role3 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
<a class="btn btn-icon up-can-clean" aria-label="Search" title="Search" header-search-bar-opener="true" up-instant="false" href="/en/search"><span class="icon -header-search"></span> </a>
<div aria-live="polite" class="screen-reader-only" id="screen-reader-announcements-container"></div>
<a class="btn btn-secondary" target="_blank" aria-labelledby="item-ae00da29-e478-49fe-a03a-58c99d4c0016-title" title="Learn more" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow"><span class="icon -flex-external-link -spacer"></span>Discover Audi Models</a>
ARIA attributes must conform to valid names3 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
<a class="btn btn-icon up-can-clean" aria-label="Search" title="Search" header-search-bar-opener="true" up-instant="false" href="/en/search"><span class="icon -header-search"></span> </a>
<div aria-live="polite" class="screen-reader-only" id="screen-reader-announcements-container"></div>
<a class="btn btn-secondary" target="_blank" aria-labelledby="item-ae00da29-e478-49fe-a03a-58c99d4c0016-title" title="Learn more" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow"><span class="icon -flex-external-link -spacer"></span>Discover Audi Models</a>
ARIA attributes must conform to valid values3 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
<a class="btn btn-icon up-can-clean" aria-label="Search" title="Search" header-search-bar-opener="true" up-instant="false" href="/en/search"><span class="icon -header-search"></span> </a>
<div aria-live="polite" class="screen-reader-only" id="screen-reader-announcements-container"></div>
<a class="btn btn-secondary" target="_blank" aria-labelledby="item-ae00da29-e478-49fe-a03a-58c99d4c0016-title" title="Learn more" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow"><span class="icon -flex-external-link -spacer"></span>Discover Audi Models</a>
ARIA hidden element must not be focusable or contain focusable elements3 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<div aria-hidden="true" class="main-stage-list--divider"></div>
<div aria-hidden="true" class="main-stage-list--divider"></div>
<svg aria-hidden="true" role="presentation" id="logo" viewBox="0 0 90 32" width="80" height="80">
ARIA role should be appropriate for the element15 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
<input aria-autocomplete="list" aria-label="Search" autocomplete="off" class="form-control up-can-clean" name="query" placeholder="What are you looking for today?" role="combobox" search-input="true" type="text" aria-controls="" aria-expanded="false">
<input aria-autocomplete="list" aria-label="Search" autocomplete="off" class="form-control up-can-clean" name="query" placeholder="Search" role="combobox" search-input="true" type="text" aria-controls="" aria-expanded="false">
<input aria-autocomplete="list" aria-label="Search" autocomplete="off" autofocus="" class="form-control -iconless" name="query" role="combobox" search-input="true" type="text" aria-controls="" aria-expanded="false">
<div class="layout--flashes" role="alert" up-flashes="true" up-hungry="" up-if-layer="subtree" up-keep=""> </div>
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom">
<svg aria-hidden="true" role="presentation" id="logo" viewBox="0 0 90 32" width="80" height="80">
<div class="ensToggleRowWrapper" role="list">
<div class="ensToggleRow" role="listitem" style="opacity: .5;" id="toggleRow-default">
<div class="description" id="defaultdescription" role="definition">
<div class="ensToggleRow" role="listitem" id="toggleRow-functional">
Showing first 10 of 15 audited elements.
ARIA roles used must conform to valid values1 element
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 class="layout--flashes" role="alert" up-flashes="true" up-hungry="" up-if-layer="subtree" up-keep=""> </div>
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 add-body-classes="true" class="layout up-can-clean" data-available-local...="["de", "en"]" data-base-url="https://www.audi.com..." data-environment="production" up-data="{"classNames":[]}" zoom-detector="" data-device-type="desktop" data-safari="false" style="--consumption-data-b..." ...>Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header class="layout--header up-can-clean" up-fixed="top">
Buttons must have discernible text1 element
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="header--menu btn btn-text from-md" main-menu-opener="true" type="button"> <span class="icon -header-menu -spacer"></span><span>Menu</span> </button>
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="layout--footer">
Deprecated ARIA roles must not be used1 element
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 class="layout--flashes" role="alert" up-flashes="true" up-hungry="" up-if-layer="subtree" up-keep=""> </div>
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en" class="alpha-redesign privacy-increased-width privacy-en-DE privacy-v2" up-source="/en">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header class="layout--header up-can-clean" up-fixed="top">
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="layout--footer">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main class="layout--content">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en" class="alpha-redesign privacy-increased-width privacy-en-DE privacy-v2" up-source="/en">
Elements must meet minimum color contrast ratio thresholds63 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
<span>Menu</span>
<input aria-autocomplete="list" aria-label="Search" autocomplete="off" class="form-control up-can-clean" name="query" placeholder="What are you looking for today?" role="combobox" search-input="true" type="text" aria-controls="" aria-expanded="false">
<input aria-autocomplete="list" aria-label="Search" autocomplete="off" class="form-control up-can-clean" name="query" placeholder="Search" role="combobox" search-input="true" type="text" aria-controls="" aria-expanded="false">
<input aria-autocomplete="list" aria-label="Search" autocomplete="off" autofocus="" class="form-control -iconless" name="query" role="combobox" search-input="true" type="text" aria-controls="" aria-expanded="false">
<a rel="alternate" up-follow="false" up-preload="false" href="/de?set_locale=true">DE</a>
<a class="-active" rel="alternate" up-follow="false" up-preload="false" href="/en?set_locale=true">EN</a>
<h1 id="discover-audi">Discover Audi </h1>
<p>Company. People. Innovations.</p>
<span>Learn more</span>
<h4 class="main-stage-list-item--title" hyphenate="true"> Audi Nuvolari at Goodwood Festival of Speed </h4>
Showing first 10 of 63 audited elements.
Elements must only use permitted ARIA attributes3 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
<a class="btn btn-icon up-can-clean" aria-label="Search" title="Search" header-search-bar-opener="true" up-instant="false" href="/en/search"><span class="icon -header-search"></span> </a>
<div aria-live="polite" class="screen-reader-only" id="screen-reader-announcements-container"></div>
<a class="btn btn-secondary" target="_blank" aria-labelledby="item-ae00da29-e478-49fe-a03a-58c99d4c0016-title" title="Learn more" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow"><span class="icon -flex-external-link -spacer"></span>Discover Audi Models</a>
Elements must only use supported ARIA attributes3 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
<a class="btn btn-icon up-can-clean" aria-label="Search" title="Search" header-search-bar-opener="true" up-instant="false" href="/en/search"><span class="icon -header-search"></span> </a>
<div aria-live="polite" class="screen-reader-only" id="screen-reader-announcements-container"></div>
<a class="btn btn-secondary" target="_blank" aria-labelledby="item-ae00da29-e478-49fe-a03a-58c99d4c0016-title" title="Learn more" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow"><span class="icon -flex-external-link -spacer"></span>Discover Audi Models</a>
Elements should not have tabindex greater than zero4 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
<a tabindex="-1" target="_blank" class="external-page-card--intro" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow"><p>Find the configurator, pricing, and purchase and leasing information here.</p> </a>
<a tabindex="-1" href="/en/press-releases/the-right-car-for-any-situation-the-audi-q4-e-tron-takes-to-the-streets-18015" class="up-can-clean">
<a tabindex="-1" href="/en/press-releases/upgrade-for-audi-a3-models-18028" class="up-can-clean">
<a tabindex="-1" href="/en/press-releases/audi-nuvolari-from-the-racetrack-to-series-production-at-record-pace-18013" class="up-can-clean">
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
<h1 id="discover-audi">Discover Audi </h1>
<h2 class="main-stage-main-content-info--title"> A seamless experience: in-car entertainment in the Audi Q6 <span class="nowrap">e-tron</span> </h2>
<h4 class="main-stage-list-item--title" hyphenate="true"> Audi upgrades the Q3 for the 2027 model year </h4>
<h4 class="main-stage-list-item--title" hyphenate="true"> Two characters. One <span class="nowrap">RS 5</span>. </h4>
<h2 class="cars-overview-teaser--title"> Audi Models </h2>
<h3 class="external-page-card--title" id="item-ae00da29-e478-49fe-a03a-58c99d4c0016-title"> <a target="_blank" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow">Discover the Audi Models </a></h3>
<h2 id="step-into-the-world-of-audi">Step into the world of Audi </h2>
<h3 class="flex--title"> Formula 1® and Audi </h3>
<h3 class="flex--title"> Driving sustainability </h3>
<h3 class="flex--title"> Behind the scenes </h3>
Showing first 10 of 18 audited elements.
Headings should not be empty20 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 id="discover-audi">Discover Audi </h1>
<h2 class="main-stage-main-content-info--title"> A seamless experience: in-car entertainment in the Audi Q6 <span class="nowrap">e-tron</span> </h2>
<h4 class="main-stage-list-item--title" hyphenate="true"> Audi Nuvolari at Goodwood Festival of Speed </h4>
<h4 class="main-stage-list-item--title" hyphenate="true"> Audi upgrades the Q3 for the 2027 model year </h4>
<h4 class="main-stage-list-item--title" hyphenate="true"> Two characters. One <span class="nowrap">RS 5</span>. </h4>
<h2 class="cars-overview-teaser--title"> Audi Models </h2>
<h3 class="external-page-card--title" id="item-ae00da29-e478-49fe-a03a-58c99d4c0016-title"> <a target="_blank" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow">Discover the Audi Models </a></h3>
<h2 id="step-into-the-world-of-audi">Step into the world of Audi </h2>
<h3 class="flex--title"> Formula 1® and Audi </h3>
<h3 class="flex--title"> Driving sustainability </h3>
Showing first 10 of 20 audited elements.
IDs used in ARIA and labels must be unique10 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
<h3 class="external-page-card--title" id="item-ae00da29-e478-49fe-a03a-58c99d4c0016-title"> <a target="_blank" href="https://www.audi.de/de/neuwagen/" rel="noopener nofollow">Discover the Audi Models </a></h3>
<header class="ensTitle" id="ensTitle">
<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">
<input class="ensCheckbox" aria-describedby="Functionaldescription" id="FunctionalSlide" type="checkbox" name="FunctionalSlide">
<div class="description" id="Functionaldescription" role="definition"><p> Functional cookies enable the recording and saving of user settings (e.g. user name, configurations) in order to increase user-friendliness. </p></div>
<input class="ensCheckbox" aria-describedby="Performancedescription" id="PerformanceSlide" type="checkbox" name="PerformanceSlide">
<div class="description" id="Performancedescription" role="definition">
<input class="ensCheckbox" aria-describedby="Do Not Trackdescription" id="Do Not TrackSlide" type="checkbox" name="Do Not TrackSlide">
Images must have alternative text15 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img alt="Audi Q6 e-tron Lifec..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="1438px">
<img alt="Audi Nuvolari at Goo..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi Q3 Sportback - ..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="179.34065934065933px">
<img alt="Audi RS 5 Avant - Au..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="153px">
<img alt="Audi A6 allroad - Au..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi Revolut F1 Team..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="All charged up: from..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Raphaela Fritz - Rap..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi presents its fi..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Team meeting at a co..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
Showing first 10 of 15 audited elements.
Inline text spacing must be adjustable with custom stylesheets34 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<body add-body-classes="true" class="layout up-can-clean" data-available-local...="["de", "en"]" data-base-url="https://www.audi.com..." data-environment="production" up-data="{"classNames":[]}" zoom-detector="" data-device-type="desktop" data-safari="false" style="--consumption-data-b..." ...><div class="header up-can-clean" style="--title-width: 69px; --menu-width: 0px;">
<ul class="grid -topic-teaser" style="--topic-teaser-element-count: 6">
<span class="cropped-image--sizer" style="padding-top:56.25%"></span>
<img alt="Audi Q6 e-tron Lifec..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="1438px">
<span class="cropped-image--sizer" style="padding-top:75.0%"></span>
<img alt="Audi Nuvolari at Goo..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<span class="cropped-image--sizer" style="padding-top:75.0%"></span>
<img alt="Audi Q3 Sportback - ..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="179.34065934065933px">
<span class="cropped-image--sizer" style="padding-top:75.0%"></span>
Showing first 10 of 34 audited elements.
Interactive 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.
Audit Elements
<button class="header--menu btn btn-text from-md" main-menu-opener="true" type="button"> <span class="icon -header-menu -spacer"></span><span>Menu</span> </button>
<img alt="Audi Q6 e-tron Lifec..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="1438px">
<img alt="Audi Nuvolari at Goo..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi Q3 Sportback - ..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="179.34065934065933px">
<img alt="Audi RS 5 Avant - Au..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://uploads.audi..." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyautosizes ls-is-..." decoding="async" sizes="153px">
<img alt="Audi A6 allroad - Au..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi Revolut F1 Team..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="All charged up: from..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Raphaela Fritz - Rap..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
<img alt="Audi presents its fi..." style="width:100%;height:10..." src="https://uploads.audi..." srcset="https://static.audi...." data-sizes="auto" data-srcset="https://uploads.audi..." class="lazyload" decoding="async">
Showing first 10 of 16 audited elements.
Interactive elements must have a visible focus indicator9 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-use...">
<a target="_blank" href="https://www.audi-mediacenter.com/en/privacy-3699?p...">
<a target="_blank" href="https://www.audi-mediacenter.com/en/imprint-3697?p...">
<a target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-use...">
<input class="ensCheckbox" aria-describedby="Functionaldescription" id="FunctionalSlide" type="checkbox" name="FunctionalSlide">
<input class="ensCheckbox" aria-describedby="Performancedescription" id="PerformanceSlide" type="checkbox" name="PerformanceSlide">
<a target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-use...">
<button id="ensAcceptAll" tabindex="0" aria-label="Accept all" class="button raised blue" style="margin-left: 0px !important;">
<button id="ensSave" tabindex="0" aria-label="Save settings and proceed" class="button raised blue">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination3 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<header class="layout--header up-can-clean" up-fixed="top">
<main class="layout--content">
<footer class="layout--footer">
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 target="_blank" class="wltp-link" href="https://www.audi.de/wltp" rel="noopener nofollow">www.audi.de/wltp</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 class="btn btn-icon up-can-clean" aria-label="Search" title="Search" header-search-bar-opener="true" up-instant="false" href="/en/search"><span class="icon -header-search"></span> </a>
<a rel="alternate" up-follow="false" up-preload="false" href="/de?set_locale=true">DE</a>
<a class="-active" rel="alternate" up-follow="false" up-preload="false" href="/en?set_locale=true">EN</a>
<a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/audi-at-a-glance-15904"><div class="topic-teaser-element--text"> Audi at a glance </div> </a>
<a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/models-4"><div class="topic-teaser-element--text"> Models </div> </a>
<a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/formula-1r-17158"><div class="topic-teaser-element--text"> Formula 1® </div> </a>
<a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/investor-relations-17156"><div class="topic-teaser-element--text"> Investor Relations </div> </a>
<a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/careers-at-audidriven-by-tech-driven-by-people-17124"><div class="topic-teaser-element--text"> Careers </div> </a>
<a class="topic-teaser--tile topic-teaser-element up-can-clean" href="/en/service-2305"><div class="topic-teaser-element--text"> Media </div> </a>
<a class="btn btn-primary up-can-clean" href="/en/articles/a-seamless-experience-in-car-entertainment-in-the-audi-q6-e-tron-18116"><span>Learn more</span></a>
Showing first 10 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="layout--content">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en" class="alpha-redesign privacy-increased-width privacy-en-DE privacy-v2" up-source="/en">
Page should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Audit Elements
<html lang="en" class="alpha-redesign privacy-increased-width privacy-en-DE privacy-v2" up-source="/en">
Required ARIA attributes must be provided1 element
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 class="layout--flashes" role="alert" up-flashes="true" up-hungry="" up-if-layer="subtree" up-keep=""> </div>
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 content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
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 content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">