Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://agoda.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://agoda.com/manifest.json

Manifest contains invalid JSON.

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 ✗

Heading Hierarchy

11 headings, 1 skip(s)

REVIEW

11 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H6 (missing H3)

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

1 empty heading(s)

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

H1 See the world for less
H2 (empty)
H6 Hotels skipped
H6 Homes & Apts
H6 Long stays
H6 Airport transfer
H2 Top destinations in France
H3 Paris
H3 Lyon
H3 Marseille
H3 Nice

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

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

Link & Button Quality

1 issue(s) across 15 links and 7 buttons

REVIEW

1 issue(s) across 15 links and 7 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /info/privacy.html#cookies ("here")

6 link(s) open in new tab without warning

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

Got: https://www.getyourguide.com/?partner_id=HYFZ1GI&cmp=desktop; /deals; /apartments; /clickouts/esim?source=desktop&medium=-1&campaign=header_esim_link&currency=EUR; /travel-guides; /traveltips/

8 link(s) with descriptive text

15 links

0 empty

1 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/info/privacy.html#cookies	here	generic text	Replace with descriptive text
Before: here Suggested: Privacy.Html#Cookies
https://www.getyourguide.com/?partner_id…	Things to do	new tab	Add '(opens in new tab)' to text
/deals	Coupons & Deals	new tab	Add '(opens in new tab)' to text
/apartments	Apartments	new tab	Add '(opens in new tab)' to text
/clickouts/esim?source=desktop&medium=-1…	eSIM	new tab	Add '(opens in new tab)' to text
/travel-guides	Travel Guides	new tab	Add '(opens in new tab)' to text
/traveltips/	Travel Itineraries	new tab	Add '(opens in new tab)' to text

15 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/info/privacy.html#cookies ("here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.getyourguide.com/?partner_id=HYFZ1GI&cmp=desktop; /deals; /apartments; /clickouts/esim?source=desktop&medium=-1&campaign=header_esim_link&currency=EUR; /travel-guides; /traveltips/

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

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 2 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 See the world for le…	19.91:1	3.0:1	#000000	#F7F9FC	Pass
h2 Top destinations in …	7.19:1	3.0:1	#000000	#A1958B	Pass
h3 Paris	7.19:1	3.0:1	#000000	#A1958B	Pass
h3 Lyon	7.19:1	3.0:1	#000000	#A1958B	Pass
h3 Marseille	7.19:1	3.0:1	#000000	#A1958B	Pass
h3 Nice	7.19:1	3.0:1	#000000	#A1958B	Pass
title Agoda Official Site …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Manage Cookie Prefer…	17.74:1	4.5:1	#000000	#EAECEF	Pass
div Agoda only uses cook…	4.92:1	4.5:1	#000000	#0084AF	Pass
a here	4.79:1	4.5:1	#000000	#0082AC	Pass
button Dismiss	9.07:1	4.5:1	#000000	#68B5CC	Pass
span Skip to main content	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span Hotels & Homes	19.96:1	4.5:1	#000000	#F9F9FA	Pass
span Transport	20.65:1	4.5:1	#000000	#FDFDFD	Pass
span Things to do	20.48:1	4.5:1	#000000	#FCFCFD	Pass
span Coupons & Deals	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Apartments	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span eSIM	20.48:1	4.5:1	#000000	#FCFCFD	Pass
span Travel Guides	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Travel Itineraries	20.17:1	4.5:1	#000000	#FBFAFB	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.

Lighthouse Accessibility Audits

Score 85/100 — 4 failing, 22 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.

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
here `div.ConsentBannerFunctionalOnly > div.Text > div.Text__Description > a`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.Sticky__menuTransition--8xIFx > div.ConsentBannerFunctionalOnly > div.Text > img `div.Sticky__menuTransition--8xIFx > div.ConsentBannerFunctionalOnly > div.Text > img`

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.

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1Room,2Adults,0Children `div.SearchPanelContextAware__criteria--3yJQU > div.a3445-box > div.Box-sc-kv6pi1-0 > button.Button__primary--1Y5so`

○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

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

●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

○`[accesskey]` values are unique

○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

○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

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

○Identical links have the same purpose.

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

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Alt Text Quality

1 of 8 images have issues

PASS

1 of 8 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image(s) with good alt text

8 images 7 good alt text 1 missing

Issue	Count
missing	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#textInput	text	Enter a destination or property	aria-label

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