Skip to content
https://westjet.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
PNG Icons Missing
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://westjet.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://westjet.com/manifest.json

Manifest contains invalid JSON.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
13 landmarks
REVIEW
13 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Warning::
1 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE CONTENTINFO footer

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Oops! Page not found. | WestJet official site Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h1 Book a flight
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Canadian connections
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 True North
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Prepare for travel
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get ready for take off
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About WestJet
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Other Services
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Guest Support
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Legal, Restrictions and Terms and Condit…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Add bags to your trip
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Advance seat selection
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Travel help & support
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Add bags to your trip
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Advance seat selection
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Travel help & support
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Add bags to your trip
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Advance seat selection
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Travel help & support
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Check-in within 24 hours
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Book a flight1.66:13.0:1
#000000
#333333
Fail
h2 Sign in21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Canadian connections1.66:13.0:1
#000000
#333333
Fail
h2 True North1.66:13.0:1
#000000
#333333
Fail
h2 Prepare for travel1.66:13.0:1
#000000
#333333
Fail
h2 Get ready for take o…1.66:13.0:1
#000000
#333333
Fail
h2 About WestJet1.66:13.0:1
#000000
#333333
Fail
h2 Other Services1.66:13.0:1
#000000
#333333
Fail
h2 Guest Support1.66:13.0:1
#000000
#333333
Fail
h2 Legal, Restrictions …1.66:13.0:1
#000000
#333333
Fail
h3 Add bags to your tri…1.66:13.0:1
#000000
#333333
Fail
h3 Advance seat selecti…1.66:13.0:1
#000000
#333333
Fail
h3 Travel help & suppor…1.66:13.0:1
#000000
#333333
Fail
h3 Add bags to your tri…1.66:13.0:1
#000000
#333333
Fail
h3 Advance seat selecti…1.66:13.0:1
#000000
#333333
Fail
h3 Travel help & suppor…1.66:13.0:1
#000000
#333333
Fail
h3 Add bags to your tri…1.66:13.0:1
#000000
#333333
Fail
h3 Advance seat selecti…1.66:13.0:1
#000000
#333333
Fail
h3 Travel help & suppor…1.66:13.0:1
#000000
#333333
Fail
h3 Check-in within 24 h…1.66:13.0:1
#000000
#333333
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
30 headings
PASS
30 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Sign in
  • H1 Book a flight
  • H1 Canada starts with WestJet duplicate H1
  • H2 Canadian connections
  • H2 True North
  • H2 Prepare for travel
  • H3 Add bags to your trip
  • H3 Advance seat selection
  • H3 Travel help & support
  • H3 Add bags to your trip
  • H3 Advance seat selection
  • H3 Travel help & support
  • H3 Add bags to your trip
  • H3 Advance seat selection
  • H3 Travel help & support
  • H2 Get ready for take off
  • H3 Check-in within 24 hours
  • H3 Flight status
  • H3 Manage your trip
  • H3 Check-in within 24 hours
  • H3 Flight status
  • H3 Manage your trip
  • H3 Check-in within 24 hours
  • H3 Flight status
  • H3 Manage your trip
  • H2 About WestJet
  • H2 Other Services
  • H2 Guest Support
  • H3 Legal
  • H2 Legal, Restrictions and Terms and Conditions

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

A+
Alt Text Quality
All 7 images OK
PASS
All 7 images OK
Info::
2 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
7 images 5 good alt text 2 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 11 controls have issues
PASS
1 of 11 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
10 control(s) properly labeled
11 controls
10 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#westjetId-wj-input-ex4ydumt6x6textEmail or WestJet Rewards IDfor/id
#password-wj-input-7cbd1sxrt3hpasswordPasswordfor/id
#text-input-26e58c6f-22b7-4034-a145-e85ec28d7988textTrip typefor/id
#text-input-13d6b989-dfe8-4573-856a-6a5b7584b212textFromfor/id
#text-input-2cb2c4c7-baaf-4170-b0cf-ab7ec157e81ctextGoing tofor/id
#text-input-75dc1711-975c-4c77-b10e-e225d6e7c76btextNew departurefor/id
#text-input-4081ddc4-6812-4183-bb7e-09d7e726c72ftextReturn datefor/id
#text-input-0a4c58e2-2a2d-4774-9630-eae8df2e65f0textGuestsfor/id
#country-selectionselectSelect countryaria-label
#language-selectionselectSelect languagearia-label
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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 94/100 — 2 failing, 28 passed
PASS
94

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div#flex-container > div.advisory-desktop > button.close div.container > div#flex-container > div.advisory-desktop > button.close

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-touch html.no-touch

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
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
`[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.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
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
Elements with `role="dialog"` or `role="alertdialog"` 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
`<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.
`<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.
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