Airbnb airbnb.com
Accessibility score
League position
7thof 10
Issues found
3
Audits passed
41
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousFocusing an element must not trigger an unexpected change of context2 elements
Keyboard and switch-device users move focus carefully before deciding to activate anything. When focusing an element opens a new window, submits a form, steals focus, or navigates away, they are thrown off course before they have chosen to act.
Failing Elements
<div class="fhzfs0e atm_mk_h2mmj6 atm_9j_tlke0l atm_5j_1vi7ecw..." role="button" tabindex="0" aria-expanded="false" style="grid-column:center">
<div class="fhzfs0e atm_mk_h2mmj6 atm_9j_tlke0l atm_5j_1vi7ecw..." role="button" tabindex="0" aria-expanded="false" style="--search-button-length:6ch;grid-column:last">
SeriousText must remain readable when spacing is increased16 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
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="vkhxe59 atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
Showing first 10 of 16 failing elements.
ModerateAll page content should be contained by landmarks1 element
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<h1 class="vkhxe59 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">Airbnb homepage</h1>
Fix any of the following:
- Some page content is not contained by landmarks
Passed audits41 across 1 page
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en-NZ" dir="ltr" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vg7vsjx" style="--vh: 8px;">
<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-NZ" dir="ltr" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vg7vsjx" style="--vh: 8px;">
All page content should be contained by landmarks139 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div id="site-skip-links">
<a class="screen-reader-only screen-reader-only-focusable skip-to-content skip-to-content_v2-link" data-hook="skip-to-content" href="#site-content" tabindex="0">
<span id="popups-everywhere-skip-link"></span>
<div id="smart-banner"></div>
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
Showing first 5 of 139 audited elements.
All touch targets must be 24px large, or leave sufficient space13 elements
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Audit Elements
<a class="screen-reader-only screen-reader-only-focusable skip-to-content skip-to-content_v2-link" data-hook="skip-to-content" href="#site-content" tabindex="0">
<a class="c1s33i3w atm_kd_glyw..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 13 audited elements.
ARIA attributes must be used as specified for the element's role30 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
<a class="c1s33i3w atm_kd_glyw..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 30 audited elements.
ARIA attributes must conform to valid names30 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
<a class="c1s33i3w atm_kd_glyw..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 30 audited elements.
ARIA attributes must conform to valid values30 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
<a class="c1s33i3w atm_kd_glyw..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 30 audited elements.
ARIA commands must have an accessible name2 elements
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div class="fhzfs0e atm_mk_h2mmj..." role="button" tabindex="0" aria-expanded="false" aria-label="When" style="grid-column:center">
<div class="fhzfs0e atm_mk_h2mmj..." role="button" tabindex="0" aria-expanded="false" aria-label="Who" style="--search-button-leng...">
ARIA hidden element must not be focusable or contain focusable elements36 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<svg xmlns="http://www.w3.org/2000/svg" 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">
<span class="i17dpylj atm_mk_h2mmj6 atm_9s_1ulexfb atm_vy_14noui3 atm_e2_14noui3 dir dir-ltr" style="transform:none" aria-hidden="true">
<span data-tab-label="true" class="timi9jf atm_ti_1q9ccgz atm_cs_1mexzig atm_c8_dlk8xv atm_g3_f6fqlb atm_7l_hfv0h6_1nos8r t1kxodx6 atm_7l_hfv0h6 tlt01p9 atm_gy_ftgil2 dir dir-ltr" aria-hidden="true">
<span class="i17dpylj atm_mk_h2mmj6 atm_9s_1ulexfb atm_vy_14noui3 atm_e2_14noui3 dir dir-ltr" style="transform:none" aria-hidden="true">
<span data-tab-label="true" class="timi9jf atm_7l_xeyu1p atm_ti_1q9ccgz atm_cs_1mexzig atm_c8_dlk8xv atm_g3_f6fqlb atm_7l_hfv0h6_1nos8r tgwsc4z atm_gy_exct8b dir dir-ltr" aria-hidden="true">
Showing first 5 of 36 audited elements.
ARIA role should be appropriate for the element40 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"></div>
<form class="f1hztvqy atm_vy_1osqo2v atm_e2_1osqo2v atm_mk_stnw88 atm_tk_idpfg4 atm_f9_idpfg4 atm_lh_ke7zzc atm_wq_idpfg4 dir dir-ltr" method="get" role="search" action="/homes" data-xray-jira-component="Guest: Navigation: Header">
<div class="c1q7wpad atm_mk_h2mmj6 atm_9s_11p5wf0 atm_d5_1bp4okc atm_d3_184xf1m atm_fc_1h6ojuz atm_h3_ftgil2 atm_cx_ldb6wv dir dir-ltr" role="tablist">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 40 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
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
<form class="f1hztvqy atm_vy_1osqo2v atm_e2_1osqo2v atm_mk_stnw88 atm_tk_idpfg4 atm_f9_idpfg4 atm_lh_ke7zzc atm_wq_idpfg4 dir dir-ltr" method="get" role="search" action="/homes" data-xray-jira-component="Guest: Navigation: Header">
<div class="c1q7wpad atm_mk_h2mmj6 atm_9s_11p5wf0 atm_d5_1bp4okc atm_d3_184xf1m atm_fc_1h6ojuz atm_h3_ftgil2 atm_cx_ldb6wv dir dir-ltr" role="tablist">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
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 class="with-new-header">
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="c2zxfaj atm_9s_1txwivl atm_fc_1yb4nlp atm_h_1h6ojuz atm_gn_idpfg4 atm_gw_1wugsn5 atm_j3_1vvhni0 atm_lj_1tcgj5g atm_li_1tcgj5g atm_e2_u29brm atm_lj_1vi7ecw__1v156lz atm_lj_fyhuej__jx8car atm_li_1vi7ecw__1v156lz atm_li_fyhuej__jx8car atm_e2_rw9lz9__jx8car dir dir-ltr">
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 class="bc003v3 atm_1s_glywf..." type="button" data-testid="structured-search-in..." aria-label="Search">
<button aria-label="Log in or sign up" variant="fill" style="--dls-icon-button_ps..." type="button" class="l1lx1n3h atm_npmupv_...">
Certain ARIA roles must be contained by particular parents4 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
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/services" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-SERVICES" id="search-block-tab-SER..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
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="c1q7wpad atm_mk_h2mmj6 atm_9s_11p5wf0 atm_d5_1bp4okc atm_d3_184xf1m atm_fc_1h6ojuz atm_h3_ftgil2 atm_cx_ldb6wv dir dir-ltr" role="tablist">
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
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
<form class="f1hztvqy atm_vy_1osqo2v atm_e2_1osqo2v atm_mk_stnw88 atm_tk_idpfg4 atm_f9_idpfg4 atm_lh_ke7zzc atm_wq_idpfg4 dir dir-ltr" method="get" role="search" action="/homes" data-xray-jira-component="Guest: Navigation: Header">
<div class="c1q7wpad atm_mk_h2mmj6 atm_9s_11p5wf0 atm_d5_1bp4okc atm_d3_184xf1m atm_fc_1h6ojuz atm_h3_ftgil2 atm_cx_ldb6wv dir dir-ltr" role="tablist">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 12 audited elements.
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en-NZ" dir="ltr" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vg7vsjx" style="--vh: 8px;">
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="c2zxfaj atm_9s_1txwivl atm_fc_1yb4nlp atm_h_1h6ojuz atm_gn_idpfg4 atm_gw_1wugsn5 atm_j3_1vvhni0 atm_lj_1tcgj5g atm_li_1tcgj5g atm_e2_u29brm atm_lj_1vi7ecw__1v156lz atm_lj_fyhuej__jx8car atm_li_1vi7ecw__1v156lz atm_li_fyhuej__jx8car atm_e2_rw9lz9__jx8car dir dir-ltr">
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="m1460ofs atm_gq_189ypq0 atm_gy_y71723__2ygr2h atm_gx_1gbbub3__2ygr2h atm_lj_ysyi00__2ygr2h atm_li_1kk8o5g__2ygr2h dir dir-ltr" id="site-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-NZ" dir="ltr" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vg7vsjx" style="--vh: 8px;">
Elements must meet minimum color contrast ratio thresholds1 element
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
<input class="fp9kp52 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="" ...>
Elements must only use permitted ARIA attributes30 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
<a class="c1s33i3w atm_kd_glyw..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 30 audited elements.
Elements must only use supported ARIA attributes30 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
<a class="c1s33i3w atm_kd_glyw..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 30 audited elements.
Elements should not have tabindex greater than zero10 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 class="screen-reader-only screen-reader-only-focusable skip-to-content skip-to-content_v2-link" data-hook="skip-to-content" href="#site-content" tabindex="0">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/services" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-SERVICES" id="search-block-tab-SER..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 10 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 class="screen-reader-only screen-reader-only-focusable sk..." data-hook="skip-to-content" href="#site-content" tabindex="0">
<a class="c1s33i3w atm_kd_glywfm atm_h_1h6ojuz atm_9s_116y0a..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0l atm_vb_glywfm atm_r2_1j28jx2..." data-happo-focus-visible="false">
<input class="fp9kp52 atm_9s_1ulexfb atm_3f_idpfg4 atm_gi_idpfg4..." type="search" placeholder="Search destinations" aria-describedby="bigsearch-query-location-description" data-testid="structured-search-input-field-query" aria-label="Where" aria-autocomplete="none" autocomplete="off" autocorrect="o...
<div class="fhzfs0e atm_mk_h2mmj6 atm_9j_tlke0l atm_5j_1vi7ecw..." role="button" tabindex="0" aria-expanded="false" style="grid-column:center">
Showing first 5 of 50 audited elements.
Heading levels should only increase by one1 element
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="vkhxe59 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">Airbnb homepage</h1>
Headings should not be empty1 element
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="vkhxe59 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">Airbnb homepage</h1>
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
<html lang="en-NZ" dir="ltr" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vg7vsjx" style="--vh: 8px;">
<div data-theme="" data-color-scheme="light" data-testid="linaria-injector" class="t1bgcr6e cjz5kiq di..." style="display:contents;--t...">
<div class="whb0xmj atm_mk_1if85x1 atm_tk_idpfg4 atm_vy_1osqo2v atm_wq_b4wlg atm_h3_lsrmwu dir dir-ltr" data-testid="shimmer-css-variable-index-0" style="--dls-shimmer_count:0">
<div style="display:contents">
<a variant="tertiary" style="--dls-button_padding..." data-variant="tertiary" href="#guest-header-become..." class="l1lx1n3h atm_npmupv_...">
Interactive controls must not be nested8 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
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/services" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-SERVICES" id="search-block-tab-SER..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<div class="fhzfs0e atm_mk_h2mmj..." role="button" tabindex="0" aria-expanded="false" aria-label="When" style="grid-column:center">
Showing first 5 of 8 audited elements.
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 class="screen-reader-only screen-reader-only-focusable sk..." data-hook="skip-to-content" href="#site-content" tabindex="0">
<a class="c1s33i3w atm_kd_glywfm atm_h_1h6ojuz atm_9s_116y0a..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0l atm_vb_glywfm atm_r2_1j28jx2..." data-happo-focus-visible="false">
<input class="fp9kp52 atm_9s_1ulexfb atm_3f_idpfg4 atm_gi_idpfg4..." type="search" placeholder="Search destinations" aria-describedby="bigsearch-query-location-description" data-testid="structured-search-input-field-query" aria-label="Where" aria-autocomplete="none" autocomplete="off" autocorrect="o...
<div class="fhzfs0e atm_mk_h2mmj6 atm_9j_tlke0l atm_5j_1vi7ecw..." role="button" tabindex="0" aria-expanded="false" style="grid-column:center">
Showing first 5 of 50 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination4 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="c2zxfaj atm_9s_1txwivl atm_fc_1yb4nlp atm_h_1h6ojuz atm_gn_idpfg4 atm_gw_1wugsn5 atm_j3_1vvhni0 atm_lj_1tcgj5g atm_li_1tcgj5g atm_e2_u29brm atm_lj_1vi7ecw__1v156lz atm_lj_fyhuej__jx8car atm_li_1vi7ecw__1v156lz atm_li_fyhuej__jx8car atm_e2_rw9lz9__jx8car dir dir-ltr">
<form class="f1hztvqy atm_vy_1osqo2v atm_e2_1osqo2v atm_mk_stnw88 atm_tk_idpfg4 atm_f9_idpfg4 atm_lh_ke7zzc atm_wq_idpfg4 dir dir-ltr" method="get" role="search" action="/homes" data-xray-jira-component="Guest: Navigation: Header">
<nav aria-label="Profile" class="c1ons4qp atm_mk_h2mmj6 atm_9s_1txwivl atm_h_1h6ojuz atm_fc_esu3gu atm_e2_u29brm dir dir-ltr">
<main class="m1460ofs atm_gq_189ypq0 atm_gy_y71723__2ygr2h atm_gx_1gbbub3__2ygr2h atm_lj_ysyi00__2ygr2h atm_li_1kk8o5g__2ygr2h dir dir-ltr" id="site-content">
Links must have discernible text9 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="screen-reader-only screen-reader-only-focusable skip-to-content skip-to-content_v2-link" data-hook="skip-to-content" href="#site-content" tabindex="0">
<a class="c1s33i3w atm_kd_glyw..." aria-label="Airbnb homepage" href="/">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/experiences" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-EXPERIENC..." id="search-block-tab-EXP..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 9 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="m1460ofs atm_gq_189ypq0 atm_gy_y71723__2ygr2h atm_gx_1gbbub3__2ygr2h atm_lj_ysyi00__2ygr2h atm_li_1kk8o5g__2ygr2h dir dir-ltr" id="site-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-NZ" dir="ltr" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vg7vsjx" style="--vh: 8px;">
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-NZ" dir="ltr" data-is-hyperloop="true" data-is-async-local-storage="true" class="scrollbar-gutter dir native vz2oe5x vg7vsjx" style="--vh: 8px;">
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
<div id="flash-container" class="flash-container" role="alert" aria-live="assertive"></div>
<form class="f1hztvqy atm_vy_1osqo2v atm_e2_1osqo2v atm_mk_stnw88 atm_tk_idpfg4 atm_f9_idpfg4 atm_lh_ke7zzc atm_wq_idpfg4 dir dir-ltr" method="get" role="search" action="/homes" data-xray-jira-component="Guest: Navigation: Header">
<div class="c1q7wpad atm_mk_h2mmj6 atm_9s_11p5wf0 atm_d5_1bp4okc atm_d3_184xf1m atm_fc_1h6ojuz atm_h3_ftgil2 atm_cx_ldb6wv dir dir-ltr" role="tablist">
<a href="/" role="tab" aria-selected="true" tabindex="0" data-tabid="tabBarItem-ALL" id="search-block-tab-ALL" class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<a href="/homes" role="tab" aria-selected="false" tabindex="-1" data-tabid="tabBarItem-STAYS" id="search-block-tab-STA..." class="c5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 12 audited elements.
The skip-link target should exist and be focusable1 element
Skip links allow keyboard users to bypass repetitive navigation and jump directly to main content. Without skip links, users must tab through potentially hundreds of navigation links on every page, which is time-consuming and can cause physical pain for users with motor limitations.
Audit Elements
<a class="screen-reader-only screen-reader-only-focusable skip-to-content skip-to-content_v2-link" data-hook="skip-to-content" href="#site-content" tabindex="0">
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">
How does your site stack up against Airbnb?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Travel & Hospitality
- Kayak90 out of 100, good
- TripAdvisor90 out of 100, good
- Hotels.com85 out of 100, needs improvement
- Booking.com78 out of 100, needs improvement
- Hilton75 out of 100, needs improvement
- Marriott75 out of 100, needs improvement
- Delta Air Lines60 out of 100, poor
- United Airlines48 out of 100, poor
- Expedia45 out of 100, poor