This topic explains the accessibility features of the igLayoutManager™ control and provides information on how to achieve accessibility compliance for pages containing this control.
The following topics are prerequisites to understanding this topic:
igLayoutManager Overview: This topic explains the igLayoutManager control conceptually and provides information on the supported layouts and their uses.
Adding igLayoutManager: This topic demonstrates, with code examples, how to add the igLayoutManager control to an HTML page using either pure HTML, JavaScript, or ASP.MVC implementations.
All of the Ignite UI for jQuery® controls 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 igLayoutManager 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 igLayoutManager 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 igLayoutManager 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 igLayoutManager 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