Booking.combooking.com
Accessibility Score
Issues Found
Issues Found
Passed Audits
[role="img"] elements must have alternative text1 element
Screen readers cannot convert visual images with role="img" into text without an accessible alternative. All users with visual disabilities, from complete blindness to low vision and color blindness, require text alternatives to access the information that images convey.
Audit Elements
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
<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 dir="ltr" lang="en-us">
<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 dir="ltr" lang="en-us">
All page content should be contained by landmarks34 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 class="dc7e768484 a37804931c">
<div class="bbe73dce14">
<div class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<div class="a5c71b0007">
<div class="c1cb99b7ca">
<div class="fd1bba3c6c a5d282bede">
<div class="b779265b5e">
<div class="e1e158e66b afdff78c97 ce103e449e fe169dc72b">
<button aria-label="Dismiss sign-in info." type="button" class="de576f5064 b46cd7aad7 e26a59bb37 c295306d66 c7a901b0e7 daf5d4cb1c e7f2b1a356">
<span class="ec1ff2f0cb">
Showing first 10 of 34 audited elements.
ARIA attributes must be used as specified for the element's role3 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<div class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<button aria-label="Dismiss sign-in info." type="button" class="de576f5064 b46cd7aad7 e26a59bb37 c295306d66 c7a901b0e7 daf5d4cb1c e7f2b1a356">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
ARIA attributes must conform to valid names3 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<div class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<button aria-label="Dismiss sign-in info." type="button" class="de576f5064 b46cd7aad7 e26a59bb37 c295306d66 c7a901b0e7 daf5d4cb1c e7f2b1a356">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
ARIA attributes must conform to valid values3 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<div class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<button aria-label="Dismiss sign-in info." type="button" class="de576f5064 b46cd7aad7 e26a59bb37 c295306d66 c7a901b0e7 daf5d4cb1c e7f2b1a356">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
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 class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
ARIA hidden element must not be focusable or contain focusable elements69 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
<script type="application/json" data-capla-application-context="" nonce="" aria-hidden="true">
<script type="application/json" id="__CAPLA_CHUNK_METADATA__b-index-lp-web-mfePFJYTMYZ/Homepage" nonce="" aria-hidden="true">
<script type="application/json" data-capla-store-data="apollo" data-capla-namespace="b-index-lp-web-mfePFJYTMYZ" nonce="" aria-hidden="true">
<script nonce="" aria-hidden="true">window.Promise||document.write('<script src="https://cf.bstatic.com/libs/promise/7.0.4/promise-7.0.4.min.js" nonce="UxMbU2Mwxjzo8yaoyuWa6w=="><\/script>')</script><script nonce="" aria-hidden="true">"currentScript"in document||document.write('<script src="https://cf.bstatic.com/libs/current-script-polyfill/1.0.0/current-script-polyfill.min.js" nonce="UxMbU2Mwxjzo8yaoyuWa6w=="><\/script>')</script><script nonce="" async="" data-webpack="b-index-lp-web-mfe:bWebShellComponents" src="https://cf.bstatic.com/psb/capla/static/js/remoteEntry.a1402efb.client.js" aria-hidden="true"></script>
<script nonce="" async="" data-chunk="bWebShellComponents-bWebShellComponents-AccommodationHeader" src="https://cf.bstatic.com/psb/capla/static/js/dc32f6b7.bcb26503.chunk.js" aria-hidden="true"></script>
<script nonce="" async="" data-chunk="bWebShellComponents-bWebShellComponents-BottomNavMobile" src="https://cf.bstatic.com/psb/capla/static/js/2d35db29.3f03d9f8.chunk.js" aria-hidden="true"></script>
<script nonce="" async="" data-chunk="bWebShellComponents-bWebShellComponents-GlobalAlerts" src="https://cf.bstatic.com/psb/capla/static/js/b9a82cb8.366f649e.chunk.js" aria-hidden="true"></script>
<script nonce="" async="" data-chunk="bWebShellComponents-bWebShellComponents-AccommodationFooter" src="https://cf.bstatic.com/psb/capla/static/js/81da5f32.9d589f6f.chunk.js" aria-hidden="true"></script>
Showing first 10 of 69 audited elements.
ARIA role should be appropriate for the element238 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
<img class="f6c12c77eb c0e44985a8 c09abd8a52 ca3dad4476" src="https://t-cf.bstatic.com/design-assets/assets/v3.176.0/images-flags/[email protected]" alt="" role="presentation" loading="lazy">
<ul class="c4a6e8e871" role="menubar">
<li role="none" class="ddb4fbcb64 c857e7fdc3">
<a id="accommodations" role="menuitem" aria-current="page" tabindex="0" href="https://www.booking...." class="de576f5064 f63e3c83f...">
<li role="none" class="ddb4fbcb64">
<a id="flights" role="menuitem" tabindex="-1" href="https://booking.com/..." class="de576f5064 f63e3c83f...">
<li role="none" class="ddb4fbcb64">
<a id="packages" role="menuitem" tabindex="-1" href="https://www.booking...." class="de576f5064 f63e3c83f...">
<li role="none" class="ddb4fbcb64">
<a id="cars" role="menuitem" tabindex="-1" href="https://www.booking...." class="de576f5064 f63e3c83f...">
Showing first 10 of 238 audited elements.
ARIA roles used must conform to valid values2 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 class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
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 data-bui-theme="traveller-light" data-capla-fpr="true" style="overflow: hidden;">
Buttons must have discernible text1 element
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button aria-label="Dismiss sign-in info." type="button" class="de576f5064 b46cd7aad7 e26a59bb37 c295306d66 c7a901b0e7 daf5d4cb1c e7f2b1a356">
Deprecated ARIA roles must not be used2 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 class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
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 dir="ltr" lang="en-us">
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 dir="ltr" lang="en-us">
Elements must meet minimum color contrast ratio thresholds289 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<span class="ca2ca5203b">USD</span>
<span class="ca2ca5203b">List your property</span>
<span class="ca2ca5203b">Register</span>
<span class="ca2ca5203b">Sign in</span>
<span class="b99b6ef58f">Flights</span>
<span class="b99b6ef58f">Flight + Hotel</span>
<span class="b99b6ef58f">Car rental</span>
<span class="b99b6ef58f">Cruises</span>
<span class="b99b6ef58f">Attractions</span>
<span class="b99b6ef58f">Airport taxis</span>
Showing first 10 of 289 audited elements.
Elements must only use permitted ARIA attributes3 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<div class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<button aria-label="Dismiss sign-in info." type="button" class="de576f5064 b46cd7aad7 e26a59bb37 c295306d66 c7a901b0e7 daf5d4cb1c e7f2b1a356">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
Elements must only use supported ARIA attributes3 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<div class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<button aria-label="Dismiss sign-in info." type="button" class="de576f5064 b46cd7aad7 e26a59bb37 c295306d66 c7a901b0e7 daf5d4cb1c e7f2b1a356">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
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
<h2 class="ecb8d66605 daadf70613"><div class="a4ac75716e f546354b44 fab9d44163 cc045b173b">Sign in, save money</div></h2>
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
<h2 class="ecb8d66605 daadf70613"><div class="a4ac75716e f546354b44 fab9d44163 cc045b173b">Sign in, save money</div></h2>
IDs used in ARIA and labels must be unique18 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
<a id="accommodations" role="menuitem" aria-current="page" tabindex="0" href="https://www.booking...." class="de576f5064 f63e3c83f...">
<a id="flights" role="menuitem" tabindex="-1" href="https://booking.com/..." class="de576f5064 f63e3c83f...">
<a id="packages" role="menuitem" tabindex="-1" href="https://www.booking...." class="de576f5064 f63e3c83f...">
<a id="cars" role="menuitem" tabindex="-1" href="https://www.booking...." class="de576f5064 f63e3c83f...">
<a id="cruises" role="menuitem" tabindex="-1" href="https://booking.com/..." class="de576f5064 f63e3c83f...">
<a id="attractions" role="menuitem" tabindex="-1" href="https://www.booking...." class="de576f5064 f63e3c83f...">
<a id="airport_taxis" role="menuitem" tabindex="-1" href="https://www.booking...." class="de576f5064 f63e3c83f...">
<input id=":R5qmr5:" class="faadc60545" type="checkbox" name="sb_flight_search" value="flight">
<button id="mainIndexInterlinkingTab-1-tab-trigger" data-testid="in-product-interlinking-tab-mainIndexInterlinkingTab-1" tabindex="0" type="button" class="de576f5064 f63e3c83f3 e7f2b1a356" role="tab" aria-selected="true" aria-controls="mainIndexInterlinkingTab-1">
<button id="mainIndexInterlinkingTab-2-tab-trigger" data-testid="in-product-interlinking-tab-mainIndexInterlinkingTab-2" tabindex="-1" type="button" class="de576f5064 f63e3c83f3 e7f2b1a356" role="tab" aria-selected="false" aria-controls="mainIndexInterlinkingTab-2">
Showing first 10 of 18 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
<body data-bui-theme="traveller-light" data-capla-fpr="true" style="overflow: hidden;">
<div class="f6e3a11b0d ae5dbab14d a81870d302 e95943ce9b" style="--bui_stack_spaced_gap--s: 3;">
<div class="c3bdfd4ac2" style="--bui_box_spaced_padding--s: 6;">
<div class="f6e3a11b0d ae5dbab14d a81870d302 e95943ce9b aee2fac107" style="--bui_stack_spaced_gap--s: 3;">
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="Dismiss sign-in info." type="button" class="de576f5064 b46cd7aad7 e26a59bb37 c295306d66 c7a901b0e7 daf5d4cb1c e7f2b1a356">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
Links must have discernible text1 element
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a href="https://account.book..." class="de576f5064 b46cd7aad...">
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 dir="ltr" lang="en-us">
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 dir="ltr" lang="en-us">
Required ARIA attributes must be provided2 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 class="a9f1d9ba2c f67e3e9cde c99c8fdd99" role="dialog" aria-modal="true" aria-label="Window offering discounts of 10% or more when you sign in to Booking.com">
<span role="img" class="fc70cba028 a618c196ed" aria-label="blue Genius logo">
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 data-rh="true" name="viewport" content="width=device-width, initial-scale=1.0">
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 data-rh="true" name="viewport" content="width=device-width, initial-scale=1.0">