Airbnb airbnb.com
Accessibility score
League position
7thof 8
Issues found
3
Audits passed
52
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousARIA hidden element must not be focusable or contain focusable elements12 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.
Failing Elements
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should be disabled or be removed from the DOM
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should be disabled or be removed from the DOM
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should be disabled or be removed from the DOM
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should be disabled or be removed from the DOM
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should be disabled or be removed from the DOM
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should be disabled or be removed from the DOM
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should have tabindex="-1" or be removed from the DOM
<div aria-hidden="true" class="">
Fix all of the following:
- Focusable content should be disabled or be removed from the DOM
- Focusable content should have tabindex="-1" or be removed from the DOM
Showing first 10 of 12 failing elements.
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="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
<span class="a8jt5op atm_3f_idpfg4 atm_7h_hxbz6r atm_7i_ysn8ba ...">
Showing first 10 of 16 failing elements.
ModerateAll page content should be contained by landmarks5 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.
Failing Elements
<h1 class="vsvqdle 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
<h2 class="hifxi0b atm_c8_21sjza atm_g3_1wvsxh1 atm_fr_1t2fc69 atm_cs_1mexzig atm_gq_ftgil2 dir dir-ltr">Inspiration for future getaways</h2>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="t159igf7 atm_9s_1txwivl atm_vv_1q9ccgz atm_ks_ewfl5b dir dir-ltr" role="tablist">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="t1l7kq0f atm_lo_1vi7ecw atm_1g7blql_cs5v99 atm_1g7blql_11wpgbn__1v156lz atm_1g7blql_ouytup__qky54b dir dir-ltr" role="tabpanel" id="panel--seo-link-section-tabbed-dense-grid--0" aria-labelledby="tab--seo-link-section-tabbed-dense-grid--0">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="wehp6mz atm_gi_ftgil2 atm_am_kb7nvz atm_jb_hv4lt8 atm_gx_exct8b__qky54b dir dir-ltr">
Fix any of the following:
- Some page content is not contained by landmarks
Passed audits52 across 1 page
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en" dir="ltr" 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;">
<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;">
<li> elements must be contained in a <ul> or <ol>49 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li>
<li>
<li>
<li>
<li>
Showing first 5 of 49 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements6 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul class="gjo09wt atm_9s_11p5wf0 atm_84_ftgil2 atm_n5_1tcgj5g atm_gi_idpfg4 atm_l8_idpfg4 atm_gb_glywfm atm_dz_1datsov dir dir-ltr">
<ul class="l1qzr284 atm_gi_idpfg4 atm_l8_idpfg4 atm_gb_glywfm atm_9s_11p5wf0 atm_cx_exct8b dir dir-ltr">
<ul class="l1qzr284 atm_gi_idpfg4 atm_l8_idpfg4 atm_gb_glywfm atm_9s_11p5wf0 atm_cx_exct8b dir dir-ltr">
<ul class="l1qzr284 atm_gi_idpfg4 atm_l8_idpfg4 atm_gb_glywfm atm_9s_11p5wf0 atm_cx_exct8b dir dir-ltr">
<ol class="r1nzp7jo atm_gi_idpfg4 atm_l8_idpfg4 dir dir-ltr">
Showing first 5 of 6 audited elements.
All page content should be contained by landmarks1433 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 1433 audited elements.
ARIA attributes must be used as specified for the element's role159 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="c13cw3wj 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 159 audited elements.
ARIA attributes must conform to valid names159 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="c13cw3wj 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 159 audited elements.
ARIA attributes must conform to valid values158 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="c13cw3wj 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 158 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" style="grid-column:center">
<div class="fhzfs0e atm_mk_h2mmj..." role="button" tabindex="0" aria-expanded="false" style="--search-button-leng...">
ARIA hidden element must not be focusable or contain focusable elements237 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="w55pwm7 atm_mk_h2mmj6 dir dir-ltr" style="transform: none;" aria-hidden="true">
<span class="sxeg3i2 atm_ti_1q9ccgz atm_cs_1mexzig sgwsc4z atm_7l_hfv0h6 whclhl1 atm_c8_dlk8xv atm_g3_f6fqlb atm_7l_hfv0h6_1nos8r w1dbwz2n atm_gy_ftgil2 dir dir-ltr" aria-hidden="true">All</span>
<span class="w55pwm7 atm_mk_h2mmj6 dir dir-ltr" style="transform: none;" aria-hidden="true">
<span class="sxeg3i2 atm_7l_xeyu1p atm_ti_1q9ccgz atm_cs_1mexzig whclhl1 atm_c8_dlk8xv atm_g3_f6fqlb atm_7l_hfv0h6_1nos8r w6avlzg atm_gy_exct8b dir dir-ltr" aria-hidden="true">Homes</span>
Showing first 5 of 237 audited elements.
ARIA role should be appropriate for the element196 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 cearn0u atm_9s_11p5wf0 atm_dz_vud8gm 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 196 audited elements.
ARIA roles used must conform to valid values48 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 cearn0u atm_9s_11p5wf0 atm_dz_vud8gm 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 48 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">
autocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<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="" ...>
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 text50 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="siey6h7 atm_1s_glywf..." type="button" data-testid="structured-search-in..." aria-label="Search">
<button variant="tertiary" data-variant="tertiary" type="button" class="l1lx1n3h atm_npmupv_..." style="--dls-button_padding...">
<button aria-expanded="false" aria-label="Choose a language an..." variant="fill" type="button" class="l1lx1n3h atm_npmupv_..." style="--dls-icon-button_ps...">
<button aria-expanded="false" aria-label="Main navigation menu" data-testid="cypress-headernav-pr..." data-tooltip-anchor-...="guest-header-dropdow..." variant="fill" type="button" class="l1lx1n3h atm_npmupv_..." style="--dls-icon-button_ps...">
<button aria-label="Previous" variant="fill" disabled="" type="button" class="l1lx1n3h atm_npmupv_..." style="--dls-icon-button_ps...">
Showing first 5 of 50 audited elements.
Certain ARIA roles must be contained by particular parents12 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="s5o62i6 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<button type="button" id="tab--seo-link-sectio..." aria-controls="panel--seo-link-sect..." aria-selected="true" class="t1jiriwb atm_bx_nm7n..." role="tab">
Showing first 5 of 12 audited elements.
Certain ARIA roles must contain particular children2 elements
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Audit Elements
<div class="c1q7wpad atm_mk_h2mmj6 cearn0u atm_9s_11p5wf0 atm_dz_vud8gm atm_fc_1h6ojuz atm_h3_ftgil2 atm_cx_ldb6wv dir dir-ltr" role="tablist">
<div class="t159igf7 atm_9s_1txwivl atm_vv_1q9ccgz atm_ks_ewfl5b 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.
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer class="f12ytkur atm_mk_h2mmj6 atm_26_1qgma6g atm_gy_y71723 atm_gx_1gbbub3 atm_lj_ysyi00 atm_li_1kk8o5g atm_le_u29brm dir dir-ltr" data-xray-jira-component="Guest: Footer">
Deprecated ARIA roles must not be used48 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 cearn0u atm_9s_11p5wf0 atm_dz_vud8gm 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 48 audited elements.
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en" dir="ltr" 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;">
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 contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer class="f12ytkur atm_mk_h2mmj6 atm_26_1qgma6g atm_gy_y71723 atm_gx_1gbbub3 atm_lj_ysyi00 atm_li_1kk8o5g atm_le_u29brm dir dir-ltr" data-xray-jira-component="Guest: Footer">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main class="m3wbj8l 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" 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;">
Elements must meet minimum color contrast ratio thresholds149 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_14zl091 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_14zl091 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_gyfspu 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_14zl091 atm_le_yh40bf atm_vv_1q9ccgz atm_ks_zryt35 atm_sq_1l2sidv dir dir-ltr">Who</div>
Showing first 5 of 149 audited elements.
Elements must only use permitted ARIA attributes153 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="c13cw3wj 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 153 audited elements.
Elements must only use supported ARIA attributes159 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="c13cw3wj 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 159 audited elements.
Elements should not have tabindex greater than zero19 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="s5o62i6 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 19 audited elements.
Focused elements must not be entirely hidden by author-created content3 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
<button type="button" class="l1lx1n3h atm_npmupv_14b5rvc_10saat9 atm_4s4swg_18x...">
<button type="button" class="l1lx1n3h atm_npmupv_14b5rvc_10saat9 atm_4s4swg_18x...">
<button type="button" class="l1lx1n3h atm_npmupv_14b5rvc_10saat9 atm_4s4swg_18x...">
Form elements must have labels1 element
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="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="" ...>
Form elements should have a visible label1 element
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="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="" ...>
Form field must not have multiple label elements1 element
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="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="" ...>
Heading levels should only increase by one11 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="vsvqdle 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>
<h2 class="skp76t2 atm_h3_idpfg4 atm_gq_idpfg4 atm_c8_n7od8j atm_cs_n7od8j dir dir-ltr">
<h2 class="skp76t2 atm_h3_idpfg4 atm_gq_idpfg4 atm_c8_n7od8j atm_cs_n7od8j dir dir-ltr">
<h2 class="skp76t2 atm_h3_idpfg4 atm_gq_idpfg4 atm_c8_n7od8j atm_cs_n7od8j dir dir-ltr">
<h2 class="skp76t2 atm_h3_idpfg4 atm_gq_idpfg4 atm_c8_n7od8j atm_cs_n7od8j dir dir-ltr">
Showing first 5 of 11 audited elements.
Headings should not be empty11 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="vsvqdle 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>
<h2 class="skp76t2 atm_h3_idpfg4 atm_gq_idpfg4 atm_c8_n7od8j atm_cs_n7od8j dir dir-ltr">
<h2 class="skp76t2 atm_h3_idpfg4 atm_gq_idpfg4 atm_c8_n7od8j atm_cs_n7od8j dir dir-ltr">
<h2 class="skp76t2 atm_h3_idpfg4 atm_gq_idpfg4 atm_c8_n7od8j atm_cs_n7od8j dir dir-ltr">
<h2 class="skp76t2 atm_h3_idpfg4 atm_gq_idpfg4 atm_c8_n7od8j atm_cs_n7od8j dir dir-ltr">
Showing first 5 of 11 audited elements.
IDs used in ARIA and labels must be unique64 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="bf866747-b423-4ae9-a6f8-9a64c50ea98f-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="bf866747-b423-4ae9-a6f8-9a64c50ea98f-description">6 of 9 items showing</div>
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_16121665342220...">
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_14200215569857...">
<div class="t1ms2xzu atm_ks_15vq..." data-testid="listing-card-title" id="title_15055191921205...">
Showing first 5 of 64 audited elements.
Inline text spacing must be adjustable with custom stylesheets127 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;">
<div data-theme="" data-color-scheme="light" data-testid="linaria-injector" class="t1bgcr6e cjz5kiq di..." style="display:contents;--t...">
<div id="homepage-scroll-element-target" style="top:0px;position:absolute;height:1px;width:1px;z-index:-1;contain:strict"></div>
<div class="w1un5iz5 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">
Showing first 5 of 127 audited elements.
Interactive controls must not be nested56 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="s5o62i6 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
<div class="fhzfs0e atm_mk_h2mmj..." role="button" tabindex="0" aria-expanded="false" style="grid-column:center">
Showing first 5 of 56 audited elements.
Interactive elements must have a visible focus indicator3 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 type="button" class="l1lx1n3h atm_npmupv_14b5rvc_10saat9 atm_4s4swg_18x...">
<button type="button" class="l1lx1n3h atm_npmupv_14b5rvc_10saat9 atm_4s4swg_18x...">
<button type="button" class="l1lx1n3h atm_npmupv_14b5rvc_10saat9 atm_4s4swg_18x...">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination5 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="cg7l307 atm_mk_h2mmj6 atm_9s_1txwivl atm_h_1h6ojuz atm_fc_esu3gu atm_e2_u29brm dir dir-ltr">
<main class="m3wbj8l 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">
<footer class="f12ytkur atm_mk_h2mmj6 atm_26_1qgma6g atm_gy_y71723 atm_gx_1gbbub3 atm_lj_ysyi00 atm_li_1kk8o5g atm_le_u29brm dir dir-ltr" data-xray-jira-component="Guest: Footer">
Links must be distinguishable without relying on color1 element
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a href="/terms/cookie_policy" class="l1lx1n3h atm_npmupv_...">
Links must have discernible text83 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="c13cw3wj 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="s5o62i6 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 83 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="m3wbj8l 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" 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;">
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;">
Required ARIA attributes must be provided48 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 cearn0u atm_9s_11p5wf0 atm_dz_vud8gm 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="s5o62i6 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="s5o62i6 atm_9j_tlke0..." data-happo-focus-vis...="false">
Showing first 5 of 48 audited elements.
Scrollable region must have keyboard access4 elements
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
<div class="c148ie1q atm_uc_15df..." tabindex="-1">
<div class="c148ie1q atm_uc_15df..." tabindex="-1">
<div class="c148ie1q atm_uc_15df..." tabindex="-1">
<div class="c148ie1q atm_uc_15df..." tabindex="-1">
Skip links must move keyboard focus to their target1 element
Keyboard users rely on skip links to bypass repeated navigation. A skip link whose target is missing, or that does not move keyboard focus when activated, leaves those users tabbing through the same blocks on every page.
Audit Elements
<a class="screen-reader-only screen-reader-only-focusable sk..." data-hook="skip-to-content" href="#site-content" tabindex="0">
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