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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 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::
4 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!) 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

F
Heading Hierarchy
Action
43 headings, 5 skip(s)
FIX
43 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 PLATFORM
  • H3 CAPABILITIES
  • H3 ASANA AI
  • H3 PLANS
  • H3 Company Type
  • H3 Teams
  • H3 Industries
  • H3 Use Cases
  • H3 LEARN
  • H3 SUPPORT
  • H3 SERVICES
  • H1 Supercharge your teams with AI that gets work done
  • H4 85% of Fortune 100 companies choose Asana¹ skipped
  • H2 The platform for human + AI collaboration
  • H3 Maximize campaign ROI
  • H3 Drive better outcomes
  • H3 Prioritize and streamline IT requests
  • H3 Drive team alignment and impact
  • H2 See how Asana keeps work moving across use cases
  • H5 Campaign management skipped
  • H5 Creative production
  • H5 Project intake
  • H5 Product launches
  • H5 Organizational planning
  • H5 Resource planning
  • H5 Goal management
  • H5 Employee onboarding
  • H2 What sets Asana apart
  • H3 Amplify your impact 
with AI
  • H3 More clarity and accountability
  • H5 Stay secure and compliant with Asana Gov skipped
  • H2 Connect over 300+ integrations
  • H2 The world’s top companies trust Asana
  • H6 Simon Levinson skipped
  • H6 Romain Ehrhard
  • H6 Eugenia Contreras
  • H6 Steven Tai
  • H2 Get started easily
  • H4 Try the Asana demo skipped
  • H4 Discover resources
  • H4 Start with a template
  • H2 (empty)
  • H2 The only platform that can support your company at any scale

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

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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: #2e3c54
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::
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.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Content Not Found • Asana ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
11 icon(s) detected
REVIEW
11 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
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 24 passed
REVIEW
83

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

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms div.siteFooter__secondary__col > div.terms-and-privacy > div.css-yuiwnc > div#/terms
Privacy div.siteFooter__secondary__col > div.terms-and-privacy > div.css-yuiwnc > div#/terms/privacy-statement
Download the Asana iOS app div.siteFooter__secondary__col-wrapper > div.siteFooter__secondary__col > div.css-yuiwnc > div#https://itunes.apple.com/us/app/asana-mobile/id489969512?mt=8
Download the Asana Android app div.siteFooter__secondary__col-wrapper > div.siteFooter__secondary__col > div.css-yuiwnc > div#https://play.google.com/store/apps/details?id=com.asana.app

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Project intake Capture, prioritize, and assign requests automatically so your … div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Product launches Coordinate teams, tasks, and timelines to keep every launch o… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Organizational planning Address business needs quickly by analyzing progress, … div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Resource planning Visualize how teams are staffed and what resources are avail… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Goal management Connect everyone's work to the organizational goals they suppo… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Employee onboarding Standardize onboarding to help new employees make an impac… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Microsoft Teams div.css-1ik4zij > div.css-1eebgoq > div.css-1adq0r4 > div.appMarquee-row
Asana is our air traffic control. We have the visibility to scale production an… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Having one centralized ecosystem that brings all doers and stakeholders togethe… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide

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
85% of Fortune 100 companies choose Asana¹ div.css-1i6a9mr > div.css-4ofcuc > div.css-1t6egar > h4.css-mai43k
Campaign management div.css-1tj5lnt-link-2 > div.css-c10hy > div > h5#info-card-title-campaign-management
Stay secure and compliant with Asana Gov div.css-zt3vru > div.css-allxq9-p1-p2-p1 > div.css-0 > h5
Simon Levinson div.css-vii74e > div.css-j0ozid > div.css-1kuaip6 > h6
Try the Asana demo div.css-8ulzpr > a.css-1pf1mn9 > div.css-n01hrm > h4.css-rqx2h3

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.slick-slider > ul.slick-dots > li.slick-active > button
2 div.slick-slider > ul.slick-dots > li > button
3 div.slick-slider > ul.slick-dots > li > button
4 div.slick-slider > ul.slick-dots > li > button

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.device-android html.device-android

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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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 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 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
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●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
○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
○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.
○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>`.
○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.
A+
Alt Text Quality
All 74 images OK
PASS
All 74 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
22 decorative image(s) correctly marked
Info::
51 image(s) with good alt text
74 images 51 good alt text 22 decorative
IssueCount
too long1 image(s)
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 Supercharge your tea…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The platform for hum…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 See how Asana keeps …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What sets Asana apar…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect over 300+ in…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The world’s top co…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get started easily21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The only platform th…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 PLATFORM21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CAPABILITIES21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ASANA AI21.00:13.0:1
#000000
#FFFFFF
Pass
h3 PLANS21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Company Type21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Teams21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Industries21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Use Cases21.00:13.0:1
#000000
#FFFFFF
Pass
h3 LEARN21.00:13.0:1
#000000
#FFFFFF
Pass
h3 SUPPORT21.00:13.0:1
#000000
#FFFFFF
Pass
h3 SERVICES21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Maximize campaign RO…21.00:13.0: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.

Send Feedback