https://finnair.com
Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
65
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
136 PASS 3 REVIEW 4 FIX
F404 Error PageActionSoft 404 detectedFIX
404 Error Page
ActionSoft 404 detected
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-rpiwcv
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
No print styles
Info::
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 ✗
BLandmark Structure2 landmarksREVIEW
Landmark Structure
2 landmarks
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Warning::
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
BFavicon & Branding8 icon(s) detectedREVIEW
Favicon & Branding
8 icon(s) detected
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
BWeb ManifestValid manifestREVIEW
Web Manifest
Valid manifest
Valid manifest
Info::
Name present: Finnair.com
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Finnair.com ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Finnair.com Display Mode standalone Theme Color #ffffff Icons 2 icon(s)
A+Heading Hierarchy1 headingsPASS
Heading Hierarchy
1 headings
1 headings
Info::
Single H1 present
- H1 Hi! Please set your location and language.
A+Alt Text QualityNo imagesPASS
Alt Text Quality
No images
No images
Info::
No images on this page
No images on this page.
A+Form AccessibilityAll 1 controls labeledPASS
Form Accessibility
All 1 controls labeled
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| #select-country | text | Location * | for/id |
A+Link & Button Quality2 links, 2 buttons — all OKPASS
Link & Button Quality
2 links, 2 buttons — all OK
2 links, 2 buttons — all OK
Info::
2 link(s) with descriptive text
2 links
0 empty
0 generic text
0 new tab
0 empty buttons
All links and buttons have descriptive accessible text.
4 links and buttons have descriptive text
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
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 Hi! Please set your … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Flight bookings | se… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Flight bookings | se… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Skip to main content | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Location | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Finland (EUR €) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Australia (AUD $) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Austria (EUR €) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Belgium (EUR €) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Canada (CAD $) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span China (CNY ¥) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Czech Republic (CZK … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Denmark (DKK kr) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Estonia (EUR €) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span France (EUR €) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Germany (EUR €) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Hong Kong, China (HK… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Hungary (HUF Ft) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Iceland (ISK kr) | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span India (INR ₹) | 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.
ALighthouse Accessibility AuditsScore 90/100 — 2 failing, 25 passedPASS
Lighthouse Accessibility Audits
Score 90/100 — 2 failing, 25 passed
90
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
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.relative > div > div.text-input > fcom-text-input div.relative > div > div.text-input > fcom-text-input |
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
- div.relative > div.relative > div > button#select-language-button |
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.
○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>`
●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 are valid and not misspelled
●Buttons have an accessible name
●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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●ARIA toggle fields 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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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 `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
○Image elements have `[alt]` attributes
○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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.