This topic explains the accessibility features of the igTileManager™ control and provides information on how to achieve accessibility compliance for pages containing this control.
The following topics are prerequisites to understanding this topic:
igTileManager Overview: This topic provides conceptual information about the igTileManager control including its main features, minimum requirements, and user functionality.
Adding igTileManager: This topic demonstrates, with code examples, how to add the igTileManager control to an HTML page in either JavaScript or ASP.NET MVC. The topic covers initializing igTileManager on the HTML markup. For instantiating the control from the data source, refer to the Binding igTileManager to Data topic.
All of the Ignite UI for jQuery® and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973. The table below contains the specific rules of Subpart 1194.22 that pertain to the control. Also detailed is how the igTileManager control complies with each rule.
To meet the requirements for each accessibility rule, in some cases, you may need to interact with the control by setting a specific option, but, in other cases, the control does the work for you.
The following table summarizes the accessibility compliance rules for the igTileManager control.
| Rules | Rule Text | How We Comply |
|---|---|---|
| (c)* | Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | The igTileManager control does not depend on color. |
| (j) | Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | The igTileManager control does not itself contribute to causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. (There are no BLINK or MARQUEE elements as part of the control.) |
*- control limitation
The following topics provide additional information related to this topic.
View on GitHub