Skip to content
https://dji.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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
Alt Text Quality
2 of 31 images have issues
REVIEW
2 of 31 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
6 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
31 images 23 good alt text 6 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

B
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="input" id="subscribe-modal-email-input">; <input type="text">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtext(Search dji.com...)placeholder only
#subscribe-modal-email-inputinput(Email Address)placeholder only
inputtext(Your email address)placeholder only

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

<input type="text" name="q">; <input type="input" id="subscribe-modal-email-input">; <input type="text">

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

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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page - Page not found - DJI Singapore ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 23 passed
REVIEW
85

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
Industy Insight Report div.swiper-slide > a.banner-link > div.text-box > div.eyebrow-text

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
The World In My Pocket ul.products-banner-list > li.products-banner-item > div.products-banner-text > h5.subhead

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
nav#site-header-m > div.navbar-container > div.navbar-header > a.navbar-search nav#site-header-m > div.navbar-container > div.navbar-header > a.navbar-search
nav#site-header-m > div.navbar-container > div.navbar-header > a.navbar-shopingbag nav#site-header-m > div.navbar-container > div.navbar-header > a.navbar-shopingbag

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.

○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
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Document has a main landmark.
●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
○Buttons have an accessible name
○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
○Links are distinguishable without relying on color.
○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.
○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+
Landmark Structure
3 landmarks
PASS
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN CONTENTINFO footer
A+
Heading Hierarchy
51 headings
PASS
51 headings
Info::
Single H1 present
  • H3 Please Change Your Browser
  • H3 Select Your Country/Region
  • H3 Suggested Searches
  • H3 RECOMMENDED
  • H1 DJI
  • H2 MAVIC 3
  • H2 romo-226
  • H3 Make a Clean Sweep
  • H2 More Than Sound
  • H3 28 April 2026, 12 PM (GMT)
  • H2 avata-360
  • H3 Above It All, See It All
  • H2 mavic-4-pro
  • H3 Spin Your World
  • H2 air-3s
  • H3 Chase the View
  • H2 osmo-action-6
  • H3 Square Up, Nail the Move
  • H2 rs-5
  • H3 Lead the Scene
  • H2 t100-t70
  • H3 Big Drone, Big Jobs.
  • H2 flycart-100
  • H3 Achieve More Deliveries
  • H2 romo-226
  • H3 Make a Clean Sweep
  • H2 More Than Sound
  • H3 28 April 2026, 12 PM (GMT)
  • H2 Just Fly.
  • H3 23 April 2026, 12 PM (GMT)
  • H4 osmo-pocket-4
  • H5 The World In My Pocket
  • H4 neo-2
  • H5 Fly Your Way
  • H4 osmo-mobile-8
  • H5 In Tune With Every Move
  • H5 See product overviews and comparisons here
  • H3 Osmo Pocket 4
  • H3 DJI Avata 360
  • H3 DJI RS 5
  • H3 Osmo Action 6
  • H3 Osmo Mobile 8
  • H3 Osmo Nano
  • H3 DJI Mini 5 Pro
  • H3 Osmo 360
  • H3 DJI Mavic 4 Pro
  • H3 DJI Flip
  • H3 Thanks for signing up!
  • H3 Subscribe
  • H3 Subscribe
  • H3 Select Your Country/Region
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
h1 DJI12.77:13.0:1
#000000
#A2D1E3
Pass
h2 MAVIC 312.77:13.0:1
#000000
#A2D1E3
Pass
h2 romo-22612.77:13.0:1
#000000
#A2D1E3
Pass
h2 More Than Sound12.77:13.0:1
#000000
#A2D1E3
Pass
h2 avata-36012.77:13.0:1
#000000
#A2D1E3
Pass
h2 mavic-4-pro12.77:13.0:1
#000000
#A2D1E3
Pass
h2 air-3s12.77:13.0:1
#000000
#A2D1E3
Pass
h2 osmo-action-612.77:13.0:1
#000000
#A2D1E3
Pass
h2 rs-512.77:13.0:1
#000000
#A2D1E3
Pass
h2 t100-t7012.77:13.0:1
#000000
#A2D1E3
Pass
h2 flycart-10012.77:13.0:1
#000000
#A2D1E3
Pass
h2 romo-22612.77:13.0:1
#000000
#A2D1E3
Pass
h2 More Than Sound12.77:13.0:1
#000000
#A2D1E3
Pass
h2 Just Fly.12.77:13.0:1
#000000
#A2D1E3
Pass
h3 Please Change Your B…7.03:13.0:1
#000000
#929697
Pass
h3 Select Your Country/…12.77:13.0:1
#000000
#A2D1E3
Pass
h3 Suggested Searches12.77:13.0:1
#000000
#A2D1E3
Pass
h3 RECOMMENDED12.77:13.0:1
#000000
#A2D1E3
Pass
h3 Make a Clean Sweep12.77:13.0:1
#000000
#A2D1E3
Pass
h3 28 April 2026, 12 PM…12.77:13.0:1
#000000
#A2D1E3
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