The following blog post was written together with Rumen Jekov, who is the most experienced support officer at Telerik and has been supporting RadEditor for a number of years now. If you are a RadEditor user, and you contact us, chances are you will be receiving an answer from him.
The blog post discusses the accessibility features of RadEditor. While accessibility options were not considered important couple of years ago, things have changed - and will be changing even more in the future. For enterprize customers and governmental institutions accessibility is becoming a top priority, and we have gone at great lengths to add accessibility features to our products. Of course, this is an ongoing effort, rather than a one-time go. We keep adding accessibility features to the RadEditor, such as the ability to navigate tools with the keyboard, or switch focus from the content area to the toolbars and back using a keyboard shortcut. One accessibility feature that was added recently to RadEditor is (cross-browser) support for AccessKey.
We hope the following information will be helpful to all who want to learn more about the editor's accessibility features.
Telerik RadEditor satisfies the requirements for accessibility, which is a result of the following:
|<telerik:radeditor runat="server" ID="RadEditor1"></telerik:radeditor>|
|<telerik:radeditor runat="server" ID="RadEditor2" ToolProviderID="RadEditor1"></telerik:radeditor>|
|<telerik:radeditor runat="server" ID="RadEditor3" ToolProviderID="RadEditor1"></telerik:radeditor>|
|<telerik:radeditor runat="server" ID="RadEditor1" AccessKey="1"></telerik:radeditor>|
|<telerik:radeditor runat="server" ID="RadEditor2" AccessKey="2"></telerik:radeditor>|
|<telerik:radeditor runat="server" ID="RadEditor3" AccessKey="3"></telerik:radeditor>|
Note: In Internet Explorer use Alt + AccessKey to give focus to the element with a specified access key.
To activate an access key in Firefox 2.0 use Shift + Alt + AccessKey.
Full keyboard accessibility - RadEditor is a fully keyboard navigable component, including shortcuts to open and operate with drop-downs, tools and dialogs, achieving true accessibility.
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 enterprize 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:
For more details on W3C "Web Content Accessibility Guidelines 1.0" see http://www.w3.org/TR/WAI-WEBCONTENT/
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.
Iana Tsolova is Product Manager at Telerik’s DevTools division. She joined the company back in the beginning of 2008 as a Support Officer and has since occupied various positions at Telerik, including Senior Support Officer, Team Lead at one of the ASP.NET AJAX teams and Technical Support Director. Iana’s main interests are web development, reading articles related to geography, wild nature and latest renewable energy technologies.
Subscribe to be the first to get our expert-written articles and tutorials for developers!
All fields are required
We see that you have already chosen to receive marketing materials from us. If you wish to change this at any time you may do so by clicking here.