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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
Alt Text Quality
Action
45 of 65 images have issues
FIX
45 of 65 images have issues
Critical::
45 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
16 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
65 images 4 good alt text 16 decorative 45 missing
IssueCount
missing45 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

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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 69/100 — 7 failing, 16 passed
FIX
69

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.brand_2aHQJ > div.productLogo__1LRH > div > img a.brand_2aHQJ > div.productLogo__1LRH > div > img
div.header_1YX7j > div.header1_3hffQ > div > img div.header_1YX7j > div.header1_3hffQ > div > img
div.header_1YX7j > div.header2_1bz_R > div > img div.header_1YX7j > div.header2_1bz_R > div > img
div.choices_3gEFq > div.choice_p55YW > div > img div.choices_3gEFq > div.choice_p55YW > div > img
div.choices_3gEFq > div.choice_p55YW > div > img div.choices_3gEFq > div.choice_p55YW > div > img
div.choices_3gEFq > div.choice_p55YW > div > img div.choices_3gEFq > div.choice_p55YW > div > img
div.choices_3gEFq > div.choice_p55YW > div > img div.choices_3gEFq > div.choice_p55YW > div > img
div.img_22ZNa > div > div > img div.img_22ZNa > div > div > img
div.img_22ZNa > div > div > img div.img_22ZNa > div > div > img
div.img_22ZNa > div > div > img div.img_22ZNa > div > div > img
div.img_22ZNa > div > div > img div.img_22ZNa > div > div > img
div.img_22ZNa > div > div > img div.img_22ZNa > div > div > img
div.content_X4x7O > div.mobilePic_1MeIA > div > img div.content_X4x7O > div.mobilePic_1MeIA > div > img
div.container_37-FB > div.card_2X3m_ > div > img div.container_37-FB > div.card_2X3m_ > div > img
div.content_BWuxK > div.pic_1e-rZ > div > img div.content_BWuxK > div.pic_1e-rZ > div > img
div.header_e9eaU > div.avatar_1glbR > div > img.mediaIcon_1l8E0 div.header_e9eaU > div.avatar_1glbR > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0 li.slideControl_3bI9p > div.removeTapEffect > div > img.mediaIcon_1l8E0
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img
div.userItem_1fSHi > div.userAvatar_uadde > div > img div.userItem_1fSHi > div.userAvatar_uadde > div > img

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.navCollapse_2tnl9 > div.menuHeader_1Mqim > div.menuHeaderInner_LpwJe > a.brand_2aHQJ div.navCollapse_2tnl9 > div.menuHeader_1Mqim > div.menuHeaderInner_LpwJe > a.brand_2aHQJ
div.mediaCardList_1K9lc > div.mediaWrapper__0k_D > div.mediaCard_2dz6z > a div.mediaCardList_1K9lc > div.mediaWrapper__0k_D > div.mediaCard_2dz6z > a

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.

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
Features Download Premium Resources Sign In div.navCollapse_2tnl9 > div.menu_3afjO > div.container_1HIRZ > ul.navbar_2uuBv

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
Resources ul.navbar_2uuBv > details > summary#resource-summary > li.navItem_2K7pc

These are opportunities to improve the experience of reading tabular or list data using 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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●Buttons have an accessible name
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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 a valid value for its `[lang]` attribute
○`<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
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○Elements with visible text labels have matching accessible names.
○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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found - TickTick ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 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
A
Heading Hierarchy
7 headings
PASS
7 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Stay Organized, Stay Creative.
  • H2 Powerful and intuitive features
  • H2 A comprehensive suite of features
  • H1 Sync across all platforms duplicate H1
  • H2 Recommended by top media
  • H2 Highly rated by users
  • H2 Ready to be more productive?

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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 Sync across all plat…17.73:13.0:1
#000000
#DBEFF9
Pass
h2 Powerful and intuiti…17.73:13.0:1
#000000
#DBEFF9
Pass
h2 A comprehensive suit…17.73:13.0:1
#000000
#DBEFF9
Pass
h2 Recommended by top m…17.73:13.0:1
#000000
#DBEFF9
Pass
h2 Highly rated by user…17.73:13.0:1
#000000
#DBEFF9
Pass
h2 Ready to be more pro…17.73:13.0:1
#000000
#DBEFF9
Pass
title TickTick: A To-Do Li…20.85:14.5:1
#000000
#FBFFFF
Pass
a Features20.23:14.5:1
#000000
#F5FCFD
Pass
a Download19.77:14.5:1
#000000
#F0FAFB
Pass
a Premium19.70:14.5:1
#000000
#EEFAFB
Pass
div Resources19.37:14.5:1
#000000
#ECF8FA
Pass
a Help Center19.18:14.5:1
#000000
#EAF7FA
Pass
a Productivity Guides18.98:14.5:1
#000000
#E8F6F9
Pass
a Sign In18.83:14.5:1
#000000
#E7F5F9
Pass
a Sign Up for Free18.81:14.5:1
#000000
#E6F5FA
Pass
a Features18.61:14.5:1
#000000
#E4F4F9
Pass
a Download18.53:14.5:1
#000000
#E2F4F8
Pass
a Premium18.38:14.5:1
#000000
#E1F3F8
Pass
span Resources18.23:14.5:1
#000000
#E0F2F8
Pass
a Help Center18.04:14.5:1
#000000
#DEF1F8
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