Skip to content
https://ritzcarlton.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 500, bare page
FIX
HTTP 500, bare page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 500 ✗Page Title 500 Internal Server Error ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
23 landmarks
REVIEW
23 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Heading Hierarchy
15 headings
REVIEW
15 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Author a room pool for which API response Exists
  • H2 Author a room pool for which API response Exists
  • H2 Author a room pool for which API response Exists
  • H2 Privacy Preference Center
  • H3 Your Privacy
  • H3 Strictly Necessary Cookies
  • H3 Functional Cookies
  • H3 Advertising Cookies
  • H3 Analytics Cookies
  • H4 Your Privacy
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Advertising Cookies
  • H4 Analytics Cookies
  • H3 Cookie List

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Form Accessibility
Action
9 of 67 controls have issues
REVIEW
9 of 67 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="vjs_select_651">; <select id="vjs_select_670">; <select id="vjs_select_685">; <select id="vjs_select_1454">; <select id="vjs_select_1473">; <select id="vjs_select_1488">; <select id="vjs_select_2259">; <select id="vjs_select_2278">; <select id="vjs_select_2293">
Info::
58 control(s) properly labeled
67 controls
58 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
#container_copy-staticsearchform_destinationInputinputWhere can we take you?aria-label
#container_copy-staticsearchform_hotelssearchfilters-date-frominputCheck Inaria-label
#container_copy-staticsearchform_hotelssearchfilters-date-toinputCheck Outaria-label
#container_copy-staticsearchform_hotelssearchfilters-date-flexibleinputAdd Datesaria-label
inputtextRoom Countaria-label
numAdultsPerRoomtextAdult Countaria-label
inputtextAdult Countaria-label
inputtextChildren Countaria-label
inputtextChildren Agearia-label
#container_copy-staticsearchform_noneradioLowest Regular Ratefor/id
#container_copy-staticsearchform_aaaradioAAA/CAAfor/id
#container_copy-staticsearchform_S9RradioSenior Discountfor/id
#container_copy-staticsearchform_govradioGovernment & Militaryfor/id
#container_copy-staticsearchform_corpradioCorp/Promo Codefor/id
#container_copy-staticsearchform_promoCodetextADD CORP/PROMO CODEaria-label
#container_copy-staticsearchform_XMIMIUCM_useRewardsPointscheckboxUse Points/Certificatesfor/id
#vjs_select_601selectColorfor/id
#vjs_select_606selectOpacityfor/id
#vjs_select_616selectColorfor/id
#vjs_select_621selectOpacityfor/id
#vjs_select_631selectColorfor/id
#vjs_select_636selectOpacityfor/id
#vjs_select_1404selectColorfor/id
#vjs_select_1409selectOpacityfor/id
#vjs_select_1419selectColorfor/id
#vjs_select_1424selectOpacityfor/id
#vjs_select_1434selectColorfor/id
#vjs_select_1439selectOpacityfor/id
#vjs_select_2209selectColorfor/id
#vjs_select_2214selectOpacityfor/id
#vjs_select_2224selectColorfor/id
#vjs_select_2229selectOpacityfor/id
#vjs_select_2239selectColorfor/id
#vjs_select_2244selectOpacityfor/id
#container_147165786-staticsearchform_cop_destinationInputinputWhere can we take you?aria-label
#container_147165786-staticsearchform_cop_hotelssearchfilters-date-frominputCheck Inaria-label
#container_147165786-staticsearchform_cop_hotelssearchfilters-date-toinputCheck Outaria-label
#container_147165786-staticsearchform_cop_hotelssearchfilters-date-flexibleinputAdd Datesaria-label
inputtextRoom Countaria-label
numAdultsPerRoomtextAdult Countaria-label
inputtextAdult Countaria-label
inputtextChildren Countaria-label
inputtextChildren Agearia-label
#container_147165786-staticsearchform_cop_noneradioLowest Regular Ratefor/id
#container_147165786-staticsearchform_cop_aaaradioAAA/CAAfor/id
#container_147165786-staticsearchform_cop_S9RradioSenior Discountfor/id
#container_147165786-staticsearchform_cop_govradioGovernment & Militaryfor/id
#container_147165786-staticsearchform_cop_corpradioCorp/Promo Codefor/id
#container_147165786-staticsearchform_cop_promoCodetextADD CORP/PROMO CODEaria-label
#container_147165786-staticsearchform_cop_XMIMIUCM_useRewardsPointscheckboxUse Points/Certificatesfor/id
#ot-group-id-3checkboxFunctional Cookiesfor/id
#ot-group-id-4checkboxAdvertising Cookiesfor/id
#ot-group-id-6checkboxAnalytics Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#vjs_select_2259select(none)none
#vjs_select_2278select(none)none
#vjs_select_2293select(none)none
#vjs_select_651select(none)none
#vjs_select_670select(none)none
#vjs_select_685select(none)none
#vjs_select_1454select(none)none
#vjs_select_1473select(none)none
#vjs_select_1488select(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select id="vjs_select_651">; <select id="vjs_select_670">; <select id="vjs_select_685">; <select id="vjs_select_1454">; <select id="vjs_select_1473">; <select id="vjs_select_1488">; <select id="vjs_select_2259">; <select id="vjs_select_2278">; <select id="vjs_select_2293">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+
Alt Text Quality
All 61 images OK
PASS
All 61 images OK
Info::
8 decorative image(s) correctly marked
Info::
53 image(s) with good alt text
61 images 53 good alt text 8 decorative
All images have appropriate alt text.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your Privacy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Strictly Necessary C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Functional Cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Advertising Cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Analytics Cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title The Ritz-Carlton - L…21.00:14.5:1
#000000
#FFFFFF
Pass
span The Ritz-Carlton21.00:14.5:1
#000000
#FFFFFF
Pass
span English21.00:14.5:1
#000000
#FFFFFF
Pass
a Sign in or Join21.00:14.5:1
#000000
#FFFFFF
Pass
div Hotels & Resorts21.00:14.5:1
#000000
#FFFFFF
Pass
div Hotels & Resorts21.00:14.5:1
#000000
#FFFFFF
Pass
div New Hotels21.00:14.5:1
#000000
#FFFFFF
Pass
div Meetings & Celebrati…21.00:14.5:1
#000000
#FFFFFF
Pass
div Ritz-Carlton Reserve21.00:14.5:1
#000000
#FFFFFF
Pass
div Residences21.00:14.5:1
#000000
#FFFFFF
Pass
div Yachts21.00:14.5:1
#000000
#FFFFFF
Pass
div About The Ritz-Carlt…21.00:14.5:1
#000000
#FFFFFF
Pass
div About The Ritz-Carlt…21.00:14.5:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 28 passed
PASS
95

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CITY SERENITY The Ritz-Carlton, Bangkok Elevated above the capital, refined su… div.featured-carousel-component > div.glide > div.glide__track > ul.glide__slides

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Deprecated ARIA roles were not used
●The page contains a heading, skip link, or landmark region
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○Heading elements appear in a sequentially-descending order
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback