ASANA Web Application March 2025 release
Accessibility Conformance Report published by Asana
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 32 criteria
- Supports
- 23
- Partially supports
- 3
- Does not support
- 0
- Not applicable
- 6
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 15
- Partially supports
- 4
- Does not support
- 0
- Not applicable
- 5
- Not evaluated
- 0
Source: View the original report published by Asana.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (56)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | Asana provides text alternatives to non-text content such as buttons, and graphics. Programmatic labels allow assistive technology users to understand the nature and purpose of non-text content. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | There is no audio-only or video-only time-based media available in the current iteration of the product. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Synchronized captions are available for the video content (e.g., tutorial video). |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | A transcript is provided for the video content from the caption menu (e.g., tutorial video). |
| 1.3.1 | Info and Relationships | A | Partially Supports | For most of the elements like buttons, checkboxes, and toggle buttons, screen readers announce associated labels. However, there are exceptions: ● Screen reader automatically announces all top three side bar options (Home, My tasks, Inbox) after login. ● On the task pane, the screen reader does not announce the tooltip text present on the "Make public" button. |
| 1.3.2 | Meaningful Sequence | A | Supports | All the content is in a meaningful and correct reading sequence that can be programmatically determined. |
| 1.3.3 | Sensory Characteristics | A | Supports | Instructions provided do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. Hints, descriptive text, and labels are used. |
| 1.4.1 | Use of Color | A | Supports | Color is not used generally as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. e.g., using red color indicators for the wrong email/ password also shows the error message with it, and information is conveyed to the user this way in other instances as well. |
| 1.4.2 | Audio Control | A | Not Applicable | Asana does not include any automatically playing audio or video content. |
| 2.1.1 | Keyboard | A | Partially Supports | Asana supports standard keyboard navigation and input functions (such as pressing [Tab] to move between input fields, pressing the arrow keys to move between list items, and pressing [Space] or [Enter] to make selections). However, there are exceptions: ● Keyboard focus is not being set on the remove project icon for added projects on the quick task pane. ● Keyboard focus does not set on the "Copy collaborator" button on the quick task pane and task pane. |
| 2.1.2 | No Keyboard Trap | A | Supports | No keyboard trap issues are present in Asana features. |
| 2.1.4 | Character Key Shortcuts | A | Supports | The keyboard shortcut for a user interface component is only active when that component has focus. |
| 2.2.1 | Timing Adjustable | A | Supports | Asana does not have session timeout functionality implemented for the majority of features. Additionally there is an option to set a duration for the pop-up notification. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | Asana does not include moving, blinking, scrolling, or auto-updating information. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Asana does not use flashing interface elements. |
| 2.4.1 | Bypass Blocks | A | Supports | Skip links are provided to help users efficiently bypass repetitive elements and skip to the main content. |
| 2.4.2 | Page Titled | A | Supports | Web pages within Asana have descriptive titles that indicate the topic and purpose of each page. |
| 2.4.3 | Focus Order | A | Partially Supports | Asana supports the focus order on the majority of elements. However, there are exceptions: ● On the Home page, focus gets lost and reset on closing the Customization pane, removing the widget. ● On the Home page, focus resets on expanding and collapsing task pane, making a task as private or public, adding or removing due date on task from the My tasks widget. ● On the search modal, focus resets after the "More" option, and on closing "More" menu using ESC key. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | In Asana, the purpose of each link is determined from the link text alone. |
| 2.5.1 | Pointer Gestures | A | Not Applicable | Asana does not rely on multipoint or path-based gestures for operation. |
| 2.5.2 | Pointer Cancellation | A | Supports | Asana allows for pointer cancellation to prevent accidental or erroneous pointer input. |
| 2.5.3 | Label in Name | A | Supports | Accessible names of all the user interface controls match with their visual labels. |
| 2.5.4 | Motion Actuation | A | Not Applicable | Asana does not include functionality offered through motion. |
| 3.1.1 | Language of Page | A | Supports | In Asana, the pages have the language attribute on the HTML element to specify the default language. |
| 3.2.1 | On Focus | A | Supports | When any component receives focus, it does not initiate any unintended change of context. |
| 3.2.2 | On Input | A | Supports | Asana does not change the context of use without the user initiating an explicit action. |
| 3.2.6 | Consistent Help | A | Supports | In Asana, help is available and displayed in a consistent location. |
| 3.3.1 | Error Identification | A | Supports | Asana clearly identifies the input error and errors and is described to the user in text in the flow like Reset Email, Change Password, and Profile Settings. |
| 3.3.2 | Labels or Instructions | A | Supports | Asana have provided clear labels and instructions to the |
| 3.3.7 | Redundant Entry | A | Supports | In Asana, no processes require users to enter the same information more than once within the same session until it is essential. |
| 4.1.1 | Parsing | A | Supports | For WCAG 2.0 and the 508 standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata. |
| 4.1.2 | Name, Role, Value | A | Supports | The name, role, and value used in the user interface elements are available to assistive technologies via HTML which describes the identity, operation, and state. |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Asana has no live videos or audio. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Asana has a couple of videos for which an audio description is also provided. |
| 1.3.4 | Orientation | AA | Not Applicable | Asana website does not support orientation [As it is specific to Mobile Applications only]. |
| 1.3.5 | Identify Input Purpose | AA | Supports | Asana provides capabilities for auto-complete. |
| 1.4.3 | Contrast (Minimum) | AA | Supports | The visual presentation of the text in Asana provides a sufficient contrast ratio of 4.5:1. |
| 1.4.4 | Resize text | AA | Supports | Asana is responsive and content gets resized when the browser zoom level is set to 200%. |
| 1.4.5 | Images of Text | AA | Not Applicable | Asana does not contain any images with text content. |
| 1.4.10 | Reflow | AA | Partially Supports | The content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions in a responsive view. However, there are exceptions: ● The Account setup page during onboarding is not responsive. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Asana provides sufficient contrast for non-text content in most places. However, there are a significant amount of non-text elements that fail minimum contrast across the site such as: ● Form field borders ● Grid borders |
| 1.4.12 | Text Spacing | AA | Supports | Asana allows users to override text spacing via bookmarklets to help improve the reading experience. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | In Asana, additional tooltips and menu content are dismissible, hoverable, and persistent. |
| 2.4.5 | Multiple Ways | AA | Supports | Asana has capabilities for incorporating navigation links and search functions in user interfaces. Application designers may choose to implement these techniques as they see fit (e.g., Search, Sidebar, Invite, Asana object linking). |
| 2.4.6 | Headings and Labels | AA | Supports | Descriptive headings and subheadings are used in content where appropriate. |
| 2.4.7 | Focus Visible | AA | Partially Supports | In most places, the keyboard focus indicator is visible on elements like buttons, input fields, checkboxes, tabs, dropdowns, etc. However, there are exceptions: ● The "Show options" button in the Home page portfolio widget receives keyboard focus but the element and focus ring is not visible. ● The Chat icon on the Contact Support page has a focus ring, but it is not sufficiently visible. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Supports | Any interactive component receiving keyboard focus remains at least partially visible to the user. |
| 2.5.7 | Dragging Movements | AA | Supports | All interactions that require drag and drop have alternative ways to interact that do not require dragging movements like attaching a file in a task, rearranging tasks etc,. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | All targets for pointer inputs meet the minimum required size or are accessible via an alternative means. |
| 3.1.2 | Language of Parts | AA | Not Applicable | In Asana, the language of a page can be programmatically determined. However, there is no content in a different language than the primary selected language. |
| 3.2.3 | Consistent Navigation | AA | Supports | Asana uses the same navigation mechanisms across pages. |
| 3.2.4 | Consistent Identification | AA | Supports | Asana provides standard components ensuring consistent functionality and presentation across pages for Project, Search, and Sidebar. |
| 3.3.3 | Error Suggestion | AA | Supports | Asana provides possible suggestions with the elements where there is a chance of error. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | No legal or financial data is used in the scope of the selected flow of Asana. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Asana provides third-party OAuth and other SSO authentication mechanisms to provide alternatives to the default username and password. |
| 4.1.3 | Status Messages | AA | Partially Supports | The status messages are provided to the user when needed, e.g., when a user deletes any task. However, there are exceptions: ● No acknowledgement via screen reader when the Home page finishes loading. ● Not notifying the user when the widget is removed or, on marking a task complete/incomplete on the Home page. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.