Aha! application
Voluntary Product Accessibility Template
Version 2.4 — International Edition
Report Date: 12/13/2021
This document is provided for information purposes only and the contents hereof are subject to change without notice. Aha! does not warrant that this document is error-free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Aha! specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Aha! further makes no representation concerning the ability of assistive technologies or other products to interoperate with Aha! software or services.
Overview
Aha! provides a powerful suite of products for product development teams:
Aha! Roadmaps enables product teams to set brilliant strategy, prioritize features, and share visual plans
Aha! Ideas helps organizations crowdsource feedback, engage in the community, and develop customer empathy
Aha! Develop provides a fully extendable agile development tool for engineering teams
This VPAT, or Voluntary Product Accessibility Template, is the result of an accessibility audit conducted by a third-party company specializing in accessibility testing, auditing, and remediation. As noted below, the audit was performed to the Web Content Accessibility Guideline (WCAG) 2.1 Level AA standard.
The audit was performed in an Aha! account with Roadmaps, Ideas, and Develop enabled.
The first section of this report provides an overview of the standard/guidelines and the terms used in the report. The second section details how our software conforms to the WCAG 2.1 AA guidelines. There are three columns in tables 1 and 2:
The first column details the success criteria evaluated in the audit
The second column states the software's conformance level
The third column shares additional remarks and explanations
Applicable standards and guidelines
This report covers the degree of conformance for the following accessibility standards and guidelines:
Standard/Guideline | Included in report |
Level A (Yes) Level AA (Yes) Level AAA (No) | |
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | Yes |
EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, - V3.1.1 (2019-11) | Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criterion.
Does Not Support: The majority of product functionality does not meet the criterion.
Not Applicable: The criterion is not relevant to the product.
Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.1 AA Report
Tables 1 and 2 also document conformance with:
EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.1 AA Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
Criteria | Conformance Level | Remarks and Explanations | ||
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Does Not Support | Web: Most graphs/charts are missing alternative text to provide context. Most decorative icons receive screen reader focus where nothing goes announced. | ||
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No video/audio content is present. | ||
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No prerecorded video is present. | ||
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No video content is present. | ||
1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Many headings are missing when visually implied or are not marked up in a hierarchical fashion. Some controls containing icons to visually imply purpose are missing accessible names. Context for some elements need further programmatic explanations to provide clear purpose for them. | ||
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Focus will occasionally move through the page in an order that doesn’t match the visual sequence intended. Some elements that are shown when activated are not placed in the focus order logically as users must navigate through the entire page before reaching the shown content. | ||
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components. | ||
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Links are often identified by color alone; links do not have another means to identify them such as an underline in any case. Colors used for graphs/charts are always accompanied by text elements to provide context programmatically. | ||
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No audio plays automatically on any page. | ||
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Every page has elements that would not receive focus. Many modals have close buttons that won’t receive focus. Calendars and graphs/charts often cannot be interacted with while using a keyboard interface alone. Some elements cannot be triggered with keyboard by pressing the space or enter keys. | ||
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: There are a few occasions where focus becomes trapped in a message field, a table, or in a loop on the page. Refreshing the page is the only way to free focus. | ||
2.1.4 Character Key Shortcuts (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Does Not Support | Web: The application uses 3 single character keyboard shortcuts. These cannot be remapped or disabled. | ||
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: The application does not require timed input from the user. | ||
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No content in the application moves, auto-updates, or is animated. | ||
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No content in the application blinks or flashes. | ||
2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Does Not Support | Web: There is no means to bypass repeated blocks of content such as hidden skip to main content links. | ||
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Multiple pages do not have titles that are unique or descriptive. | ||
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Focus does not return to buttons that open modals after they are closed. Similarly, focus does not remain trapped in modals and slide-out drawers. There are several instances where the focus will move to an element in the page first before moving back to the top of the page to move through the page sequentially. | ||
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: The purpose of links cannot always be determined. Many elements that behave like buttons are marked up as links. | ||
2.5.1 Pointer Gestures (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports | Web: The application does not rely on any path-based gestures. | ||
2.5.2 Pointer Cancellation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports | Web: All pointer actions can be cancelled. No actions occur on the down event of the mouse click. | ||
2.5.3 Label in Name (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports | Web: Symbolic text characters and labels are properly named. | ||
2.5.4 Motion Actuation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports | Web: No functionality is present that is triggered by device or user motion. | ||
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Does Not Support | Web: A default human language is not programmatically set for any pages. | ||
3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
501 (Web)(Software)
| Web: Partially Supports | Web: Some search fields trigger their search functionality upon receiving keyboard focus. | ||
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
501 (Web)(Software)
| Web: Supports | Web: All components have predictable effects. | ||
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Errors are accurately identified for the most part. There are some occasions where the error doesn’t indicate which field it is referring to, such as when creating an initiative. | ||
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Most labels are correctly implemented. However, fields that are required are not explicitly stated for any forms. | ||
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Does Not Support | Web: Parsing errors are present on most pages for the use of duplicate IDs attributes; this potentially causes assistive technologies to crash. | ||
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Does Not Support | Web: States such as checked, selected, expanded, etc. are not programmatically implemented. Many elements are missing accessible names while others are missing accessible roles as well. This is especially true for buttons that are depicted by icons as opposed to text. Buttons are often marked up as links. Table sorting functionality is not provided programmatically. |
Table 2: Success Criteria, Level AA
Criteria | Conformance Level | Remarks and Explanations | ||
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No live audio content is not present. | ||
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No video/audio is present. | ||
1.3.4 Orientation (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports | Web: Content does not restrict its view and operation to a single display orientation. | ||
1.3.5 Identify Input Purpose (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports | Web: No input fields collect information about the user, and therefore, no autofill attributes are present. | ||
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Many text elements do not meet minimum contrast thresholds. This is especially true for most of the grey text elements contained in the application. Charts and graphs can have text elements placed in them that do not meet contrast expectations because of the different colors used for the diagrams. | ||
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Does Not Support | Web: There is loss of content and functionality throughout the application when text is resized to 200%. | ||
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No images of text are present. | ||
1.4.10 Reflow (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Does Not Support | Web: The application is not functionable when the browser zoom is increased to 400%. Content becomes clipped and obscured while the scrollbar disappears, disallowing users to scroll through the page at all. | ||
1.4.11 Non-text Contrast (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Partially Supports | Web: Some instances occur where the visible focus indicator is hard to distinguish, especially for those with low vision or colorblindness. | ||
1.4.12 Text Spacing (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports | Web: Text spacing can be adjusted without loss content or functionality. | ||
1.4.13 Content on Hover or Focus (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports | Web: Hoverable content behaves as expected. | ||
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: There are multiple means of navigating through the application including navigational links, back buttons, and home buttons. | ||
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: Some headings in the application have buttons and/or links nested in them. However, all headings and labels accurately describe topic and purpose. | ||
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially Supports | Web: There are several instances where the keyboard focus indicator is not present. | ||
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No content in the application deviates from the default language. | ||
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: Navigational mechanisms that are repeated on multiple pages are in a consistent order. | ||
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: Repeated components are identified consistently. | ||
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: All errors are given suggestions that are valid for all users. | ||
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports | Web: No pages collect information from the user pertaining to legal commitments or financial transactions. | ||
4.1.3 Status Messages (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Does Not Support | Web: Errors are not announced upon displaying to the screen. Messages such as success and failure banners that display to the screen are also not announced. |
Table 3: Success Criteria, Level AAA
Notes: The Aha! application has not been evaluated for WCAG 2.1 AAA conformance.
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes: The site was not evaluated against chapter 3.
Chapter 4: Hardware
Notes: Chapter 4 does not apply to this product.
Chapter 5: Software
Notes: Chapter 5 does not apply to this product.
Chapter 6: Support Documentation and Services
Notes:
Criteria | Conformance Level | Remarks and Explanations |
601.1 Scope | Heading cell – no response required | Heading cell – no response required |
Heading cell – no response required | Heading cell – no response required | |
602.2 Accessibility and Compatibility Features | Does not support | Aha! does not have accessibility feature documentation. |
602.3 Electronic Support Documentation | See WCAG 2.1 AA report section | See WCAG 2.1 AA report section |
602.4 Alternate Formats for Non-Electronic Support Documentation | Supports | Product does not contain any print materials. |
Heading cell – no response required | Heading cell – no response required | |
603.2 Information on Accessibility and Compatibility Features | Does not support | Aha! does not have accessibility feature documentation. |
603.3 Accommodation of Communication Needs | Supports | Users can use telephone support, chat, and email for communication. Contact us
|
EN 301 549 Report
Chapter 4: Functional Performance Statements (FPS)
Notes: The site was not evaluated against chapter 4.
Chapter 5: Generic Requirements
Notes: Chapter 5 does not apply to this product.
Chapter 6: ICT with Two-Way Voice Communication
Notes: Chapter 6 does not apply to this product.
Chapter 7: ICT with Video Capabilities
Notes: Chapter 7 does not apply to this product.
Chapter 8: Hardware
Notes: Chapter 8 does not apply to this product.
Chapter 9: Web (see WCAG 2.1 AA report section)
Notes:
Chapter 10: Non-Web Software
Notes: Chapter 10 does not apply to this product.
Chapter 11: Software
Notes: Chapter 11 does not apply to this product.
Chapter 12: Documentation and Support Services
Criteria | Conformance Level | Remarks and Explanations |
12.1 Product documentation | Heading cell – no response required | Heading cell – no response required |
12.1.1 Accessibility and compatibility features | Does not support | Aha! does not have accessibility feature documentation. |
12.1.2 Accessible documentation | See WCAG 2.1 AA report section | See WCAG 2.1 AA report section |
12.2 Support Services | Heading cell – no response required | Heading cell – no response required |
12.2.2 Information on accessibility and compatibility features | Does not support | Aha! provides up-to-date support documentation at https://www.aha.io/support but there is no accessibility feature documentation. |
12.2.3 Effective communication | Supports | Users can use telephone support, chat, and email for communication. Contact us
|
12.2.4 Accessible documentation | See WCAG 2.1 AA report section | See WCAG 2.1 AA report section |
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Chapter 13 does not apply to this product.