Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

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

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

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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: Ryanair cheap flights

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name Ryanair cheap flights ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode standalone ✓

Name Ryanair cheap flights Display Mode standalone Theme Color #0d49c0 Background Color #ecb707 Icons 3 icon(s)

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: #0d49c0

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 ✗

Alt Text Quality

2 of 2 images have issues

REVIEW

2 of 2 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 images 2 missing

Issue	Count
missing	2 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

Favicon & Branding

16 icon(s) detected

REVIEW

16 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA 1 pass AA only

title Officiële Ryanair-site | Vliegtickets |…

1.60:1

#000000

#072B73

needs 4.5:1 (normal text)

16px · top of page (header area)

a Doorgaan naar hoofdinhoud

1.60:1

#000000

#072B73

needs 4.5:1 (normal text)

16px · top of page (header area)

span Plan

1.43:1

#000000

#052460

needs 4.5:1 (normal text)

16px · top of page (header area)

span Veelgestelde vragen

1.43:1

#000000

#052460

needs 4.5:1 (normal text)

16px · top of page (header area)

button Mijn boekingen

2.52:1

#000000

#3A4E74

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

button Aanmelden

1.43:1

#000000

#052460

needs 4.5:1 (normal text)

16px · above the fold

1 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)

Element	Ratio	Required	FG	BG	Result
h1 Meld je aan en bespa…	4.11:1	3.0:1	#000000	#776C64	Pass
title Officiële Ryanair-s…	1.60:1	4.5:1	#000000	#072B73	Fail
a Doorgaan naar hoofdi…	1.60:1	4.5:1	#000000	#072B73	Fail
span Plan	1.43:1	4.5:1	#000000	#052460	Fail
span Veelgestelde vragen	1.43:1	4.5:1	#000000	#052460	Fail
button Mijn boekingen	2.52:1	4.5:1	#000000	#3A4E74	Fail
button Aanmelden	1.43:1	4.5:1	#000000	#052460	Fail
button myRyanair-portal	10.94:1	4.5:1	#000000	#BBBBBB	Pass
div vluchten	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div autoverhuur	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div hotel	20.82:1	4.5:1	#000000	#FEFEFE	Pass
div Cadeaubonnen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Geverifieerd	21.00:1	3.0:1	#000000	#FFFFFF	Pass
div door Ryanair	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Retourvlucht	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Enkele reis	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Promotiecode toepass…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Van	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Naar	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Zoeken	21.00:1	4.5:1	#000000	#FFFFFF	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.

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Meld je aan en bespaar

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="email" name="undefined">

4 control(s) properly labeled

5 controls

4 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#ry-radio-button--1	radio	Retourvlucht	for/id
#ry-radio-button--0	radio	Enkele reis	for/id
#input-button__departure	text	Van	for/id
#input-button__destination	text	Naar	for/id
undefined	email	(E-mailadres)	placeholder only

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

Link & Button Quality

7 links, 18 buttons — all OK

PASS

7 links, 18 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://www.ryanair.com/nl/nl/r/help; https://www.ryanair.com/nl/nl/r/help/special-assistance; https://www.ryanair.com/nl/nl/lp/privacy-policy; https://www.ryanair.com/nl/nl/cookie-policy; /nl/nl/lp/privacybeleid

2 link(s) with descriptive text

7 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
http://www.ryanair.com/nl/nl/r/help	Veelgestelde vragen	new tab	Add '(opens in new tab)' to text
https://www.ryanair.com/nl/nl/r/help/spe…	Assistentie	new tab	Add '(opens in new tab)' to text
https://www.ryanair.com/nl/nl/lp/privacy…	Privacybeleid	new tab	Add '(opens in new tab)' to text
https://www.ryanair.com/nl/nl/cookie-pol…	cookiebeleid	new tab	Add '(opens in new tab)' to text
/nl/nl/lp/privacybeleid	privacybeleid	new tab	Add '(opens in new tab)' to text

20 links and buttons have descriptive text

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

http://www.ryanair.com/nl/nl/r/help; https://www.ryanair.com/nl/nl/r/help/special-assistance; https://www.ryanair.com/nl/nl/lp/privacy-policy; https://www.ryanair.com/nl/nl/cookie-policy; /nl/nl/lp/privacybeleid

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

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 26 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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Algemene Vervoersvoorwaarden `footer.legal-footer > div.legal-footer__row > div.legal-footer__processing-fee > a`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Algemene vervoersvoorwaarden `footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item`
Gebruiksvoorwaarden `footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item`
Privacybeleid `footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item`
Cookies `footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item`
Contact `footer.legal-footer > div.legal-footer__row > div.legal-footer__links > a.legal-footer__links-item`

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

●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

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

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

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●ARIA `tooltip` elements have accessible names

●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 have a discernible name

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

●Heading elements appear in a sequentially-descending order

●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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields 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.

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