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, 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 ✓Page Title Oops! - Vueling ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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 Missing

✓ 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 ✗

Landmark Structure

Action

2 landmarks

REVIEW

2 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

13 headings

REVIEW

13 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Cookie policy
H2 Cookie settings panel
H3 Your Privacy
H3 Technical cookies (strictly necessary)
H3 Preference cookies
H3 Analytics cookies
H3 Advertising cookies
H4 Your Privacy
H4 Technical cookies (strictly necessary)
H4 Preference cookies
H4 Analytics cookies
H4 Advertising cookies
H3 Back

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 3 pass AA only

title Vueling: cheap flights to major European…

2.52:1

#000000

#4E4E4E

needs 4.5:1 (normal text)

16px · top of page (header area)

span FLIGHTS

2.73:1

#000000

#535353

needs 4.5:1 (normal text)

16px · top of page (header area)

span HOTELS

2.95:1

#000000

#585858

needs 4.5:1 (normal text)

16px · top of page (header area)

span CARS

3.19:1

#000000

#5D5D5D

needs 4.5:1 (normal text)

16px · top of page (header area)

label From

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · above the fold

label Outbound

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

label Return

3.77:1

#000000

#686868

needs 4.5:1 (normal text)

16px · above the fold

label 1 Adult ,

4.06:1

#000000

#6D6D6D

needs 4.5:1 (normal text)

16px · above the fold

label 0 Children ,

4.30:1

#000000

#717171

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Cookie policy	4.96:1	3.0:1	#000000	#7B7B7B	Pass
h2 Cookie settings pane…	4.96:1	3.0:1	#000000	#7B7B7B	Pass
h3 Your Privacy	4.96:1	3.0:1	#000000	#7B7B7B	Pass
h3 Technical cookies (s…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Preference cookies	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Analytics cookies	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Advertising cookies	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Back	5.24:1	3.0:1	#000000	#7F7F7F	Pass
title Vueling: cheap fligh…	2.52:1	4.5:1	#000000	#4E4E4E	Fail
span FLIGHTS	2.73:1	4.5:1	#000000	#535353	Fail
span HOTELS	2.95:1	4.5:1	#000000	#585858	Fail
span CARS	3.19:1	4.5:1	#000000	#5D5D5D	Fail
label From	3.44:1	4.5:1	#000000	#626262	Fail
label Outbound	3.66:1	4.5:1	#000000	#666666	Fail
label Return	3.77:1	4.5:1	#000000	#686868	Fail
label 1 Adult ,	4.06:1	4.5:1	#000000	#6D6D6D	Fail
label 0 Children ,	4.30:1	4.5:1	#000000	#717171	Fail
label 0 Infants	4.62:1	4.5:1	#000000	#767676	Pass
span Search	4.96:1	4.5:1	#000000	#7B7B7B	Pass
p We use our own and t…	4.96:1	4.5:1	#000000	#7B7B7B	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 89/100 — 3 failing, 23 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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
COOKIE POLICY We use our own and third-party cookies for analytical, personali… `body.ui-mobile-viewport > div#onetrust-consent-sdk > div#onetrust-banner-sdk`

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.

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
Cookie policy `div#onetrust-group-container > div#onetrust-policy > p#onetrust-policy-text > a.ot-cookie-policy-link`

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

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

●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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

○`[accesskey]` values are unique

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

○Uses ARIA roles only on compatible elements

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

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

7 decorative image(s) correctly marked

1 image(s) with good alt text

8 images 1 good alt text 7 decorative

All images have appropriate alt text.

Form Accessibility

1 of 13 controls have issues

PASS

1 of 13 controls have issues

1 control(s) without accessible label

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

Got: <input type="text" name="vendor-search-handler" id="vendor-search-handler">

12 control(s) properly labeled

13 controls

12 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#originInput	text	From	for/id
#destinationInput	text	To	for/id
#outboundDate	text	Outbound	for/id
#returnDate	text	Return	for/id
#passengersInput	text	1 Adult , 0 Children , 0 Infants	for/id
#ot-group-id-C0003	checkbox	Preference cookies	for/id
#ot-group-id-C0002	checkbox	Analytics cookies	for/id
#ot-group-id-C0004	checkbox	Advertising cookies	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#chkbox-id	checkbox	checkbox label	for/id
#vendor-search-handler	text	(none)	none

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

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

Link & Button Quality

5 links, 13 buttons — all OK

PASS

5 links, 13 buttons — all OK

5 link(s) open in new tab without warning

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

Got: http://hotel.vueling.com/?aid=348292&label=pagesbtab-sbx-348292-click&lang=en; https://cars.vueling.com/en/?clientID=198383#/searchcars; https://www.vueling.com/en/customer-services/cookie-policy; https://www.vueling.com/en/customer-services/cookie-policy; https://www.onetrust.com/products/cookie-consent/

5 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
http://hotel.vueling.com/?aid=348292&lab…	HOTELS	new tab	Add '(opens in new tab)' to text
https://cars.vueling.com/en/?clientID=19…	CARS	new tab	Add '(opens in new tab)' to text
https://www.vueling.com/en/customer-serv…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.vueling.com/en/customer-serv…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text

13 links and buttons have descriptive text

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

http://hotel.vueling.com/?aid=348292&label=pagesbtab-sbx-348292-click&lang=en; https://cars.vueling.com/en/?clientID=198383#/searchcars; https://www.vueling.com/en/customer-services/cookie-policy; https://www.vueling.com/en/customer-services/cookie-policy; https://www.onetrust.com/products/cookie-consent/

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

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