Page Comparison

...

Recent Accessibility Improvements

...

• 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 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 implemented for the supported in Kyvos Viz. charts, as mentioned above:  

    • 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. 

...

• Sections in the worksheet: Change cube semantic model panel, shelves, visualization rendering area, filter panel, and properties panel. 

...

• Register Data: Users can perform all operations while registering data through quick data modeler.

• Define Relationships: Users can perform all operations while defining relationship through quick data modeler. Keyboard behavior would be same as Relationship use case.

• Design CubeSemantic Model: Users can perform all operations while designing cube semantic model through quick data modeler. Keyboard behavior would be same as Cube semantic model Designer use case.

• BuildProcess: Users can perform all operations while building cube processing semantic model through quick data modeler.

...

• Section Navigation: The relationships designer screen supports section navigation to jump quickly from one area to another by keyboard.

• Components

  • Field List: Field list for files and datasets is accessible by keyboard and user can perform operations on them. Drag drop functionality is also accessible by keyboard through context menu options.

  • DRD Designer: All the elements of designer area are accessible through keyboard and uses can perform actions on them using key combinations such as tab, shift tab, and enter.

  • DRD Nodes: DRD Nodes are accessible by keyboard. Context menu operations and node/edge properties selections also support navigation using a keyboard.

  • Properties Panel: All the operations are accessible and can be performed using keyboard such as switching between nodes, opening the source entity for node, and so on.

...

Semantic Model Designer

• Section Navigation: The cube semantic model designer screen allows section navigation to jump quickly from one area to another using a keyboard.
  Sections in cubesemantic model:

  • Design tab: Candidate panel, main design tab content, property panel, filter panel.

  • Refine tab: Physical view, property panel, filter panel.

  • Build Process tab: Build Process history Grid area and filter area.

• Components

  • Drag-Drop: Users can use keyboard navigation to drag-drop field to dimension or measure panel which automatically creates measure/attribute/level.

  • Sorting: Cube Semantic model elements in designer screen can be rearranged to alter design anytime, which is possible by sorting feature. As part of keyboard accessibility, users can sort cube semantic model elements using the keyboard.

    • Sorting is supported for single and multiple elements.

    • All current restrictions of sorting remain same while sorting by keyboard.

    • If active element is in focus then it should consider all other active elements for multiple elements sorting otherwise it should be single element sorting.

    • Users can remove sorting at any point using the Esc key.

    • After placing element to its desired place user can press enter to apply sorting.

• Cube Build

  Build

  Semantic Model Process

  • Process history grid should be keyboard accessible. Context menu operations and summary/edit operation should be operable by keyboard.

• Build Process tab: All the functionality is accessible via keyboard, including the following dialogs:

  • Full, incremental, Test, Update aggregates, Cache buildprocess, Drop partition, Data profile.

  • Job summary/data profile result

  • Manage build process instances

  • Clear Test build process data

• Refine tab: All the functionality is accessible via keyboard

  • Physical view: Sorting and property panel operations are keyboard accessible.

  • Partition Strategy options are keyboard accessible.

  • Aggregation Strategy options are keyboard accessible.

  • Cache Strategy options are keyboard accessible.

  • Advanced Properties are keyboard accessible including child dialogs and other UI functionalities.

• All other context menu dialogs are also be accessible by keyboard.

  • SQL Metadata

  • Data Security

  • Cube Semantic model Metadata Export (TDS)

  • Data Field Lineage

  • Workspace settings

  • Expand collapse

  • Refresh

  • Validate

  • Share Menu

  • Add Note

  • Set Query patterns

  • Get Recommendations

...