Audi audi.com
Accessibility score
League position
4thof 9
Issues found
3
Audits passed
37
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousLinks 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.
Failing Elements
<a target="_blank" class="wltp-link" href="https://www.audi.de/wltp" rel="noopener nofollow">www.audi.de/wltp</a>
Fix any of the following:
- The link has insufficient color contrast of 2.08:1 with the surrounding text. (Minimum contrast is 3:1, link text: #fcfcfd, surrounding text: #b1b1b2)
- The link has no styling (such as underline) to distinguish it from the surrounding text
SeriousText must remain readable when spacing is increased2 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
Failing Elements
<h4 class="main-stage-list-item--title" hyphenate="true">
<span class="nowrap">
MinorARIA role should be appropriate for the element3 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Failing Elements
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
Fix any of the following:
- ARIA role heading is not allowed for given element
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
Fix any of the following:
- ARIA role heading is not allowed for given element
<label class="ensToggleLabel" for="PerformanceSlide" role="heading" aria-level="2" tabindex="-1">
Fix any of the following:
- ARIA role heading is not allowed for given element
Passed audits37 across 1 page
All page content should be contained by landmarks35 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<div class="ensModal" aria-label="Consent Configuration" data-nosnippet="true">
<header class="ensTitle" id="ensTitle">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<div class="consentDescription" id="ensDescription">
Showing first 5 of 35 audited elements.
ARIA attributes must be used as specified for the element's role10 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<div class="ensModal" aria-label="Consent Configuration" data-nosnippet="true">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
Showing first 5 of 10 audited elements.
ARIA attributes must conform to valid names10 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<div class="ensModal" aria-label="Consent Configuration" data-nosnippet="true">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
Showing first 5 of 10 audited elements.
ARIA attributes must conform to valid values10 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<div class="ensModal" aria-label="Consent Configuration" data-nosnippet="true">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
Showing first 5 of 10 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
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
<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">
<span class="switch" aria-hidden="true"></span>
<span class="toggle" aria-hidden="true"></span>
Showing first 5 of 10 audited elements.
ARIA role should be appropriate for the element16 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 -iconless" name="query" placeholder="What are you looking for today?" role="combobox" search-input="true" type="text" aria-controls="" aria-expanded="false">
<input type="text" name="query" class="form-control -iconless" autocomplete="off" placeholder="Search" role="combobox" aria-autocomplete="list" aria-label="Search" search-input="" 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" style="display: block;" open="">
Showing first 5 of 16 audited elements.
ARIA roles used must conform to valid values12 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<div class="ensToggleRowWrapper" role="list">
<div class="ensToggleRow" role="listitem" style="opacity: .5;" id="toggleRow-default">
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
Showing first 5 of 12 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 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="ensTitle" id="ensTitle">
Buttons must have discernible text2 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" tabindex="0" aria-label="Accept all" class="button raised blue" style="margin-left: 0px !important;"><div id="ensAcceptAllText" class="ensCenter">Accept all</div></button>
<button id="ensSave" tabindex="0" aria-label="Save settings and proceed" class="button raised blue"><div id="ensSaveText" class="ensCenter">Save settings and proceed</div></button>
Certain ARIA roles must be contained by particular parents3 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
<div class="ensToggleRow" role="listitem" style="opacity: .5;" id="toggleRow-default">
<div class="ensToggleRow" role="listitem" id="toggleRow-functional">
<div class="ensToggleRow" role="listitem" id="toggleRow-performance">
Certain ARIA roles must contain particular children1 element
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 class="ensToggleRowWrapper" role="list">
Content must reflow without two-dimensional scrolling0 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.
Deprecated ARIA roles must not be used12 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<div class="ensToggleRowWrapper" role="list">
<div class="ensToggleRow" role="listitem" style="opacity: .5;" id="toggleRow-default">
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
Showing first 5 of 12 audited elements.
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="ensTitle" id="ensTitle">
Elements must meet minimum color contrast ratio thresholds13 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 class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<p>
<p>
<a target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-user-tracking-policy-14197?privacySource=1"> Cookie Policy</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/privacy-3699?privacySource=1">Privacy Policy</a>
Showing first 5 of 13 audited elements.
Elements must only use permitted ARIA attributes9 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
<input class="ensCheckbox" aria-describedby="Functionaldescription" id="FunctionalSlide" type="checkbox" name="FunctionalSlide">
Showing first 5 of 9 audited elements.
Elements must only use supported ARIA attributes10 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<div class="ensModal" aria-label="Consent Configuration" data-nosnippet="true">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
Showing first 5 of 10 audited elements.
Elements should not have tabindex greater than zero6 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
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
<label class="ensToggleLabel" for="PerformanceSlide" role="heading" aria-level="2" tabindex="-1">
<button id="ensAcceptAll" tabindex="0" aria-label="Accept all" class="button raised blue" style="margin-left: 0px !important;"><div id="ensAcceptAllText" class="ensCenter">Accept all</div></button>
Showing first 5 of 6 audited elements.
Focused elements must not be entirely hidden by author-created content50 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a 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">
Showing first 5 of 50 audited elements.
Form elements must have labels2 elements
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input class="ensCheckbox" aria-describedby="Functionaldescription" id="FunctionalSlide" type="checkbox" name="FunctionalSlide">
<input class="ensCheckbox" aria-describedby="Performancedescription" id="PerformanceSlide" type="checkbox" name="PerformanceSlide">
Form elements should have a visible label2 elements
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input class="ensCheckbox" aria-describedby="Functionaldescription" id="FunctionalSlide" type="checkbox" name="FunctionalSlide">
<input class="ensCheckbox" aria-describedby="Performancedescription" id="PerformanceSlide" type="checkbox" name="PerformanceSlide">
Form field must not have multiple label elements2 elements
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input class="ensCheckbox" aria-describedby="Functionaldescription" id="FunctionalSlide" type="checkbox" name="FunctionalSlide">
<input class="ensCheckbox" aria-describedby="Performancedescription" id="PerformanceSlide" type="checkbox" name="PerformanceSlide">
Heading levels should only increase by one4 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
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
<label class="ensToggleLabel" for="PerformanceSlide" role="heading" aria-level="2" tabindex="-1">
Headings should not be empty4 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
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<label class="ensToggleLabel" for="FunctionalSlide" role="heading" aria-level="2" tabindex="-1">
<label class="ensToggleLabel" for="PerformanceSlide" role="heading" aria-level="2" tabindex="-1">
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-48bdf1fb-bc77-45f4-a1a3-c23d9ce0260e-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">
Showing first 5 of 10 audited elements.
Inline text spacing must be adjustable with custom stylesheets5 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<div class="ensToggleRow" role="listitem" style="opacity: .5;" id="toggleRow-default">
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
<div class="card" style=""><input class="ensCheckbox" aria-describedby="Functionaldescription" id="FunctionalSlide" type="checkbox" name="FunctionalSlide"><span class="switch" aria-hidden="true"></span><span class="toggle" aria-hidden="true"></span></div>
<button id="ensAcceptAll" tabindex="0" aria-label="Accept all" class="button raised blue" style="margin-left: 0px !important;"><div id="ensAcceptAllText" class="ensCenter">Accept all</div></button>
Interactive controls must not be nested4 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
<input class="ensCheckbox" aria-describedby="Functionaldescription" id="FunctionalSlide" type="checkbox" name="FunctionalSlide">
<input class="ensCheckbox" aria-describedby="Performancedescription" id="PerformanceSlide" type="checkbox" name="PerformanceSlide">
<button id="ensAcceptAll" tabindex="0" aria-label="Accept all" class="button raised blue" style="margin-left: 0px !important;"><div id="ensAcceptAllText" class="ensCenter">Accept all</div></button>
<button id="ensSave" tabindex="0" aria-label="Save settings and proceed" class="button raised blue"><div id="ensSaveText" class="ensCenter">Save settings and proceed</div></button>
Interactive elements must have a visible focus indicator50 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a 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">
Showing first 5 of 50 audited elements.
Landmarks 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.
Audit Elements
<header class="ensTitle" id="ensTitle">
Links must be distinguishable without relying on color5 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 target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-user-tracking-policy-14197?privacySource=1"> Cookie Policy</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/privacy-3699?privacySource=1">Privacy Policy</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/imprint-3697?privacySource=1">Imprint</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-user-tracking-policy-14197?privacySource=1">Cookie Policy</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-user-tracking-policy-14197?privacySource=1"> Cookie Policy</a>
Links must have discernible text5 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 target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-user-tracking-policy-14197?privacySource=1"> Cookie Policy</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/privacy-3699?privacySource=1">Privacy Policy</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/imprint-3697?privacySource=1">Imprint</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-user-tracking-policy-14197?privacySource=1">Cookie Policy</a>
<a target="_blank" href="https://www.audi-mediacenter.com/en/cookie-and-user-tracking-policy-14197?privacySource=1"> Cookie Policy</a>
Required ARIA attributes must be provided12 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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
<span class="ensTitleText" role="heading" aria-level="1" tabindex="-1">Cookie settings</span>
<div class="ensToggleRowWrapper" role="list">
<div class="ensToggleRow" role="listitem" style="opacity: .5;" id="toggleRow-default">
<label class="ensToggleLabel" for="defaultSlide" role="heading" aria-level="2" tabindex="-1" style="cursor: default !important;">
Showing first 5 of 12 audited elements.
Scrollable region must have keyboard access1 element
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
<dialog id="ensModalWrapper" role="dialog" aria-labelledby="ensTitle" aria-describedby="ensDescription" focusable="true" aria-modal="true" class="ensPrivacyManager buttons-color-black buttons-placement-bottom" style="display: block;" open="">
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">
How does your site stack up against Audi?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Automotive