Accessibility for Section 508 Compliance
Authentications do not have page titles - When a Datapage uses an authentication, I noticed that the <title> element within the <head> code for that page is empty. But once a DataPage is launched, the <title> element is the same as the DataPage name (which is good). WCAG 2.0 SC 2.4.2https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html states that all Web pages must have a <title> that describes the topic or purpose of the page. Currently, we are out of compliance with this success criterion since our authentication pages do not have titles. This is something we would like to work with Caspio developers to remediate.
Color Alone for Chart DataPages - WCAG 2.0 SC 1.4.1https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-without-color.html states that color alone cannot convey meaning. This is because users who are color blind, or who have difficulty distinguishing colors from one another would not be able to interpret a bar graph or pie chart with a legend based solely on color. The remediation for this is to make available a secondary visual characteristic, such as a pattern fill, a shape, or outline. It seems like adding additional styling options for charts would be an easy fix for Caspio developers.
Sort by form element is not labeled correctly - After generating a tabular report, the “sort by” form element is not associated with the <label> element. WCAG 2.0 SC 3.3.2https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html requires that labels or instructions are present for all form elements. All you need hear is to add for = “asort” into the <label> tag and then this element will be labeled properly.
DataPage charts are really image maps, but we do not have any control over the tab order of the elements in the charts. For example, I made a basic bar graph, and both the label and the data value receive focus by a screen reader, but that focus is out of order so it does not make sense. This is yet another accessibility issue since screen reader users land on the elements in the charts and cannot make sense of what data goes with what label. It would be great if we could have the option to set the tabindex for the elements in the charts, or at least have access to the chart source code so we could do this manually. The only workaround I can come up with at this point is to use aria-hidden in the iframe tag so that the chart is ignored by screen readers and then provide a text alternative for AT users.
Marla
shared this idea