Airbnbairbnb.com
Accessibility Score
Issues Found
Issues Found
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" dir="ltr" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vyb6402" style="--vh: 8px; --vw: 12.8px; --vw-unitless: 1280; min-height: calc(var(--vh, 1vh) * 100); scrollbar-gutter: auto;">
<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" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vyb6402" style="--vh: 8px; --vw: 12.8px; --vw-unitless: 1280; min-height: calc(var(--vh, 1vh) * 100); scrollbar-gutter: auto;">
All page content should be contained by landmarks21 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>
<div dir="ltr">
<div data-theme="" data-color-scheme="light" data-testid="linaria-injector" class="t1bgcr6e cjz5kiq di..." style="display: contents; -...">
<div class="oygfumd atm_wq_z68epy atm_mk_1n9t6rb atm_tk_idpfg4 atm_n3_idpfg4 atm_6i_idpfg4 atm_fq_idpfg4 atm_l1_1wugsn5 atm_kx_i4x0gi atm_26_1dmvgf5 atm_y_1bbsqr7 atm_16_kb7nvz atm_12_1hrf63d atm_1c_ykdhe8 atm_1k_s8y6um atm_26_1dmvgf5__oggzyc o107ghws dir dir-ltr"></div>
<section>
<div class="c193ry1k atm_wq_z68e..." data-testid="modal-container">
<div class="p1psejvv atm_9s_1bgihbq dir dir-ltr">
<div class="p1psejvv atm_9s_1bgihbq dir dir-ltr">
<div role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
<div class="crxfja2 atm_mk_stnw88 atm_9s_1txwivl atm_tk_183y3yt atm_n3_1tcgj5g atm_wq_kb7nvz atm_tk_o7aogt__oggzyc atm_vy_1ylpe5n_1ttlabj atm_e2_1ylpe5n_1ttlabj dir dir-ltr">
Showing first 10 of 21 audited elements.
ARIA attributes must be used as specified for the element's role4 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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
<button aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_..." style="--dls-icon-button_ps...">
<div aria-live="polite" aria-atomic="true"></div>
<div aria-live="assertive" aria-atomic="true"></div>
ARIA attributes must conform to valid names4 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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
<button aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_..." style="--dls-icon-button_ps...">
<div aria-live="polite" aria-atomic="true"></div>
<div aria-live="assertive" aria-atomic="true"></div>
ARIA attributes must conform to valid values4 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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
<button aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_..." style="--dls-icon-button_ps...">
<div aria-live="polite" aria-atomic="true"></div>
<div aria-live="assertive" aria-atomic="true"></div>
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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
ARIA hidden element must not be focusable or contain focusable elements11 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 id="smart-banner" aria-hidden="true"></div>
<noscript aria-hidden="true"><div class="alert alert-with-icon alert-error no-js-alert" data-nosnippet="true"><i class="icon alert-icon icon-alert-alt"></i>We’re sorry, some parts of the Airbnb website don’t work properly without JavaScript enabled.</div></noscript>
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive" aria-hidden="true"></div>
<div id="education-overlay-root" aria-hidden="true"></div>
<div data-xray="{"Framework":"[email protected]"}" aria-hidden="true"></div><div id="fb-root" aria-hidden="true"></div>
<div id="authModals" aria-hidden="true"></div>
<link rel="preload" as="image" imagesrcset="https://a0.muscache...." media="(min-width: 0px)" fetchpriority="high" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32" aria-hidden="true" role="presentation" focusable="false" style="display: block; fill: none; height: 16px; width: 16px; stroke: currentcolor; stroke-width: 4; overflow: visible;"><path d="m6 6 20 20M26 6 6 26"></path></svg>
<div class="tmmw4en atm_j_1h6ojuz atm_9s_1txwivl atm_ar_1bp4okc atm_mk_h2mmj6 atm_j6_11qbsc1 atm_gi_1wugsn5 atm_vy_auwlz6 atm_j3_1m8piqu atm_e2_h3di85 dir dir-ltr" aria-hidden="true" style="--text-height: 68px;">
Showing first 10 of 11 audited elements.
ARIA role should be appropriate for the element94 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
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32" style="display:block;fill:none;height:16px;width:16px;stroke:currentColor;stroke-width:4;overflow:visible" aria-hidden="true" role="presentation" focusable="false">
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive" aria-hidden="true"></div>
<form class="f1hztvqy atm_vy_1osqo2v atm_e2_1osqo2v atm_mk_stnw88 atm_tk_idpfg4 atm_fq_idpfg4 atm_lh_ke7zzc atm_wq_idpfg4 dir dir-ltr" method="get" role="search" data-xray-jira-component="Guest: Navigation: Header" action="/homes">
<div class="c1q7wpad atm_mk_h2mmj6 cearn0u atm_9s_11p5wf0 atm_dz_1a6ah5s atm_fc_1h6ojuz atm_h3_ftgil2 atm_cx_ldb6wv dir dir-ltr" role="tablist">
<a href="/homes" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="s5o62i6 atm_9j_tlke0..." data-happo-focus="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="s5o62i6 atm_9j_tlke0..." data-happo-focus="false">
<a href="/services" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-SERVICES" id="search-block-tab-SER..." class="s5o62i6 atm_9j_tlke0..." data-happo-focus="false">
<div class="fhzfs0e atm_mk_h2mmj..." role="button" tabindex="0" aria-expanded="false" style="grid-column: center;">
<div class="fhzfs0e atm_mk_h2mmj..." role="button" tabindex="0" aria-expanded="false" style="--search-button-leng...">
<svg viewBox="0 0 32 32" xmlns="http://www.w3.org/2000/svg" style="display:block;fill:none;height:16px;width:16px;stroke:currentColor;stroke-width:4;overflow:visible" aria-hidden="true" role="presentation" focusable="false">
Showing first 10 of 94 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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
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="with-new-header" style="overflow: hidden; inset: 0px; margin: 0px; inset-inline-end: 15px; position: fixed; --scrollbar-gutter: 15px;">
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 aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_..." style="--dls-icon-button_ps...">
<button type="button" class="l1ovpqvx atm_npmupv_...">
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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
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" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vyb6402" style="--vh: 8px; --vw: 12.8px; --vw-unitless: 1280; min-height: calc(var(--vh, 1vh) * 100); scrollbar-gutter: auto;">
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" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vyb6402" style="--vh: 8px; --vw: 12.8px; --vw-unitless: 1280; min-height: calc(var(--vh, 1vh) * 100); scrollbar-gutter: auto;">
Elements must meet minimum color contrast ratio thresholds23 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
<div class="f1i5a5z atm_c8_1gcojkr atm_g3_15xinxl atm_fr_8r8w0r atm_cs_1mexzig atm_7l_1dmvgf5 atm_le_yh40bf atm_vv_1q9ccgz atm_ks_zryt35 atm_sq_1l2sidv dir dir-ltr" elementtiming="time_to_search_rendered">Where</div>
<input class="fornie7 atm_9s_1ulex..." type="search" placeholder="Search destinations" aria-describedby="bigsearch-query-loca..." data-testid="structured-search-in..." aria-label="Where" aria-autocomplete="none" autocomplete="off" autocorrect="off" spellcheck="false" name="query" value="" ...>
<div class="f1i5a5z atm_c8_1gcojkr atm_g3_15xinxl atm_fr_8r8w0r atm_cs_1mexzig atm_7l_1dmvgf5 atm_le_yh40bf atm_vv_1q9ccgz atm_ks_zryt35 atm_sq_1l2sidv dir dir-ltr">When</div>
<div class="f1izdi3g atm_c8_1h3mmnw atm_g3_1vnrj90 atm_fr_b3emyl atm_cs_1dh25pa atm_7l_1kkyeqd atm_vv_1q9ccgz atm_ks_zryt35 atm_sq_1l2sidv dir dir-ltr">Add dates</div>
<div class="f1i5a5z atm_c8_1gcojkr atm_g3_15xinxl atm_fr_8r8w0r atm_cs_1mexzig atm_7l_1dmvgf5 atm_le_yh40bf atm_vv_1q9ccgz atm_ks_zryt35 atm_sq_1l2sidv dir dir-ltr">Who</div>
<div class="f1izdi3g atm_c8_1h3mmnw atm_g3_1vnrj90 atm_fr_b3emyl atm_cs_1dh25pa atm_7l_1kkyeqd atm_vv_1q9ccgz atm_ks_zryt35 atm_sq_1l2sidv dir dir-ltr">Add guests</div>
<span class="t1myg1k4 atm_d2_1cy2u2k atm_h_1q9ycp6 atm_c8_zq0p2w atm_g3_10i4u4q atm_fr_i8y2z4 atm_cs_1madr4d atm_9s_cj1kg8 atm_6w_1e54zos atm_fy_cs5v99 atm_ks_15vqwwr atm_c8_1k92wuq__oggzyc atm_g3_1k8s52q__oggzyc atm_ks_ewfl5b__oggzyc dir dir-ltr" id="something-id">Popular homes in Vancouver</span>
<span class="u174bpcy atm_7l_mhi6a6 atm_cs_80qqwn atm_rd_14k51in atm_rq_glywfm atm_cs_l3jtxx__1v156lz dir dir-ltr">$799</span>
<span class="qesosmo atm_7l_100huhz atm_cs_4gwzjb atm_c8_epp50g atm_g3_e3z31c atm_jb_becq3w atm_ks_abwceb atm_sq_g8k74l dir dir-ltr" aria-hidden="true">for 2 nights</span>
<span class="u174bpcy atm_7l_mhi6a6 atm_cs_80qqwn atm_rd_14k51in atm_rq_glywfm atm_cs_l3jtxx__1v156lz dir dir-ltr">$257</span>
Showing first 10 of 23 audited elements.
Elements must only use permitted ARIA attributes4 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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
<button aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_..." style="--dls-icon-button_ps...">
<div aria-live="polite" aria-atomic="true"></div>
<div aria-live="assertive" aria-atomic="true"></div>
Elements must only use supported ARIA attributes4 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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
<button aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_..." style="--dls-icon-button_ps...">
<div aria-live="polite" aria-atomic="true"></div>
<div aria-live="assertive" aria-atomic="true"></div>
Elements should not have tabindex greater than zero1 element
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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
IDs used in ARIA and labels must be unique22 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 class="h3gq68b atm_d2_12u9ljr atm_mh_qgii4y dir dir-ltr" id="129c6ed4-8580-4dd4-be9f-178a0af359c2-label">
<div class="d1rom923 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba atm_e2_t94yts atm_ks_zryt35 atm_l8_idpfg4 atm_mk_stnw88 atm_vv_1q9ccgz atm_vy_t94yts dir dir-ltr" aria-hidden="false" id="129c6ed4-8580-4dd4-be9f-178a0af359c2-description">6 of 9 items showing</div>
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_10516918515092...">
<div class="t1ms2xzu atm_ks_15vqwwr atm_sq_1l2sidv atm_9s_cj1kg8 atm_6w_1e54zos atm_fy_13sk2c1 atm_7l_hfv0h6 atm_c8_457lj7 atm_cs_1mexzig atm_g3_cicc0q atm_kz_fg65tv atm_ti_1imq76w atm_ks_zryt35__1rgatj2 atm_ti_pv6q5__19dvqzg dir dir-ltr" data-testid="listing-card-title" id="title_32646786">
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_16024198776924...">
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_10155629963057...">
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_92355813705463...">
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_11301058949877...">
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_16169979198991...">
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_60533260616928...">
Showing first 10 of 22 audited elements.
Inline text spacing must be adjustable with custom stylesheets4 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" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vyb6402" style="--vh: 8px; --vw: 12.8px; --vw-unitless: 1280; min-height: calc(var(--vh, 1vh) * 100); scrollbar-gutter: auto;">
<body class="with-new-header" style="overflow: hidden; inset: 0px; margin: 0px; inset-inline-end: 15px; position: fixed; --scrollbar-gutter: 15px;">
<div role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
<button aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_..." style="--dls-icon-button_ps...">
Interactive controls must not be nested2 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 aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_..." style="--dls-icon-button_ps...">
<button type="button" class="l1ovpqvx atm_npmupv_...">
Interactive elements must have a visible focus indicator2 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
<button aria-label="Close" variant="isolated" type="button" class="l1ovpqvx atm_npmupv_14b5rvc_10saat9 atm_4s4swg_18x..." style="--dls-icon-button_pseudo-width: 32px; --dls-icon-b...">
<button type="button" class="l1ovpqvx atm_npmupv_14b5rvc_10saat9 atm_4s4swg_18x...">
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" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vyb6402" style="--vh: 8px; --vw: 12.8px; --vw-unitless: 1280; min-height: calc(var(--vh, 1vh) * 100); scrollbar-gutter: auto;">
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" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vyb6402" style="--vh: 8px; --vw: 12.8px; --vw-unitless: 1280; min-height: calc(var(--vh, 1vh) * 100); scrollbar-gutter: auto;">
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 role="dialog" aria-label="Now you’ll see one p..." aria-modal="true" class="dtriyoj atm_ks_zryt3..." style="position: relative;" tabindex="-1">
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">