Skip to content
https://duckduckgo.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
3
REVIEW
8
PASS
13
INFO
0
Checks
24
13 PASS 8 REVIEW 3 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-fyrvr5
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

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.

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::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <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.
C
Landmark Structure
Action
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

B
Heading Hierarchy
16 headings, 1 skip(s)
REVIEW
16 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 DuckDuckGo
  • H1 DuckDuckGo duplicate H1
  • H2 Protect your personal information on all your devices.
  • H2 Discover more from DuckDuckGo.
  • H2 See how DuckDuckGo compares.
  • H3 Protection. Privacy. Peace of mind.Get the browser built for data protection, not data collection.
  • H3 Take back control of your personal information.
  • H3 Block most ads & cookie pop-ups for fewer interruptions.
  • H3 Data protection, not data collection.
  • H2 Don’t just take our word for it.
  • H3 Trusted by tens of millions worldwide!
  • H6 Get our free browser today! skipped
  • H3 Still have questions?
  • H4 Learn More
  • H4 Other Resources
  • H4 About DuckDuckGo

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

B
Tabindex Anti-Patterns
0 positive, 4 -1-on-focusable
REVIEW
0 positive, 4 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
B
Mobile-Readable Font Sizes
99% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
99% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.4px ("Search Privately").
B
Favicon & Branding
12 icon(s) detected
REVIEW
12 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 Present
Multiple Sizes Present
B
Web Manifest
PWA-ready
REVIEW
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: DuckDuckGo
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name DuckDuckGo 192×192 icon 512×512 icon Start URL /?t=crhs Display Mode standalone
Name DuckDuckGo Display Mode standalone Icons 6 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light dark
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta light dark Dark theme-color Not set CSS indicators Detected

Detection limited to meta tags and inline styles.

A+
Heading Text Quality
All 16 heading(s) have substantive, well-formed text
PASS
All 16 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 67 images OK
PASS
All 67 images OK
Info::
32 decorative image(s) correctly marked
Info::
35 image(s) with good alt text
67 images 35 good alt text 32 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtextSearch with DuckDuckGoaria-label
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
PWA Depth
2 PWA signal(s) surfaced
PASS
2 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
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 DuckDuckGo20.14:13.0:1
#000000
#FBFAF9
Pass
h1 DuckDuckGo20.14:13.0:1
#000000
#FBFAF9
Pass
h2 Protect your persona…20.14:13.0:1
#000000
#FBFAF9
Pass
h2 devices.20.14:13.0:1
#000000
#FBFAF9
Pass
h2 Discover more from D…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 See how DuckDuckGo c…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Don’t just take ou…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get the browser buil…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Take back control of…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Block most ads & coo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Data protection, not…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Trusted by tens of m…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Still have questions…21.00:13.0:1
#000000
#FFFFFF
Pass
title DuckDuckGo - Protect…20.14:14.5:1
#000000
#FBFAF9
Pass
span Duck.ai20.14:14.5:1
#000000
#FBFAF9
Pass
span Main navigation menu…20.14:14.5:1
#000000
#FBFAF9
Pass
span Menu20.14:14.5:1
#000000
#FBFAF9
Pass
span Search20.14:14.5:1
#000000
#FBFAF9
Pass
span Duck.ai20.14:14.5:1
#000000
#FBFAF9
Pass
span Protection. Privacy.…19.97:14.5:1
#000000
#FAF9F8
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
Lighthouse Accessibility Audits
Score 91/100 — 4 failing, 28 passed
PASS
91

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chrome div.chip-tabs_root___5P_z > div > div > button#tabs--tab--0

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.

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
Take back your privacy! div.mobile-atb-banner_atbBanner__2BCOH > div.mobile-atb-banner_wrapperComponent__f_cud > div.mobile-atb-banner_atbContent__j5f2T > h4.mobile-atb-banner_newTitle__0Ih7K
Learn more main.minimal-homepage_layout__5B6f9 > div.minimal-homepage_minimalHero__2yzex > div.homepage-cta-section_scrollCta__Wmixn > h6.heading_heading6__1lVXi
Protection div.app-hero-card-buttons_root__lL3qk > button.card_card___ZlNq > div.app-hero-card-buttons_headingAndBodyContainer__EdbRh > h5.app-hero-card-buttons_headingText__OaqQi
Protection div.app-hero-card-buttons_root__lL3qk > button.card_card___ZlNq > div.app-hero-card-buttons_headingAndBodyContainer__EdbRh > h5.app-hero-card-buttons_headingText__OaqQi
Goodbye Incognito mode, hello real privacy in every tab div.single-column-feature-card_bitesContainer__9erSa > div.single-column-feature-card-detail-bite_root__8q0rO > button.card_card___ZlNq > h5.single-column-feature-card-detail-bite_cardButtonHeading__KJQuU
Stop ads following you everywhere div.single-column-feature-card_bitesContainer__9erSa > div.single-column-feature-card-detail-bite_root__8q0rO > button.card_card___ZlNq > h5.single-column-feature-card-detail-bite_cardButtonHeading__KJQuU
Search without being tracked div.single-column-feature-card_bitesContainer__9erSa > div.single-column-feature-card-detail-bite_root__8q0rO > button.card_card___ZlNq > h5.single-column-feature-card-detail-bite_cardButtonHeading__KJQuU

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
div.minimal-homepage_minimalHero__2yzex > section.mobile-badge-banner_hideOnLandscape__ji4KC > div.mobile-badge-banner_atbBadge__ISxcF > a div.minimal-homepage_minimalHero__2yzex > section.mobile-badge-banner_hideOnLandscape__ji4KC > div.mobile-badge-banner_atbBadge__ISxcF > a
div.minimal-homepage_minimalHero__2yzex > section.mobile-badge-banner_hideOnLandscape__ji4KC > div.mobile-badge-banner_atbBadge__ISxcF > a div.minimal-homepage_minimalHero__2yzex > section.mobile-badge-banner_hideOnLandscape__ji4KC > div.mobile-badge-banner_atbBadge__ISxcF > a
main.minimal-homepage_layout__5B6f9 > div.minimal-homepage_minimalHero__2yzex > div.homepage-cta-section_scrollCta__Wmixn > a.homepage-cta-section_scrollArow__of6hD main.minimal-homepage_layout__5B6f9 > div.minimal-homepage_minimalHero__2yzex > div.homepage-cta-section_scrollCta__Wmixn > a.homepage-cta-section_scrollArow__of6hD

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search privately by default Chat privately with popular AI chatb… div.stack_root__raz5U > div.stack_root__raz5U > div.stack_root__raz5U > table.marketing-compare-privacy-table_table__UDHdq
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
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 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
`[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.
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.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`[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 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.
`<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.
Elements with visible text labels have matching accessible names.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback