Skip to content
https://mandarinoriental.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
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 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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.
B
Heading Hierarchy
16 headings
REVIEW
16 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H4 One More Summer Night
  • H4 Bangkok
  • H2 Stay
  • H3 Make Your Experience Exceptional.
  • H2 Dine
  • H2 Wellness
  • H2 More at Mandarin Oriental
  • H2 Help us improve your digital experience
  • H2 Privacy Preference Centre
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H4 Social Media 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
Favicon & Branding
Action
19 icon(s) detected
REVIEW
19 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
title Luxury 5 Star Hotels & Resorts Worldwide…
4.18:1
#000000
on
#8E6919
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to Navigation
4.18:1
#000000
on
#8E6919
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to Content
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to Footer
2.53:1
#000000
on
#475051
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div Stay a little longer this summer with a …
1.16:1
#000000
on
#1A1514
needs 4.5:1 (normal text)
16px · above the fold
a Book Now
1.15:1
#000000
on
#171513
needs 4.5:1 (normal text)
16px · above the fold
span Global Home
1.15:1
#000000
on
#171513
needs 4.5:1 (normal text)
16px · above the fold
span Our Hotels & Resorts
1.15:1
#000000
on
#171513
needs 4.5:1 (normal text)
16px · above the fold
span Sign In / Join Now
1.18:1
#000000
on
#191716
needs 4.5:1 (normal text)
16px · above the fold
span Languages
1.22:1
#000000
on
#1E1A1B
needs 4.5:1 (normal text)
16px · above the fold
a Stay
4.17:1
#000000
on
#68716C
needs 4.5:1 (normal text)
16px · above the fold
a Dine
3.81:1
#000000
on
#5F6C63
needs 4.5:1 (normal text)
16px · above the fold
a Wellness
3.42:1
#000000
on
#5A645D
needs 4.5:1 (normal text)
16px · above the fold
a Explore
3.11:1
#000000
on
#575D56
needs 4.5:1 (normal text)
16px · mid-page
a Celebrate
2.78:1
#000000
on
#4F564F
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Help us improve your…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Privacy Preference C…19.26:13.0:1
#000000
#F5F5F5
Pass
h3 Make Your Experience…19.26:13.0:1
#000000
#F5F5F5
Pass
h3 Manage Consent Prefe…19.26:13.0:1
#000000
#F5F5F5
Pass
h3 Cookie List19.26:13.0:1
#000000
#F5F5F5
Pass
title Luxury 5 Star Hotels…4.18:14.5:1
#000000
#8E6919
Fail
a Skip to Navigation4.18:14.5:1
#000000
#8E6919
Fail
a Skip to Content1.00:14.5:1
#000000
#000000
Fail
a Skip to Footer2.53:14.5:1
#000000
#475051
Fail
div Stay a little longer…1.16:14.5:1
#000000
#1A1514
Fail
a Book Now1.15:14.5:1
#000000
#171513
Fail
span Global Home1.15:14.5:1
#000000
#171513
Fail
span Our Hotels & Resorts1.15:14.5:1
#000000
#171513
Fail
span Sign In / Join Now1.18:14.5:1
#000000
#191716
Fail
span Languages1.22:14.5:1
#000000
#1E1A1B
Fail
a Stay4.17:14.5:1
#000000
#68716C
Fail
a Dine3.81:14.5:1
#000000
#5F6C63
Fail
a Wellness3.42:14.5:1
#000000
#5A645D
Fail
a Explore3.11:14.5:1
#000000
#575D56
Fail
a Celebrate2.78:14.5:1
#000000
#4F564F
Fail

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
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+
Alt Text Quality
1 of 103 images have issues
PASS
1 of 103 images have issues
Warning::
1 image(s) with generic alt text
Info::
2 decorative image(s) correctly marked
Info::
100 image(s) with good alt text
103 images 100 good alt text 2 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Accessibility
All 9 controls labeled
PASS
All 9 controls labeled
Info::
9 control(s) properly labeled
9 controls
9 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0005checkboxSocial Media Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 31 passed
PASS
94

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close header#header > div#alert-ff42a17d-4693-44a5-bbfc-815a95eb7df9 > div.alert-wrapper > span.alert-icon

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CORPORATE div.footer-middle-wrapper > div.quick-link-wrapper > div.quick-links > div.quick-links-title
EXPLORE div.footer-middle-wrapper > div.quick-link-wrapper > div.quick-links > div.quick-links-title
SUPPORT div.footer-middle-wrapper > div.quick-link-wrapper > div.quick-links > div.quick-links-title
CONNECT div.footer-middle-wrapper > div.quick-link-wrapper > div.quick-links > div.quick-links-title
2026 © Mandarin Oriental Hotel Group Limited div.footer-middle > div.footer-bottom > div.utility-nav > div.utility-nav-title

These are opportunities to improve the legibility of your content.

○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
●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
●`[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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○The page contains a heading, skip link, or landmark region
○`<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
○`<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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○`[lang]` attributes have a valid value
○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.
○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