This topic contains the following sections:
Section 508 of the Rehabilitation Act was amended in 1998 by Congress to require all Federal agencies to make their electronic and information technology accessible to people with disabilities. Since then, Section 508 compliance has not only been a requirement in government agencies, but it's also important when providing software solutions and designing Web pages.
Section 1194.22 of the Section 508 law specifically targets Web-based intranet and internet information and systems, and contains a set of 16 rules to follow. In order to enable you to keep your Web applications and Web sites compatible with these rules with minimal effort on your part, Infragistics has taken steps to ensure that the Ignite UI for jQuery™ controls and components are compliant with the relevant accessibility rules.
The matrix below provides a high-level outline of the accessibility support provided by our visual controls (and related components). To learn more about an individual control/component's accessibility compliance, click the name of the control/component.
| Legend | |
|---|---|
 |
The control/component is completely accessible in this particular area. |
| 'white space' | this particular rule does not apply to the control. |
 |
The control/component is not entirely accessible unless you perform some sort of action. |
a - A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
b - Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
c - Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
d - Documents shall be organized so they are readable without requiring an associated style sheet.
e - Redundant text links shall be provided for each active region of a server-side image map.
f - Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
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.
i - Frames shall be titled with text that facilitates frame identification and navigation.
j - Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
k - A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
l - When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
m - When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through l.
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.
o - A method shall be provided that permits users to skip repetitive navigation links.
p - When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
In 2014 the W3C finalized their WAI-ARIA specification which defined how to design Web content and Web applications to be more accessible to users with disabilities.
The list below provides links to more details on how WAI-ARIA support has been implemented in various controls.
View on GitHub