Skip to content
https://deepl.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
Landmark Structure
Action
7 landmarks
FIX
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
3 of 4 <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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE "Supported languages" CONTENTINFO footer

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

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
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
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 4 <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
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
Info::
2 control(s) properly labeled
4 controls
2 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#source-text-areatextareanone
#target-text-areatextareanone
inputtext(replyPlaceholder)placeholder only
inputfile(none)none

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

<input type="file">

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

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

<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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found — DeepL ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 28 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Logo Cloud section.bg-white > div > div.animatedLogoCloud_logoCloudWrapper__97Vcl > div.animatedLogoCloud_scroller__b69y9
Translator Voice Write Documents API section.bg-brand > div.px-redesign-6 > div.mt-redesign-8 > div.border-redesign-quartz-gray-100

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.StorefrontTabSwitcher_root__xXrHt > div.flex > div.w-full > button.relative div.StorefrontTabSwitcher_root__xXrHt > div.flex > div.w-full > button.relative
div.StorefrontTabSwitcher_root__xXrHt > div.flex > div.w-full > button.relative div.StorefrontTabSwitcher_root__xXrHt > div.flex > div.w-full > button.relative
div.StorefrontTabSwitcher_root__xXrHt > div.flex > div.w-full > button.relative div.StorefrontTabSwitcher_root__xXrHt > div.flex > div.w-full > button.relative

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
Close div#cookieBanner > div.flex > button#cookie-banner-lax-close-button > span.__content

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
70 million words securely translated each month with DeepL 30,000 glossary e… section.homeExperience_customerStories__yEkiB > div.py-redesign-8 > div.homeExperience__outerContainer > ul.homeExperience__scrollContainer
Windows logo div.flex > div.divide-brand > div.pb-4 > ul.grid
Chrome logo div.flex > div.divide-brand > div.pt-4 > ul.grid
Life sciences Manufacturing Legal Finance Government Retail section.homeExperience_industries__FHu4I > div.py-redesign-8 > div.homeExperience__outerContainer > ul.homeExperience__scrollContainer

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Sign up for free div.flex > div.px-redesign-6 > div.flex > a.relative
○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]`s are contained by their required parent element
●`[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
●`[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
●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
●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
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[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 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.
○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.
○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+
Heading Hierarchy
49 headings
PASS
49 headings
Info::
Single H1 present
  • H1 AI solutions that help you get work done
  • H2 Drag-and-drop translation for any file type
  • H2 Real-time voice translation
  • H2 Checking if the connection is secure...
  • H2 Trusted by over 200,000 businesses globally
  • H2 Spring Launch 2026
  • H2 Join DeepL in making language work borderless.
  • H3 Register now for our Spring event.
  • H2 DeepL is transforming how 200,000+ businesses communicate globally
  • H3 70 million
  • H3 30,000
  • H3 86%
  • H3 10%
  • H2 A full suite of language tools, built to power your global voice
  • H3 The DeepL Language AI platform
  • H4 Translator
  • H4 Translator
  • H4 Voice
  • H4 Voice
  • H4 Write
  • H4 Write
  • H4 Documents
  • H4 Documents
  • H4 API
  • H4 API
  • H2 DeepL AI labs
  • H2 Integrate better communication wherever you work
  • H3 Apps
  • H3 Integrations
  • H2 We speak the language of your industry
  • H3 Life sciences
  • H3 Manufacturing
  • H3 Legal
  • H3 Finance
  • H3 Government
  • H3 Retail
  • H2 Build in world-class translations effortlessly with our API
  • H3 Read our quick‒start guide and get started in minutes
  • H3 Connect with our community for pro tips and support
  • H3 Give it a go yourself with a free trial
  • H2 Ready to transform your business communication with DeepL?
  • H2 Explore our 100+ languages
  • H3 Products
  • H3 Why DeepL
  • H3 Features
  • H3 Solutions
  • H3 Download
  • H3 Resources
  • H3 Company
A+
Alt Text Quality
All 38 images OK
PASS
All 38 images OK
Info::
30 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
38 images 8 good alt text 30 decorative
All images have appropriate alt text.
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 AI solutions that he…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Drag-and-drop transl…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Real-time voice tran…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Checking if the conn…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Trusted by over 200,…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Spring Launch 202614.60:13.0:1
#000000
#B9DBFC
Pass
h2 Join DeepL in making…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 DeepL is transformin…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 A full suite of lang…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 DeepL AI labs14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Integrate better com…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 We speak the languag…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Build in world-class…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Ready to transform y…14.60:13.0:1
#000000
#B9DBFC
Pass
h2 Explore our 100+ lan…14.60:13.0:1
#000000
#B9DBFC
Pass
h3 Register now for our…14.60:13.0:1
#000000
#B9DBFC
Pass
h3 70 million14.60:13.0:1
#000000
#B9DBFC
Pass
h3 30,00014.60:13.0:1
#000000
#B9DBFC
Pass
h3 86%14.60:13.0:1
#000000
#B9DBFC
Pass
h3 10%14.60:13.0:1
#000000
#B9DBFC
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