Hotels.com hotels.com
Accessibility score
League position
1stof 10
Issues found
1
Audits passed
56
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousFocus must not be shown by a change of text color alone1 element
When the only sign of focus is text turning a slightly different color, many users cannot see where focus is. People with color vision deficiencies may not perceive the change at all, and people with low vision or using a dim or glare-affected screen may miss a small shift in shade. A change in lightness of at least 3:1, or an indicator that does not rely on color such as an outline or underline, keeps focus visible to everyone.
Failing Elements
<input id="destination_form_field-input" autocapitalize="off" autocomplete="off" autocorrect="off" type="text" spellcheck="false" data-stid="destination_form_field-menu-trigger" name="destination_form_field" aria-label="Where to?" class="uitk-field-input" placeholder="Where to?" aria-required="false...
Passed audits56 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 data-language="en_NZ" dir="ltr" lang="en" class="">
<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 data-language="en_NZ" dir="ltr" lang="en" class="">
<li> elements must be contained in a <ul> or <ol>10 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 class="uitk-typelist-item uitk-typelist-item-undefined uitk-typelist-item-no-indent">
<li class="uitk-typelist-item uitk-typelist-item-undefined uitk-typelist-item-no-indent">
<li class="uitk-typelist-item uitk-typelist-item-undefined uitk-typelist-item-no-indent">
<li class="uitk-typelist-item uitk-typelist-item-undefined uitk-typelist-item-no-indent">
<li class="uitk-typelist-item uitk-typelist-item-undefined uitk-typelist-item-no-indent">
Showing first 5 of 10 audited elements.
<svg> elements with an img or image role must have alternative text3 elements
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<svg class="uitk-icon uitk-icon-small" aria-describedby="info_outline-description" aria-label="More information" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<svg class="uitk-icon uitk-icon-leading uitk-icon-directional" aria-label="Next card" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements3 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="uitk-layout-flex uitk-layout-flex-align-items-center uitk-layout-flex-justify-content-flex-end uitk-layout-flex-flex-wrap-nowrap uitk-layout-flex-item uitk-layout-flex-item-flex-grow-1">
<ul class="uitk-typelist uitk-typelist-orientation-stacked uitk-typelist-size-2">
<ul class="uitk-typelist uitk-typelist-orientation-stacked uitk-typelist-size-2">
Accessible names must not be code or placeholder text32 elements
Screen reader users hear a control's accessible name in place of what sighted users see. When the name is a class name like "quantity-selector", a script value like "undefined" or an unrendered template like "{{title}}", they hear noise and cannot tell what the control does. Every check that only asks whether a name exists passes these, because the name is there.
Audit Elements
<a class="uitk-list-item" href="#main_content">
<a class="uitk-header-brand-logo" href="https://nz.hotels.com/" data-testid="header-brand-logo-anchor">
<a href="https://hotelsapp.onelink.me/fSyN?pid=BRAND&af..." data-context="global_navigation" class="uitk-button uitk-button-small uitk-button-has-text...">
<button data-stid="button-type-picker-trigger" data-context="global_navigation" data-button-type="tertiary" type="button" class="uitk-button uitk-button-medium uitk-button-tertiar...">
<a href="https://apps.expediapartnercentral.com/en_NZ/list?..." target="_blank" rel="noopener" data-stid="listYourProperty-link" data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-button-medium uitk-button-has-tex...">
Showing first 5 of 32 audited elements.
All page content should be contained by landmarks369 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="app-lotus-home-ui">
<div id="app-layer-manager">
<div id="app-layer-base" aria-hidden="false" class="app-layer-base--active">
<div class="pageWhiteBackground">
<div class="page-header with-shadow">
Showing first 5 of 369 audited elements.
All touch targets must be 24px large, or leave sufficient space33 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="uitk-list-item" href="#main_content"><span class="uitk-menu-list-item-label">Skip to main content</span></a>
<a class="uitk-header-brand-logo" href="https://nz.hotels.com/" data-testid="header-brand-logo-anchor"><img src="https://nz.hotels.com/_dms/header/logo.svg?locale=en_NZ&siteid=300000038&theme=dark&variant=refresh&2" alt="Hotels logo"></a>
<a href="https://hotelsapp.on..." data-context="global_navigation" class="uitk-button uitk-but...">
<button data-stid="button-type-picker-trigger" data-context="global_navigation" data-button-type="tertiary" type="button" class="uitk-button uitk-button-medium uitk-button-tertiary uitk-spacing global-navigation-nav-button">
<a href="https://apps.expedia..." target="_blank" rel="noopener" data-stid="listYourProperty-lin..." data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-but...">
Showing first 5 of 33 audited elements.
Alt text must not be a filename or placeholder text10 elements
Screen reader users hear an image's alt text in place of the image. When the alt text is a filename like "IMG_4032.jpg" or a placeholder like "image", they hear meaningless noise and learn nothing about what the image shows. Many content management systems fill in the filename automatically, so this passes every check that only asks whether alt text exists.
Audit Elements
<img src="https://nz.hotels.com/_dms/header/logo.svg?locale=..." alt="Hotels logo">
<img class="uitk-mark uitk-spacing uitk-spacing-margin-inlines..." alt="New Zealand" src="https://a.travel-assets.com/egds/marks/flags/nz.sv..." id="NZ">
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<svg class="uitk-icon uitk-icon-small" aria-describedby="info_outline-description" aria-label="More information" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<img alt="A geothermal area with a green pool, an orange rim..." class="uitk-image-media" src="https://images.trvl-media.com/place/6048125/9a8a8a..." decoding="async">
Showing first 5 of 10 audited elements.
Alternative text of images should not be repeated as text11 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img src="https://nz.hotels.com/_dms/header/logo.svg?locale=en_NZ&siteid=300000038&theme=dark&variant=refresh&2" alt="Hotels logo">
<img class="uitk-mark uitk-spacing uitk-spacing-margin-inlinestart-one uitk-mark-flag" alt="New Zealand" src="https://a.travel-assets.com/egds/marks/flags/nz.svg" id="NZ">
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__open_lock.png" style="--uitk-mark-token-size:var(--mark-size-12)">
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__rewards_2.png" style="--uitk-mark-token-size:var(--mark-size-12)">
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__checkmark.png" style="--uitk-mark-token-size:var(--mark-size-12)">
Showing first 5 of 11 audited elements.
ARIA attributes must be used as specified for the element's role23 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="app-layer-base" aria-hidden="false" class="app-layer-base--active">
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<button title="" tabindex="0" aria-expanded="true" data-testid="header-menu-button" data-context="global_navigation" data-button-type="tertiary" type="button" ...>
<div class="uitk-menu-container animation-disabled uitk-menu-open uitk-menu-pos-right uitk-menu-container-autoposition uitk-menu-container-has-intersection-root-el" aria-hidden="false" style="width: 375px;">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
Showing first 5 of 23 audited elements.
ARIA attributes must conform to valid names23 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="app-layer-base" aria-hidden="false" class="app-layer-base--active">
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<button title="" tabindex="0" aria-expanded="true" data-testid="header-menu-button" data-context="global_navigation" data-button-type="tertiary" type="button" ...>
<div class="uitk-menu-container animation-disabled uitk-menu-open uitk-menu-pos-right uitk-menu-container-autoposition uitk-menu-container-has-intersection-root-el" aria-hidden="false" style="width: 375px;">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
Showing first 5 of 23 audited elements.
ARIA attributes must conform to valid values22 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="app-layer-base" aria-hidden="false" class="app-layer-base--active">
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<button title="" tabindex="0" aria-expanded="true" data-testid="header-menu-button" data-context="global_navigation" data-button-type="tertiary" type="button" ...>
<div class="uitk-menu-container animation-disabled uitk-menu-open uitk-menu-pos-right uitk-menu-container-autoposition uitk-menu-container-has-intersection-root-el" aria-hidden="false" style="width: 375px;">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
Showing first 5 of 22 audited elements.
ARIA hidden element must not be focusable or contain focusable elements30 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 class="animated-icon" aria-hidden="true" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<div class="uitk-text uitk-type-400 uitk-type-bold in-global-navigation-main-layer uitk-text-default-theme" aria-hidden="true">•</div>
<svg class="uitk-icon uitk-field-icon" aria-hidden="true" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<svg class="uitk-icon uitk-field-icon" aria-hidden="true" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<svg class="uitk-icon uitk-field-icon" aria-hidden="true" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
Showing first 5 of 30 audited elements.
ARIA role should be appropriate for the element48 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
<iframe src="about:blank" title="" role="presentation" loading="eager" style="width: 0px; height: 0px; border: 0px; display: none;"></iframe>
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
<div role="main">
<svg class="uitk-icon uitk-step-input-icon" aria-label="Decrease the number of adults in room 1" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
Showing first 5 of 48 audited elements.
ARIA roles used must conform to valid values25 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
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
<div role="main">
<svg class="uitk-icon uitk-icon-small" aria-describedby="info_outline-description" aria-label="More information" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<a href="https://nz.hotels.com/login?uurl=e3id%3Dredr%26rurl%3D%2Fwelcome-hotels-rewards" target="_self" class="uitk-link uitk-link-align-left uitk-link-layout-inline uitk-link-medium" role="link">Join for free</a>
Showing first 5 of 25 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 data-theme-light="light-1" class="uitk-no-outline">
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 id="destination_form_fie..." autocapitalize="off" autocomplete="off" autocorrect="off" type="text" spellcheck="false" data-stid="destination_form_fie..." name="destination_form_fie..." aria-label="Where to?" class="uitk-field-input" placeholder="Where to?" aria-required="false" 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="global-navigation-site-header">
Buttons must have discernible text7 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 data-stid="button-type-picker-trigger" data-context="global_navigation" data-button-type="tertiary" type="button" class="uitk-button uitk-button-medium uitk-button-tertiary uitk-spacing global-navigation-nav-button">
<button title="" tabindex="0" aria-expanded="true" data-testid="header-menu-button" data-context="global_navigation" data-button-type="tertiary" type="button" ...>
<button data-testid="uitk-date-selector-i..." data-stid="uitk-date-selector-i..." name="EGDSDateRange-date-s..." aria-invalid="false" aria-describedby="id__R1heabtt7vhvvpkp..." aria-expanded="false" aria-label="Dates, Mon, 23 Nov -..." class="uitk-fake-input uitk..." type="button">
<button aria-roledescription="expand to change the..." data-stid="open-room-picker" aria-expanded="false" aria-haspopup="menu" aria-label="Travellers, 2 travel..." class="uitk-menu-trigger op..." type="button">
<button type="button" class="uitk-more-info-trigger uitk-more-info-trigger-size-medium uitk-more-info-trigger-weight-regular uitk-more-info-trigger-theme-default uitk-more-info-trigger-align-leading">
Showing first 5 of 7 audited elements.
Certain ARIA roles must be contained by particular parents5 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="#dui-tabs-0" class="uitk-tab-anchor uitk-tab-anchor-selected" aria-controls="tab-id__r1m_-0" aria-selected="true" role="tab" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Beach</span></a>
<a href="#dui-tabs-1" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-1" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Culture</span></a>
<a href="#dui-tabs-2" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-2" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Ski</span></a>
<a href="#dui-tabs-3" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-3" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Family</span></a>
<a href="#dui-tabs-4" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-4" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Wellness and Relaxation</span></a>
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
<ul class="uitk-tabs uitk-tabs-natural background-primary uitk-tabs-default uitk-tabs-with-border" role="tablist">
Deprecated ARIA roles must not be used25 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
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
<div role="main">
<svg class="uitk-icon uitk-icon-small" aria-describedby="info_outline-description" aria-label="More information" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<a href="https://nz.hotels.com/login?uurl=e3id%3Dredr%26rurl%3D%2Fwelcome-hotels-rewards" target="_self" class="uitk-link uitk-link-align-left uitk-link-layout-inline uitk-link-medium" role="link">Join for free</a>
Showing first 5 of 25 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 data-language="en_NZ" dir="ltr" lang="en" class="">
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="global-navigation-site-header">
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
<div role="main">
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 data-language="en_NZ" dir="ltr" lang="en" class="">
Elements marked as presentational should be consistently ignored9 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__open_lock.png" style="--uitk-mark-token-size:var(--mark-size-12)">
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__rewards_2.png" style="--uitk-mark-token-size:var(--mark-size-12)">
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__checkmark.png" style="--uitk-mark-token-size:var(--mark-size-12)">
<li data-stid="uitk-tab-active" role="presentation" class="uitk-tab active"><a href="#dui-tabs-0" class="uitk-tab-anchor uitk-tab-anchor-selected" aria-controls="tab-id__r1m_-0" aria-selected="true" role="tab" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Beach</span></a></li>
<li role="presentation" class="uitk-tab"><a href="#dui-tabs-1" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-1" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Culture</span></a></li>
Showing first 5 of 9 audited elements.
Elements must have their visible text as part of their accessible name3 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Audit Elements
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
<button data-testid="uitk-date-selector-i..." data-stid="uitk-date-selector-i..." name="EGDSDateRange-date-s..." aria-invalid="false" aria-describedby="id__R1heabtt7vhvvpkp..." aria-expanded="false" aria-label="Dates, Mon, 23 Nov -..." class="uitk-fake-input uitk..." type="button">
<button aria-roledescription="expand to change the..." data-stid="open-room-picker" aria-expanded="false" aria-haspopup="menu" aria-label="Travellers, 2 travel..." class="uitk-menu-trigger op..." type="button">
Elements must meet minimum color contrast ratio thresholds32 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="uitk-text truncate uitk-type-300 uitk-text-white-space-nowrap in-global-navigation-main-layer uitk-text-default-theme">Open app</div>
<span class="uitk-spacing uitk-spacing-margin-inline-one">NZD</span>
<a href="https://apps.expedia..." target="_blank" rel="noopener" data-stid="listYourProperty-lin..." data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-but...">
<a href="/helpcenter" target="_self" rel="" data-stid="support-cs-link" data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-but...">
<a href="/trips" target="_self" rel="" data-stid="itinerary-link" data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-but...">
Showing first 5 of 32 audited elements.
Elements must only use permitted ARIA attributes23 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="app-layer-base" aria-hidden="false" class="app-layer-base--active">
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<button title="" tabindex="0" aria-expanded="true" data-testid="header-menu-button" data-context="global_navigation" data-button-type="tertiary" type="button" ...>
<div class="uitk-menu-container animation-disabled uitk-menu-open uitk-menu-pos-right uitk-menu-container-autoposition uitk-menu-container-has-intersection-root-el" aria-hidden="false" style="width: 375px;">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
Showing first 5 of 23 audited elements.
Elements must only use supported ARIA attributes23 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="app-layer-base" aria-hidden="false" class="app-layer-base--active">
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<button title="" tabindex="0" aria-expanded="true" data-testid="header-menu-button" data-context="global_navigation" data-button-type="tertiary" type="button" ...>
<div class="uitk-menu-container animation-disabled uitk-menu-open uitk-menu-pos-right uitk-menu-container-autoposition uitk-menu-container-has-intersection-root-el" aria-hidden="false" style="width: 375px;">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
Showing first 5 of 23 audited elements.
Elements should not have tabindex greater than zero7 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
<button title="" tabindex="0" aria-expanded="true" data-testid="header-menu-button" data-context="global_navigation" data-button-type="tertiary" type="button" ...>
<div id="main_content" class="is-visually-hidden" tabindex="-1"></div>
<a href="#dui-tabs-1" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-1" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Culture</span></a>
<a href="#dui-tabs-2" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-2" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Ski</span></a>
<a href="#dui-tabs-3" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-3" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false"><span class="uitk-tab-text">Family</span></a>
Showing first 5 of 7 audited elements.
Focused elements must not be entirely hidden by author-created content27 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="uitk-list-item" href="#main_content">
<a class="uitk-header-brand-logo" href="https://nz.hotels.com/" data-testid="header-brand-logo-anchor">
<a href="https://hotelsapp.onelink.me/fSyN?pid=BRAND&af..." data-context="global_navigation" class="uitk-button uitk-button-small uitk-button-has-text...">
<button data-stid="button-type-picker-trigger" data-context="global_navigation" data-button-type="tertiary" type="button" class="uitk-button uitk-button-medium uitk-button-tertiar...">
<a href="https://apps.expediapartnercentral.com/en_NZ/list?..." target="_blank" rel="noopener" data-stid="listYourProperty-link" data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-button-medium uitk-button-has-tex...">
Showing first 5 of 27 audited elements.
Form elements must have labels2 elements
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input id="destination_form_fie..." autocapitalize="off" autocomplete="off" autocorrect="off" type="text" spellcheck="false" data-stid="destination_form_fie..." name="destination_form_fie..." aria-label="Where to?" class="uitk-field-input" placeholder="Where to?" aria-required="false" value="" ...>
<input type="checkbox" name="EGDSSearchFormCheckboxWithInfo-business-verification" id="business-verification-check" class="uitk-layout-flex-item uitk-layout-flex-item-flex-shrink-0" aria-required="false" aria-label="I'm travelling for business" value="unmanagedBusiness">
Form elements should have a visible label2 elements
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input id="destination_form_fie..." autocapitalize="off" autocomplete="off" autocorrect="off" type="text" spellcheck="false" data-stid="destination_form_fie..." name="destination_form_fie..." aria-label="Where to?" class="uitk-field-input" placeholder="Where to?" aria-required="false" value="" ...>
<input type="checkbox" name="EGDSSearchFormCheckboxWithInfo-business-verification" id="business-verification-check" class="uitk-layout-flex-item uitk-layout-flex-item-flex-shrink-0" aria-required="false" aria-label="I'm travelling for business" value="unmanagedBusiness">
Form field must not have multiple label elements2 elements
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input id="destination_form_fie..." autocapitalize="off" autocomplete="off" autocorrect="off" type="text" spellcheck="false" data-stid="destination_form_fie..." name="destination_form_fie..." aria-label="Where to?" class="uitk-field-input" placeholder="Where to?" aria-required="false" value="" ...>
<input type="checkbox" name="EGDSSearchFormCheckboxWithInfo-business-verification" id="business-verification-check" class="uitk-layout-flex-item uitk-layout-flex-item-flex-shrink-0" aria-required="false" aria-label="I'm travelling for business" value="unmanagedBusiness">
Heading levels should only increase by one6 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="uitk-heading uitk-heading-6 uitk-spacing uitk-spacing-margin-blockend-eight uitk-layout-grid-item uitk-layout-grid-item-justify-self-center uitk-type-style-display-medium" type-style-theme="standard">
<h2 class="uitk-heading uitk-type-start uitk-heading-2 overflow-wrap uitk-type-style-headline-large" type-style-theme="standard">Save with instant discounts</h2>
<h2 class="uitk-heading uitk-type-start uitk-heading-2 overflow-wrap uitk-type-style-headline-large" type-style-theme="standard">Earn 1 reward night</h2>
<h2 class="uitk-heading uitk-type-start uitk-heading-2 overflow-wrap uitk-type-style-headline-large" type-style-theme="standard">Plans change. We get it.</h2>
<h3 class="uitk-heading uitk-heading-6 uitk-type-style-headline-extra-large" type-style-theme="standard">Your style. These stays. A perfect match.</h3>
Showing first 5 of 6 audited elements.
Headings should not be empty6 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="uitk-heading uitk-heading-6 uitk-spacing uitk-spacing-margin-blockend-eight uitk-layout-grid-item uitk-layout-grid-item-justify-self-center uitk-type-style-display-medium" type-style-theme="standard">
<h2 class="uitk-heading uitk-type-start uitk-heading-2 overflow-wrap uitk-type-style-headline-large" type-style-theme="standard">Save with instant discounts</h2>
<h2 class="uitk-heading uitk-type-start uitk-heading-2 overflow-wrap uitk-type-style-headline-large" type-style-theme="standard">Earn 1 reward night</h2>
<h2 class="uitk-heading uitk-type-start uitk-heading-2 overflow-wrap uitk-type-style-headline-large" type-style-theme="standard">Plans change. We get it.</h2>
<h3 class="uitk-heading uitk-heading-6 uitk-type-style-headline-extra-large" type-style-theme="standard">Your style. These stays. A perfect match.</h3>
Showing first 5 of 6 audited elements.
IDs used in ARIA and labels must be unique6 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
<input id="destination_form_fie..." autocapitalize="off" autocomplete="off" autocorrect="off" type="text" spellcheck="false" data-stid="destination_form_fie..." name="destination_form_fie..." aria-label="Where to?" class="uitk-field-input" placeholder="Where to?" aria-required="false" value="" ...>
<input id="id__R1heabtt7vhvvpkpl9_-input1" type="text" class="uitk-field-input is-hidden" placeholder="Placeholder" aria-required="false" aria-invalid="false" value="Mon, 23 Nov - Wed, 25 Nov">
<input id="input-id__ri_" type="text" class="uitk-field-input is-hidden" placeholder="Placeholder" aria-required="false" aria-invalid="false" value="2 travellers, 1 room">
<input type="checkbox" name="EGDSSearchFormCheckboxWithInfo-business-verification" id="business-verification-check" class="uitk-layout-flex-item uitk-layout-flex-item-flex-shrink-0" aria-required="false" aria-label="I'm travelling for business" value="unmanagedBusiness">
<desc id="info_outline-description">More information</desc>
Showing first 5 of 6 audited elements.
Images must have alternative text11 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img src="https://nz.hotels.com/_dms/header/logo.svg?locale=en_NZ&siteid=300000038&theme=dark&variant=refresh&2" alt="Hotels logo">
<img class="uitk-mark uitk-spacing uitk-spacing-margin-inlinestart-one uitk-mark-flag" alt="New Zealand" src="https://a.travel-assets.com/egds/marks/flags/nz.svg" id="NZ">
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__open_lock.png" style="--uitk-mark-token-size:var(--mark-size-12)">
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__rewards_2.png" style="--uitk-mark-token-size:var(--mark-size-12)">
<img class="uitk-mark uitk-mark-landscape-oriented" alt="" src="https://a.travel-assets.com/travel-assets-manager/pictogram-hcom-2026/light__checkmark.png" style="--uitk-mark-token-size:var(--mark-size-12)">
Showing first 5 of 11 audited elements.
Inline text spacing must be adjustable with custom stylesheets42 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
<span style="opacity:0.5"><div class="uitk-text uitk-type-400 uitk-type-bold in-global-navigation-main-layer uitk-text-default-theme" aria-hidden="true">•</div></span>
<div class="uitk-menu-container animation-disabled uitk-menu-open uitk-menu-pos-right uitk-menu-container-autoposition uitk-menu-container-has-intersection-root-el" aria-hidden="false" style="width: 375px;">
<div data-testid="hero-card" style="padding:0">
<div class="uitk-layout-grid uit..." style="--uitk-layoutgrid-au...">
<div class="uitk-layout-position..." style="--uitk-layoutgrid-co...">
Showing first 5 of 42 audited elements.
Interactive controls must not be nested24 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
<img src="https://nz.hotels.com/_dms/header/logo.svg?locale=en_NZ&siteid=300000038&theme=dark&variant=refresh&2" alt="Hotels logo">
<button data-stid="button-type-picker-trigger" data-context="global_navigation" data-button-type="tertiary" type="button" class="uitk-button uitk-button-medium uitk-button-tertiary uitk-spacing global-navigation-nav-button">
<img class="uitk-mark uitk-spacing uitk-spacing-margin-inlinestart-one uitk-mark-flag" alt="New Zealand" src="https://a.travel-assets.com/egds/marks/flags/nz.svg" id="NZ">
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<button title="" tabindex="0" aria-expanded="true" data-testid="header-menu-button" data-context="global_navigation" data-button-type="tertiary" type="button" ...>
Showing first 5 of 24 audited elements.
Interactive elements must have a visible focus indicator27 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="uitk-list-item" href="#main_content">
<a class="uitk-header-brand-logo" href="https://nz.hotels.com/" data-testid="header-brand-logo-anchor">
<a href="https://hotelsapp.onelink.me/fSyN?pid=BRAND&af..." data-context="global_navigation" class="uitk-button uitk-button-small uitk-button-has-text...">
<button data-stid="button-type-picker-trigger" data-context="global_navigation" data-button-type="tertiary" type="button" class="uitk-button uitk-button-medium uitk-button-tertiar...">
<a href="https://apps.expediapartnercentral.com/en_NZ/list?..." target="_blank" rel="noopener" data-stid="listYourProperty-link" data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-button-medium uitk-button-has-tex...">
Showing first 5 of 27 audited elements.
Keyboard focus must be able to leave every component it can enter0 elements
Keyboard users move through a page with Tab, Shift+Tab, arrow keys and Escape. When focus enters a component and none of those keys lets it leave, the rest of the page becomes unreachable and the only way out is to reload or abandon it.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination3 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="global-navigation-site-header">
<div role="main">
<div class="uitk-carousel no-peek no-inset no-touch items-max-height has-inner-spacing uitk-spacing uitk-spacing-margin-blockstart-one xl" data-stid="carousel-wrapper" role="region" aria-roledescription="carousel" aria-label="Your style. These stays. A perfect match.">
Links must have discernible text24 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="uitk-list-item" href="#main_content"><span class="uitk-menu-list-item-label">Skip to main content</span></a>
<a class="uitk-header-brand-logo" href="https://nz.hotels.com/" data-testid="header-brand-logo-anchor"><img src="https://nz.hotels.com/_dms/header/logo.svg?locale=en_NZ&siteid=300000038&theme=dark&variant=refresh&2" alt="Hotels logo"></a>
<a href="https://hotelsapp.on..." data-context="global_navigation" class="uitk-button uitk-but...">
<a href="https://apps.expedia..." target="_blank" rel="noopener" data-stid="listYourProperty-lin..." data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-but...">
<a href="/helpcenter" target="_self" rel="" data-stid="support-cs-link" data-context="global_navigation" data-button-type="tertiary" class="uitk-button uitk-but...">
Showing first 5 of 24 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
<div role="main">
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 data-language="en_NZ" dir="ltr" lang="en" class="">
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 data-language="en_NZ" dir="ltr" lang="en" class="">
Required ARIA attributes must be provided25 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
<svg class="uitk-icon uitk-icon-large" aria-label="Communication Center" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<a role="link" aria-label="Feedback" data-stid="support-feedback-lin..." href="https://www.directwo..." target="_blank" rel="noopener" class="uitk-link uitk-list-...">
<div role="main">
<svg class="uitk-icon uitk-icon-small" aria-describedby="info_outline-description" aria-label="More information" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<a href="https://nz.hotels.com/login?uurl=e3id%3Dredr%26rurl%3D%2Fwelcome-hotels-rewards" target="_self" class="uitk-link uitk-link-align-left uitk-link-layout-inline uitk-link-medium" role="link">Join for free</a>
Showing first 5 of 25 audited elements.
Scrollable region must have keyboard access1 element
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<div class="uitk-carousel-contai..." data-stid="carousel-container" style="--uitk-carousel-item...">
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="uitk-list-item" href="#main_content">
Tabs must control a tab panel, and tab panels must belong to a tab6 elements
Screen readers announce an element with the tab role as part of a tab interface, such as "tab, 1 of 5", and users expect activating it to show a panel of content on the same page. When there is no tab panel, or the tab is really a link to another page, that promise is broken, and users are left unsure where they are or what activating the control will do.
Audit Elements
<a href="#dui-tabs-0" class="uitk-tab-anchor uitk-tab-anchor-selected" aria-controls="tab-id__r1m_-0" aria-selected="true" role="tab" data-toggle="tab" draggable="false">
<a href="#dui-tabs-1" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-1" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false">
<a href="#dui-tabs-2" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-2" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false">
<a href="#dui-tabs-3" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-3" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false">
<a href="#dui-tabs-4" class="uitk-tab-anchor" aria-controls="tab-id__r1m_-4" aria-selected="false" role="tab" tabindex="-1" data-toggle="tab" draggable="false">
Showing first 5 of 6 audited elements.
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.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 name="viewport" content="width=device-width, initial-scale=1.0">
How does your site stack up against Hotels.com?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Travel & Hospitality