Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 2 REVIEW 8 FIX

Form Accessibility

Action

16 of 32 controls have issues

FIX

16 of 32 controls have issues

11 control(s) without accessible label

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

Got: <input type="date" name="arrival_date">; <input type="date" name="departure_date">; <input type="number" name="adults">; <input type="number" name="children">; <input type="number" name="rooms">; <select name="budget">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText"> (+1 more)

5 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input name="name">; <input name="country">; <input type="email" name="email">; <input name="whatsapp">; <textarea name="requirements">

16 control(s) properly labeled

32 controls

16 labeled

5 placeholder only

11 unlabeled

Control	Type	Label	Method
select	select	Select language	aria-label
select	select	Widget de idiomas del Traductor	aria-label
hotel_category	radio		none
hotel_category	radio		none
hotel_category	radio		none
hotel_category	radio		none
hotel_category	radio		none
meal_plan	radio		none
meal_plan	radio		none
meal_plan	radio		none
interests[]	checkbox		none
interests[]	checkbox		none
interests[]	checkbox		none
interests[]	checkbox		none
interests[]	checkbox		none
interests[]	checkbox		none
email	email	(name@example.com)	placeholder only
whatsapp	input	(+94 756 661 610)	placeholder only
name	input	(Your full name)	placeholder only
country	input	(Your country)	placeholder only
requirements	textarea	(Special requests, dietary needs, accessibility requirements, dream destinations...)	placeholder only
children	number	(none)	none
rooms	number	(none)	none
budget	select	(none)	none
arrival_date	date	(none)	none
departure_date	date	(none)	none
adults	number	(none)	none
#goog-gt-votingInputSrcLang	text	(none)	none
#goog-gt-votingInputTrgLang	text	(none)	none
#goog-gt-votingInputSrcText	text	(none)	none
#goog-gt-votingInputTrgText	text	(none)	none
#goog-gt-votingInputVote	text	(none)	none

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

<input type="date" name="arrival_date">; <input type="date" name="departure_date">; <input type="number" name="adults">; <input type="number" name="children">; <input type="number" name="rooms">; <select name="budget">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText"> (+1 more)

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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Mobile Keyboard & Autofill

Action

7/7 eligible field(s) missing autocomplete or inputmode

FIX

7/7 eligible field(s) missing autocomplete or inputmode

3 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name, country-name, email.

Got: <input name="name">, <input name="country">, <input type="email" name="email">

4 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: email, numeric.

Got: <input type="email" name="email">, <input type="number" name="adults">, <input type="number" name="children">, <input type="number" name="rooms">

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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

No dark mode signals

FIX

No dark mode signals

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

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

1 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 1 <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-Readable Font Sizes

Action

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

REVIEW

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

77 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: <div> 0.0px ("Con la tecnología de"); <span> 11.0px ("Years Experience"); <span> 11.0px ("Destinations"); <span> 11.0px ("Custom Journeys"); <span> 10.0px ("Beach & Water").

Lighthouse Accessibility Audits

Action

Score 75/100 — 5 failing, 16 passed

REVIEW

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Seleccionar idioma español alemán árabe chino (simplificado) cingalés coreano d… `div.nav-shell > div.nav-actions > div.translate-widget > div#google_translate_element`

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
5 star rating `div.modern-testimonials > article.modern-review-card > div.review-topline > div.review-rating`
5 star rating `div.modern-testimonials > article.modern-review-card > div.review-topline > div.review-rating`
5 star rating `div.modern-testimonials > article.modern-review-card > div.review-topline > div.review-rating`

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
Website Designed & Developed by WhiteCoder (Pvt) Ltd `body > footer.site-footer > div.container > span.developer-credit`
WhiteCoder (Pvt) Ltd `footer.site-footer > div.container > span.developer-credit > a`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form.form-panel > div.form-row > div.field > input `form.form-panel > div.form-row > div.field > input`
form.form-panel > div.form-row > div.field > input `form.form-panel > div.form-row > div.field > input`
form.form-panel > div.form-row > div.field > input `form.form-panel > div.form-row > div.field > input`
form.form-panel > div.form-row > div.field > input `form.form-panel > div.form-row > div.field > input`
form.form-panel > div.form-row > div.field > input `form.form-panel > div.form-row > div.field > input`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select budget range Budget Friendly Comfort Premium Luxury Need Guidance `div.trip-form-block > form.form-panel > div.field > select`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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

●`[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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[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

○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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○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

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

○Identical links have the same purpose.

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

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Heading Hierarchy

32 headings

PASS

32 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Explore the full journey
H1 The Heart of Sri Lankan Hospitality
H2 Sri Lanka, a Story to Experience
H2 Authentic Ayurvedic Wellness Journeys by Nexus Ceylon Travels
H2 Warm Hospitality, Local Expertise, Reliable Service
H3 Warm Hospitality
H3 Local Expertise
H3 Reliable Service
H3 Meaningful Travel
H2 Select locations and plan your perfect route
H3 Arugambay
H2 A paradise of endless experiences
H3 Arugambay
H3 Anuradhapura
H3 Bentota
H3 Dambulla
H3 Ella
H3 Habarana
H2 Where the heart finds beautiful stories
H3 Gangaramaya Temple
H3 Colombo National Museum
H3 Waterfalls Trek
H2 Honeymoon Special Offer
H2 Protecting nature through meaningful travel
H2 Travel Moments & Guest Words
H2 Let's Plan Your Trip
H3 Prefer WhatsApp?
H3 Quick Answers
H4 Quick Links
H4 Our Services
H4 Contact
H2 (empty)

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 28 images OK

PASS

All 28 images OK

1 decorative image(s) correctly marked

27 image(s) with good alt text

28 images 27 good alt text 1 decorative

All images have appropriate alt text.

Link & Button Quality

62 links, 37 buttons — all OK

PASS

62 links, 37 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://translate.google.com; https://wa.me/94756661610?text=Hi%20Nexus%20Ceylon%20Travels%2C%20I%20want%20…; https://www.google.com/maps/search/?api=1&query=Arugambay%2C%20Sri%20Lanka; https://wa.me/94756661610?text=Hi%20Nexus%20Ceylon%20Travels%2C%20I%20want%20…; https://whitecoder.lk/; https://wa.me/94756661610?text=Hi%20Nexus%20Ceylon%20Travels%2C%20I%20need%20…

56 link(s) with descriptive text

62 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://translate.google.com	Traductor de Google	new tab	Add '(opens in new tab)' to text
https://wa.me/94756661610?text=Hi%20Nexu…	WhatsApp Us	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps/search/?api=…	Open in Google Maps	new tab	Add '(opens in new tab)' to text
https://wa.me/94756661610?text=Hi%20Nexu…	Start a Conversation	new tab	Add '(opens in new tab)' to text
https://whitecoder.lk/	WhiteCoder (Pvt) Ltd	new tab	Add '(opens in new tab)' to text
https://wa.me/94756661610?text=Hi%20Nexu…	WhatsApp	new tab	Add '(opens in new tab)' to text

93 links and buttons have descriptive text

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

https://translate.google.com; https://wa.me/94756661610?text=Hi%20Nexus%20Ceylon%20Travels%2C%20I%20want%20…; https://www.google.com/maps/search/?api=1&query=Arugambay%2C%20Sri%20Lanka; https://wa.me/94756661610?text=Hi%20Nexus%20Ceylon%20Travels%2C%20I%20want%20…; https://whitecoder.lk/; https://wa.me/94756661610?text=Hi%20Nexus%20Ceylon%20Travels%2C%20I%20need%20…

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

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

32 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

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -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.)

Iframe Accessibility

1/2 iframe(s) missing title; 0 placeholder(s)

PASS

1/2 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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+

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)

Element	Ratio	Required	FG	BG	Result
h1 The Heart of Sri Lan…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Explore the full jou…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Sri Lanka, a Story t…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Authentic Ayurvedic …	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Warm Hospitality, Lo…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Select locations and…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 A paradise of endles…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Where the heart find…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Honeymoon Special Of…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Protecting nature th…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Travel Moments & Gue…	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h2 Let's Plan Your Trip	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h3 Warm Hospitality	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h3 Local Expertise	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h3 Reliable Service	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h3 Meaningful Travel	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h3 Arugambay	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h3 Arugambay	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h3 Anuradhapura	19.59:1	3.0:1	#000000	#F8F7F3	Pass
h3 Bentota	19.59:1	3.0:1	#000000	#F8F7F3	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.