Accessibility Conformance Reports
Available reports:
Talend Studio – Accessibility Conformance Report (International Edition)
Talend Management Console – Accessibility Conformance Report (International Edition)
PDF downloads:
[Talend Studio] Accessibility Conformance Report
International Edition
(Based on VPAT® Version 2.4)
Name of Product/Version:
Talend Studio
Report Date:
May 11, 2023
Product Description:
Talend Studio v8 (R2023-04). Talend Studio is a developer environment. It is where the jobs get developed and sent for execution through the Talend Management Console. This is a graphical development environment, an IDE.
Contact Information:
Notes:
The testing process was carried out in compliance to the WCAG 2.1 AA guidelines. The product was not found to be supportive. The product is not accessible for disabled users.
As a summary, almost entire content and elements of software are not accessible through screen reader and keyboard. The software is not navigable.
Accessibility for Americans with Disabilities Act (ADA) website compliance requires all public and (large) private organizations to make their websites and web content conform with mandatory accessibility standards (WCAG 2.0). WCAG is simply a set of formal guidelines on how to develop accessible web content. These standards represent a higher level of accessibility than 508 standards, although they are identical or very similar. WCAG focuses primarily on HTML accessibility.
Evaluation Methods Used:
The product was tested against all of the applicable 50 success criteria within the Web Content Accessibility Guidelines (WCAG) 2.1 Conformance Level A and AA. The testing methodology included a combination of automated testing, manual testing conducted via paired testing methodology involving two testers, one of them is a non-sighted and the other is a sighted accessibility expert. This testing methodology ensures that every aspect related to accessibility and user experience is included in our analysis. Below is a list of some of the technologies and environments used:
- Assistive technologies – Screen readers NVDA, Jaws, Voiceover
- Keyboard only interaction
- Automated tools – Axe, Color Contrast Analyzer
- Desktop- Windows 10, Mac
The combinations of technologies used were the following:
- Windows 10 with JAWS and NVDA
- Mac with Voiceover
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline | Included In Report |
---|---|
Web Content Accessibility Guidelines 2.0 |
Level A (Yes) Level AA (Yes) Level AAA (No) |
Web Content Accessibility Guidelines 2.1 | 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) | (No) |
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 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.x 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
Notes:
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Graphics are not used in the software application. |
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Audio and video only content is not present in the application. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Multimedia content is not present in the application. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Multimedia content is not present in the application. |
1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Color is not used to indicate any type of information on the application. |
1.4.2 Audio Control (Level A)Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Audio is not available in the application that plays automatically as soon as the page is launched. |
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: The application has support for keyboard interaction, but the tab focus indicator is not visible on elements. That’s why the user is not able to identify which keyboard focus element is present. |
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: The application has support for keyboard interaction, but the tab focus indicator is not visible on elements. That’s why the user is not able to check the keyboard trap violation. |
2.1.4 Character Key Shortcuts (Level A 2.1 only) Also applies to: EEN 301 549 Criteria
|
Not applicable | Remark: Character key shortcuts are not required in the application to operate any feature that clash with the predefined screen reader shortcuts. |
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Session time out functionality is not present in the application. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Moving content is not present in the application. |
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Flashing / blinking content is not present in the application. |
2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Skip to the main content link is not required in the application. |
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Descriptive and unique page titles are not provided for different pages in the application. |
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
2.5.1 Pointer Gestures (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
2.5.2 Pointer Cancellation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
2.5.3 Label in Name (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
2.5.4 Motion Actuation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Functionality is not in the application that can be operated by device motion or user motion. |
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Lang attribute ‘En’ is provided in the application. |
3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The application does not have any feature/functionality that triggers automatically on receiving the focus. |
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: This evaluation is not applicable for the software application. |
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
Table 2: Success Criteria, Level AA
Notes:
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Live multimedia content is not present in the application. |
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Multimedia content is not present in the application that requires audio description. |
1.3.4 Orientation (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The application provides support and works equally in both landscape/portrait orientation modes. |
1.3.5 Identify Input Purpose (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exception: |
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: This success criteria is not applicable for the software application. |
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Information is not present in the application that is in the form of a text image. |
1.4.10 Reflow (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: The success criteria are not applicable for the software application. |
1.4.11 Non-text Contrast (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exceptions: |
1.4.12 Text Spacing (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: The success criteria are not applicable for the software application. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Remark: There are web elements available in the application that trigger the additional content after receiving pointer hover or keyboard focus. |
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Multiple ways of navigation are not required in the application. |
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: The tab focus indicator is not visible on interactive elements. |
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: The application content is available in the English language only. There is not a change in language throughout the application. |
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Repeated components are occurring in the same order on every page of the application. This helps the screen reader and cognitive user to predict the location of different web elements on each page. |
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Elements that have the same functionality across multiple pages in the application have the same labels or same name. |
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: This success criterion is related to legal commitment, financial data, etc., which involves serious risk, if an option is not provided for users to review or revert the data before submission. However, the application does not have any forms where this risk is associated. |
4.1.3 Status Messages (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
Table 3: Success Criteria, Level AAA
Notes: Not applicable
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
302.1 Without Vision | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
302.2 With Limited Vision | Partially supports | Remark: There are a few instances where the low vision user will find it difficult to recognize web elements because the color contrast ratio is less than the standard ratio. Exceptions: |
302.3 Without Perception of Color | Not applicable | Remark: Color is not used to indicate any type of information on pages such as a bulleted point, section headings, link, button, etc. |
302.4 Without Hearing | Not applicable | Remark: Multimedia content is not present in the application. |
302.5 With Limited Hearing | Not applicable | Remark: Multimedia content is not present in the application |
302.6 Without Speech | Not applicable | Remark: Speech is not required to complete any task or activity. |
302.7 With Limited Manipulation | Not applicable | Remark: There are not any complicated keyboard actions required in the application to perform any task, which requires simultaneous actions or fine motor control. |
302.8 With Limited Reach and Strength | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | Remark: 1. The application does not have any moving text/images/animations that
disrupt reading. |
Chapter 4: Hardware
Notes: This website is not subjected to the requirements of this section
Chapter 5: Software
Notes:
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA | See WCAG 2.x section | See information in WCAG 2.x section |
502 Interoperability with Assistive Technology | Heading cell – no response required | Heading cell – no response required |
502.2.1 User Control of Accessibility Features | Not applicable | Remark: The application is not considered platform software as defined by Section 508. |
502.2.2 No Disruption of Accessibility Features | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3 Accessibility Services | Heading cell – no response required | Heading cell – no response required |
502.3.1 Object Information | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.2 Modification of Object Information | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.3 Row, Column, and Headers | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.4 Values | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.5 Modification of Values | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.6 Label Relationships | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.7 Hierarchical Relationships | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screenreader is not recognizing the software content. |
502.3.8 Text | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.9 Modification of Text | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.10 List of Actions | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.11 Actions on Objects | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.12 Focus Cursor | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.3.13 Modification of Focus Cursor | Not applicable | Remark: The application is not considered platform software as defined by Section 508. |
502.3.14 Event Notification | Does not support | Remark: The content and elements of the software application are not accessible through the screen reader. The screen reader is not recognizing the software content. |
502.4 Platform Accessibility Features | Not Applicable (platform software) | Remark: The application is not considered platform software as defined by Section 508. |
503 Applications | Heading cell – no response required | Heading cell – no response required |
503.2 User Preferences | Not applicable | Remark: Browser zoom is not applicable in the desktop application. |
503.3 Alternative User Interfaces | Not applicable | Remark: Application does not provide any alternative user interfaces that function as assistive technology. |
503.4 User Controls for Captions and Audio Description | Heading cell – no response required | Heading cell – no response required |
503.4.1 Caption Controls | Not applicable | Remark: Audio and video only content is not present in the application. |
503.4.2 Audio Description Controls | Not applicable | Remark: Audio and video only content is not present in the application. |
504 Authoring Tools | Heading cell – no response required | Heading cell – no response required |
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) | See WCAG 2.x section | See information in WCAG 2.x section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not applicable | Remark: A feature to convert content from one format to another is not present in the application. |
504.2.2 PDF Export | Not applicable | Remark: A PDF export feature is not in the application. |
504.3 Prompts | Not applicable | Remark: A prompt in the application to create content is not present in the application. |
504.4 Templates | Not applicable | Remark: Templates are not provided in the application to create content. |
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 |
602 Support Documentation | Heading cell – no response required | Heading cell – no response required |
602.2 Accessibility and Compatibility Features | Does not support | Remark: A section is not available in the application that describes information regarding accessibility and its compatibility with different assistive technologies. |
602.3 Electronic Support Documentation | See WCAG 2.1 section | The application provides Help content pages which gives information on available content. People with visual disability are not able to read and understand this information easily because user guide PDFs are not tagged for screen reader user. |
602.4 Alternate Formats for Non-Electronic Support Documentation | Not applicable | Remark: The application provides information through the digital medium and it allows users to access the ‘Help’ feature for further help regarding the digital content and documentation. There is not a requirement for alternate formats for non-electronic support documentation because support services are available electronically. |
603 Support Services | Heading cell – no response required | Heading cell – no response required |
603.2 Information on Accessibility and Compatibility Features | Does not support | A accessibility information section is not available in the application that provides information regarding accessibility and compatibility features. |
603.3 Accommodation of Communication Needs | Does not support | A phone number/email address is not mentioned under the support section where a user can contact tech support. |
Legal Disclaimer (Talend)
Talend, Inc. is committed to making the digital property accessible to all users, including those with disabilities. Our goal is to provide an accessible digital property that conforms to Section 508 Guidelines and the World Wide Web Consortium's Accessibility Guidelines
(WCAG) 2.1 Level AA. Some existing content may not be in compliance, and some content may meet only the minimum required compliance standards. This will be resolved as we continue our efforts to monitor and maintain acceptable compliance levels. We continue to make every effort to test the digital property and to remove barriers that prevent persons with disabilities from interacting with or accessing information made available on our website. If we become aware of content that does not conform to the WCAG 2.1 Level AA standards, we will make every reasonably good faith effort to make the content conform to the standards.
While we strive to adhere to the accepted guidelines and standards for accessibility and usability, it is not always possible to do so in all areas of the digital property, particularly as it relates to content by third parties. Talend, Inc. is not responsible for ensuring that thirdparty content, software/tools, widgets, Add-ins, APIs, etc., which are not owned by Talend, Inc. but are otherwise located on or linked to the Talend, Inc. digital property, conform to WCAG 2.1 Level AA, and shall not be liable if they are inaccessible to individuals with disabilities.
While this policy does provide the standard for individuals with disabilities to access digital property-based information, this policy cannot anticipate every accessibility need, due to known limitations of existing technology. There may be other circumstances, independent of technology that may limit the accessibility of the Talend, Inc.
Ongoing Efforts to Ensure Accessible Content:
Talend, Inc. uses the Web Content Accessibility Guidelines (WCAG) version 2.1 as its guiding principle. As we develop new pages and functionality, the principles of accessible design and development are an integral part of conception and realization.
We continually test content and features for WCAG 2.1 Level AA compliance and remediate any issues to ensure we meet or exceed the standards. Testing of our digital content is performed by our accessibility experts using automated testing, screen readers, a color
contrast analyzer, keyboard-only navigation techniques, and a variety of bookmarklets.
Summary of Accessibility Features
- Navigational aids are provided on all pages. Skip navigation links have been incorporated to facilitate keyboard navigation and to bypass groups of links on a page and jump directly to main content.
- The title attribute has been used to make linked text more meaningful or to indicate if the link opens a new browser window.
- Type ahead search results are announced automatically.
- Radio buttons are grouped together.
How Can We Help?
We welcome any comments, questions, or feedback on our site. If you notice aspects of our site that aren’t working for you or your assistive technology, please let us know.
We try to respond to feedback within 5 business days.
[Talend Management Console] Accessibility Conformance Report
International Edition
(Based on VPAT® Version 2.4)
Name of Product/Version:
Talend Management Console
Report Date:
May 11, 2023
Product Description:
TMC or Talend Management Console is a product which is part of Talend Cloud platform. The Management Console is mostly used by administrators (as opposite to developers which are more on Studio). In the TMC, as an admin, you can: define roles and accesses for developers, operators and other roles depending on the organization you work for. You can also set up connections to projects/jobs that are developed in the Studio, set up the execution engines and schedule, automate and orchestrate the execution of “Jobs”.
Contact Information:
Notes:
The testing process was carried out in compliance to the WCAG 2.1 AA guidelines. The product was found to be overall partially supportive.
As a summary, there are some elements and functionalities that are not being supported such as alert message, role, headings etc. However, the page is navigable, and, in most cases, there is a solution for the features that are not being supported.
Accessibility for Americans with Disabilities Act (ADA) website compliance requires all public and (large) private organizations to make their websites and web content conform with mandatory accessibility standards (WCAG 2.0). WCAG is simply a set of formal guidelines on how to develop accessible web content. These standards represent a higher level of accessibility than 508 standards, although they are identical or very similar. WCAG focuses primarily on HTML accessibility.
Evaluation Methods Used:
The product was tested against all of the applicable 50 success criteria within the Web Content Accessibility Guidelines (WCAG) 2.1 Conformance Level A and AA. The testing methodology included a combination of automated testing, manual testing conducted via paired testing methodology involving two testers, one of them is a non-sighted and the other is a sighted accessibility expert. This testing methodology ensures that every aspect related to accessibility and user experience is included in our analysis. Below is a list of some of the technologies and environments used:
- Assistive technologies – Screen readers NVDA, Jaws, Voiceover, Talkback
- Keyboard only interaction, Browser zoom
- Automated tools – Axe, Color Contrast Analyzer
- Browsers – Chrome, Edge, Firefox, Safari
- Accessibility plugins – Axe
- Desktop- Windows 10, Mac, Android, iOS
The combinations of technologies used were the following:
- Windows with Firefox/ Chrome and NVDA
- Windows with Chrome and Jaws
- Windows with Edge and Jaws
- Windows with Chrome and Axe
- Windows with Google Chrome and Zoom
- Windows with Google Chrome and Color Contrast Analyzer
- Mac with Safari and Voiceover
- iOS with Safari and Voiceover
- Android with Chrome and Talkback
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline | Included In Report |
---|---|
Web Content Accessibility Guidelines 2.0 |
Level A (Yes) Level AA (Yes) Level AAA (No) |
Web Content Accessibility Guidelines 2.1 | 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) | (No) |
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 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.x Success Criteria, they are scoped for full pages, complete processes, and accessibilitysupported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
Notes:
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Proper alt text has been provided to all the graphics present in the application and decorative images are hidden for screen reader users. |
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Audio and video only content is not present in the application. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Multimedia content is not present in the application. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Multimedia content is not present in the application. |
1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exceptions: |
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The screen reader reads all the content present in the application in a meaningful sequence with the help of arrow keys and other reading commands. |
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Exceptions: |
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Color is not used to indicate any type of information on the application. |
1.4.2 Audio Control (Level A)Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Audio is not available in the application that plays automatically as soon as the page is launched. |
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The application has good support for keyboard interaction and all the interactive elements are accessible using the keyboard commands. It works similarly for both screen reader and keyboard-only users. |
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Application has good support for keyboard interaction and there is not a keyboard trap issue throughout the application. |
2.1.4 Character Key Shortcuts (Level A 2.1 only) Also applies to: EEN 301 549 Criteria
|
Not applicable | Remark: Character key shortcuts are not required in the application to operate any feature which clash with the predefined screen reader shortcuts. |
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Session time out functionality is not present in the application. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Moving content is not present in the application. |
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Flashing / blinking content is not present anywhere in the application. |
2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Skip to the main content link is present on top of all web pages. |
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Descriptive and unique page titles are not provided for different pages in the application. |
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exceptions: |
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exception: |
2.5.1 Pointer Gestures (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Remark: All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture. |
2.5.2 Pointer Cancellation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The entire application supports pointer cancellation as the down-event and is not used to execute any part of the function. Elements are triggered only by using the up-event. |
2.5.3 Label in Name (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The visual label matches the accessible or programmatic name for all of the elements. |
2.5.4 Motion Actuation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Functionality is not in the application that can be operated by device or user motion. |
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Lang attribute ‘En’ is provided for the all the pages in the application. |
3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The application does not have any feature / functionality that triggers automatically on receiving the focus. |
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Change of context does not happen anywhere in the application when changing the setting of any UI component. |
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The error message which appears is descriptive and sufficient enough to understand its purpose. |
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark:
Exceptions: |
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: This evaluation requires a code level check to validate the start and end tags, elements nesting according to specification, duplicate attribute etc. While reviewing the source code of the application using the axe tool, we came across code level issues on pages that could cause parsing or compatibility concerns. |
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exceptions: |
Table 2: Success Criteria, Level AA
Notes:
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Live multimedia content is not present in the application. |
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Multimedia content is not present in the application that requires audio description. |
1.3.4 Orientation (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The application provides supports and works equally in both landscape/portrait orientation modes. |
1.3.5 Identify Input Purpose (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: The purpose of each input field collecting information about the user is not programmatically determined. Auto complete attribute is not present in the application. |
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exception: |
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: The entire page content truncated at 200% browser zoom. |
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Information is not present in the application that is in the form of Image of text. |
1.4.10 Reflow (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Entire page content truncated at 400% browser zoom. |
1.4.11 Non-text Contrast (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exceptions: |
1.4.12 Text Spacing (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The application provides support for people with low vision and cognitive disabilities because it allows users to view application content in the desired text (letter, word, line and paragraph) spacing. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exception: |
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: Multiple ways of navigation are not required in the application. |
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Headings present in the application are descriptive enough to understand their purpose and sufficient labels are provided for each form field wherever a descriptive label is needed. |
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
|
Partially supports | Remark: Exception: |
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: The application content is available in the English language only. There isn’t a change in language throughout the application. |
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Repeated components are occurring in the same order on every page of the application. This helps screen reader and cognitive users predict the location of different web elements on each page. |
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Remark: Elements that have the same functionality across multiple pages in the application have the same labels or name. |
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
|
Supports | Remark: The error message that appears is descriptive and precise. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
|
Not applicable | Remark: This success criterion is related to legal commitment, financial data, etc. This involves serious risk an option is not provided for users to review or revert the data before submission. The application does not have any forms where this risk is associated. |
4.1.3 Status Messages (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
|
Does not support | Remark: Exceptions: |
Table 3: Success Criteria, Level AAA
Notes: Not applicable
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
302.1 Without Vision | Partially supports | Remark:
Exceptions: |
302.2 With Limited Vision | Partially supports | Remark: Exceptions: |
302.3 Without Perception of Color | Not applicable | Remark: Color is not used to indicate any type of on page information such as bulleted point, section headings, link, button, etc. |
302.4 Without Hearing | Not applicable | Remark: Multimedia content is not present in the application. |
302.5 With Limited Hearing | Not applicable | Remark: Multimedia content is not present in the application. |
302.6 Without Speech | Not applicable | Remark: Speech is not required to complete any task or activity. |
302.7 With Limited Manipulation | Not applicable | Remark: There are no complicated keyboard actions required in the application to perform any task that requires simultaneous actions or fine motor control. |
302.8 With Limited Reach and Strength | Supports (keyboard) | Remark: The application has good support for keyboard interaction because the interactive elements are accessible using the keyboard commands. |
302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | Remark: 1. The application does not have any moving text/images/animation that
disrupts reading. |
Chapter 4: Hardware
Notes: This website is not subjected to the requirements of this section
Chapter 5: Software
Notes: This website is not subjected to the requirements of this section
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 |
602 Support Documentation | Heading cell – no response required | Heading cell – no response required |
602.2 Accessibility and Compatibility Features | Does not support | Remark: A section is not available in the application that describes the information regarding accessibility and its compatibility with different assistive technologies. |
602.3 Electronic Support Documentation | See WCAG 2.1 section | The application provides Help content pages which gives information on available content. People with visual disabilities are no able to read and understand this information easily because the user guide PDFs are not tagged for screen reader users. |
602.4 Alternate Formats for Non-Electronic Support Documentation | Not applicable | Remark: The application provides information through the digital medium and it allows users to access the ‘Help’ feature for further help regarding digital content and documentation. There is not a requirement of alternate formats for non-electronic support documentation because support services are available electronically. |
603 Support Services | Heading cell – no response required | Heading cell – no response required |
603.2 Information on Accessibility and Compatibility Features | Does not support | An accessibility information section is not available in the application which provides information regarding accessibility and compatibility features. |
603.3 Accommodation of Communication Needs | Does not support | A phone number/email address is not mentioned in the support section where the user can contact tech support. |
Legal Disclaimer (Talend)
Talend, Inc. is committed to making the digital property accessible to all users, including those with disabilities. Our goal is to provide an accessible digital property that conforms to Section 508 Guidelines and the World Wide Web Consortium's Accessibility Guidelines (WCAG) 2.1 Level AA. Some existing content may not be in compliance, and some content may meet only the minimum required compliance standards. This will be resolved as we continue our efforts to monitor and maintain acceptable compliance levels. We continue to make every effort to test the digital property and to remove barriers that prevent persons with disabilities from interacting with or accessing information made available on our website. If we become aware of content that does not conform to the WCAG 2.1 Level AA standards, we will make every reasonably good faith effort to make the content conform to the standards.
While we strive to adhere to the accepted guidelines and standards for accessibility and usability, it is not always possible to do so in all areas of the digital property, particularly as it relates to content by third parties. Talend, Inc. is not responsible for ensuring that thirdparty content, software/tools, widgets, Add-ins, APIs, etc., which are not owned by Talend, Inc. but are otherwise located on or linked to the Talend, Inc. digital property, conform to WCAG 2.1 Level AA, and shall not be liable if they are inaccessible to individuals with disabilities.
While this policy does provide the standard for individuals with disabilities to access digital property-based information, this policy cannot anticipate every accessibility need, due to known limitations of existing technology. There may be other circumstances, independent of technology that may limit the accessibility of the Talend, Inc.
Ongoing Efforts to Ensure Accessible Content:
Talend, Inc. uses the Web Content Accessibility Guidelines (WCAG) version 2.1 as its guiding principle. As we develop new pages and functionality, the principles of accessible design and development are an integral part of conception and realization.
We continually test content and features for WCAG 2.1 Level AA compliance and remediate any issues to ensure we meet or exceed the standards. Testing of our digital content is performed by our accessibility experts using automated testing, screen readers, a color contrast analyzer, keyboard-only navigation techniques, and a variety of bookmarklets.
Summary of Accessibility Features
- Navigational aids are provided on all pages. Skip navigation links have been incorporated to facilitate keyboard navigation and to bypass groups of links on a page and jump directly to main content.
- The title attribute has been used to make linked text more meaningful or to indicate if the link opens a new browser window.
- Type ahead search results are announced automatically.
- Radio buttons are grouped together
How Can We Help?
We welcome any comments, questions, or feedback on our site. If you notice aspects of our site that aren’t working for you or your assistive technology, please let us know.
We try to respond to feedback within 5 business days.