Hotels.comhotels.com
Accessibility Score
Issues Found
Issues Found
Serious<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.
Failing Elements
<html>
Fix any of the following:
- The <html> element does not have a lang attribute
ModeratePage 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.
Failing Elements
<html>
Fix all of the following:
- Page must have a level-one heading
Passed Audits
All page content should be contained by landmarks21 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div id="app-captcha-pwa">
<div id="app-layer-manager">
<div id="app-layer-base" aria-hidden="false" class="app-layer-base--active">
<div class="page-container">
<header class="global-navigation-site-header">
<div class="global-navigation-site-header-container">
<section class="global-navigation-row primary">
<div class="global-navigation-row-container">
<div class="uitk-layout-flex uitk-layout-flex-align-items-center uitk-layout-flex-justify-content-center uitk-layout-flex-gap-six uitk-spacing uitk-spacing-padding-inline-six">
<a class="uitk-header-brand-logo" href="/" data-testid="header-brand-logo-anchor"><img src="https://www.hotels.com/_dms/header/logo.svg?locale=en_US&siteid=300000001" alt="hotels Logo"></a>
Showing first 10 of 21 audited elements.
Alternative text of images should not be repeated as text1 element
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://www.hotels.com/_dms/header/logo.svg?locale=en_US&siteid=300000001" alt="hotels Logo">
ARIA attributes must be used as specified for the element's role1 element
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">
ARIA attributes must conform to valid names1 element
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">
ARIA attributes must conform to valid values1 element
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">
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">
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">
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>
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
<main class="captcha-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>
Elements must meet minimum color contrast ratio thresholds3 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
<h2 class="uitk-heading uitk-heading-5">Show us your human side...</h2>
<p class="uitk-paragraph uitk-paragraph-2">We can't tell if you're a human or a bot.</p>
<div class="captcha-debug-id">3b9c7bff-b713-4d92-89fa-a681dfca8d52</div>
Elements must only use permitted ARIA attributes1 element
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">
Elements must only use supported ARIA attributes1 element
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">
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="uitk-heading uitk-heading-5">Show us your human side...</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="uitk-heading uitk-heading-5">Show us your human side...</h2>
Images must have alternative text1 element
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://www.hotels.com/_dms/header/logo.svg?locale=en_US&siteid=300000001" alt="hotels Logo">
Inline text spacing must be adjustable with custom stylesheets1 element
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
<div class="uitk-card uitk-card-roundcorner-all uitk-spacing uitk-spacing-margin-blockstart-four datadome-container uitk-card-has-primary-theme" style="display: block;">
Interactive controls must not be nested1 element
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://www.hotels.com/_dms/header/logo.svg?locale=en_US&siteid=300000001" alt="hotels Logo">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination2 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">
<main class="captcha-main">
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 class="uitk-header-brand-logo" href="/" data-testid="header-brand-logo-anchor"><img src="https://www.hotels.com/_dms/header/logo.svg?locale=en_US&siteid=300000001" alt="hotels Logo"></a>
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="captcha-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>
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">