Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #1f3a2e

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Mobile Keyboard & Autofill

Action

6/11 eligible field(s) missing autocomplete or inputmode

REVIEW

6/11 eligible field(s) missing autocomplete or inputmode

6 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email, numeric.

Got: <input type="search" id="q">, <input type="email" name="email" id="pEmail">, <input type="number" name="days" id="pDays">, <input type="number" name="adults" id="pAd">, <input type="email" name="email" id="nEmail">

Mobile-Readable Font Sizes

Action

77% of visible text renders at >= 12 CSS px (74 below threshold)

REVIEW

77% of visible text renders at >= 12 CSS px (74 below threshold)

74 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.5px ("EN"); <p> 11.8px ("Marrakech\u00a0· High\u00a0Atlas\u00a0· Agafay\u00a0desert\u00a0·..."); <span> 11.5px ("Marrakech and the High Atlas"); <span> 11.5px ("02 / 05"); <span> 11.8px ("Marrakech Atlas").

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | Marrakech Atlas ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Morocco, felt before it is seen.

1.11:1

#000000

#180F0C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Four ways into Morocco

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Recently viewed

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Where do you want to go?

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Choose your day

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why travellers feel at ease with us

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The people behind your day

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What we stand behind

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tell us your dates, we plan your days

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Read before you go

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Morocco travel guide, free

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Good to know

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Questions? Talk to us.

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Rise above the plains at dawn, then end …

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Walk where the Atlas meets the people wh…

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Marrakech, unhurried, with a guide who k…

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 A day of sea air, blue boats and grilled…

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Small groups

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Local guides

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pay on the day

1.11:1

#000000

#170F0C

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Morocco, felt before…	1.11:1	3.0:1	#000000	#180F0C	Fail
h2 Four ways into Moroc…	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 Recently viewed	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 Where do you want to…	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 Choose your day	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 Why travellers feel …	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 The people behind yo…	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 What we stand behind	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 Tell us your dates, …	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 Read before you go	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 The Morocco travel g…	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 Good to know	1.11:1	3.0:1	#000000	#170F0C	Fail
h2 Questions? Talk to u…	1.11:1	3.0:1	#000000	#170F0C	Fail
h3 Rise above the plain…	1.11:1	3.0:1	#000000	#170F0C	Fail
h3 Walk where the Atlas…	1.11:1	3.0:1	#000000	#170F0C	Fail
h3 Marrakech, unhurried…	1.11:1	3.0:1	#000000	#170F0C	Fail
h3 A day of sea air, bl…	1.11:1	3.0:1	#000000	#170F0C	Fail
h3 Small groups	1.11:1	3.0:1	#000000	#170F0C	Fail
h3 Local guides	1.11:1	3.0:1	#000000	#170F0C	Fail
h3 Pay on the day	1.11:1	3.0:1	#000000	#170F0C	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.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

Heading Hierarchy

53 headings, 1 skip(s)

PASS

53 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Morocco, felt before it is seen.
H2 Four ways into Morocco
H3 Rise above the plains at dawn, then end the day in the stone desert.
H3 Walk where the Atlas meets the people who live in it.
H3 Marrakech, unhurried, with a guide who knows every courtyard.
H3 A day of sea air, blue boats and grilled fish.
H2 Recently viewed
H2 Where do you want to go?
H2 Choose your day
H3 Agafay Desert Dinner & Show at Sunset
H3 Hot Air Balloon Flight over Marrakech with Berber Breakfast
H3 Quad Adventure in the Agafay Desert
H3 Ourika Valley, Atlas Mountains & Setti Fatma Waterfalls
H3 4x4 Tour in the Atlas Mountains with Lunch in a Berber Village
H3 Ouzoud Waterfalls Day Trip with Imi n'Ifri and Lunch
H3 Marrakech Camel Safari in the Palmeraie
H3 Buggy Adventure in the Agafay Desert
H3 Essaouira Day Trip: Atlantic Port & Old Medina
H3 Marrakech City Tour with Lunch and Optional Monument Entry
H3 Road of the Kasbahs by 4x4: Telouet & Aït Benhaddou with Lunch
H3 Marrakech Buggy Adventure in the Palmeraie
H3 Marrakech History Tour: Koutoubia, Bahia Palace & Tiskiwin
H3 Marrakech Horse Carriage Ride and Jemaa el Fna Square
H3 Marrakech Gardens Tour: Majorelle & Le Jardin Secret
H3 Traditional Moroccan Hammam & Massage in a Riad
H2 Why travellers feel at ease with us
H3 Small groups
H3 Local guides
H3 Pay on the day
H3 Free cancellation
H3 Hotel pickup
H3 Answers by email
H2 The people behind your day
H3 City guides
H3 Mountain guides
H3 Drivers
H2 What we stand behind
H3 Animal welfare
H3 Safety first
H3 Real tickets, no queues
H3 Honest advice
H2 Tell us your dates, we plan your days
H2 Read before you go
H3 10 Days in Morocco: A Realistic Itinerary Starting in Marrakech
H3 The Sahara From Marrakech: What Is Realistic, and What the Agafay Offers Instead
H3 Hidden Gems of Marrakech: Quiet Corners, Small Museums and Places Beyond the Checklist
H2 The Morocco travel guide, free
H2 Good to know
H2 Questions? Talk to us.
H4 Explore skipped
H4 Plan
H4 Contact
H3 Book this tour

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Heading Text Quality

All 53 heading(s) have substantive, well-formed text

PASS

All 53 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 30 images OK

PASS

All 30 images OK

2 decorative image(s) correctly marked

28 image(s) with good alt text

30 images 28 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 24 controls labeled

PASS

All 24 controls labeled

24 control(s) properly labeled

24 controls

24 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#q	search		none
#pName	input	Name	for/id
#pEmail	email	Email	for/id
#pFrom	date	Arriving	for/id
#pDays	number	Days in Marrakech	for/id
#pAd	number	Adults	for/id
#pCh	input	Children (ages)	for/id
interest_0	checkbox		none
interest_1	checkbox		none
interest_2	checkbox		none
interest_3	checkbox		none
interest_4	checkbox		none
interest_5	checkbox		none
interest_6	checkbox		none
interest_7	checkbox		none
#pTy	select	Style	for/id
#pMsg	textarea	Anything else?	for/id
#nEmail	email	Your email	for/id
#bDate	date	Date	for/id
#bName	text	Your name	for/id
#bEmail	email	Your email	for/id
#bHotel	text	Hotel or riad	for/id
#bType	select	Tour type	for/id
#bNote	textarea	Message (optional)	for/id

A+

Link & Button Quality

83 links, 36 buttons — all OK

PASS

83 links, 36 buttons — all OK

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.instagram.com/activities_marrakesh/

82 link(s) with descriptive text

83 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	Marrakech Atlas home	img no alt	Add alt attribute to the image
/	Marrakech Atlas home	img no alt	Add alt attribute to the image
https://www.instagram.com/activities_mar…	Instagram	new tab	Add '(opens in new tab)' to text

118 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.instagram.com/activities_marrakesh/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

24 form control(s) checked, no type mismatches

PASS

24 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

24 form control(s) checked, no input-semantic issues

PASS

24 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <input>

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Lighthouse Accessibility Audits

Score 99/100 — 1 failing, 28 passed

PASS

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EXPLORE `div.wrap > div.ft > div > h4`

These are opportunities to improve keyboard navigation in your application.

○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.

●Select elements have associated label elements.

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○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

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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.

○Uses ARIA roles only on compatible elements

○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.