Section 508/WCAG Compliance

Editors from the Data Editors suite are designed to comply with Section 508 Standards and W3C's latest accessibility recommendations such as WCAG (2.0) and WAI-ARIA (1.0). As most of DevExpress ASP.NET controls, data editors implement the AccessibilityCompliant property, which allows more accessible markup to be generated for a control.

This demo illustrates how to make data editors more accessible for end-users by enabling the AccessibilityCompliant property of each editor. Editors for required fields are marked with an asterisk character and are recognizable by screen readers. Each time an editor is focused, the screen reader pronounces both the editor label text and further actions with the focused editor (e.g., type in text in a text box or open a drop-down window for a calendar).

Here is a short summary on this accessible webpage implementation:

• Define the page areas with landmark roles such as navigation, search, main content, etc.
• Add the aria-labelledby attribute for the page area with the role="form" role to provide information about the “form” landmark area for Assistive Technologies.
• Place DevExpress ASP.NET Data Editors controls to the form and set their AccessibilityCompliant property to true.
• Specify ValidationSettings and SetFocusOnError properties for the data editors.

Check the accessibility level of editors in this demo by clicking the Validate with WAVE link and running WAVE (a web accessibility evaluation tool). Note that data editors can look and operate correctly when the High Contrast mode is enabled in Windows OS.

To learn more on accessibility support in DevExpress ASP.NET controls, please view the Section 508 and Accessibility and Accessibility Support topics.

• Accessibility Techniques Used in DevExpress Demos