Skip to content
https://www.todoist.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 ✓Page Title Error ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
No navigation patterns
FIX
No navigation patterns
Info::
1 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 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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) ASIDE 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

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

C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Heading Hierarchy
5 headings
PASS
5 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Clarity, finally.
  • H2 Kickstart your next project with Todoist Templates
  • H2 A task manager you can trust for life
  • H2 Gain calmness and clarity with the world’s most beloved productivity app
  • H1 We respect your privacy duplicate H1

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

A+
Alt Text Quality
All 88 images OK
PASS
All 88 images OK
Info::
74 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
88 images 14 good alt text 74 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 13 controls labeled
PASS
All 13 controls labeled
Info::
13 control(s) properly labeled
13 controls
13 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
template-category-desktopradionone
template-category-desktopradionone
template-category-desktopradionone
template-category-desktopradionone
template-category-desktopradionone
template-category-desktopradionone
template-category-mobileradionone
template-category-mobileradionone
template-category-mobileradionone
template-category-mobileradionone
template-category-mobileradionone
template-category-mobileradionone
#language-picker-«r645Ra»selectSelect your languagearia-label
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Todoist
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Todoist ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Todoist Display Mode standalone Theme Color #E44332 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)
ElementRatioRequiredFGBGResult
h1 Clarity, finally.20.67:13.0:1
#000000
#FEFDFC
Pass
h1 We respect your priv…20.67:13.0:1
#000000
#FEFDFC
Pass
h2 Kickstart your next …20.67:13.0:1
#000000
#FEFDFC
Pass
h2 A task manager you c…20.67:13.0:1
#000000
#FEFDFC
Pass
h2 Gain calmness and cl…20.67:13.0:1
#000000
#FEFDFC
Pass
title Todoist | A To-Do Li…14.35:14.5:1
#000000
#D7D5D3
Pass
span Made For14.35:14.5:1
#000000
#D7D5D3
Pass
p Task Management17.96:14.5:1
#000000
#EEEDEC
Pass
p Project Management20.67:14.5:1
#000000
#FEFDFC
Pass
p Time Management20.67:14.5:1
#000000
#FEFDFC
Pass
p Habit Forming20.67:14.5:1
#000000
#FEFDFC
Pass
p Teamwork20.67:14.5:1
#000000
#FEFDFC
Pass
span Resources20.67:14.5:1
#000000
#FEFDFC
Pass
p Integrations20.67:14.5:1
#000000
#FEFDFC
Pass
p Templates20.67:14.5:1
#000000
#FEFDFC
Pass
p Getting Started20.67:14.5:1
#000000
#FEFDFC
Pass
p Help Center20.67:14.5:1
#000000
#FEFDFC
Pass
p Customer Stories20.67:14.5:1
#000000
#FEFDFC
Pass
p Productivity Methods…20.67:14.5:1
#000000
#FEFDFC
Pass
p Inspiration Hub20.67:14.5:1
#000000
#FEFDFC
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 90/100 — 3 failing, 27 passed
PASS
90

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.todoistTheme > div.appContainer > astro-island > div._overlay_1d1qk_6 body.todoistTheme > div.appContainer > astro-island > div._overlay_1d1qk_6

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.

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
Start for free li._mobileRegisterItem_1v9k5_27 > span._navbarItem_53i31_1 > a._text_qx30j_1 > span._textWrapper_1yend_73
Clear your mind div > div.text-lock-up > div.text-container > p._text_qx30j_1
Plan with confidence div > div.text-lock-up > div.text-container > p._text_qx30j_1

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Work Accounting Tasks Business Travel Packing div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Personal div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Education div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Management div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Marketing & Sales div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li
Customer Support div._hidden_snh3y_1 > feature-radio-tile-group.mbe-24 > ul > li

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

○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
●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.
●Select elements have associated label elements.
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback