Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FAlt Text QualityAction4 of 12 images have issuesFIX
| Issue | Count |
|---|---|
| missing | 4 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
An image inside a link with no alt creates an empty link.
Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.
Learn more ▾ ▴
An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.
Source: WCAG 2.1 SC 2.4.4
FLink & Button QualityAction11 issue(s) across 37 links and 7 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.flightradar24.com/premium | Try free for 7 days | new tab | Add '(opens in new tab)' to text |
| https://www.flightradar24.com/premium | Upgrade now I Try free for 7 … | new tab | Add '(opens in new tab)' to text |
| https://apps.apple.com/app/apple-store/i… | Download on the App Store | new tab | Add '(opens in new tab)' to text |
| https://play.google.com/store/apps/detai… | Get it on Google Play | new tab | Add '(opens in new tab)' to text |
| https://www.flightradar24.com/blog/newsl… | Subscribe to newsletter | img no alt | Add alt attribute to the image |
| https://www.flightradar24.com/blog | Check out blog | img no alt | Add alt attribute to the image |
| https://www.flightradar24.com/blog/avtal… | Listen to podcast | img no alt | Add alt attribute to the image |
| https://www.flightradar24.com/blog/fligh… | Watch videos | img no alt | Add alt attribute to the image |
| https://www.facebook.com/flightradar24 | (empty) | empty | Add link text or aria-label |
| https://www.instagram.com/flightradar24 | (empty) | empty | Add link text or aria-label |
| https://twitter.com/flightradar24 | (empty) | empty | Add link text or aria-label |
| https://www.linkedin.com/company/flightr… | (empty) | empty | Add link text or aria-label |
| https://www.youtube.com/@Flightradar24Do… | (empty) | empty | Add link text or aria-label |
| https://bsky.app/profile/flightradar24.c… | (empty) | empty | Add link text or aria-label |
| https://www.tiktok.com/@therealflightrad… | (empty) | empty | Add link text or aria-label |
| https://get.webgl.org/get-a-webgl-implem… | See what browsers are supporte… | new tab | Add '(opens in new tab)' to text |
| https://get.webgl.org/webgl2/ | Check if your browser supports… | new tab | Add '(opens in new tab)' to text |
| https://webglreport.com/?v=2 | Get WebGL2 report for your bro… | new tab | Add '(opens in new tab)' to text |
| https://apps.apple.com/app/apple-store/i… | Download on the App Store | new tab | Add '(opens in new tab)' to text |
| https://play.google.com/store/apps/detai… | Get it on Google Play | new tab | Add '(opens in new tab)' to text |
| https://www.flightradar24.com/premium | Learn more | Create account | new tab | Add '(opens in new tab)' to text |
| <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 |
Links without text are announced as raw URLs by screen readers.
https://www.facebook.com/flightradar24; https://www.instagram.com/flightradar24; https://twitter.com/flightradar24; https://www.linkedin.com/company/flightradar24-ab; https://www.youtube.com/@Flightradar24DotCom; https://bsky.app/profile/flightradar24.com; https://www.tiktok.com/@therealflightradar24
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
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a[href="https://www.flightradar24.com/blog/newsletter"]; a[href="https://www.flightradar24.com/blog"]; a[href="https://www.flightradar24.com/blog/avtalk-podcast"]; a[href="https://www.flightradar24.com/blog/flightradar24-videos"]
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://www.flightradar24.com/premium; https://www.flightradar24.com/premium; https://apps.apple.com/app/apple-store/id382233851?pt=6561867&mt=8&ct=fr24_mo…; https://play.google.com/store/apps/details?id=com.flightradar24free&hl=en&ref…; https://get.webgl.org/get-a-webgl-implementation/#:~:text=The%20WebGL%202.0,f…; https://get.webgl.org/webgl2/; https://webglreport.com/?v=2; https://apps.apple.com/app/apple-store/id382233851?pt=6561867&mt=8&ct=fr24_mo…; https://play.google.com/store/apps/details?id=com.flightradar24free&hl=en&ref…; https://www.flightradar24.com/premium
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.
button#aside-main-menu-close-button; button#hamburger-menu-button; button.absolute (#350 on page); button[data-testid="password-input__toggle-password"]
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
F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure3 landmarksREVIEW
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
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
BHeading Hierarchy4 headings, 1 skip(s)REVIEW
- H1 Flight tracker map
- H1 Issue with your browser duplicate H1
- H3 Read more about WebGL2 below or use our apps skipped
- H1 Log in duplicate H1
A page should have only one H1. Multiple H1s dilute the document outline.
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.
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
BForm Accessibility3 of 4 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| #remember_me | checkbox | none | |
| ( ) | placeholder only | ||
| props.name | password | ( ) | placeholder only |
| input | text | ( ) | placeholder only |
Placeholder text disappears on focus and is not a reliable label.
<input type="text">; <input type="email" name="email">; <input type="password" name="props.name">
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
BFavicon & Branding11 icon(s) detectedREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Flight tracker map | 1.23:1 | 3.0:1 | #000000 | #111D28 | Fail |
| h1 Issue with your brow… | 1.27:1 | 3.0:1 | #000000 | #13202D | Fail |
| h1 Log in | 1.32:1 | 3.0:1 | #000000 | #152331 | Fail |
| h3 Read more about WebG… | 1.32:1 | 3.0:1 | #000000 | #152331 | Fail |
| title Flightradar24: Live … | 1.11:1 | 4.5:1 | #000000 | #0F1113 | Fail |
| a Try free for 7 days | 1.15:1 | 4.5:1 | #000000 | #11161B | Fail |
| a Upgrade now I Try f… | 1.18:1 | 4.5:1 | #000000 | #101922 | Fail |
| span Aviation data | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Email alerts | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Subscription plans | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Add coverage | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Commercial services … | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Press & media center | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span About | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span MyFR24 – flight lo… | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span JetPhotos – aviati… | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Forum | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Skycards - aviation … | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Subscribe to newslet… | 1.23:1 | 4.5:1 | #000000 | #111D28 | Fail |
| span Check out blog | 1.23:1 | 4.5:1 | #000000 | #111D28 | 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.
BLighthouse Accessibility AuditsScore 87/100 — 3 failing, 22 passedREVIEW
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
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
PREMIUM FEATURE
Airport Statistics: Runway usage
See the last 7 days of total t… div#headlessui-portal-root > div > div > div#headlessui-dialog-v-24-1 |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 |
article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 |
article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 |
article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 |
article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 |
article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 article.max-h-[calc(100vh-2rem)] > article.relative > nav.z-10 > button.size-2 |
article.relative > section.group > nav > button.absolute article.relative > section.group > nav > button.absolute |
article.relative > section.group > nav > button.absolute article.relative > section.group > nav > button.absolute |
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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Agree and close div#gravitoCMP-tab-container-id > div.gravitoCMP-action-footer-div > div.gravitoCMP-action-container > button#gravitoTCFCMP-layer1-accept-all |
These are opportunities to improve the legibility of your content.