|
| 1 | +--- |
| 2 | +title: Section 508 |
| 3 | +page_title: Kendo UI Section 508 Support |
| 4 | +description: Kendo UI Section 508 checklist |
| 5 | +--- |
| 6 | + |
| 7 | +# Kendo UI Section 508 Support |
| 8 | + |
| 9 | +The following table shows the level of support that Kendo UI provides for the [Section 508 Web standard](http://www.section508.gov/section-508-standards-guide#Web). |
| 10 | + |
| 11 | +|508 Standard|Yes (Pass)|No (Fail)|N/A (Pass)| |
| 12 | +|------------|----|----|---| |
| 13 | +|[(a)](https://www.webaccessibility.com/best_practices.php?standard_id=1000704) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).|All images (`img` HTML elements) that Kendo UI renders have `alt` attribute set. If the developer uses the `img` element via Kendo UI templates he or she must set the "alt" or "longdesc".)||| |
| 14 | +|[(b)](https://www.webaccessibility.com/best_practices.php?standard_id=1000727) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.|||Kendo UI doesn't use multimedia (sound or video) presentation.| |
| 15 | +|[(c)](https://www.webaccessibility.com/best_practices.php?standard_id=1000730) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.|Kendo UI widgets make sure that information is conveyed by other means besides color. For example the visual selected state also uses ARIA attributes.||| |
| 16 | +|[(d)](https://www.webaccessibility.com/best_practices.php?standard_id=1000736) Documents shall be organized so they are readable without requiring an associated style sheet.||Kendo UI widgets will work without an applied stylesheet but will not look nearly as good.|| |
| 17 | +|[(e)](https://www.webaccessibility.com/best_practices.php?standard_id=1000739) Redundant text links shall be provided for each active region of a server-side image map.|||Kendo UI does not use image maps.| |
| 18 | +|[(f)](https://www.webaccessibility.com/best_practices.php?standard_id=1000741) 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.|||Kendo UI does not use image maps.| |
| 19 | +|[(g)](https://www.webaccessibility.com/best_practices.php?standard_id=1000743) Row and column headers shall be identified for data tables.|The Kendo UI grid, gantt and treelist widgets use attributes to identify the column headers.||| |
| 20 | +|[(h)](https://www.webaccessibility.com/best_practices.php?standard_id=1000750) 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.||Kendo UI doesn't provide such markup in cases where cells have more than one logical level of headers (scheduler, gantt, pivot, multi-header grid).|| |
| 21 | +|[(i)](https://www.webaccessibility.com/best_practices.php?standard_id=1000753) Frames shall be titled with text that facilitates frame identification and navigation.||The Kendo UI Editor doesn't set the title of the content editable iframe.|| |
| 22 | +|[(j)](https://www.webaccessibility.com/best_practices.php?standard_id=1000756) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.|Kendo UI does not cause screen flicker with a frequency greater than 2 Hz and lower than 55 Hz.||| |
| 23 | +|[(k)](https://www.webaccessibility.com/best_practices.php?standard_id=1000759) 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.|||N/A to Kendo UI. The developer is responsible for providing text-only content for pages that uses Kendo UI widgets.| |
| 24 | +|[(l)](https://www.webaccessibility.com/best_practices.php?standard_id=1000763) 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.|Kendo UI is a JavaScript framework and can't operate when JavaScript is disabled. Kendo UI provides keyboard navigation support and screen reader support (via ARIA attributes).||| |
| 25 | +|[(m)](https://www.webaccessibility.com/best_practices.php?standard_id=1000782) 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).|||Kendo UI doesn't use any external plug-ins or applets.| |
| 26 | +|[(n)](https://www.webaccessibility.com/best_practices.php?standard_id=1000785) 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 built-in edit forms in the Kendo UI widgets conform to this requirement.||| |
| 27 | +|[(o)](https://www.webaccessibility.com/best_practices.php?standard_id=1000794) A method shall be provided that permits users to skip repetitive navigation links.|Kendo UI does not provide a 'skip navigation link', but instead offers keyboard shortcuts to most of the features in the user interface.||| |
| 28 | +|[(p)](https://www.webaccessibility.com/best_practices.php?standard_id=1000797) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.|Kendo UI does not require a timed response as part of its core functionality.||| |
0 commit comments