Skip to content
https://shangri-la.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-n5obwq
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://shangri-la.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://shangri-la.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #000000
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 ModePartial Dark Mode
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 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 banner (header) 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 (missing!) NAV MAIN (missing!) CONTENTINFO footer

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA 2 pass AA only
div Sign In
1.12:1
#000000
on
#200C03
needs 4.5:1 (normal text)
16px · top of page (header area)
span Join Now
1.08:1
#000000
on
#1B0801
needs 4.5:1 (normal text)
16px · top of page (header area)
span Find Reservations
1.10:1
#000000
on
#230700
needs 4.5:1 (normal text)
16px · above the fold
em
1.23:1
#000000
on
#2F1506
needs 4.5:1 (normal text)
16px · above the fold
span English
1.98:1
#000000
on
#4C3C21
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div USD
1.38:1
#000000
on
#292614
needs 4.5:1 (normal text)
16px · above the fold
em
1.27:1
#000000
on
#281D0E
needs 4.5:1 (normal text)
16px · above the fold
em
1.77:1
#000000
on
#3C3816
needs 4.5:1 (normal text)
16px · above the fold
em
1.20:1
#000000
on
#1E1905
needs 4.5:1 (normal text)
16px · above the fold
em
3.05:1
#000000
on
#62594B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Hotels & Resorts
1.22:1
#000000
on
#221A0F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Offers
1.08:1
#000000
on
#110D08
needs 4.5:1 (normal text)
16px · mid-page
a Experiences
1.08:1
#000000
on
#100D09
needs 4.5:1 (normal text)
16px · mid-page
a Weddings & Celebrations
1.05:1
#000000
on
#0A0704
needs 4.5:1 (normal text)
16px · mid-page
a Meetings & Events
1.27:1
#000000
on
#231E1A
needs 4.5:1 (normal text)
16px · mid-page
a Family Experiences
1.22:1
#000000
on
#1E1B17
needs 4.5:1 (normal text)
16px · mid-page

3 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
h1 Join Shangri-La Circ…5.77:13.0:1
#000000
#868687
Pass
h2 Meetings & Events5.77:13.0:1
#000000
#868687
Pass
title Luxury Escape at Bes…5.64:14.5:1
#000000
#868483
Pass
em 5.64:14.5:1
#000000
#868483
Pass
div Sign In1.12:14.5:1
#000000
#200C03
Fail
span Join Now1.08:14.5:1
#000000
#1B0801
Fail
span Find Reservations1.10:14.5:1
#000000
#230700
Fail
em 1.23:14.5:1
#000000
#2F1506
Fail
span English1.98:14.5:1
#000000
#4C3C21
Fail
div USD1.38:14.5:1
#000000
#292614
Fail
em 1.27:14.5:1
#000000
#281D0E
Fail
em 1.77:14.5:1
#000000
#3C3816
Fail
em 1.20:14.5:1
#000000
#1E1905
Fail
em 3.05:14.5:1
#000000
#62594B
Fail
a Hotels & Resorts1.22:14.5:1
#000000
#221A0F
Fail
a Offers1.08:14.5:1
#000000
#110D08
Fail
a Experiences1.08:14.5:1
#000000
#100D09
Fail
a Weddings & Celebrati…1.05:14.5:1
#000000
#0A0704
Fail
a Meetings & Events1.27:14.5:1
#000000
#231E1A
Fail
a Family Experiences1.22:14.5:1
#000000
#1E1B17
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.

B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 23 passed
REVIEW
87

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.

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
Cookies Policy div#js-cookie-modal > div.sl-cookie-modal-content > div.sl-cookie-modal-desc > a

These are opportunities to improve the legibility of your content.

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
div.LegoHome_bannerWarp__jHWuj > div.Banner_bannerContainer___m0_4 > div.Banner_swiperOperation___4AHr > ul.Banner_swiperPagination__FVHhS div.LegoHome_bannerWarp__jHWuj > div.Banner_bannerContainer___m0_4 > div.Banner_swiperOperation___4AHr > ul.Banner_swiperPagination__FVHhS
Our Destinations Find a Reservation Meetings & Events Restaurant & Bars div.sectionList > div.linkList > div.linkListContainer > ul.ul
Programme Overview Join Shangri-La Circle Account Overview FAQ Contact Us div.sectionList > div.linkList > div.linkListContainer > ul.ul
About Us Our Hotel Brands Shangri-La Centre Residences Contact Us div.sectionList > div.linkList > div.linkListContainer > ul.ul
Investors Careers Global Citizenships News div.sectionList > div.linkList > div.linkListContainer > ul.ul

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○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.
A+
Heading Hierarchy
2 headings
PASS
2 headings
Info::
Single H1 present
  • H1 Join Shangri-La Circle today
  • H2 Meetings & Events
A+
Alt Text Quality
All 42 images OK
PASS
All 42 images OK
Info::
22 decorative image(s) correctly marked
Info::
20 image(s) with good alt text
42 images 20 good alt text 22 decorative
All images have appropriate alt text.
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
#rc_select_0searchDestination & Hotelaria-label
inputinputStart datearia-label
inputinputEnd datearia-label
emailtext输入框aria-label
email-codetext输入框aria-label
Necessarycheckboxnone
Functionalcheckboxnone
Performancecheckboxnone
Advertisingcheckboxnone
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback