-
a) Non-compliance with accessibility requirements
-
Images, icons and non-text content
Some icons, images and graphic controls may lack an appropriate accessible alternative or have labels that do not allow their purpose to be correctly determined using TalkBack.
[Requirement 11.1.1.1 — Non-text content, UNE-EN 301 549:2022]
-
Multimedia content
Some audiovisual content may not have all the alternatives necessary for its information to be perceived by people with hearing or visual impairments.
[Requirement 11.1.2.2 — Captions (prerecorded); requirement 11.1.2.3 — Audio description or alternative multimedia; requirement 11.1.2.5 — Audio description (prerecorded), UNE-EN 301 549:2022]
-
Structure, relationships and semantic labelling
On certain screens, there may be buttons, fields, controls and other components whose structure, relationship or purpose is not correctly communicated using TalkBack. In some cases, certain buttons may be announced only as “button”, without identifying their function.
[Requirement 11.1.3.1 — Information and relationships, UNE-EN 301 549:2022]
-
Reading order
In certain processes, the order in which TalkBack presents content may not match the logical sequence needed to interpret the information correctly. This situation may affect the selection of dates, routes, flight purchases and other operations.
[Requirement 11.1.3.2 — Meaningful sequence, UNE-EN 301 549:2022]
-
Use of sensory characteristics and color
In some components, colors, shapes or positions are used to communicate selection, status or other information without always providing an equivalent alternative.
[Requirement 11.1.3.3 — Sensory characteristics; requirement 11.1.4.1 — Use of color, UNE-EN 301 549:2022]
-
Screen orientation
Certain content and functionality may not adapt correctly to the device's horizontal orientation.
[Requirement 11.1.3.4 — Orientation, UNE-EN 301 549:2022]
-
Form fields
Some forms may present difficulties in adequately identifying the purpose of certain fields or correctly associating labels and instructions with the corresponding controls.
[Requirement 11.1.3.5 — Identification of input purpose; requirement 11.3.3.2 — Labels or instructions, UNE-EN 301 549:2022]
-
Text and component contrast
On certain screens, there may be text, controls, separators, icons or other components with insufficient contrast against the background or adjacent elements.
[Requirement 11.1.4.3 — Minimum contrast; requirement 11.1.4.11 — Non-text contrast, UNE-EN 301 549:2022]
-
Content enlargement and adaptation
Some elements may not adapt correctly to text size preferences or certain device display settings.
[Requirement 11.1.4.4 — Text resizing; requirement 11.1.4.10 — Reflow, UNE-EN 301 549:2022]
-
Interaction using alternative technologies
Certain functionality may be difficult to use with TalkBack, voice control or other accessible interaction mechanisms available on Android. These barriers may prevent some processes from being completed independently.
[Requirement 11.2.1.1 — Keyboard, UNE-EN 301 549:2022]
-
Focus order and management
In certain interactions, TalkBack focus may not follow the sequence necessary to understand and operate the content correctly.
[Requirement 11.2.4.3 — Focus order, UNE-EN 301 549:2022]
-
Purpose and labelling of controls
Some controls may lack a sufficiently descriptive accessible name or may not correctly communicate their purpose and state.
[Requirement 11.2.4.4 — Link purpose in context; requirement 11.2.4.6 — Headings and labels; requirement 11.2.5.3 — Label in name, UNE-EN 301 549:2022]
-
Abbreviations and content comprehension
In certain processes, abbreviations are used that may be difficult to interpret using TalkBack or whose announcement does not match the expected visual meaning. These situations may affect the understanding of information relating to cities, bookings, seats or other travel data.
[Requirement 11.1.3.1 — Information and relationships; requirement 11.2.4.6 — Headings and labels, UNE-EN 301 549:2022]
-
Error identification and correction
In certain forms and processes, it may be difficult to identify which field contains an error, understand its cause or know how to correct it.
[Requirement 11.3.3.1 — Error identification; requirement 11.3.3.2 — Labels or instructions; requirement 11.3.3.3 — Error suggestions, UNE-EN 301 549:2022]
-
Name, role, value and state of components
Some interactive elements may not correctly communicate their name, role, state or value through TalkBack.
[Requirement 11.4.1.2 — Name, role, value, UNE-EN 301 549:2022]
-
Status messages and dynamic changes
Certain notifications, errors, content changes or interaction results may not be correctly announced using TalkBack.
[Requirement 11.4.1.3 — Status messages, UNE-EN 301 549:2022]
-
Size of certain interaction areas
Some controls may have a reduced touch interaction area, making them difficult to use for people with limited mobility or precision.
-
[WCAG 2.2, criterion 2.5.8 — Minimum target size]
-
Seat selection and seat map
During the seat selection process, there may be difficulties related to seat labelling, reading order, selection states and the transmission through TalkBack of information expressed visually through position, color or shape.
-
[Applicable requirements 11.1.1.1 — Non-text content; 11.1.3.1 — Information and relationships; 11.1.3.2 — Meaningful sequence; 11.1.4.1 — Use of color; 11.4.1.2 — Name, role, value, UNE-EN 301 549:2022]
-
Documents generated or provided by the application
Some documents associated with certain processes may not have all the structural elements necessary for their interpretation using assistive technologies.
-
[Applicable requirements of Chapter 10 — Non-web documents, UNE-EN 301 549:2022]
-
b) Disproportionate burden
The disproportionate burden exception has not been invoked in preparing this statement to justify the identified non-compliances.
-
c) Content outside the scope of accessibility requirements
Only the exceptions expressly provided for in the applicable regulations fall outside the scope, including certain prerecorded multimedia content and office documents published before 28 June 2025, third-party content that is not funded, developed or controlled by Iberia, and content considered archival, provided that the legally established conditions are met.
These possible exclusions do not prevent Iberia from making accessibility improvements to such content.
-
d) Alternatives while barriers are being corrected
While corrective measures are being implemented, users who encounter difficulties completing an operation in the application can use www.iberia.com and/or the alternative customer service and management channels.
