...
Consistent with our commitment to accessibility, the following accessibility improvements and functionalities have been released recently:
Kyvos 2023.5
The Kyvos Viewer module now adheres to WCAG 2.1 Level A and AA guidelines.
Non-text Content (1.1.1):
All non-text content that includes active images (image links), area maps, informative images, complex charts and graphs, CSS images, decorative images, input image controls, CAPTCHA, audio, and video content must have text alternatives. This Success Criterion helps people who have difficulty perceiving visual content. Assistive technology can read text aloud, present it visually, or convert it to braille.All the icon action buttons and legend icons have alternate text as a tooltip.
All the charts have textual information about the chart on the tooltip.
The quick start video has a text description of the video.
The Kyvos/Kyvos Lite logo has alternate text as a tooltip.
All image tags have alt attributes.
If an image or icon is used as a button or link, the image has a text alternative sufficient to describe the purpose of the button or link.
Labels or Instructions Level A (3.3.2):
Labels or instructions are provided when content requires user input.Descriptive labels for inputs. Visually position labels consistently, making associating labels with form controls easy.
Set fields that describe the necessary input.
Indicate required fields.
Name, Role, Value A 4.1.2:
For all user interface components (including but not limited to form elements, links, and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that the user can set can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.ARIA labels, descriptions, roles, states, and properties to expose information about the component.
ARIA enhances accessibility only when HTML is not sufficient.
Role attribute on HTML elements wherever needed.
All form controls and other interactive elements have an accessible name.
Identify Input Purpose Level AA (1.3.5):
All the input form controls are defined with the type attribute.Label in name Level A (2.5.3):
The accessible name for a User Interface element contains any visual label for the element.
Accessible names for UI elements match visual labels.
Info and Relationships Level A (1.3.1):
Semantic markup to designate headings, lists, figures, emphasized text, etc.
Page organization using nested HTML headings.
Indicate required fields.
The text indicates the required fields that have been left blank or missed.
Error Identification Level A (3.3.1):
All the input elements have an error style when an error comes.
Error information is shown in the form of text.
Programmatically indicate required fields using the required or aria-required attributes. Also, visually indicate required fields in the form's instructions or form labels.
Identify errors using aria-invalid.
Character key shortcuts Level A 2.1.4 :
No global shortcuts have only letters.
If a keyboard shortcut is implemented in content using only letters (including upper- and lower-case letters), punctuation, numbers, or symbol characters
Accessibility in Amcharts Kyvos Viz. charts
Supported Kyvos Viz. Chart types are Bar Chart, Column Chart, Dot Chart, Curve Chart, Area Chart, Pie Chart, Scatter Chart, Line Chart and Gantt Chart.
The following rules have been supported in
Kyvos Viz. charts:
Keyboard Navigation:
Users can navigate across chart elements using the tab key.
Users can use the context menu shortcut (ctrl + shift + M) on focused chart elements if the context menu is available.
Aria Label and Role (Name, Role, Value A 4.1.2) :
Chart elements have role and aria-label attributes. These are used by assistive technologies to enhance accessibility.
Tooltip:
All the charts have textual information about the chart on the tooltip.
Tooltips will be visible to users when the chart element is focused using the tab key.
...