Accessibility

D

Landmark Structure

Action

18 landmarks

FIX

18 landmarks

No <main> landmark found

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

16 <nav> landmark(s) found

16 of 16 <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

F

Heading Hierarchy

Action

17 headings, 4 skip(s)

FIX

17 headings, 4 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

H3 An innovative lineup of data products and applications.
H6 Data Products skipped
H6 Applications
H6 ADS-B
H3 Tailored solutions for each aviation industry.
H6 Industries skipped
H3 A worldwide network of coverage.
H6 ADS-B skipped
H3 Real-time, historical, and predictive flight tracking.
H6 Delays & Cancellations skipped
H6 Search Flights
H6 Other
H6 About
H6 Community
H6 Tracking
H6 Products
H6 Customer Service

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

D

Web Manifest

Action

Not found

FIX

Not found

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

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

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

16 navigation landmark(s) detected

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 16 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

B

Link & Button Quality

4 issue(s) across 76 links and 10 buttons

REVIEW

4 issue(s) across 76 links and 10 buttons

4 button(s) with no accessible text

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

Got: button.absolute (#106 on page); button.absolute (#136 on page); button.absolute (#171 on page); button.absolute (#220 on page)

76 link(s) with descriptive text

76 links

0 empty

0 generic text

0 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

82 links and buttons have descriptive text

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

button.absolute (#106 on page); button.absolute (#136 on page); button.absolute (#171 on page); button.absolute (#220 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

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found ✈ FlightAware ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

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 2 pass AA only

title FlightAware - Flight Tracker / Flight St…

1.17:1

#000000

on

#00153D

needs 4.5:1 (normal text)

16px · top of page (header area)

summary Products

1.17:1

#000000

on

#00153D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Go to: All Products

3.13:1

#000000

on

#605968

needs 4.5:1 (normal text)

16px · top of page (header area)

a AeroAPI

3.45:1

#000000

on

#66606B

needs 4.5:1 (normal text)

16px · above the fold

p On-demand flight status and tracking dat…

3.59:1

#000000

on

#6B626C

needs 4.5:1 (normal text)

16px · above the fold

a FlightAware Firehose

3.87:1

#000000

on

#71676F

needs 4.5:1 (normal text)

16px · above the fold

p Real-time, historical, and predictive fl…

4.03:1

#000000

on

#746A6E

needs 4.5:1 (normal text)

16px · above the fold

a FlightAware Foresight

4.17:1

#000000

on

#776C72

needs 4.5:1 (normal text)

16px · above the fold

p Increase operational efficiency gate-to-…

4.16:1

#000000

on

#766C72

needs 4.5:1 (normal text)

16px · above the fold

a Integrated Maps

1.45:1

#000000

on

#232938

needs 4.5:1 (normal text)

16px · mid-page

p Comprehensive mapping solutions for appl…

1.28:1

#000000

on

#15202E

needs 4.5:1 (normal text)

16px · mid-page

a FlightAware Aviator

2.04:1

#000000

on

#31415D

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 An innovative lineup…	3.13:1	3.0:1	#000000	#605969	Pass
h3 Tailored solutions f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A worldwide network …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Real-time, historica…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title FlightAware - Flight…	1.17:1	4.5:1	#000000	#00153D	Fail
summary Products	1.17:1	4.5:1	#000000	#00153D	Fail
span Go to: All Products	3.13:1	4.5:1	#000000	#605968	Fail
a AeroAPI	3.45:1	4.5:1	#000000	#66606B	Fail
p On-demand flight sta…	3.59:1	4.5:1	#000000	#6B626C	Fail
a FlightAware Firehose	3.87:1	4.5:1	#000000	#71676F	Fail
p Real-time, historica…	4.03:1	4.5:1	#000000	#746A6E	Fail
a FlightAware Foresigh…	4.17:1	4.5:1	#000000	#776C72	Fail
p Increase operational…	4.16:1	4.5:1	#000000	#766C72	Fail
a Reports	5.86:1	4.5:1	#000000	#8B8688	Pass
p Generate instant avi…	7.07:1	4.5:1	#000000	#959695	Pass
a Integrated Maps	1.45:1	4.5:1	#000000	#232938	Fail
p Comprehensive mappin…	1.28:1	4.5:1	#000000	#15202E	Fail
a FlightAware Aviator	2.04:1	4.5:1	#000000	#31415D	Fail
p Flight tracking for …	8.68:1	4.5:1	#000000	#A1A7B1	Pass
a Premium Subscription…	21.00:1	4.5: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.

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 25 passed

PASS

90

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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.pointer-events-auto > div.input-md > form.group > input.text-primary `div.pointer-events-auto > div.input-md > form.group > input.text-primary`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

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
Privacy Statement `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-imprint-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-*]` 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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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