amCharts 5 Accessibility Conformance Report
Download PDF version of this report
Revised Section 508 Edition
VPAT® Version 2.4 (February 2020)
Name of Product/Version
amCharts 5
Product Description
amCharts 5 is a collection of client-side JavaScript libraries for charts and maps.
Technical documentation for accessibility: https://www.amcharts.com/docs/v5/concepts/accessibility/
Report Date
Original publication date: October 26, 2021.
Revision 2: October 13, 2026. Covers amCharts 5.21.0.
Contact Information
For questions about this report, email contact@amcharts.com.
Notes
amCharts 5 is tested for compliance with WCAG 2.0 Success Criteria, Levels A and AA. Therefore, “Table 3: Success Criteria, Level AAA” is not included in the report.
The Revised Section 508 Report includes only “Chapter 3: Functional Performance Criteria” and “Chapter 5: Software”, because amCharts 5 is a software-only solution and the other chapters do not apply.
amCharts 5 is a programming library: end users do not use it directly as standalone software or a web page. It has no end-user documentation, so “Chapter 6: Support Documentation and Services” does not apply either.
JavaScript, the platform amCharts 5 is built on, is a web technology. Even in desktop and mobile applications, it runs in a browser-like environment. amCharts 5 is therefore evaluated for the web only, and all conformance levels in the tables apply to the web unless stated otherwise.
Evaluation Methods Used
The product was evaluated during development with two screen readers:
and with this diagnostic software:
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standards/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Revised 508 Standards and 255 Guidelines | (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.0 Report
Tables 1 and 2 also document conformance with:
- Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
Note: When reporting on conformance with the WCAG 2.0 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) | Supports | Built-in controls, such as buttons, legend items and scrollbar grips, come with text labels in aria-label. Data elements, such as columns, slices, bullets and map polygons, get text labels through their ariaLabel setting, which can include the element’s own data (for example series name, category and value). |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Supports | amCharts 5 displays no pre-recorded audio or video, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 1.2.2 Captions (Prerecorded) (Level A) | Supports | amCharts 5 displays no pre-recorded audio or video that would need captions, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Supports | amCharts 5 displays no pre-recorded audio or video that would need a description or media alternative, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 1.3.1 Info and Relationships (Level A) | Supports | Relationships between elements are exposed as text and ARIA attributes. For example, a column’s label can name the series it belongs to, and a legend item exposes whether its series is shown with aria-checked. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | Elements are read in a meaningful order: columns in a series follow the order of the data, and series follow the order they were added to the chart. The order can be changed with the Root’s tabindex and each element’s tabindexOrder setting. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Elements that users can operate also give text instructions through ARIA attributes. For example, a scrollbar grip reads out its current position, and a legend item reads out “Press ENTER to toggle”. |
| 1.4.1 Use of Color (Level A) | Supports | Color is not needed to tell data apart: pattern fills, and the built-in Patterns and Colorblind themes, can be used instead of or along with color. They are not enabled by default. |
| 1.4.2 Audio Control (Level A) | Supports | amCharts 5 plays no audio, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 2.1.1 Keyboard (Level A) | Supports | Everything that can be done with a mouse or touch can also be done with a keyboard. TAB moves between focusable elements. Arrow keys move draggable elements (such as scrollbar grips) and move between the members of a focusable group. ENTER or SPACE activates buttons and toggles (such as legend items). ESC hides a tooltip and ends a keyboard drag. The hoverOnFocus setting makes focus act as hover: the element shows its tooltip and hover state, and screen readers read the tooltip out. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | amCharts 5 uses standard TAB navigation. Focus can always leave a chart with TAB or SHIFT+TAB; no special keys are needed. |
| 2.2.1 Timing Adjustable (Level A) | Supports | amCharts 5 has no time limits, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | amCharts 5 does not start moving, blinking, scrolling or auto-updating content that lasts more than five seconds. Built-in animations, such as a chart appearing or a series being toggled, are short. Therefore, this criterion is classified as “Supports” as per VPAT recommendations. Implementers can add longer motion or auto-updating, such as a rotating globe or live data. They are then responsible for a way to pause or stop it. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | amCharts 5 has no flashing or blinking content, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 2.4.1 Bypass Blocks (Level A) | Supports | Elements in a focusable group (focusableGroup) take a single TAB stop, so users can move past a series with many elements in one step.The focusable setting can also take the whole chart, or any of its elements, out of the TAB order. |
| 2.4.2 Page Titled (Level A) | Supports | amCharts 5 renders elements of a page, not whole pages, so the page title is set by the host page. Charts and their common elements get default labels. Implementers can change these labels in code. |
| 2.4.3 Focus Order (Level A) | Supports | Focusable elements are focused in a meaningful order: columns in a series follow the order of the data, and series follow the order they were added to the chart. The order can be changed with the Root’s tabindex and each element’s tabindexOrder setting. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | amCharts 5 shows no links by default, therefore this criterion is classified as “Supports” as per VPAT recommendations. If implementers add links, they can give them screen reader text with ariaLabel where the visible text is not enough. |
| 3.1.1 Language of Page (Level A) | Supports | The page language is set by the host page. amCharts 5 comes with translations to many languages, which implementers enable in code. |
| 3.2.1 On Focus (Level A) | Supports | Focusing an element only highlights it and, optionally, shows its tooltip. It does not change the context. |
| 3.2.2 On Input (Level A) | Supports | No input in amCharts 5 changes the context of the page it is on. |
| 3.3.1 Error Identification (Level A) | Supports | Charts have no input fields that could cause an error, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Charts have no text inputs. Controls such as scrollbar grips and legend items give instructions or their current state through ARIA attributes. |
| 4.1.1 Parsing (Level A) | Supports | Since the 2023 errata to WCAG 2.0, this criterion is always satisfied for content that uses HTML or XML. amCharts 5 also builds its elements directly in the DOM with JavaScript, not from text markup that could fail to parse. |
| 4.1.2 Name, Role, Value (Level A) | Supports | Interactive elements have proper names, roles and states. For example, a legend item has the role “checkbox” with aria-checked; a scrollbar grip has the role “slider” with aria-valuemin, aria-valuemax, aria-valuenow and aria-valuetext; a toggle button is exposed as pressed or not pressed.Implementers can change any role with the role setting. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Supports | amCharts 5 displays no audio or video that would need captions, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Supports | amCharts 5 displays no pre-recorded video, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | By default, text is colored to contrast with its background. For example, a tooltip that takes the color of its element gets black or white text, depending on how light the background is. In Windows High Contrast and other forced colors modes, labels, grid, axes and buttons take the system colors. Implementers can set the color of every element, including text, in code. |
| 1.4.4 Resize text (Level AA) | Supports | Charts scale with browser zoom without losing content, layout or meaning. Text size can also be set in code. |
| 1.4.5 Images of Text (Level AA) | Supports | amCharts 5 uses no images of text, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 2.4.5 Multiple Ways (Level AA) | Supports | amCharts 5 renders elements of a page, not whole pages or sets of pages, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 2.4.6 Headings and Labels (Level AA) | Supports | amCharts 5 renders elements of a page, not whole pages, so page headings are set by the host page. Charts and their common elements get default labels. Implementers can change these labels in code, and add their own HTML headings or labels around a chart. |
| 2.4.7 Focus Visible (Level AA) | Supports | A focused element gets a high-contrast outline. The outline’s color, thickness, opacity and distance from the element ( focusPadding) can be changed in code.Implementers can add more cues to focused elements, such as a change of color, opacity or size. |
| 3.1.2 Language of Parts (Level AA) | Supports | amCharts 5 comes with translations to many languages, which implementers enable in code. Every piece of text, visible or read out by screen readers, can be changed, added or removed in code. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | Charts of the same kind keep the same order and layout of their elements. Implementers can change this order in code. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Elements with the same function are named the same way in every chart. Implementers can change these names in code. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Charts have no input fields that could cause an error, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | amCharts 5 has no controls that make legal commitments, change stored data or submit user data, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Supports | Built-in controls come with text labels for screen readers. Data elements, such as columns, slices, bullets and map polygons, get text labels through their ariaLabel setting, which can include the element’s own data. |
| 302.2 With Limited Vision | Supports | Besides screen reader support, charts follow Windows High Contrast and other forced colors modes, scale with browser zoom, can use pattern fills, and outline focused elements in high contrast. |
| 302.3 Without Perception of Color | Supports | Color is not needed to tell data apart: pattern fills, and the built-in Patterns and Colorblind themes, can be used instead of or along with color. They are not enabled by default. |
| 302.4 Without Hearing | Supports | amCharts 5 produces no audio, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 302.5 With Limited Hearing | Supports | amCharts 5 produces no audio, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 302.6 Without Speech | Supports | Nothing in amCharts 5 requires speech, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 302.7 With Limited Manipulation | Supports | Everything that can be done with a mouse or touch can also be done with a keyboard. TAB moves between focusable elements. Arrow keys move draggable elements (such as scrollbar grips) and move between the members of a focusable group. ENTER or SPACE activates buttons and toggles (such as legend items). The hoverOnFocus setting makes focus act as hover, so the element’s tooltip is shown without a pointer. |
| 302.8 With Limited Reach and Strength | Supports | amCharts 5 needs no particular reach, strength or speed. It can be operated with a mouse, touch, a keyboard, or any technology that simulates keyboard input, such as voice control. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | The information shown in a chart is chosen by the implementer, who can tailor it and its presentation to the audience. |
Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope – Incorporation of WCAG 2.0 AA | See WCAG 2.0 section | See information in WCAG 2.0 section |
| 502 Interoperability with Assistive Technology | Heading cell – no response required | Heading cell – no response required |
| 502.2 Documented Accessibility Features | Heading cell – no response required | Heading cell – no response required |
| 502.2.1 User Control of Accessibility Features | Supports | amCharts 5 is designed to work with built-in platform accessibility features and assistive technologies. |
| 502.2.2 No Disruption of Accessibility Features | Supports | amCharts 5 does not disable or override platform accessibility features. Charts follow the system’s forced colors (high contrast) setting. |
| 502.3 Accessibility Services | Heading cell – no response required | Heading cell – no response required |
| 502.3.1 Object Information | Supports | Focusable elements and controls expose their role, state, name and value through ARIA attributes where applicable. |
| 502.3.2 Modification of Object Information | Supports | All settings, including accessibility ones, can be changed in code, also on a live chart. |
| 502.3.3 Row, Column, and Headers | Supports | amCharts 5 shows no information in tables, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 502.3.4 Values | Supports | Elements that hold a value also expose it as text through ARIA attributes. This text can be changed in code. |
| 502.3.5 Modification of Values | Supports | Every setting in amCharts 5 can be set in code, including those that users can set through input. |
| 502.3.6 Label Relationships | Supports | Relationships between elements are exposed as text and ARIA attributes. For example, a column’s label can name the series it belongs to, and a legend item exposes whether its series is shown with aria-checked. |
| 502.3.7 Hierarchical Relationships | Supports | Where applicable, hierarchy is exposed through roles and the DOM structure. For example, items with the role menuitem in the export menu sit inside an element with the role menu, and Gantt tasks and hierarchy nodes with children expose aria-expanded. |
| 502.3.8 Text | Supports | The font, size and color of all text can be set in code, and charts follow the system’s forced colors setting. |
| 502.3.9 Modification of Text | Supports | All text can be changed in code. |
| 502.3.10 List of Actions | Supports | Each control has an ARIA label that says what it does and how to use it, and its current value where it has one. |
| 502.3.11 Actions on Objects | Supports | amCharts 5 does not prevent changing values or performing actions on any of its elements, including actions invoked in code. |
| 502.3.12 Focus Cursor | Supports | A focused element gets a high-contrast outline. |
| 502.3.13 Modification of Focus Cursor | Supports | The outline’s color, thickness, opacity and distance from the element can be changed in code. Implementers can add more cues to focused elements, such as a change of color, opacity or size. |
| 502.3.14 Event Notification | Supports | amCharts 5 tells screen readers about relevant changes. For example, a map announces its new zoom level when zooming stops, toggles expose whether they are on or off, and tooltips with readerAnnounce are read out when shown or when their data changes. |
| 502.4 Platform Accessibility Features | Supports | Charts follow the platform’s forced colors (high contrast) setting and do not override other platform accessibility features. |
| 503 Applications | Heading cell – no response required | Heading cell – no response required |
| 503.2 User Preferences | Supports | Charts follow the system’s forced colors (high contrast) setting. Colors, sizes and contrast can be customized in code. As a client-side library, amCharts 5 does not store user preferences; implementers can. |
| 503.3 Alternative User Interfaces | Supports | amCharts 5 works with assistive technologies and provides no alternative user interface, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 503.4 User Controls for Captions and Audio Description | Heading cell – no response required | Heading cell – no response required |
| 503.4.1 Caption Controls | Supports | amCharts 5 displays no audio or video that would need captions, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 503.4.2 Audio Description Controls | Supports | amCharts 5 displays no video that would need audio description, therefore this criterion is classified as “Supports” as per VPAT recommendations. |
| 504 Authoring Tools | Heading cell – no response required | Heading cell – no response required |
| 504.2 Content Creation or Editing | Not Applicable | amCharts 5 is not an authoring tool. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not Applicable | amCharts 5 is not an authoring tool. |
| 504.2.2 PDF Export | Not Applicable | amCharts 5 is not an authoring tool. |
| 504.3 Prompts | Not Applicable | amCharts 5 is not an authoring tool. |
| 504.4 Templates | Not Applicable | amCharts 5 is not an authoring tool. |
Legal Disclaimer
This report was prepared by the amCharts team to be published on amCharts-controlled websites or distributed to amCharts clients.
Quoting or publishing this report, other than linking to its web version on amcharts.com, requires explicit permission from amCharts.
To ask for permission, contact amCharts at contact@amcharts.com.