Hiltonhilton.com
Accessibility Score
Issues Found
Issues Found
CriticalImages must have alternative text2 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.
Failing Elements
<img width="96" height="36" src="data:image/png;base6...">
Fix any of the following:
- Element does not have an alt attribute
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element's default semantics were not overridden with role="none" or role="presentation"
<img width="70" height="14" src="data:image/png;base6...">
Fix any of the following:
- Element does not have an alt attribute
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element's default semantics were not overridden with role="none" or role="presentation"
SeriousElements 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.
Failing Elements
<h1>Something went wrong</h1>
Fix any of the following:
- Element has insufficient color contrast of 2.73 (foreground color: #00a8e1, background color: #ffffff, font size: 36.0pt (48px), font weight: normal). Expected contrast ratio of 3:1
<a href="https://www.hilton.com/en//" target="_blank">Hilton.com</a>
Fix any of the following:
- Element has insufficient color contrast of 2.73 (foreground color: #00a8e1, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="https://help.hilton.com/s/" target="_blank">Customer Service</a>
Fix any of the following:
- Element has insufficient color contrast of 2.73 (foreground color: #00a8e1, background color: #ffffff, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
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 class="no-js" lang="">
Fix any of the following:
- The <html> element does not have a lang attribute
SeriousLinks must have discernible text2 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.
Failing Elements
<a target="_blank" href="/"><span class="brand-bar-color-hilton-color"></span></a>
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a href="http://www.aboutads.info/choices/" target="_blank">
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
ModerateDocument 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.
Failing Elements
<html class="no-js" lang="">
Fix all of the following:
- Document does not have a main landmark
ModerateAll page content should be contained by landmarks1 element
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<section class="cp-content inner-width">
Fix any of the following:
- Some page content is not contained by landmarks
Passed Audits
<li> elements must be contained in a <ul> or <ol>41 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><a target="_blank" href="http://www.ar.hilton.com/">
<div>العربية</div>
</a></li><li><a target="_blank" href="http://www.hiltonhotels.com/bg_BG/">
<div>Български</div>
</a></li><li><a target="_blank" href="http://www.hilton.com.cn/zh-cn/">
<div>简体中文</div>
</a></li><li><a target="_blank" href="http://www.hilton.com.cn/zh-HK/">
<div>繁體中文</div>
</a></li><li><a target="_blank" href="http://www.hiltonhotels.com/cs_CZ/">
<div>Česky</div>
</a></li><li><a href="http://www.hiltonhotels.com/da_DK/">
<div>Dansk</div>
</a></li><li><a target="_blank" href="http://www.hiltonhotels.com/nl_NL/">
<div>Nederlands</div>
</a></li><li><a target="_blank" href="http://www.hiltonhotels.com/fi_FI/">
<div>Suomi</div>
</a></li><li><a target="_blank" href="http://www.hiltonhotels.de/">
<div>Deutsch</div>
</a></li><li><a target="_blank" href="http://www.hiltonhotels.com/fr_FR/">
<div>Français</div>
</a></li>Showing first 10 of 41 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements2 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>
<ul>
All page content should be contained by landmarks301 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
<header>
<div class="inner-width-2">
<img width="96" height="36" src="data:image/png;base6...">
<div class="cp-content__top">
<h1>Something went wrong</h1>
<p>Maybe it’s us, maybe it’s you.<br>(It’s probably us).</p>
<span class="cp-content__top--reference">Reference No. 18.17a7cb17.1777251730.292af324</span>
</div><h1>Something went wrong</h1>
<p>Maybe it’s us, maybe it’s you.<br>(It’s probably us).</p>
<br>
<span class="cp-content__top--reference">Reference No. 18.17a7cb17.1777251730.292af324</span>
<div class="cp-content__bottom">
<a href="/" class="cp-button">Go Back</a>
Showing first 10 of 301 audited elements.
Alternative text of images should not be repeated as text2 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 width="96" height="36" src="data:image/png;base6...">
<img width="70" height="14" src="data:image/png;base6...">
ARIA hidden element must not be focusable or contain focusable elements1 element
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
<iframe id="rokt-controller-fram..." data-core-type="controller" aria-hidden="true" tabindex="-1" allow="payment" sandbox="allow-scripts allow-..." src="https://apps.rokt-ap..." name="9ef3334c-58c3-41a2-9..." style="width: 0px !importan...">
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>
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>
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="inner-width">
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>
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="inner-width">
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 class="no-js" lang="">
Elements must meet minimum color contrast ratio thresholds44 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
<p>Maybe it’s us, maybe it’s you.<br>(It’s probably us).</p>
<span class="cp-content__top--reference">Reference No. 18.17a7cb17.1777251730.292af324</span>
<a href="/" class="cp-button">Go Back</a>
<p>or try:<br>
<a href="https://www.hilton.com/en//" target="_blank">Hilton.com</a>
<a href="https://help.hilton.com/s/" target="_blank">Customer Service</a>
</p><span>Global Sites:</span>
<div>Български</div>
<div>简体中文</div>
<div>繁體中文</div>
<div>Česky</div>
<div>Dansk</div>
Showing first 10 of 44 audited elements.
Heading levels should only increase by one1 element
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1>Something went wrong</h1>
Headings should not be empty1 element
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1>Something went wrong</h1>
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
<img width="96" height="36" src="data:image/png;base6...">
<img width="70" height="14" src="data:image/png;base6...">
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>
<footer class="inner-width">
Links must have discernible text55 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 href="/" class="cp-button">Go Back</a>
<a href="https://www.hilton.com/en//" target="_blank">Hilton.com</a>
<a href="https://help.hilton.com/s/" target="_blank">Customer Service</a>
<a class="tooltip" title="The luxury brand offering a unique service experience and the world's landmark hotels." target="_blank" href="https://www.hilton.com/en/brands/waldorf-astoria/">
<span class="brand-bar-color-waldorf-astoria-color"></span>
</a><a class="tooltip" title="A world of style, service and connection for today's sophisticated traveler." target="_blank" href="https://www.hilton.com/en/brands/conrad-hotels/">
<span class="brand-bar-color-conrad-color"></span>
</a><a class="tooltip" title="A world of style, service and connection for today's sophisticated traveler." target="_blank" href="https://www.hilton.com/en/brands/canopy-by-hilton/">
<span class="brand-bar-color-canopy-color"></span>
</a><a class="tooltip" title="The global leader in hospitality with more than 530 hotels & resorts across six continents." target="_blank" href="https://www.hilton.com/en/brands/hilton-hotels/">
<a class="tooltip" title="A collection of unique hotels appealing to travelers seeking local discovery." target="_blank" href=" https://www.hilton.com/en/brands/curio-collection/">
<span class="brand-bar-color-curio-color"></span>
</a><a class="tooltip" title="Warm. Comfortable. Smart. The hotel that turns travel into a human experience again." target="_blank" href="https://www.hilton.com/en/brands/doubletree-by-hilton/">
<span class="brand-bar-color-doubletree-color"></span>
</a><a class="tooltip" title="A collection of hotels that gives you the peace of mind to travel independently." target="_blank" href="https://www.hilton.com/en/brands/tapestry-collection/">
Showing first 10 of 55 audited elements.
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 class="no-js" lang="">
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 class="no-js" lang="">
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">
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">