Accessibility Support

Home

Products

RadControls for DNN

Accessibility Support

What is Section 508

The USA federal mandate requires that information technology be made accessible to people with disabilities. Much of Section 508 compliance concerns making Web sites, intranets, and web-enabled applications accessible. Section 508 compliance has since become a major prerequisite not only in government related software, but also in most enterprise and corporate software solutions.

W3C Web Content Accessibility Guidelines 1.0

The main goal of these guidelines is to encourage developers in creating applications providing accessible contents. However, adhering to these guidelines will also make Web content more accessible to all kind of users, using different devices and interfaces: desktop browser, voice browser, mobile phone, automobile-based personal computer, etc.

In accordance with these guidelines W3C defines three levels of conformance developers may implement in order to provide some level of content compliance to their products:

Compliance Level "A"
Compliance Level "AA"
Compliance Level "AAA"

For more details on W3C "Web Content Accessibility Guidelines 1.0" see
http://www.w3.org/TR/WAI-WEBCONTENT/

RadControls Accessibility compliance

In our attempt to make our products content compliant, each web-control we develop and its QSF strive to obtain at least one of conformance levels listed above. More information about RadControls' compliance can be found in the HELP documentation of the respective control.

Section 508
compliance

W3C compliance

* Level A *

Level A

Level AAA

Level A

Level A

* Level A *

Level A

Level AAA

Level AAA

Level AAA

Level AA

Level AA

Level AA

Level AAA

Level A

Level A

Level A

* Level A

Compliance Level

RadAjax does not satisfy the requirements for accessibility as most screen readers (similar to the browser) do not recognize that the page (or part of it) has been updated. Nevertheless, RadAjax's loading panel does offer visual indication that the page (or part of it) has been updated.
In order to provide better compliance, Telerik will need to wait for the readers and catch up with the ajax technology and offer better way of reading the screen content. As soon as this happens, we will be able to provide better compliance. More on the "ajax accessibility" topic can be located in Google.

Compliance Level

RadEditor satisfies the requirements for accessibility, which is a result of the following:

The interface of the RadEditor is "Level A" accessible (in compliance with the W3C Web Accessibility Guidelines 1.0). Listed below are the product's accessibility features:

RadEditor passes the check of the W3C accessibility validator (click the W3C logo on one of the on-line examples)
all tools and commands can be associated with shortcuts either in ToolsFile.xml or with a property of the object.
each toolbar button may contain text. The text is displayed when the ShowText property is set to "true". You can also control the position of the text (bottom/right) using the ToolsTextPosition property.
all toolbars can be arranged in accordance with your preferences. You can drag and dock the toolbars on the edges of the editable area, just like in Microsoft Office applications.
you can create custom skins with more accessible appearance (e.g. larger buttons, high-contrast colors, etc.)

The content generated by the RadEditor can become accessible if the author fills in all required fields (marked with a special accessibility icon ).

every content element, which is more complex than pure text, has additional accessibility fields for detailed description (e.g. tooltip, long description, etc.)
new or existing tables can be enriched with special accessibility fields from the Table Wizard or from the Table Properties dialog

Compliance Level

RadWindow does not render any tables (<table> HTML tags) thus there's no need for extra headings / caption / summary attributes that are typically needed to make HTML tables accessible.