ebf9ffc2ca0d36db7a529a55a42c4f0b77ecad3f
FAQ/Questions/Section508-compliance.md
| ... | ... | @@ -0,0 +1,13 @@ |
| 1 | +#Section 508 Compliance |
|
| 2 | + |
|
| 3 | +[[_TOC_]] |
|
| 4 | + |
|
| 5 | +##Question |
|
| 6 | + |
|
| 7 | +Is Izenda Section 508 Compliant? Does Izenda have a VPAT or any intention of obtaining one if not? |
|
| 8 | + |
|
| 9 | +##Answer |
|
| 10 | + |
|
| 11 | +No, Izenda is not completely 508 compliant. By default, any images such as logo images and toolbar buttons have alt text to enable screen-readers to identify them. Additionally, charts and gauges have alt text when the [[/API/CodeSamples/UseImageDescriptions]] setting is enabled. However, this only applies to charts that render their content as an image. Other charts are made up of SVG 1.1 elements that some Assistive Technologies can read fairly well via the Accessibility API available in modern browsers. However, the SVG elements themselves do not generally use <title> elements. These <title> elements are only read by certain browsers currently, and only IE can make very good use of them. Izenda also does not use <desc> tags on SVG elements currently, but again browser support for <desc> tags is about as limited as support for <title> tags. Izenda does, however, use <text> tags to expose the rendered textual elements. Therefore, the text on the SVG charts is highly accessible to screen readers. |
|
| 12 | + |
|
| 13 | +Izenda has not received a VPAT and does not at this time have any plans of obtaining one. Since we integrate into customer websites, and since we aim to be highly customizable for each client's needs, the information above should be considered when applying for or renewing a VPAT. |
|
| ... | ... | \ No newline at end of file |