Skip to content
https://www.emirates.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
Heading Hierarchy
Action
73 headings, 3 skip(s)
FIX
73 headings, 3 skip(s)
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Search
  • H1 Check our current Flight Schedules
  • H1 Search flights duplicate H1
  • H3 Current location skipped
  • H3 All locations
  • H3 All locations
  • H3 Passengers
  • H2 (empty)
  • H2 (empty)
  • H3 Current location
  • H3 All locations
  • H3 All locations
  • H3 Start typing...
  • H3 Room 1
  • H4 Age of children at check-in
  • H3 Room 2
  • H4 Age of children at check-in
  • H3 Room 3
  • H4 Age of children at check-in
  • H3 Room 4
  • H4 Age of children at check-in
  • H3 Room 5
  • H4 Age of children at check-in
  • H3 Room 6
  • H4 Age of children at check-in
  • H3 Room 7
  • H4 Age of children at check-in
  • H3 Room 8
  • H4 Age of children at check-in
  • H3 Room 9
  • H4 Age of children at check-in
  • H1 Manage booking/Check in duplicate H1
  • H1 What's on your flight duplicate H1
  • H3 Current location skipped
  • H3 All locations
  • H3 All locations
  • H1 Flight status duplicate H1
  • H3 Current location skipped
  • H3 All locations
  • H3 All locations
  • H2 Featured destinations from
  • H3 All locations
  • H2 (empty)
  • H3 Athens
  • H3 Athens
  • H3 Athens
  • H3 Milan
  • H3 Milan
  • H3 Milan
  • H3 Bogotá
  • H3 Bogotá
  • H3 Bogotá
  • H2 Enhance your benefits with Skywards+
  • H2 Make it an incredible journey
  • H3 Create your Dubai Stopover Experience
  • H3 First Class
  • H3 Business Class
  • H3 Premium Economy
  • H3 Economy Class
  • H3 Create your Dubai Stopover Experience
  • H3 First Class
  • H3 Business Class
  • H3 Premium Economy
  • H3 Economy Class
  • H2 About us
  • H2 About Us About Us
  • H2 Help Help
  • H2 Book Book
  • H2 Manage Manage
  • H2 Before you fly Before you fly
  • H2 Where we fly Where we fly
  • H2 Experience Experience
  • H2 Loyalty Loyalty

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 ▾

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 ▾

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

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

D
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::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Book Flights | Find Hotels and Car Rental | Emirates ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
No dark mode signals
FIX
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.

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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
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.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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
BANNER (missing!) NAV MAIN CONTENTINFO footer

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
Form Accessibility
Action
83 of 162 controls have issues
REVIEW
83 of 162 controls have issues
Critical::
83 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <input type="checkbox">; <input type="checkbox">; <input>; <input>; <input>; <input>; <input>; <select> (+73 more)
Info::
79 control(s) properly labeled
162 controls
79 labeled
0 placeholder only
83 unlabeled
ControlTypeLabelMethod
#js-search-box-inputinputSearchfor/id
#search-flight-radio-flightradioFlightfor/id
#search-flight-radio-holidayradioVacations packagefor/id
#field-44cca8d5-0b52-4d4c-b6b6-1fe977e129e2componentDeparture Airportfor/id
#field-7244537a-797e-45c5-a342-7f16cbab81b2componentArrival Airportfor/id
#search-flight-date-picker--departtextDepartingfor/id
inputcheckboxnone
inputcheckboxnone
#field-tcm:154-73543componentPassengersaria-label
#field-search-flight-classcomponentClassfor/id
#field-bfd7368a-b66d-4e21-b4dd-0d19af7c3c43componentLeaving fromfor/id
#field-60959b18-c77f-4c98-9985-71e6e28f5ba9componentGoing tofor/id
#search-holiday-date-picker--departtextCheck-infor/id
#field-tcm:154-73543componentRoomsaria-label
#field-holiday-children-age-1-1textChild 1for/id
#field-holiday-children-age-1-2textChild 2for/id
#field-holiday-children-age-1-3textChild 3for/id
#field-holiday-children-age-1-4textChild 4for/id
#field-holiday-children-age-1-5textChild 5for/id
#field-holiday-children-age-2-1textChild 1for/id
#field-holiday-children-age-2-2textChild 2for/id
#field-holiday-children-age-2-3textChild 3for/id
#field-holiday-children-age-2-4textChild 4for/id
#field-holiday-children-age-2-5textChild 5for/id
#field-holiday-children-age-3-1textChild 1for/id
#field-holiday-children-age-3-2textChild 2for/id
#field-holiday-children-age-3-3textChild 3for/id
#field-holiday-children-age-3-4textChild 4for/id
#field-holiday-children-age-3-5textChild 5for/id
#field-holiday-children-age-4-1textChild 1for/id
#field-holiday-children-age-4-2textChild 2for/id
#field-holiday-children-age-4-3textChild 3for/id
#field-holiday-children-age-4-4textChild 4for/id
#field-holiday-children-age-4-5textChild 5for/id
#field-holiday-children-age-5-1textChild 1for/id
#field-holiday-children-age-5-2textChild 2for/id
#field-holiday-children-age-5-3textChild 3for/id
#field-holiday-children-age-5-4textChild 4for/id
#field-holiday-children-age-5-5textChild 5for/id
#field-holiday-children-age-6-1textChild 1for/id
#field-holiday-children-age-6-2textChild 2for/id
#field-holiday-children-age-6-3textChild 3for/id
#field-holiday-children-age-6-4textChild 4for/id
#field-holiday-children-age-6-5textChild 5for/id
#field-holiday-children-age-7-1textChild 1for/id
#field-holiday-children-age-7-2textChild 2for/id
#field-holiday-children-age-7-3textChild 3for/id
#field-holiday-children-age-7-4textChild 4for/id
#field-holiday-children-age-7-5textChild 5for/id
#field-holiday-children-age-8-1textChild 1for/id
#field-holiday-children-age-8-2textChild 2for/id
#field-holiday-children-age-8-3textChild 3for/id
#field-holiday-children-age-8-4textChild 4for/id
#field-holiday-children-age-8-5textChild 5for/id
#field-holiday-children-age-9-1textChild 1for/id
#field-holiday-children-age-9-2textChild 2for/id
#field-holiday-children-age-9-3textChild 3for/id
#field-holiday-children-age-9-4textChild 4for/id
#field-holiday-children-age-9-5textChild 5for/id
#field-search-holiday-classcomponentClassfor/id
#whats-on-route-radioradioRoutefor/id
#whats-on-number-radioradioFlight Numberfor/id
#field-51e522a0-d838-49ce-a012-9e4332506ea1componentDeparture Airportfor/id
#field-1c07c888-01b3-48cb-a222-8ad894cb40e7componentArrival Airportfor/id
#womf-date-picker--departtextDepartingfor/id
#field-womf__flight-number-statusnumberFlight Numberfor/id
#womf-date-picker-flight--departtextDepartingfor/id
#flight-status-route-radioradioRoutefor/id
#flight-status-number-radioradioFlight Numberfor/id
#flight-status-type-radio-departureradioDeparture dayfor/id
#flight-status-type-radio-arrivalradioArrival dayfor/id
#field-73084a58-d678-4173-b381-680d4bbbc86acomponentDeparture Airportfor/id
#field-4c1c6abe-1303-4ad3-b684-9ddb28bd19e9componentArrival Airportfor/id
#flight-status-type-radio-route-departureradioDeparture dayfor/id
#flight-status-type-radio-route-arrivalradioArrival dayfor/id
#field-tcm:154-13432componentDatefor/id
#field-check-flight__flight-number-statusnumberFlight Numberfor/id
#field-86d9bf87-99e1-4e8e-acb2-0af518ce6734componentDatefor/id
#field-homepage-subscribe-emailemailEmail addressfor/id
selectselect(none)none
inputcheckbox(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
inputcheckbox(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none
inputinput(none)none
selectselect(none)none
inputinput(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none

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

<select>; <select>; <input type="checkbox">; <input type="checkbox">; <input>; <input>; <input>; <input>; <input>; <select> (+73 more)

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

C
Favicon & Branding
Action
11 icon(s) detected
REVIEW
11 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 31 passed
REVIEW
89

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
New York John F. Kennedy div.featured-fares__destination__locations > div.js-dropdown > div > a.cta

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Call your local Emirates Contact Centre for tickets booked directly with Emirat… div.modal-backdrop > div.disruption-modal > div#modal-content > ul

These are opportunities to improve the experience of reading tabular or list data using 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
About us div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Careers Opens an external link in a new tab div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Media Center Opens an external link in a new tab div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Our planet div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Our people div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Our communities div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Help and Contact div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Travel Updates div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Special Assistance div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link
Frequently asked questions div.footer__section > ol.footer__list > li.footer__list-link > a.footer__list-link

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>`
●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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
●ARIA IDs are unique
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●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 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
○`<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
○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>`.
○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.
A+
Alt Text Quality
All 33 images OK
PASS
All 33 images OK
Info::
27 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
33 images 6 good alt text 27 decorative
All images have appropriate alt text.
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)
ElementRatioRequiredFGBGResult
h2 Featured destination…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Enhance your benefit…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Make it an incredibl…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 About us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Search21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Current location21.00:13.0:1
#000000
#FFFFFF
Pass
h3 All locations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 All locations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Passengers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Current location21.00:13.0:1
#000000
#FFFFFF
Pass
h3 All locations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 All locations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Start typing...21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Room 121.00:13.0:1
#000000
#FFFFFF
Pass
h3 Room 221.00:13.0:1
#000000
#FFFFFF
Pass
h3 Room 321.00:13.0:1
#000000
#FFFFFF
Pass
h3 Room 421.00:13.0:1
#000000
#FFFFFF
Pass
h3 Room 521.00:13.0:1
#000000
#FFFFFF
Pass
h3 Room 621.00:13.0:1
#000000
#FFFFFF
Pass
h3 Room 721.00:13.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.

Send Feedback