Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 5 REVIEW 7 FIX

Landmark Structure

Action

6 landmarks

FIX

6 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Form Accessibility

Action

4 of 21 controls have issues

FIX

4 of 21 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">

2 control(s) rely on placeholder only

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

Got: <input type="text" name="search">; <input type="text" name="search">

17 control(s) properly labeled

21 controls

17 labeled

2 placeholder only

2 unlabeled

Control	Type	Label	Method
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-IAB2V2_1	checkbox	Store and/or access information on a device	for/id
#ot-group-id-V2STACK42	checkbox	Personalised advertising and content, advertising and content measurement, audience research and services development	for/id
#ot-sub-group-id-IAB2V2_2	checkbox	Use limited data to select advertising	aria-label
#ot-sub-group-id-IAB2V2_3	checkbox	Create profiles for personalised advertising	aria-label
#ot-sub-group-id-IAB2V2_4	checkbox	Use profiles to select personalised advertising	aria-label
#ot-sub-group-id-IAB2V2_7	checkbox	Measure advertising performance	aria-label
#ot-sub-group-id-IAB2V2_9	checkbox	Understand audiences through statistics or combinations of data from different sources	aria-label
#ot-sub-group-id-IAB2V2_10	checkbox	Develop and improve services	aria-label
#ot-group-id-ISF2V2_1	checkbox	Use precise geolocation data	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#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
search	text	(Search this website)	placeholder only
search	text	(Search this website)	placeholder only
input	submit	(none)	none
input	submit	(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

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

Action

4 issue(s) across 286 links and 37 buttons

FIX

4 issue(s) across 286 links and 37 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /en/publications/economics/fuel-monitor/; https://airlines.iata.org/

13 link(s) open in new tab without warning

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

Got: https://airlines.iata.org/2026/04/19/people-taking-care-people; https://airlines.iata.org/2026/04/14/ensuring-transparency-saf-environmental-…; https://airlines.iata.org/2026/04/02/passenger-demand-fundamentals-remain-robust; https://airlines.iata.org/; https://www.facebook.com/iata.org; https://www.linkedin.com/company/international-air-transport-association-iata/; https://www.youtube.com/iatatv; https://x.com/IATA; https://www.iata.org/api/rss/pressrelease; https://www.instagram.com/iata_official/ (+3 more)

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: input[type="submit"].cursor-pointer (#103 on page); input[type="submit"].search-menu-btn (#301 on page)

271 link(s) with descriptive text

286 links

2 empty

0 generic text

13 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://airlines.iata.org/2026/04/19/peo…	19 April 2026 …	new tab	Add '(opens in new tab)' to text
https://airlines.iata.org/2026/04/14/ens…	14 April 2026 …	new tab	Add '(opens in new tab)' to text
https://airlines.iata.org/2026/04/02/pas…	2 April 2026 …	new tab	Add '(opens in new tab)' to text
https://airlines.iata.org/	Go to Airlines website	new tab	Add '(opens in new tab)' to text
/en/publications/economics/fuel-monitor/	(empty)	empty	Add link text or aria-label
https://airlines.iata.org/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/iata.org	facebook-icon.svg	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/interna…	linkedin-icon.svg	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/iatatv	youtube-icon.svg	new tab	Add '(opens in new tab)' to text
https://x.com/IATA	x-icon.svg	new tab	Add '(opens in new tab)' to text
https://www.iata.org/api/rss/pressreleas…	IATA RSS Feed	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/iata_official/	instagram-icon.svg	new tab	Add '(opens in new tab)' to text
https://www.iata.org/en/privacy/cookies/	Cookie Policy, opens in a new…	new tab	Add '(opens in new tab)' to text
https://www.iata.org/en/privacy/cookies/	Cookie Policy, opens in a new …	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
<input>	(empty)	empty	Add button text or aria-label
<input>	(empty)	empty	Add button text or aria-label

306 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/en/publications/economics/fuel-monitor/; https://airlines.iata.org/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://airlines.iata.org/2026/04/19/people-taking-care-people; https://airlines.iata.org/2026/04/14/ensuring-transparency-saf-environmental-…; https://airlines.iata.org/2026/04/02/passenger-demand-fundamentals-remain-robust; https://airlines.iata.org/; https://www.facebook.com/iata.org; https://www.linkedin.com/company/international-air-transport-association-iata/; https://www.youtube.com/iatatv; https://x.com/IATA; https://www.iata.org/api/rss/pressrelease; https://www.instagram.com/iata_official/ (+3 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

input[type="submit"].cursor-pointer (#103 on page); input[type="submit"].search-menu-btn (#301 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

Display mode: standalone

PWA Install Criteria Not Installable

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

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 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: #ffffff

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Heading Hierarchy

Action

77 headings, 2 skip(s)

REVIEW

77 headings, 2 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 International Air Transport Association (IATA)
H1 Making connections duplicate H1
H3 SUSTAINABILITY skipped
H3 SAFETY
H3 ABOUT AIR TRAVEL
H3 ANNUAL GENERAL MEETING
H3 SUSTAINABILITY
H3 SAFETY
H3 ABOUT AIR TRAVEL
H3 ANNUAL GENERAL MEETING
H3 IATA to Open New Office and BSP in Uzbekistan
H3 IATA Statement on Potential Jet Fuel Shortages
H3 Slot Relief During the Iran Crisis: Why Flexibility Matters Now
H3 Air Passenger Market Analysis - February 2026
H3 Air Cargo Market Analysis - February 2026
H3 Global Outlook for Air Transport - December 2025
H3 Value of Air Transport - Country Reports
H3 CO2 Connect for Cargo
H3 AgentIS
H3 Financial Services
H3 Human Resources: Set to Shape Aviation's Future
H3 Document Control Systems: At the Heart of Operational Safety and Efficiency
H3 Network Planning: Aviation’s Biggest Influencer?
H3 Destination Marketing: Where to Focus Attention in 2026
H3 New Report: From Origin to Destination - Ensuring Dangerous Goods Safety in the Cargo Supply Chain
H3 Luis Gallego, CEO, IAG: People taking care of people
H3 Sustainability: Ensuring transparency in SAF environmental benefits
H3 Passenger: Passenger demand fundamentals remain robust
H2 Jet Fuel Price Monitor
H3 360 Member airlines
H3 520 Strategic partners
H3 100,000 IATA-accredited agents
H2 Our mission is to represent, lead, and serve the airline industry
H4 Learn more skipped
H4 Connect with us
H4 Sign up for IATA news
H4 Read magazine
H4 Follow us
H2 We care about your privacy.
H3 We and our partners process data to provide:
H2 About your privacy
H2 About your privacy
H3 Your Privacy
H3 Strictly Necessary Cookies
H3 Performance Cookies
H3 Functional Cookies
H3 Targeting Cookies
H3 Store and/or access information on a device 4 partners can use this purpose
H3 Personalised advertising and content, advertising and content measurement, audience research and services development 4 partners can use this purpose
H3 Use precise geolocation data 2 partners can use this special feature
H3 Ensure security, prevent and detect fraud, and fix errors 4 partners can use this special purpose
H3 Deliver and present advertising and content 4 partners can use this special purpose
H3 Save and communicate privacy choices 3 partners can use this special purpose
H3 Match and combine data from other data sources 3 partners can use this feature
H3 Link different devices 2 partners can use this feature
H3 Identify devices based on information transmitted automatically 2 partners can use this feature
H4 Your Privacy
H4 Strictly Necessary Cookies
H4 Performance Cookies
H4 Functional Cookies
H4 Targeting Cookies
H4 Store and/or access information on a device 4 partners can use this purpose
H4 Personalised advertising and content, advertising and content measurement, audience research and services development 4 partners can use this purpose
H5 Use limited data to select advertising 4 partners can use this purpose
H5 Create profiles for personalised advertising 4 partners can use this purpose
H5 Use profiles to select personalised advertising 4 partners can use this purpose
H5 Measure advertising performance 4 partners can use this purpose
H5 Understand audiences through statistics or combinations of data from different sources 3 partners can use this purpose
H5 Develop and improve services 3 partners can use this purpose
H4 Use precise geolocation data 2 partners can use this special feature
H4 Ensure security, prevent and detect fraud, and fix errors 4 partners can use this special purpose
H4 Deliver and present advertising and content 4 partners can use this special purpose
H4 Save and communicate privacy choices 3 partners can use this special purpose
H4 Match and combine data from other data sources 3 partners can use this feature
H4 Link different devices 2 partners can use this feature
H4 Identify devices based on information transmitted automatically 2 partners can use this feature
H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Alt Text Quality

19 of 45 images have issues

REVIEW

19 of 45 images have issues

16 image(s) with filename as alt text

3 image(s) with generic alt text

3 decorative image(s) correctly marked

23 image(s) with good alt text

45 images 23 good alt text 3 decorative 19 generic

Issue	Count
filename	16 image(s)
generic	3 image(s)

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title IATA - 404 page ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 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

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 25 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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn more `div.block > div.rich-text > h4 > strong`
Connect with us `div.block > div.rich-text > h4 > strong`
Sign up for IATA news `div.col-12 > div.rich-text > h4 > strong`
Read magazine `div.block > div.rich-text > h4 > strong`
Follow us `div.block > div.rich-text > h4 > strong`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SUSTAINABILITY `div.block > a.stat-block > div.stat-block-head > h3.stat-block-heading`
Learn more `div.row > div.block > div.rich-text > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link `div.slide-menu__slider > ul.no-bullet > li.mobile-menu-item > a.mobile-menu-item-link`
div.block > div.rich-text > p > a `div.block > div.rich-text > p > a`
div.block > div.rich-text > p > a `div.block > div.rich-text > p > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Airline members `div.block > div.rich-text > p > a`
IATA by region `div.block > div.rich-text > p > a`
Solutions `div.block > div.rich-text > p > a`
Newsletters `div.block > div.rich-text > p > a`
Travel agent accreditation `div.block > div.rich-text > p > a`
Cargo agency program `div.block > div.rich-text > p > a`
Strategic partnerships `div.block > div.rich-text > p > a`
Our commitment `div > ul.footer-legal-container > li.block > a`
Accessibility `div > ul.footer-legal-container > li.block > a`
Anti-slavery statement `div > ul.footer-legal-container > li.block > a`
Privacy `div > ul.footer-legal-container > li.block > a`
Cookie Preferences `div > ul.footer-legal-container > li.block > a#ot-sdk-btn`

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

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

●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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

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

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

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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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 International Air Tr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Making connections	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Jet Fuel Price Monit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our mission is to re…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We care about your p…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 About your privacy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 About your privacy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 SUSTAINABILITY	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 SAFETY	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ABOUT AIR TRAVEL	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ANNUAL GENERAL MEETI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 SUSTAINABILITY	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 SAFETY	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ABOUT AIR TRAVEL	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ANNUAL GENERAL MEETI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 IATA to Open New Off…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 IATA Statement on Po…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Slot Relief During t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Air Passenger Market…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Air Cargo Market Ana…	21.00:1	3.0: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.

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