Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Alt Text Quality

Action

41 of 53 images have issues

FIX

41 of 53 images have issues

41 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

41 image-in-link without alt text

An image inside a link with no alt creates an empty link.

10 decorative image(s) correctly marked

2 image(s) with good alt text

53 images 2 good alt text 10 decorative 41 missing

Issue	Count
missing	41 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

An image inside a link with no alt creates an empty link.

Why this matters

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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 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

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

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

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

Link & Button Quality

116 links, 4 buttons — all OK

REVIEW

116 links, 4 buttons — all OK

41 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/course/en/en/Learn-English"]; a[href="/course/es/en/Learn-Spanish"]; a[href="/course/fr/en/Learn-French"]; a[href="/course/de/en/Learn-German"]; a[href="/course/it/en/Learn-Italian"]; a[href="/course/pt/en/Learn-Portuguese"]; a[href="/course/math/Learn-Math"]; a[href="/course/nl-NL/en/Learn-Dutch"]; a[href="/course/ja/en/Learn-Japanese"]; a[href="/course/ar/en/Learn-Arabic"] (+31 more)

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /cookies

74 link(s) with descriptive text

116 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/course/en/en/Learn-English	English	img no alt	Add alt attribute to the image
/course/es/en/Learn-Spanish	Spanish	img no alt	Add alt attribute to the image
/course/fr/en/Learn-French	French	img no alt	Add alt attribute to the image
/course/de/en/Learn-German	German	img no alt	Add alt attribute to the image
/course/it/en/Learn-Italian	Italian	img no alt	Add alt attribute to the image
/course/pt/en/Learn-Portuguese	Portuguese	img no alt	Add alt attribute to the image
/course/math/Learn-Math	Math	img no alt	Add alt attribute to the image
/course/nl-NL/en/Learn-Dutch	Dutch	img no alt	Add alt attribute to the image
/course/ja/en/Learn-Japanese	Japanese	img no alt	Add alt attribute to the image
/course/ar/en/Learn-Arabic	Arabic	img no alt	Add alt attribute to the image
/course/cs/en/Learn-Czech	Czech	img no alt	Add alt attribute to the image
/course/cy/en/Learn-Welsh	Welsh	img no alt	Add alt attribute to the image
/course/da/en/Learn-Danish	Danish	img no alt	Add alt attribute to the image
/course/el/en/Learn-Greek	Greek	img no alt	Add alt attribute to the image
/course/eo/en/Learn-Esperanto	Esperanto	img no alt	Add alt attribute to the image
/course/fi/en/Learn-Finnish	Finnish	img no alt	Add alt attribute to the image
/course/ga/en/Learn-Irish	Irish	img no alt	Add alt attribute to the image
/course/gd/en/Learn-Scottish%20Gaelic	Scottish Gaelic	img no alt	Add alt attribute to the image
/course/he/en/Learn-Hebrew	Hebrew	img no alt	Add alt attribute to the image
/course/hi/en/Learn-Hindi	Hindi	img no alt	Add alt attribute to the image
/course/ht/en/Learn-Haitian%20Creole	Haitian Creole	img no alt	Add alt attribute to the image
/course/hu/en/Learn-Hungarian	Hungarian	img no alt	Add alt attribute to the image
/course/hv/en/Learn-High%20Valyrian	High Valyrian	img no alt	Add alt attribute to the image
/course/hw/en/Learn-Hawaiian	Hawaiian	img no alt	Add alt attribute to the image
/course/id/en/Learn-Indonesian	Indonesian	img no alt	Add alt attribute to the image
/course/ko/en/Learn-Korean	Korean	img no alt	Add alt attribute to the image
/course/la/en/Learn-Latin	Latin	img no alt	Add alt attribute to the image
/course/no-BO/en/Learn-Norwegian%20Bokm%…	Norwegian (Bokmål)	img no alt	Add alt attribute to the image
/course/nv/en/Learn-Navajo	Navajo	img no alt	Add alt attribute to the image
/course/pl/en/Learn-Polish	Polish	img no alt	Add alt attribute to the image
/course/ro/en/Learn-Romanian	Romanian	img no alt	Add alt attribute to the image
/course/ru/en/Learn-Russian	Russian	img no alt	Add alt attribute to the image
/course/sv/en/Learn-Swedish	Swedish	img no alt	Add alt attribute to the image
/course/sw/en/Learn-Swahili	Swahili	img no alt	Add alt attribute to the image
/course/tlh/en/Learn-Klingon	Klingon	img no alt	Add alt attribute to the image
/course/tr/en/Learn-Turkish	Turkish	img no alt	Add alt attribute to the image
/course/uk/en/Learn-Ukrainian	Ukrainian	img no alt	Add alt attribute to the image
/course/vi/en/Learn-Vietnamese	Vietnamese	img no alt	Add alt attribute to the image
/course/yi/en/Learn-Yiddish	Yiddish	img no alt	Add alt attribute to the image
/course/zh/en/Learn-Chinese	Chinese	img no alt	Add alt attribute to the image
/course/zu/en/Learn-Zulu	Zulu	img no alt	Add alt attribute to the image
/cookies	More information about your pr…	new tab	Add '(opens in new tab)' to text

78 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/course/en/en/Learn-English"]; a[href="/course/es/en/Learn-Spanish"]; a[href="/course/fr/en/Learn-French"]; a[href="/course/de/en/Learn-German"]; a[href="/course/it/en/Learn-Italian"]; a[href="/course/pt/en/Learn-Portuguese"]; a[href="/course/math/Learn-Math"]; a[href="/course/nl-NL/en/Learn-Dutch"]; a[href="/course/ja/en/Learn-Japanese"]; a[href="/course/ar/en/Learn-Arabic"] (+31 more)

Why this matters

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.

/cookies

Why this matters

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

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 22 passed

REVIEW

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.qO_UG > div._3CwWq > div.zKVv4 > button._38iBE `div.qO_UG > div._3CwWq > div.zKVv4 > button._38iBE`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
free. fun. effective. `section.uU0-M > section._3k9io > div._2Yq-n > h2._3X-2C`
Learning with Duolingo is fun, and research shows that it works! With quick, bi… `section._3k9io > div._2Yq-n > p.KsAV5 > span`
research shows that it works `div._2Yq-n > p.KsAV5 > span > a._1F7oE`
backed by science `section.uU0-M > section._36L7f > div._2Yq-n > h2._3X-2C`
We use a combination of research-backed teaching methods and delightful content… `section.uU0-M > section._36L7f > div._2Yq-n > p.KsAV5`
stay motivated `section.uU0-M > section._3k9io > div._2Yq-n > h2._3X-2C`
We make it easy to form a habit of language learning with game-like features, f… `section.uU0-M > section._3k9io > div._2Yq-n > p.KsAV5`
personalized learning `section.uU0-M > section._36L7f > div._2Yq-n > h2._3X-2C`
Combining the best of AI and language science, lessons are tailored to help you… `section.uU0-M > section._36L7f > div._2Yq-n > p.KsAV5`
duolingo english test `div._2Yq-n > h2._3X-2C > span > span`
Our convenient, fast, and affordable English test integrates the latest assessm… `section._3dG3I > section._3k9io > div._2Yq-n > p.KsAV5`
duolingo for schools `section._3dG3I > section._36L7f > div._2Yq-n > h2._3X-2C`
Teachers, we’re here to help you! Our free tools support your students as they … `section._3dG3I > section._36L7f > div._2Yq-n > p.KsAV5`
duolingo abc `section._3dG3I > section._3k9io > div._2Yq-n > h2._3X-2C`
From language to literacy! With fun phonics lessons and delightful stories, Duo… `section._3dG3I > section._3k9io > div._2Yq-n > p.KsAV5`
learn a language with duolingo `section.F71XF > div._1fSpL > div._3qFL2 > h1._1FmL9`
About us `div.kWIKU > div._2zjY4 > div > div._30Vi6`
Courses `div > ul > li > a`
Mission `div > ul > li > a`
Approach `div > ul > li > a`
Efficacy `div > ul > li > a`
Duolingo Handbook `div > ul > li > a`
Research `div > ul > li > a`
Careers `div > ul > li > a`
Brand guidelines `div > ul > li > a`
Store `div > ul > li > a`
Press `div > ul > li > a`
Investors `div > ul > li > a`
Contact us `div > ul > li > a`
Products `div.kWIKU > div._2zjY4 > div > div._30Vi6`
Duolingo `div > ul > li > a`
Duolingo for Schools `div > ul > li > a`
Duolingo English Test `div > ul > li > a`
Podcast `div > ul > li > a`
Duolingo for Business `div > ul > li > a`
Super Duolingo `div > ul > li > a`
Gift Super Duolingo `div > ul > li > a`
Duolingo Max `div > ul > li > a`
Apps `div.kWIKU > div._2zjY4 > div > div._30Vi6`
Duolingo for Android `div > ul > li > a`
Duolingo for iOS `div > ul > li > a`
Help and support `div.kWIKU > div._2zjY4 > div > div._30Vi6`
Duolingo FAQs `div > ul > li > a`
Schools FAQs `div > ul > li > a`
Duolingo English Test FAQs `div > ul > li > a`
Status `div > ul > li > a`
Privacy and terms `div.kWIKU > div._2zjY4 > div > div._30Vi6`
Community guidelines `div > ul > li > a`
Terms `div > ul > li > a`
Privacy `div > ul > li > a`
Do Not Sell or Share My Personal Information `div > ul > li > a`
Social `div.kWIKU > div._2zjY4 > div > div._30Vi6`
Blog `div > ul > li > a`
Instagram `div > ul > li > a`
TikTok `div > ul > li > a`
Twitter `div > ul > li > a`
YouTube `div > ul > li > a`
LinkedIn `div > ul > li > a`
Site language: `div.qO_UG > footer._1nNuk > div.-Dahb > div._1LLyK`
العربية `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
বাংলা `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Čeština `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Deutsch `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Ελληνικά `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
English `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Español `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Français `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
हिंदी `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Magyar `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Bahasa Indonesia `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Italiano `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
日本語 `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
한국어 `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Nederlands `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Polski `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Português `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Română `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Русский `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
svenska `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
தமிழ் `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
తెలుగు `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
ภาษาไทย `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Tagalog `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Türkçe `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Українською `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
Tiếng Việt `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
中文 `div.-Dahb > ul._3PydS > li.yu122 > a.FXHbm`
4.5 `div._3CwWq > div.zKVv4 > div > span._2PsOB`
Cookie Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`
REJECT ALL `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler`
ACCEPT COOKIES `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler`

These are opportunities to improve the legibility of your content.

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
Cookie Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`

○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

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●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

●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-hidden="true"]` elements do not contain focusable descendents

○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

○Form elements have associated labels

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

Heading Hierarchy

11 headings

PASS

11 headings

Multiple H1 headings (3 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 The free, fun, and effective way to learn a language!
H2 free. fun. effective.
H2 backed by science
H2 stay motivated
H2 personalized learning
H1 learn anytime, anywhere duplicate H1
H2 duolingo english test
H2 duolingo for schools
H2 duolingo abc
H1 learn a language with duolingo duplicate H1
H2 Duo loves cookies

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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

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

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#g-recaptcha-response-100000	textarea	(none)	none

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

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

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Duolingo

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Duolingo ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa_launch ✓Display Mode standalone ✓

Name Duolingo Display Mode standalone Background Color #ffffff Icons 2 icon(s)

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)

Element	Ratio	Required	FG	BG	Result
h1 The free, fun, and e…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 learn anytime, anywh…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 learn a language wit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 free. fun. effective…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 backed by science	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 stay motivated	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 personalized learnin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 duolingo for schools	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 duolingo abc	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Duo loves cookies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Duolingo - The world…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Get started	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Get started	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span I ALREADY HAVE AN AC…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span English	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Spanish	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span French	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span German	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Italian	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Portuguese	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.