Skip to content
https://iberia.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 403 Page Title Lo sentimos:La navegación se ha interrumpido debido a un error. Custom Styling Navigation Homepage Link Search Form
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #d7192d
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 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.

D
Print Stylesheet
Action
No print styles
FIX
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
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Warning::
No <nav> landmark found
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
BANNER header MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
title Sorry!The connection was interrupted due…
1.69:1
#000000
on
#6B0C16
needs 4.5:1 (normal text)
16px · top of page (header area)
a ___
1.56:1
#000000
on
#48242A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
akaerrorcode Error code:
1.67:1
#000000
on
#2F3437
needs 4.5:1 (normal text)
16px · top of page (header area)
span Sorry!
1.75:1
#000000
on
#333739
needs 4.5:1 (normal text)
16px · top of page (header area)
div The connection was interrupted due to an…
1.88:1
#000000
on
#3B3B3C
needs 4.5:1 (normal text)
16px · above the fold
div Reference id: 18.4c251102.1776294317.465…
1.86:1
#000000
on
#393B3C
needs 4.5:1 (normal text)
16px · above the fold
a Back to Iberia.com
1.87:1
#000000
on
#3A3B3B
needs 4.5:1 (normal text)
16px · above the fold
span Cerrar
1.88:1
#000000
on
#3B3B3C
needs 4.5:1 (normal text)
16px · above the fold
p © Iberia 2024
1.86:1
#000000
on
#383B3B
needs 4.5:1 (normal text)
16px · above the fold
p Usamos cookies analíticas, de personali…
1.86:1
#000000
on
#393B3C
needs 4.5:1 (normal text)
16px · above the fold
a Política de Cookies de Iberia.
1.86:1
#000000
on
#393B3C
needs 4.5:1 (normal text)
16px · above the fold
button Configuración de cookies
1.86:1
#000000
on
#383B3B
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)
ElementRatioRequiredFGBGResult
h2 Centro de preferenci…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Su privacidad21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookies técnicas (e…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookies de análisis…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookies de publicida…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookies dirigidas21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookies de preferenc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Back16.21:13.0:1
#000000
#E2E2E2
Pass
title Sorry!The connection…1.69:14.5:1
#000000
#6B0C16
Fail
a ___1.56:14.5:1
#000000
#48242A
Fail
akaerrorcode Error code:1.67:14.5:1
#000000
#2F3437
Fail
span Sorry!1.75:14.5:1
#000000
#333739
Fail
div The connection was i…1.88:14.5:1
#000000
#3B3B3C
Fail
div Reference id: 18.4c2…1.86:14.5:1
#000000
#393B3C
Fail
a Back to Iberia.com1.87:14.5:1
#000000
#3A3B3B
Fail
span Cerrar1.88:14.5:1
#000000
#3B3B3C
Fail
p © Iberia 20241.86:14.5:1
#000000
#383B3B
Fail
p Usamos cookies anal…1.86:14.5:1
#000000
#393B3C
Fail
a Política de Cookies…1.86:14.5:1
#000000
#393B3C
Fail
button Configuración de co…1.86:14.5:1
#000000
#383B3B
Fail

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
20 headings
PASS
20 headings
Info::
Single H1 present
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Sorry!
  • H2 The connection was interrupted due to an error, but we can take you to the homepage if you want to carry on browsing.
  • H2 Reference id: 18.4c251102.1776294317.465848a
  • H2 (empty)
  • H2 Centro de preferencia de la privacidad
  • H3 Su privacidad
  • H3 Cookies técnicas (estrictamente necesarias)
  • H3 Cookies de análisis o medición
  • H3 Cookies de publicidad comportamental
  • H3 Cookies dirigidas
  • H3 Cookies de preferencias o personalización
  • H4 Su privacidad
  • H4 Cookies técnicas (estrictamente necesarias)
  • H4 Cookies de análisis o medición
  • H4 Cookies de publicidad comportamental
  • H4 Cookies dirigidas
  • H4 Cookies de preferencias o personalización
  • H3 Back
  • H3 (empty)
  • H4 (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
Alt Text Quality
2 of 8 images have issues
PASS
2 of 8 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
2 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
8 images 4 good alt text 2 decorative 1 generic 1 missing
IssueCount
missing1 image(s)
generic1 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
1 of 9 controls have issues
PASS
1 of 9 controls have issues
Critical::
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">
Info::
8 control(s) properly labeled
9 controls
8 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0002checkboxCookies de análisis o mediciónfor/id
#ot-group-id-C0005checkboxCookies de publicidad comportamentalfor/id
#ot-group-id-C0004checkboxCookies dirigidasfor/id
#ot-group-id-C0003checkboxCookies de preferencias o personalizaciónfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#vendor-search-handlertext(none)none

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

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

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

A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 31 passed
PASS
96

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
VUELO ORIGEN Click para plegar ciudades Destino Click para plegar ciudades Inte… div#m-tab-searcher-1 > div.ibe-accordion > div > div#m-tab_01

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.

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
Política de Cookies de Iberia. 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
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
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
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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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
ARIA IDs are unique
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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 `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
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback