This topic explains igScheduler™ accessibility features and provides advice how to achieve accessibility compliance for pages containing schedulers.
All of the Ignite UI for jQuery™ controls and components comply with Section 508, Subpart 1194.22 of the Rehabilitation Act of 1973.
To meet the requirements each accessibility rule, in some cases, you may need to interact with the control by to setting a specific property, but in other cases the control does the work for you.
Note: As jQuery controls are client-only, some of the rules are not supported and are marked as limitations.
The following table summarizes the accessibility compliance features of the igScheduler.
| 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. | You can control coloring and provide suitable colors for scheduler using the styling and theming capabilities of igScheduler. Using client-side events, the user can change attributes of any of the control's DOM elements reflecting the current state. |
| (d) | Documents shall be organized so they are readable without requiring an associated style sheet. | The control's markup is readable without the associated style sheet because it’s a client-side control and depends on the CSS rules.. |
| (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 igScheduler 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.) |
| (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. | When the control's scripts are changing the page markup, the new created content complies with the screen reader due to the attributes described in rule (c). |
| (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. | Keyboard navigation for selecting different date is provided and the same applies for the date picker editor when it is on focus (edit mode). |
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 igScheduler is not yet completely designed to follow these guidelines.
The list below provides links to more details on how WAI-ARIA support has been implemented in Widgets that are part of the scheduler and follows WAI-ARIA guidelines.
Following are some other topics you may find useful.
View on GitHub