This topic explains the accessibility features of the igPivotView™ control and provides advice on how to achieve accessibility compliance for pages containing this control.
The following topics are prerequisites to understanding this topic:
igPivotView Overview: This topic provides conceptual information about the igPivotView control including its main features, minimum requirements, and user functionality.
Adding igPivotView: This is a group of topics demonstrating how to add the igPivotView control to an HTML page and to an ASP.NET MVC application.
All Infragistics® Ignite UI for jQuery™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. The igPivotView accessibility compliance summary chart contains the specific rules of Subpart 1194.22 that pertain to the control.
In some cases, to meet the requirements of each accessibility rule, you may need to interact with the control by setting a specific property, but in other cases, the control performs these tasks for you.
Note: As jQuery controls are client-only, consequently some of the rules are unsupported and are marked as limitations.
The following table summarizes the accessibility compliance features of the igPivotView control.
| Rules | Rule text | How we comply |
|---|---|---|
| (a) | A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | The control provides the required attributes. |
| (c) | Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | You can control the coloring and provide suitable colors using the styling and theming capabilities of igPivotView. |
| (d)* | Documents shall be organized so they are readable without requiring an associated style sheet. | The control's markup is not readable without the associated style sheet because it is a client-side control and depends on the CSS’s rules. |
| (g) | Row and column headers shall be identified for data tables. | - |
| (h) | Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. | - |
| (n) | When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | The metadata tree part of the igPivotDataSelector™ in the igPivotView control participates in the tab sequence of the page and receives focus including via a mouse click. The Defer Update check-box and the Force Update button participate in the tab sequence as well. The Selection feature must be enabled for the igPivotGrid in order keyboard navigation for data cells to work. To use the keyboard for navigation between cells, a cell must be first selected with the mouse.
When splitter bar of the igSplitter™ control is on focus, users can perform the following actions using the keyboard:
|
* – control limitations
The following topics provide additional information related to this topic.
View on GitHub